Customer correspondence is the controlled communication of information about a customer's financial account. An account statement commonly summarizes activity over a period, including balances carried forward and at the close. An open-item list instead shows items remaining open at a specified key date. A reminder or dunning notice has a collections purpose and should not be confused with a neutral request to reconcile balances. Available correspondence variants, forms and delivery options depend on the SAP release and configuration.
A statement is not just a list of overdue invoices
Imagine a customer asking why its balance differs from the supplier's ledger. An account statement can show opening balance, invoices, credit memos, receipts or other relevant postings within a selected period, and closing balance. That timeline gives both sides an audit trail for investigation. By contrast, an open-item list takes a point-in-time view of uncleared transactions. Neither should be described as a payment demand unless the business has explicitly combined it with a collections communication.
Choose the document by the business question
If a customer asks which transactions made up the month's balance, use period activity and a carried-forward balance. If the issue is which invoices remained unpaid on a particular date, use an open-item view. If the issue is how one remittance should be allocated, a payment advice is the more specific communication. If a genuinely overdue amount needs escalation, follow an approved reminder process with correct due dates and dispute flags. The recipient, purpose and data content must align.
Example: a disputed closing balance
A distributor sends a statement showing an opening amount of ₹90,000, a new invoice of ₹30,000 and an applied receipt of ₹40,000, leading to ₹80,000 before any other postings. The customer reports a further ₹10,000 transfer. Before reissuing the statement, the AR analyst checks the bank receipt, company code, customer account and clearing reference. An unapplied receipt can make two accurate source documents appear inconsistent; escalation before reconciliation would be premature.
Correspondence parameters and delivery
SAP documents customer statement correspondence as a configurable job with company-code and customer selections, period choices, output channels and formatting options. Teams may schedule controlled delivery, but should test the exact variant and scope before automation. Settings that include or exclude cleared items, select specific document types or skip zero-balance customers can materially change what recipients see. A consultant should verify the behavior in the actual deployed edition rather than assume all systems have identical screens.
Controls before the message leaves Finance
Confirm the legal company and recipient, cutoff date, currency, open-item reconciliation, customer master contact data and agreed dispute handling. Restrict sensitive account information to the authorized audience. Keep evidence of the template version, generation timestamp, selected parameters and dispatch result where policy requires it. Statement generation is not a substitute for posting quality: missing credit memos or cash-application errors must be corrected in the underlying accounts.
When the customer challenges the document
Record the disputed item and the customer's evidence, rather than changing a statement to make it appear agreeable. Separate an agreed commercial adjustment from a bank receipt that has not yet been allocated. A reconciled statement can be resent with a clear explanation; unresolved differences should have an owner and follow-up date. This protects both customer relationships and the month-end close.
Questions for an SAP FI consultant
Who approves the correspondence template and its wording? Which company code and customer group is in scope? Are statements produced for a period or open items at key date? What happens with zero balances, credit balances, cleared items or correspondence failures? Can the AR team reproduce a sent statement for audit? Test these examples with accounting, collections and data-privacy stakeholders before rolling out automated delivery.
Related Knowledge
Customer Account Clearing · Accounts Receivable Ageing · Dispute and Deduction Handling · Bad Debt and Customer Write-Off Concepts. Explore SAP FI / FICO.