Processing Customer Payments

Outcome

Customer payments are recorded, allocated, and, if necessary, adjusted. Checks and drafts are cashed. Rejected payment documents are managed. For information on lists printed, see the respective process/instruction.

The payments processed affect your customer credit and risk management as well as your cash flow management.

The general ledger, accounts receivable, and accounts payable are updated after using this process – see the respective process/instruction for details.

Payment receipts are created, if requested, and displayed in 'Payment Receipts. Display' (ARS400). See Manage customer payment receipts for a detailed description.

Before you start

• The company must have well-defined routines and policies for its customer payment processing.
• The financial system must be configured as described in Enabling Financial Management. This includes defining the following components:
  • FAM functions to serve as entry templates must be defined in 'FAM Function. Open' (CRS405). For further information, see the respective process.
  • Accounting rules which are combinations of accounting events and accounting types controlling the automatic generation of transactions, must be defined for recording, allocating, adjusting, remitting, and reporting rejected customer payments. You do this in 'Accounting Rules. Set' (CRS395). For further information, see the respective process.
  • Payment methods must be created for the respective payment class in 'AR Payment Method. Open' (CRS076). For further information, see the respective process.
  • Settings for payment receipts, if requested, must be configured as described in Manage customer payment receipts with the optional configuration of cash register as described in Cash register for customer payment receipts.
• Starting conditions specific for certain processes are listed in the respective process document or instruction.

Follow these steps

Comment

In several cases, steps 1 and 2 – recording and allocating payments – are combined into one step. Due to the flexibility of the financial system, they are explained separately in this principal process for the sake of clarity.

Note that direct debiting management is described separately in Managing Direct Debiting in Accounts Receivable.

1. Recording Customer Payments

   Record customer payments in these programs:

   PmtClass	Customer payment	Record in ...
   0	Cash	'Payment Received. Record' (ARS110)
   1	Check with later allocation to customer invoice	'Payment Document. Enter' (ARS105)
   2	Check with direct allocation to customer invoice	'Payment Document. Enter' (ARS105), 'Payment Received. Record' (ARS110)
   3	Bank transfer, manual entry	'Payment Received. Record' (ARS110)
   3	Bank transfer, entry of electronically transferred receipt orders	'Batch Payment. Update' (ARS040)
   4	Draft/Bill of exchange	'Payment Document. Enter' (ARS105), 'Payment Received. Record' (ARS110)
   5	Direct debiting payment, entry based on printed bank statement	'Bank Remittance. Reconcile Payment' (ARS350)
   5	Direct debiting payment, entry based on electronically transferred bank statement	'Bank Statement. Open' (ABS100)

2. Allocating Customer Payments to Invoice

   Allocate recorded payments to one or several customer invoices or credit invoice records, manually or automatically, in (ARS110).

   When allocating, you can also make any adjustments of payments like write-offs, managing payment differences, and netting against supplier invoices.

3. Remitting Customer Checks/Drafts to Bank for Collection

   Select the checks or drafts you wish to send to your bank for collection and create a bank remittance statement in 'Bank Remittance. Open' (ARS300). Send the statements to the respective banks together with the payment documents.

   This process also includes reconciling collected drafts and definite postdated checks (type 1) in 'Bank Remittance. Reconcile Payment' (ARS350).

4. Managing Customer Checks/Drafts Rejected by Bank

   Report any checks or drafts that have been rejected by the bank and returned due to insufficient funds as unpaid:

   Payment document	Report in ...
   Check; preliminary postdated check.	'Draft/Check. Record Unpaid' (ARS340)
   Draft: Collected on the due date, alternatively discounted (before the due date), and reconciled but afterwards rejected.	'Draft/Check. Record Unpaid' (ARS340)
   Draft/Definite postdated check: Rejected by the bank before collection but before having been reconciled.	'Bank Remittance. Update Payment' (ARS351), called from (ARS350).