Accounts Receivable
Accounts Receivable mirrors Accounts Payable on the customer subledger: customer master with general data (address, bank details for refunds, dunning data), company code data (reconciliation account, payment terms, payment methods, dunning procedure, credit limit) and sales area data. The customer account group determines the number range and field status, and the reconciliation account receives postings only from the subledger.
Typical transactions: FB70 customer invoice, FB75 customer credit memo, F-28 incoming payment, F-32 clear, F110 automatic collection run, F150 dunning, FBL5N line items, FAGLL03 G/L line items. Down payments use special G/L indicators with alternative reconciliation accounts, so they do not change the standard receivable balance.
Clearing logic is the classic trap
- Partial payment: the invoice stays open with its original amount; a residual balance remains.
- Residual payment: the original item is cleared and a new residual item is created with the unpaid amount and new terms.
- Payment differences inside the customer tolerance group can be written off to a difference account instead of leaving items open.
Further traps: a dunning procedure must be assigned in the master and have dunning levels/forms configured; the credit limit check depends on credit management settings, not only the master field; a customer item blocked for payment is skipped by F110 even if the master allows the payment method.
Rule of thumb: before blaming the payment run, check three things on the customer – payment method in the master, payment block, and whether the item is actually due (baseline date plus payment terms).