What Is a Proforma Invoice? Guide for AP Teams

What a proforma invoice is and how it differs from a final invoice. Learn what AP teams should do when one arrives and how to reconcile it later.

Published
Updated
Reading Time
8 min
Topics:
Invoice Fundamentalsproforma invoicesaccounts payableprocurementinternational trade

What is a proforma invoice? It is a preliminary quotation in invoice format sent before delivery or final billing. It helps the buyer review pricing, quantities, and terms, but it is not a payable invoice and should not be posted to accounts payable. In practical AP terms, it is a document to review and approve, not a document to book and pay.

That distinction matters because a proforma often looks close enough to a standard invoice to enter the wrong workflow. It usually includes supplier details, line items, prices, currency, and shipping or delivery terms, which makes it useful for procurement review, shipment planning, and internal approval. What it does not do is confirm that the supplier has completed the transaction or that the amount now belongs in the AP ledger as a normal liability.

The buyer-side reading is simple: treat the document as a pre-billing reference point. It can support decisions about whether to proceed, whether a deposit is expected, and whether the commercial terms still match the purchase order or supplier quote already agreed. It should stay outside the standard invoice queue until the operative invoice arrives.

That framing is consistent with export guidance. The U.S. Commercial Service says a pro forma invoice is a quotation prepared in the format of an invoice and is not used for payment purposes, and the U.S. Commercial Service says pro forma invoices are not used for payment purposes. For AP and procurement teams, that is the rule to remember before anything is routed, booked, or approved for payment.

Proforma Invoice vs Invoice vs Commercial Invoice

Finance teams get into trouble when they treat invoice-format documents as interchangeable. A proforma invoice, a final invoice, and a commercial invoice can share many of the same fields, but they do different jobs and belong in different stages of the workflow.

  • Proforma invoice: Sent before final billing so the buyer can review the proposed transaction. It is preliminary, supports approval and planning, and does not by itself create the normal payable record AP would post and pay.
  • Standard or final invoice: Sent when the supplier is actually billing for goods or services provided under the agreed terms. This is the document AP expects to validate, code, approve, and settle through the usual invoice-to-pay process.
  • Commercial invoice: Common in cross-border trade once the transaction is moving toward shipment and customs handling. It is more operative than a proforma because it reflects the actual sale details used in fulfillment, trade documentation, and later financial processing.
  • Quote: Earlier and looser than a proforma invoice. A quote sets out proposed pricing, while a proforma usually packages those terms in invoice-style form once the transaction is closer to approval or shipment.

The practical distinction for buyers is timing and consequence. A proforma helps a team decide whether the transaction terms are acceptable. A final invoice tells AP there is something to process. A commercial invoice matters when the transaction needs formal trade documentation and later reconciliation against what was proposed earlier. For buyers, the posting consequence is straightforward: the final or commercial invoice is the document normal AP processing waits for, while the proforma stays in a pre-billing review role.

That is why the comparison should not stop at document labels. AP needs to know whether the document supports payment, whether it is evidence of the completed sale, and whether it belongs in normal liability recognition. If a team needs a wider taxonomy, the broader breakdown of invoice types and where proformas fit gives the bigger picture, but the core rule here is narrower: a proforma invoice is the preliminary document in the set, not the payable one.


When AP and Procurement Teams Receive a Proforma Invoice

AP and procurement teams usually see proforma invoices when the supplier needs agreement or action before the final bill exists. The document is common where timing, logistics, or partial payment matters before delivery is complete.

Typical cases include:

  • Import and export transactions: The buyer needs pricing, quantities, and delivery terms documented before shipment details are finalized.
  • Advance-payment or deposit requests: The supplier wants the buyer to approve an upfront amount before the final invoice is issued, which is why it helps to understand how AP teams handle advance-payment invoices before final settlement.
  • Internal procurement approval: The business wants a finance or purchasing sign-off before goods are released, production starts, or a service commitment becomes firm.
  • Quotation follow-up: The supplier moves beyond a simple quote and sends an invoice-style document that reflects the agreed commercial terms more formally.

When one arrives, the first job is not posting. It is verification. The team should confirm the supplier identity, the referenced PO or quote number, the items and quantities, the agreed pricing, the currency, the delivery terms, and any deposit language that changes who needs to act next. In cross-border deals, Incoterms and ship-to information may matter because the proforma often sets expectations that the later commercial invoice must match.

This is also where procurement and AP touch the same document for different reasons. Procurement may care about commercial accuracy and delivery commitments. AP cares about whether the document should enter any payable workflow at all. A proforma invoice often matters to both teams, but not for the same reason, which is why the routing decision matters from the start.

How to Process a Proforma Invoice Without Creating a False Payable

The safest AP rule is to treat a proforma invoice as a review document, not as the record that starts normal payment processing. It should not be posted as a supplier liability, pushed into the standard invoice approval queue, or treated as the final support for releasing payment in the usual AP workflow.

Instead, the team should classify it separately and keep it tied to the upstream business decision it supports. That may mean procurement approval, deposit review, shipment planning, or internal confirmation that the commercial terms are correct. The point is to preserve the document for reference while keeping it outside the set of invoices the business is ready to code, approve, and pay.

The common mistakes are predictable. Teams book the liability too early because the document looks complete. They assume it can support the same tax and control steps as the final invoice. They route it through the same checks as an actual payable and then have to unwind the entry when the real invoice arrives with changed quantities, terms, or charges. Strong invoice validation controls for documents that should and should not enter payment approval prevent exactly that kind of confusion.

Keeping the proforma separate also reduces downstream risk. If the final invoice arrives later with different prices, freight charges, or line items, the team can compare the two documents cleanly instead of trying to fix an AP record that was created too soon. The proforma still matters, but it matters as an approval and reconciliation reference, not as the payable itself.


What to Capture From a Proforma Invoice for Later Reconciliation

The value of a proforma invoice does not end when the team decides not to post it. Its real operational value is the reference data it provides before the final invoice arrives. If that data is captured cleanly, AP can compare the later invoice against what was originally proposed and spot changes before payment approval.

The fields worth keeping are usually the ones that will matter during matching and exception review:

  • Supplier name
  • Proforma or quotation number
  • Purchase order reference
  • Line-item descriptions
  • Quantities
  • Unit prices
  • Currency
  • Delivery terms and requested dates
  • Ship-to details
  • Deposit amounts or other estimated charges
  • Incoterms when the transaction is cross-border

Those fields create the bridge from preliminary document to payable document. When the commercial or final invoice arrives, the team can compare prices, quantities, currency, and terms against the proforma instead of reviewing the new invoice in isolation. That is especially useful in import and export scenarios, where delivery terms affect what charges appear later and how Incoterms appear on commercial invoices in cross-border trade can change what the buyer expects to reconcile.

For teams that want a cleaner handoff, invoice data extraction workflows can capture supplier names, PO references, line items, currencies, and other invoice-format fields into structured Excel, CSV, or JSON outputs for review and later matching. Used that way, extraction supports document control and reconciliation without treating the proforma invoice itself as the final AP record.

Invoice Data Extraction

Extract data from invoices and financial documents to structured spreadsheets. 50 free pages every month — no credit card required.

Try It Free
Continue Reading