Purchase Order vs Invoice: Key Differences and How They Work Together

A purchase order (PO) is what the buyer issues to commit to a purchase. An invoice is what the seller issues to request payment for goods or services already delivered. They are different documents from different parties at different points in the same transaction, and most finance teams keep both because each one does work the other can't.

If you've ever watched an AP team get stuck on a "PO mismatch" or seen an invoice rejected for a missing PO number, you've seen the cost of treating these documents as interchangeable. They aren't. The PO is your commitment. The invoice is the supplier's claim. Reconciling the two through the 3-way match is the audit trail that protects your spend.

Key Takeaways

• A purchase order is issued by the buyer to commit to a purchase before goods or services are delivered.

• An invoice is issued by the seller after delivery to request payment for what was provided.

• The two documents are reconciled through 3-way matching (PO, invoice, receipt), which is the foundation of AP controls and fraud prevention.

• Skipping the PO step exposes you to duplicate payments, ghost invoices, and budget overruns that are nearly impossible to catch after the fact.

• AP automation matches POs and invoices automatically and routes only the exceptions to a human, which is where the cost-per-invoice drops sharply.

What's the Difference Between a Purchase Order and an Invoice?

A purchase order (PO) is a buyer-issued document that authorizes a purchase and locks in price, quantity, and delivery terms before anything ships — basically a confirmation of what a buyer can expect to get and pay. An invoice is a seller-issued document that requests payment after goods or services have been delivered. Same transaction from opposite ends, but performing different jobs.

The comparison at a glance:

We'll walk through how the documents flow, why both exist, and how AP teams reconcile them at scale.

What a purchase order is

A purchase order is a formal commitment from a buyer to a seller, issued before anything is delivered. It locks in what's being bought, how much, at what price, where it's going, and when it's needed. Once the seller accepts the PO, it functions as a contract.

In practice, the PO does three things at once. It gives the seller the authorization they need to ship and bill. It creates a budget commitment in the buyer's ERP so finance can see what's been promised before any cash moves. And it gives AP a reference point for the invoice that will eventually arrive, the document AP will use to verify that the bill matches what was ordered.

What an invoice is

An invoice is a seller-issued document that requests payment for goods or services already delivered. It states what was provided, what's owed, the payment terms (e.g., Net 30), and how to pay. From the buyer's side, an invoice is a liability that gets recorded in accounts payable. From the seller's side, it's a receivable.

A well-structured invoice references the PO number, lists line items that match the PO (or notes variances), and shows a clear payment due date. When invoices arrive without a PO reference, AP teams have to track one down. That legwork is the single most common reason invoices stall.

Which Comes First: Purchase Order or Invoice?

The purchase order always comes first. The buyer issues the PO, the seller accepts it and delivers, and only then does the seller send an invoice. The sequence matters because it's how the accounting and audit trail get built. Without a PO in place, the invoice has no reference point.

Here's how the full procure-to-pay cycle typically flows:

1. Requisition. A department asks to buy something.

2. Approval. Procurement or a manager signs off on the spend, often after a review of available budget and the requesting department's recent purchasing history.

3. Purchase order issued. The buyer sends the PO.

4. Goods or services delivered. The seller fulfills the order, sometimes in full and sometimes as a partial shipment that has to be tracked separately for matching purposes later.

5. Goods receipt. The buyer logs delivery.

6. Invoice received. The seller bills the buyer, referencing the PO number so AP can find the right commitment record without hunting.

7. 3-way match. AP reconciles the PO, the receipt, and the invoice, applying tolerance rules to anything that doesn't tie out exactly.

8. Payment. AP releases the funds.

Each step creates a record. Together, those records are your audit trail. Skip the PO and you've skipped the only commitment record that ties spend back to an approved budget, which is why most controllers won't approve "no PO, no pay" exceptions without a fight.

How the PO-to-invoice workflow actually runs

