SAP functional issueObjectDown payment request not cleared against the invoiceModuleFI_FICO

Down Payment Not Offsetting Against the Final Invoice

The down payment sits open under a special G/L indicator (customer A or vendor A) while the final invoice posts as a separate open item, and nobody ran the down payment clearing transaction (F-39 for customer, F-54 for vendor) that transfers the special G/L amount against the invoice. Standard clearing transactions cannot touch special G/L items, so the two balances never net even though the customer or vendor sees them as one deal.

Covers why a posted down payment and the invoice it was meant to offset both remain open instead of netting to zero. Focuses on the difference between a noted-item down payment request and an actual down payment posting, the mandatory transfer clearing step, and the configuration and reference-field mismatches that block it.

Published 16 Sept 2026· 1,185 words

The business symptom

Accounts receivable or accounts payable reports that a customer or vendor account still shows the full invoice amount as due even though a deposit or advance was clearly paid weeks earlier. The customer statement or vendor line item report lists both the down payment and the invoice as open, sometimes for the full gross amount each, so the account looks like it owes double what it actually does. Collections calls the customer, the customer pushes back saying the advance was already paid, and finance cannot explain in five minutes why the system still shows an outstanding balance. In the vendor case, the payment run tries to pay the full invoice again on top of the advance already disbursed, and someone has to manually block the payment before it goes out.

The configuration behind it

  • Down payment request (noted item, special G/L indicator F on customer side, similar on vendor side) confused with an actual down payment. A request carries no value in the reconciliation account; only the real down payment posting (special G/L indicator A) can be cleared, so if only the request was ever posted there is nothing to net against the invoice.
  • The down payment clearing transaction was simply never run. The actual down payment posts fine, the invoice posts fine, both sit open under different special G/L statuses, and nobody executed the transfer posting (F-39 customer, F-54 vendor) that reduces the special G/L item and offsets the invoice.
  • Missing or wrong account determination for the special G/L indicator in the down payment clearing configuration. If the down payment clearing account is not assigned, the transfer posting fails outright with an account determination error, and the two items stay open by default.
  • Assignment or reference field mismatch between the down payment posting and the invoice. If the down payment carries a different sales order, purchase order, or reference number than the invoice, the transfer transaction cannot propose it as the match and the clerk either skips it or clears the wrong pair.
  • Tax code inconsistency between the down payment and the final invoice. Different tax treatment on the deposit versus the invoice produces a tolerance difference during transfer, so the system posts a partial clearing and leaves a residual open item instead of fully netting.
  • In SD milestone billing scenarios, the down payment clearing requirement configured on the billing item category was not triggered, so the final invoice was created without automatically offsetting the earlier down payment request billing document.
  • Someone attempted to clear the down payment and the invoice through ordinary open item clearing (F-32 or F-44) instead of the dedicated transfer transaction. Special G/L transactions are excluded from standard clearing by design, so this either errors out or, if forced through a manual clearing document, misstates the reconciliation account without actually resolving the underlying offset.

What to check

  • FBL5N (customer) or FBL1N (vendor): pull open items filtered by special G/L indicator to confirm whether an actual down payment (A) exists or only a noted request (F/G) is on the account.
  • FB03: display the down payment document and the invoice document side by side, compare assignment number, reference field, and any sales order or purchase order link.
  • Check whether F-39 (customer) or F-54 (vendor) was ever executed for this account and this invoice; if the transaction history shows none, that is the missing step.
  • OBXR (customer special G/L account determination) or OBYR (vendor special G/L account determination): confirm the down payment clearing account is assigned for the reconciliation account and special G/L indicator in use.
  • Compare tax codes on the down payment posting and the invoice line; a mismatch here explains a residual amount after a partial transfer attempt.
  • For SD-driven down payments, check the billing plan and item category configuration to confirm the down payment clearing requirement is set on the final invoice item.

How to prove it in the data

Pull FBL5N or FBL1N for the account with the special G/L indicator field included, filtered to show both open items: the down payment (indicator A) and the invoice (no indicator or a different one). Sum the two amounts against the actual commercial deal value; if they do not net to the expected balance, and no F-39 or F-54 document number appears linking them, the transfer never happened. Cross-check the assignment field on both lines to confirm they were even eligible to be matched automatically.

Resolution path

If the account only ever received a down payment request (noted item) and no actual payment, this is a process gap, not a system fault: the actual down payment must be posted first (F-29 customer, F-48 vendor) before any clearing is possible. If the actual down payment exists and simply was never transferred, run F-39 or F-54 referencing the invoice; this is a data fix, no transport needed. If the transfer fails on account determination, the missing special G/L clearing account assignment in OBXR or OBYR is a configuration fix requiring a transport through the normal change path, and should be corrected before more transfers are attempted rather than worked around per document. If the block is a reference or assignment mismatch, correct the assignment field on one of the two documents (where still permitted) or process the transfer manually specifying both documents explicitly rather than relying on automatic proposal. Tax mismatches usually require a manual partial clearing with the residual routed to a correction posting, agreed with tax and the account owner first.

The fix people try first (and why it fails)

The common reflex is to force the accounts through ordinary open item clearing (F-32 or F-44), selecting the down payment and the invoice together and letting the system zero the difference. This either rejects outright because special G/L items are excluded from standard clearing, or, if the poster overrides the selection and forces a manual clearing document, it removes the item from the open item list without running the proper transfer logic, meaning the down payment special G/L balance and the tax adjustment that should have happened never get posted correctly. The account looks clean but the reconciliation account and the tax ledger are now wrong underneath it.

Whose problem this is

Accounts receivable or accounts payable operations owns execution of the clearing transaction; FI configuration owns the special G/L account determination if that is broken. The handover note should list the customer or vendor number, the down payment document number and special G/L indicator, the invoice document number, the assignment and reference field values from both, and the tax codes used on each side.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-functional-issues/down-payment-request-not-cleared-against-the-invoiceERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.