A prepayment invoice is a billing document issued by a vendor requesting payment before goods are delivered or services are performed. In accounts payable, processing a prepayment invoice means recording the advance to a prepayment or vendor advance asset account rather than standard AP expense accounts, then matching and reversing it against the final invoice once delivery is complete. This distinction matters because failing to handle the settlement step correctly leads to double-counted expenses or overstated liabilities on the balance sheet.
Advance payment invoices show up in AP workflows more often than most teams realize. Vendors issue them across several industries where upfront financial commitment is standard:
- Manufacturing relies on them for custom fabrication orders where raw materials must be purchased and production scheduled before the buyer receives anything.
- Construction uses advance payments alongside progress billing, where partial payments fund each phase of a project before the final deliverable.
- Professional services firms issue retainer invoices that function as prepayments, securing capacity before billable work begins.
- International trade depends on advance payment terms (and sometimes letters of credit) to mitigate the risk inherent in shipping goods across borders with limited legal recourse.
In each case, the vendor is shifting financial risk away from their side of the deal, and your AP team absorbs the operational complexity of tracking the prepayment through to final settlement. This is not a niche practice confined to a few industries. According to Visa's 2024-2025 Growth Corporates Working Capital Index, top-performing middle-market companies paid 47% of their supplier invoices ahead of time, using early payment as a deliberate strategy to strengthen buyer-supplier relationships and build a more resilient supply chain. For AP teams at these companies, prepayment invoice processing is a core competency, not an edge case.
One point of confusion worth addressing early: prepayment invoices are not the same as prepaid expenses. Prepaid expenses (rent, insurance premiums, annual software subscriptions) are balance sheet assets amortized over time on a fixed schedule. A prepayment invoice, by contrast, is an AP document tied to a specific purchase order. It requires matching against a final invoice when the vendor delivers, followed by settlement and reversal of the advance. The accounting treatment, the GL accounts involved, and the reconciliation workflow are fundamentally different. If your process treats them the same way, your vendor subledger and your expense reporting will both be wrong.
Prepayment Invoice vs Deposit, Down Payment, and Proforma Invoice
Vendors, procurement teams, and ERP systems rarely agree on terminology. One vendor's "prepayment invoice" is another's "down payment request," and your ERP may lump all of them under a single document type. For AP professionals, the terminology matters less than what each document actually requires you to do: does it create a payment obligation, and how should you record it?
The table below provides a quick reference.
| Term | Definition | When Issued | AP Recording Treatment | Key Distinction |
|---|---|---|---|---|
| Prepayment invoice | Formal vendor request for full or substantial advance payment before goods or services are delivered | After PO execution, before delivery | Debit prepayment asset (e.g., Vendor Prepayments or Vendor Advances), credit cash or AP. Reclassified to expense when final invoice is settled. | Tied to a specific purchase order; creates a trackable asset on the buyer's balance sheet until settlement |
| Deposit invoice | Request for partial payment securing a commitment, typically a fixed percentage of the total order value | At order confirmation or contract signing | Same debit to a prepayment or deposit asset account, credit cash or AP. Often a smaller amount relative to the total. | Usually a smaller proportion of total value; common in custom manufacturing, real estate, and made-to-order goods |
| Down payment invoice | Request for an initial installment, sometimes the first in a structured payment schedule | At or near contract execution, before work begins | Recorded identically to a deposit: debit advance/deposit asset, credit cash or AP | Frequently used interchangeably with deposit; in structured contracts, it may signal the first of several scheduled payments |
| Proforma invoice | Preliminary document showing estimated costs, quantities, terms, and descriptions | Before sale is finalized, often before shipment or for customs/budget purposes | No AP liability recorded. Used for internal planning, customs declarations, or budget approvals only. | Not a demand for payment and does not create any financial obligation |
A few clarifications beyond what the table captures. Prepayment invoices are the document type that triggers the full lifecycle covered in the sections below: recording to a dedicated asset account, matching against the final invoice, settlement, and reversal. Deposits and down payments follow the same initial AP treatment (debit to an advance account, credit to cash), but deposits are typically a smaller proportion of the total order, while down payments may signal the first installment in a structured payment schedule rather than a one-time advance. The distinction usually lies in the contract terms, not in how you book the entry. Proforma invoices are the outlier: they are not a request for payment and should never trigger a payment run or create an AP liability. If a proforma arrives in your AP queue, route it for informational use only and wait for the actual commercial invoice.
The Distinction That Matters for AP
While vendors and ERPs may label these documents differently, the critical question for AP processing is binary: does this document create a payment obligation? Prepayment invoices, deposit invoices, and down payment invoices all do. They require journal entries, create assets or liabilities on your books, and must eventually be settled against a final invoice. A proforma invoice does not. Treating a proforma as a payable is a common source of duplicate payments, and treating a prepayment invoice as a proforma means missing a legitimate vendor obligation.
Prepayment invoices are one of many different types of invoices in accounts payable, each with distinct processing requirements. Getting the classification right at intake prevents errors that cascade through matching, settlement, and period-end reconciliation.
How to Record and Process Prepayment Invoices
The accounting treatment for a prepayment invoice differs from a standard vendor invoice at every stage. A standard invoice flows through the accounts payable subledger and settles with a single payment. A prepayment creates a current asset on the balance sheet that must be tracked, matched, and reversed against a future obligation. Missing any step leaves phantom balances on the general ledger that distort your working capital and vendor aging reports.
The walkthrough below uses a running example: your company orders $200,000 of custom manufacturing equipment and the vendor's contract requires a 25% advance payment of $50,000 before production begins.
1. Receiving and Validating the Prepayment Invoice
Before recording anything, verify the prepayment invoice against the underlying contract or purchase order. Confirm:
- PO reference matches an approved, open purchase order
- Prepayment amount or percentage aligns with the contractual terms (in this case, 25% of $200,000)
- Payment terms reflect the agreed schedule (e.g., due on receipt, net 15)
- Vendor banking details match what is on file to prevent misdirected payments
If any element conflicts with the purchase agreement, flag it with the vendor before processing. A validated prepayment invoice that cannot be tied back to a PO or contract is an audit finding waiting to happen.
2. Recording the Prepayment
When you issue payment against the validated prepayment invoice, the entry hits the general ledger but not the standard accounts payable subledger:
| Account | Debit | Credit |
|---|---|---|
| Vendor Prepayments (asset) | $50,000 | |
| Cash / Bank | $50,000 |
The critical distinction here is the debit account. The $50,000 goes to a dedicated prepayment asset account, often labeled Vendor Prepayments or Advance Payments to Suppliers, not to an expense or AP liability. Under both GAAP and IFRS, prepayments to vendors are classified as current assets (typically reported under "Other Current Assets" or "Prepayments and Advances") until the vendor fulfills their obligation. You have paid for goods or services not yet received, so the balance represents a right to future delivery, not a cost.
Some organizations maintain a single Vendor Prepayments account for all advance payments. Others create sub-accounts per vendor or per purchase order for tighter tracking. The right approach depends on your prepayment volume: if you rarely issue advance payments, a single account is sufficient. If your AP team processes dozens of prepayments per period across multiple vendors, sub-accounts prevent the main account from becoming an opaque bucket that is difficult to reconcile.
3. Receiving the Final Invoice
The vendor delivers the equipment and sends a final invoice for the full $200,000. Record this at face value in the accounts payable subledger:
| Account | Debit | Credit |
|---|---|---|
| Equipment / Inventory (asset) | $200,000 | |
| Accounts Payable | $200,000 |
The full invoice amount enters the subledger regardless of the prepayment already on the books. At this point, your general ledger shows both a $50,000 prepayment asset and a $200,000 AP liability for the same vendor and the same transaction. The next step resolves that.
4. Applying the Prepayment Against the Final Invoice
The prepayment is now offset against the AP liability through a settlement entry:
| Account | Debit | Credit |
|---|---|---|
| Accounts Payable | $50,000 | |
| Vendor Prepayments (asset) | $50,000 |
This entry reduces both the AP balance and the prepayment asset simultaneously. After posting, the AP subledger shows a remaining balance of $150,000 for this invoice, and the Vendor Prepayments account for this transaction returns to zero. The advance payment invoice processing cycle is nearly complete.
5. Paying the Remaining Balance
The final payment is a standard AP disbursement for the net amount:
| Account | Debit | Credit |
|---|---|---|
| Accounts Payable | $150,000 | |
| Cash / Bank | $150,000 |
After this entry, the AP balance for this vendor invoice is zero.
6. Reconciliation
With all entries posted, verify two things. First, the Vendor Prepayments account should show a zero balance for this transaction. Any residual balance means the settlement entry was incomplete or posted to the wrong account. Second, the accounts payable subledger should show the invoice as fully paid and closed. Run both checks before closing the period.
For organizations that process prepayments frequently, a monthly review of the Vendor Prepayments account is essential. Aged balances in this account indicate prepayments that were never settled, either because the final invoice was not received, the settlement entry was missed, or the vendor has not yet delivered. Each aged balance requires investigation and follow-up with the vendor or the purchasing team.
Settling Prepayments Against Final Invoices
The recording walkthrough above covers the clean case: one prepayment, one final invoice, amounts that match. In practice, AP teams rarely get a scenario that straightforward. Settling a prepayment against a final invoice adds matching complexity, reversal requirements, and edge cases that the basic journal entries do not address. Get any step wrong, and you risk double-counting the expense or overpaying the vendor.
How Prepayment Matching Differs from Standard Invoice Matching
Most AP teams are familiar with invoice matching processes including two-way and three-way matching. In a standard three-way match, you compare the final invoice against the purchase order and the goods receipt or delivery confirmation. If all three align, you approve payment for the full invoiced amount.
Prepayments add a layer on top of that process. The purchase order may show partial fulfillment while you wait for the final delivery and invoice. When the final invoice does arrive, you still perform the standard three-way match, but before releasing payment, you must also identify any prepayments tied to that PO or vendor and deduct them from the payable amount. The matching process follows the same foundational principles as standard invoice matching, with the additional step of locating, validating, and applying the advance payment.
The Settlement Workflow
The sequence follows the same steps as the recording walkthrough: three-way match the final invoice against the PO and goods receipt, identify applicable prepayments against the same PO or vendor, apply the offset, and approve the net payment. The critical addition is verifying that no other invoice has already consumed the prepayment and maintaining a clear audit trail linking the prepayment, the final invoice, and the net payment amount.
Why Reversal Matters
The prepayment invoice reversal is the accounting entry that prevents double-counting. When you originally recorded the prepayment, you debited a prepayment or advance asset account. When the final invoice posts at its full value, the corresponding expense (or inventory, or asset) is recognized in full. If you stop there, your books show both the prepayment asset and the full expense, overstating costs.
The reversal entry credits the prepayment asset account and debits accounts payable, effectively transferring the prepaid amount from the balance sheet to offset the liability created by the final invoice. Understanding how invoice accruals and reversals work in AP is critical here because the mechanics are identical in principle: you are unwinding a temporary balance sheet position once the final transaction is recorded. Without this reversal, the organization carries a phantom asset and an inflated expense.
Common Complications
Straightforward one-to-one settlements are the exception rather than the rule. AP teams frequently encounter these scenarios:
-
Multiple prepayments against one final invoice. A long-running project or phased delivery may involve two or three milestone prepayments that all need to be applied against a single final invoice. Track each prepayment separately and apply them in sequence, confirming the cumulative offset before approving the residual payment.
-
One prepayment split across multiple final invoices. A blanket prepayment to a vendor may cover several deliveries invoiced separately. Each final invoice consumes a portion of the original prepayment, and you need a running balance to know how much remains unapplied.
-
Partial deliveries. When only part of the order ships, you may need to settle a proportional share of the prepayment against a partial invoice while holding the remainder open. This requires clear documentation of how much of the prepayment has been consumed and how much is still outstanding on the purchase order.
-
Disputed amounts. If the final invoice differs from the agreed prepayment terms (pricing changes, quantity discrepancies, or rejected goods), you need a resolution process before settlement. Applying the prepayment against a disputed invoice locks in an amount that may need to be unwound later.
-
Foreign currency fluctuations. When the prepayment was made in a foreign currency, exchange rate movements between the prepayment date and the settlement date create a gain or loss. The prepayment was recorded at the original rate, but the final invoice settles at the current rate. Record the exchange rate difference as a debit or credit to a Foreign Exchange Gain/Loss account on the income statement rather than burying it in the vendor balance.
For each of these scenarios, the core discipline is the same: maintain a clear, auditable record of which prepayments have been applied, in what amounts, against which invoices, and ensure the reversal entries fully clear the prepayment asset from the balance sheet.
Automating Prepayment Tracking and Vendor Reconciliation
Manual prepayment tracking breaks down as volume grows. Spreadsheet-based registers go stale when a settlement entry is missed, the vendor prepayment account carries incorrect balances into month-end, and period-end reconciliation turns into hours of detective work. The hardest failure point is matching: vendors use inconsistent formats for referencing original prepayments on their final invoices. Some include the prepayment invoice number, others reference only a PO number, and some provide no cross-reference at all. AP staff end up searching through email threads and prior records to connect the two documents.
The core bottleneck is extracting and matching data across two separate documents (the prepayment invoice and the final invoice) that may arrive weeks or months apart in completely different formats.
How Invoice Data Extraction Closes the Gap
Automated invoice data extraction addresses this bottleneck directly. When both prepayment invoices and final invoices pass through a structured extraction step, the key fields needed for matching (reference numbers, PO numbers, amounts, vendor details, and payment terms) are captured consistently regardless of how each vendor formats their documents.
With a tool like Invoice Data Extraction, your AP team can upload batches of incoming invoices and prompt the AI to pull the specific fields that matter for prepayment matching. A prompt as straightforward as "Extract invoice number, PO number, vendor name, prepayment reference, net amount, and total" produces structured output where every document follows the same format. When a final invoice arrives from a vendor who issued a prepayment three months ago, the extracted prepayment reference from both documents connects them without manual searching. For teams processing prepayments across many vendors simultaneously, batch processing means the extraction step scales with your volume rather than requiring proportionally more staff time.
This structured data output feeds directly into your reconciliation workflow. Instead of manually cross-referencing vendor invoices against your prepayment register, you can automate prepayment invoice data extraction to produce a consistent dataset that maps prepayments to their corresponding final invoices.
Vendor Prepayment Reconciliation Best Practices
Even with automated data capture, sound reconciliation procedures are essential. Build these into your AP calendar:
Monthly prepayment account review. At minimum, review the balance of each vendor prepayment account on a monthly cycle. Every open balance should map to a specific prepayment with an expected delivery or service date. Balances that cannot be traced to an active engagement need investigation.
Aging analysis of outstanding prepayments. Prepayments that remain open beyond the expected delivery date are a red flag. They may indicate goods or services that were never delivered, a final invoice that was received but not matched, or a settlement entry that was never posted. An aging report sorted by vendor and original prepayment date surfaces these issues before they compound.
Vendor statement reconciliation. Request vendor statements quarterly (monthly for high-volume vendors) and reconcile each open prepayment balance line by line. Discrepancies often reveal final invoices that were applied on the vendor's side but not yet processed in your system, or prepayments the vendor considers settled that your records still show as open.
Period-end settlement verification. Before closing each period, confirm that every prepayment settled during the period has a corresponding reversal entry clearing the vendor prepayment account. Any prepayment that was applied against a final invoice but not reversed will overstate both your prepaid assets and your accounts payable.
When the data extraction and matching steps are handled through automation rather than manual effort, these reconciliation reviews shift from laborious detective work to verification of a process that is already largely complete.
Related Articles
Explore adjacent guides and reference articles on this topic.
Invoice Accrual and Reversal Process: A Complete AP Guide
Learn when to accrue uninvoiced liabilities, how to record journal entries, and how reversing entries prevent double-counting — with worked AP examples.
Evaluated Receipt Settlement (ERS): A Complete Guide
What is Evaluated Receipt Settlement? A practitioner's guide to ERS invoiceless processing, how it differs from self-billing, and when to adopt it.
Accounts Payable Month-End Close: Process & Checklist
Step-by-step AP month-end close process with checklists for pre-close prep, cutoff, matching, and accruals. Learn how automation accelerates each phase.
Extract invoice data to Excel with natural language prompts
Upload your invoices, describe what you need in plain language, and download clean, structured spreadsheets. No templates, no complex configuration.