The workflow runs in two parallel tracks. The buyer's track moves through PO, goods receipt, invoice approval, and payment. The seller's track moves through order acceptance, delivery, invoice, and cash receipt. The two tracks meet at the invoice. Everything before the invoice is about commitment and delivery. Everything after is about verifying and paying.

In a paper-driven AP shop, this workflow can take weeks. POs and invoices arrive in different systems, sometimes different mailboxes, often days or weeks apart. The clerk has to find the PO, find the receipt, compare line items, and resolve any variance manually. Modern invoice automation collapses most of that into seconds because the system reads the invoice, looks up the PO automatically, and only escalates to a human when something doesn't line up.

Curious how much faster this could run? Request a demo of Corpay AP automation and see the matching workflow live.

When an invoice arrives without a PO

An invoice without a PO is called a "non-PO invoice" and most AP shops have a separate (and slower) workflow for it. The clerk has to identify what was bought, find the budget owner, get approval, and decide whether to retroactively cut a PO or pay against an exception code.

Non-PO invoices are the highest-friction category in AP. They take longer to approve, are more prone to duplicate payment, and create audit issues at year-end because the spend wasn't pre-approved. According to Quadient's 20 AP Statistics for 2025, 53% of AP teams say invoice exceptions are their biggest operational challenge, and missing-PO invoices are one of the most common exception types.

Why Do You Need Both a Purchase Order and an Invoice?

You need both because each one is the audit trail for the other. The PO proves the buyer authorized the purchase at agreed terms. The invoice proves the seller delivered and is now owed money. Comparing them line by line is how AP confirms you're paying for what you actually bought, at the price you agreed to, in the quantity you received.

If you only had invoices, you'd be paying whatever a vendor billed without any pre-approved reference. If you only had POs, you'd never know whether the goods actually showed up. Together, the two documents form the closed loop that makes audited financials possible. That's why every controller's playbook starts with "no PO, no pay"... even when AP grumbles.

How 3-way matching works

