FICO Accounts Payable Part 6: Down Payments, Special G/L Transactions and Clearing
Full lesson currently free to read · AI practice limits apply separately
Handle supplier advances properly: down payment requests, down payments posted to special G/L accounts, clearing them against the final invoice, and why advances must be shown separately on the balance sheet.
Visual overview
Explanation
📌 KEY POINTS
✅ Down payments are special G/L transactions posted with a special G/L indicator (A for down payments in standard).
✅ A down payment request (F-47) is a noted item that the payment program can pay.
✅ The down payment (F-48 or via payment run) posts to an alternative reconciliation account, separate from normal payables.
✅ When the final invoice arrives, the down payment is cleared against it (F-54 or during invoice entry).
⚠️ Uncleared down payments overstate both advances and payables — check them at every month end.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–5 covered AP master data, invoices and payments. Part 6 handles advances to suppliers.
━━━━━━━━━━━━━━━━━━━━
▶ 1. WHY SPECIAL G/L
A payment before the invoice is an advance — an asset, not a reduction of a liability. Posting it to the normal vendor reconciliation account would net it against payables. Special G/L transactions use an indicator that redirects the posting to an alternative reconciliation account, so advances appear separately on the balance sheet while staying on the vendor account.
━━━━━━━━━━━━━━━━━━━━
▶ 2. REQUESTS AND PAYMENTS
A down payment request (F-47) records the agreed advance as a noted item without affecting balances. The automatic payment program can select requests and pay them, posting the actual down payment. Manual down payments can be posted directly with F-48. Purchase orders can carry down payment information that links the request to the order.
━━━━━━━━━━━━━━━━━━━━
▶ 3. CLEARING AGAINST THE INVOICE
When the final invoice is posted, the down payment must be transferred from the special G/L account to the normal payable, either during invoice entry when the system proposes open down payments or with F-54 afterwards. Only then can the remaining amount be paid and the advance balance disappear.
━━━━━━━━━━━━━━━━━━━━
▶ 4. TAX ASPECTS
In some countries, tax is due on down payments. In India, TDS may apply on advances (covered in the TDS lessons), and GST may apply on advances for services. Tax codes and withholding settings on down payments must therefore be designed together with the tax team.
━━━━━━━━━━━━━━━━━━━━
▶ 5. MONTH-END CHECKS
Report open down payments by vendor and age. Advances older than expected delivery dates may mean invoices were posted without clearing — which leaves the vendor showing both an advance and a payable — or deliveries never happened. Both need action.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Post a down payment request for a vendor and pay it in a test payment run.
- Display the vendor's special G/L balance.
- Post the final invoice and clear the down payment.
- Report open down payments by age.
✅ CHECKPOINT: an advance is paid, shown separately and cleared against the final invoice.
How the SAP process fits together
SAP PROCESS EXPLORER · Finance: post to report
ERPClimb.comAccounts Payable — process breakdown
Topic-specific conceptual flow: how key objects and decisions fit together. SAP configurations and exceptional cases can follow different paths.
Selected process stage
Invoice
Enter supplier invoice and liabilities
What this specific lesson teaches
Handle supplier advances properly: down payment requests, down payments posted to special G/L accounts, clearing them against the final invoice, and why advances must be shown separately on the balance sheet.
Key lesson principle: Down payments are special G/L transactions posted with a special G/L indicator (A for down payments in standard).
Representative SAP learning flow, not a guarantee of system runtime sequence in every scenario. The chapter-specific facts come from the published lesson text.
Real project scenario
A vendor complained of an underpayment while the books showed the company owed nothing. The vendor's advance had been paid, the invoice posted, but the down payment never cleared, so the payment program paid only part of the invoice. Clearing the advance and adding a down payment check to the month-end routine fixed it.
Common mistakes
- Posting advances to normal payables.
- Not clearing down payments against invoices.
- Ignoring tax on advances.
- No ageing review of advances.
Best practices
- Use down payment requests linked to POs.
- Clear during invoice entry where possible.
- Design tax treatment of advances.
- Monthly advance ageing review.
Interview angle
Interviewers ask why down payments use special G/L indicators, how requests are paid and how clearing works with the final invoice.
Practice this lesson
Quick check
0 of 3 questions attempted
1. Why are vendor down payments posted with a special G/L indicator?
2. Which transaction posts a down payment request?
3. A vendor shows both an advance and a payable for the same order. What was missed?
Check before use: lesson examples are educational, not a guarantee of correctness for your SAP edition or release. Sample code has not been executed on your SAP system. Confirm API availability, syntax, authorizations and business impact in an approved development or test environment.
More lessons in this topic
- FICO Accounts Payable Part 1: What AP Does and How It Connects
- FICO Accounts Payable Part 2: Supplier Master Data and Core AP Configuration
- FICO Accounts Payable Part 3: Invoice Posting, Payment Terms and Three-Way Match
- FICO Accounts Payable Part 4: Enterprise AP Architecture, Migration and Governance
- FICO Accounts Payable Part 5: Automatic Payment Program Configuration and Payment Runs
- FICO Accounts Payable Part 7: GR/IR Clearing Account — Why It Doesn't Clear and How to Fix It