Receivables accounts customer static details
Each customer is identified by a unique customer code and the customer details are defined and maintained using Customers (CUS).
Many of the customer's details are held as separate static data records and linked to the customer using Customers. In general, this static data should be defined for a new customer, before you create the new customer using Customers.
Some of the more important customer details are:
- Payment Method
- Bank Details
- One-off Customer Accounts
- Settlement Terms
Payment Method
Customer payments can be collected using an automatic bank transfer facility by setting the payment method to Bank. The payment collection records are generated by Payment Collection Run (PYC).
Bank Details
If required, you can record a customer's bank account details using Bank Details Setup (BNK). This includes the name of the account, sort codes, account number, and so on. If you intend to use Payment Collection Run to create a bank transfer file to collect payments electronically from your customers, you must have completed the appropriate bank details record.
You can create any number of bank detail records for each customer. If you have more than one bank details record, you must specify a bank subcode in Payment Run Rules otherwise the customer's default code is used.
One-Off Customer Accounts
A requirement may exist to record sales, which have been made on a 'one-off' basis. Rather than create an individual account for a customer, whom you will not deal with again, you can record such entries in a general account. If you do so, you must ensure that transaction descriptions adequately identify the customer associated with each transaction.
Settlement Terms
Payment terms enable you to define the relevant dates for settlement, for the calculation of discounts and/or interest, and the dates of which relevant documents are issued. The payment terms are assigned to a customer using Customers, or can be referenced on a particular transaction.