Three-way matching is the AP control where the invoice is compared against both the PO and the receiving record, or the receipt, before payment is approved. The three documents are the purchase order (what was ordered), the goods receipt (what was delivered), and the invoice (what's being billed). All three have to agree within tolerance, or the invoice goes to exception handling.

In practice, AP looks at:

• Vendor and PO number: Same on all three

• Line items and quantities: Invoice line items appear on the PO, and the quantities billed match what was received

• Unit prices: Invoice prices match PO prices, within an approved variance (often 5%)

• Totals: Extended totals reconcile across documents

When everything ties out, the invoice is auto-approved and scheduled for payment. When something doesn't, an AP clerk investigates. The whole point of 3-way matching is to catch errors and fraud before money moves. Without it, you're trusting that the vendor billed correctly and that nobody on the inside is colluding with a fake vendor. Corpay's primer on accounts payable fraud covers why that trust is risky.

What risks come from skipping the PO step?

Skipping the PO step exposes you to duplicate payments, ghost invoices, budget overruns, and audit failures. Most of these can't be caught after the fact because there's no reference document to compare the invoice against.

The four risks worth naming:

• Duplicate payment. A vendor (innocently or not) submits the same invoice twice. Without a PO to match against, AP has no easy way to catch it.

• Ghost invoices. A fake invoice arrives from a real-looking vendor for a service that was never delivered. Without a PO and a goods receipt, the only check is "does this look legit?"

• Budget overrun. Spend happens without approval, then the invoice arrives, and finance discovers the overage months after the fact.

• Audit failure. When external auditors test controls, "we approve the invoice once it comes in" is not an acceptable answer for any spend above the immateriality threshold.

How Do AP Teams Reconcile Purchase Orders and Invoices?

AP teams reconcile POs and invoices through either manual matching (a clerk compares documents field by field) or automated matching (software does it and flags only the exceptions). Most mid-market and enterprise teams have moved to some form of automation. Smaller teams still do it manually, often in Excel.

The cost difference is substantial. According to Ardent Partners' AP Metrics That Matter 2024, top-performing AP departments process invoices at $2.98 each, compared with $13.54 in fully manual setups, a 4.5x difference that's almost entirely matching and exception-handling labor. The same research shows touchless processing rates climbed to 52.8% in 2025, up from 47.2% in 2024, which means automated matching is doing more of the work each year.

The most common matching exceptions

The most common matching exceptions are price variances, quantity variances, missing receiving records, and duplicate invoice numbers. Each one has its own resolution path, and any serious AP system can be configured to route them automatically.

Price variances happen when the invoice price doesn't match the PO price. Sometimes the vendor raised the price legitimately and didn't tell you. Sometimes it's a data-entry error. Quantity variances happen when the invoice bills for more or fewer units than were received, often because of partial shipments. Missing receiving records happen when goods showed up but the receiving team didn't enter them into the system. Duplicate invoice numbers happen when the same invoice is submitted twice, intentionally or not.

A modern AP platform recognizes each of these patterns, applies tolerance rules, and either auto-approves within tolerance or routes to the right person for review. The piece on the most important reason to automate payments lays out the case for getting matching off your team's desk.

How AP automation handles PO/invoice matching

AP automation handles PO/invoice matching by reading invoices (OCR or e-invoicing), looking up the corresponding PO automatically, comparing the line items, and either approving the invoice within tolerance or routing exceptions to a human. The whole process can run in seconds for a clean invoice.

A single AP employee can process 23,000 invoices per year with automation compared to 6,000 manually. That productivity gain almost entirely comes from removing the manual matching step. The full case for the shift is laid out in our piece on making the case for optimizing invoice payments, and Corpay's AP automation RFP guide walks through what to look for in a platform.

Where Does Corpay's Invoice Automation Fit In?

If the friction you're feeling is "we can't keep up with matching," automated PO/invoice reconciliation is exactly the workload that machine matching was built for. Corpay's invoice automation platform reads invoices, matches them against POs and receiving records, applies tolerance rules, and routes only the genuine exceptions to a human. The result is the touchless processing rates that move cost-per-invoice from double digits to low single digits.

Where Corpay differs from a generic AP tool. It pairs the matching engine with supplier payments automation, so once an invoice is approved, payment execution (ACH, virtual card, check) happens in the same platform with the same controls.

Frequently Asked Questions

Can a purchase order be used as an invoice?

A purchase order cannot be used as an invoice. They are issued by different parties (buyer vs seller) and serve different functions (authorization vs payment request). Some small businesses combine the two on a single document for very simple transactions, but for tax, audit, and accounting purposes they remain conceptually distinct.

Do small businesses need purchase orders?

Small businesses don't legally need purchase orders, but they're useful once spend volume grows past a few transactions a week. POs create a budget commitment, give vendors a reference number for invoices, and protect against duplicate payment. Most small businesses adopt POs once they realize they can't tell which invoices have been paid before.

What are the three types of purchase orders?

The three most common types are standard POs (single specific order), blanket POs (open agreement for repeat orders over time), and contract POs (long-term agreement that triggers individual orders as needed). A fourth type, planned POs, is sometimes used for known future orders with flexible delivery dates.

What's the difference between a PO, a quote, and an invoice?

A quote is what a seller offers to a potential buyer before any commitment ("here's what it would cost"). A PO is what the buyer issues to commit ("we'll buy at these terms"). An invoice is what the seller sends after delivery to request payment. Sequence: quote → PO → delivery → invoice → payment.

How long should you keep purchase orders and invoices?

In the US, the IRS generally requires you to keep tax-relevant records for at least three years and often longer for property and capital-expense items. Many companies keep POs and invoices for seven years to cover state-level statutes and audit requirements. Check with your auditor or CPA. The rules vary by industry and jurisdiction.

Is a sales order the same as a purchase order?

A sales order and a purchase order are mirror documents. The buyer issues a PO. The seller, upon accepting, issues a corresponding sales order in their own system. They reference the same transaction but live in different parties' systems. The information overlaps, but the two are not interchangeable for audit or accounting purposes.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation

Procure-to-Pay