Customer and Supplier Payment Bank Details

If settlement is required by bank transfer, then the details of your customer or supplier bank accounts are required. You define the bank accounts for each organization using Bank Details Setup (BNK). A customer or supplier can have more than one bank account and each account is identified by a bank subcode. The default bank for each customer or supplier is identified in Customers (CUS) or Supplier (SUS).

This default bank for the customer or supplier is used in by the Payment Run (PYR) or Payment Collection Run (PYC) to determine the bank details for the bank transfer file.

Note: The Bank Subcode can be defined as a selection criterion in Payment Profiles (PYP). If you want to use this facility you must ensure that you use consistent subcodes numbering for all of the customer or supplier bank details. For example, you might use it to identify those who use the same bank as your organization does, in order to create a separate transfer file for these.

The bank account details can also be included on the remittance advices or other documents produced for the payments.

If the bank details have not been defined for a customer or supplier, Payment Run (PYR) uses the Automated Bank Payments field setting in Ledger Setup (LES) to determine how to proceed. Three options are available:

Post All - this option includes the payment transactions on the bank transfer file regardless of whether or not the bank details have been defined.
Post All and Report if Bank Record Not Present - this option includes the payment transactions on the bank transfer file and produces a warning message identifying the suppliers/customers for whom bank details have not been defined.
Post Only if Bank Record Present - this option excludes the payment transactions on the bank transfer file if the bank details have not been defined for the supplier or customer.