A customer down payment is money received before the related goods or services are fully invoiced. In SAP FI Accounts Receivable, configured special G/L indicators can direct advances to an alternative reconciliation account while preserving the link to the customer. A request for advance, cash receipt, final invoice and clearing are distinct events. Advance cash alone does not establish earned revenue.
Why advances are different from ordinary invoices
A manufacturer may ask for an advance before producing expensive equipment. The bank receipt is real, but it may represent an outstanding obligation to deliver or refund rather than an ordinary trade receivable. Finance must identify the customer and agreement, assess tax and accounting policy, and track the amount awaiting application. SAP special G/L provides a way to separate these postings while maintaining customer-level accountability.
Follow the lifecycle: request, receipt, invoice, clearing
The commercial owner approves an advance request. Depending on the configured process, the request can be represented as a noted item rather than a normal customer invoice. When the bank confirms receipt, Accounts Receivable records the payment with the appropriate special G/L indicator. Billing later creates the invoice when a contract condition is met. Finally, Finance applies the advance to the correct invoice and investigates any difference. An approved request is not evidence that cash has arrived.
Example: a ₹5 lakh equipment order
A customer pays ₹1,50,000 upfront on a ₹5,00,000 order. The bank receipt is recognized, and the customer advance is posted according to the configured special G/L treatment. When the invoice for the delivered equipment is posted, Finance may apply ₹1,50,000 of the advance, leaving ₹3,50,000 to collect, excluding tax or other adjustments for clarity. If delivery is partial, the customer cancels or the payment is refundable, the handling changes. Correct arithmetic cannot replace contractual evidence.
What the special G/L indicator actually controls
Under SAP FI posting rules, normal customer receivables typically use the customer reconciliation account. A special G/L indicator can determine a distinct account for transactions such as down payments, with the posting key and account configuration controlling the entry. SAP Help notes that the relevant account determination depends on account type, reconciliation account and indicator. Codes and tax treatment must be checked in the live system and local accounting design.
Controls and exceptions to test
Treasury verifies the receipt; Accounts Receivable owns allocation and clearing; the commercial owner confirms customer and contract conditions. Check approval limits, customer account, currency, duplicate bank-file imports, refund authority, tax impact and reporting classification. Investigate uncleared advances at month-end. A cancelled order, incorrect customer assignment or missing invoice should be resolved explicitly rather than hidden by manual clearing.
Questions consultants should ask
Which sales order or project is linked? Is the request statistical or posted? What event allows clearing? Who handles partial applications, cancellations and refunds? Which ledger reports separate advances from normal receivables? What evidence will auditors need? Answering these questions clarifies the necessary data and process controls.
Related Knowledge topics
Compare customer invoice accounting, incoming payment processing, automatic and manual clearing and customer reconciliation accounts. Return to SAP FI / FICO.