Purchase Order vs Invoice: What Each Does in Your AP Workflow

A purchase order tells a supplier what you want to buy. An invoice tells you what to pay. One comes before the goods arrive, the other after. That timing gap is where financial control lives.

The real distinction is not just sequencing. A purchase order is a formal document sent by the buyer to request goods or services from a supplier. It locks in quantities, prices, and delivery expectations before any money changes hands. An invoice is a formal document sent by the seller to request payment after goods or services are delivered. The PO authorizes spending. The invoice triggers it.

Together, they create the audit trail that catches overpayments, duplicate payments, and billing errors. Separately, each document solves a different problem. Here is how they work, what goes on each one, and why your AP workflow needs both.

What a purchase order is (and what goes on it)

A purchase order is the buyer's move. You send it to a vendor to formally request specific goods or services at specific prices. Once the vendor accepts it, the PO becomes a legally binding contract.

That legal weight matters. Before acceptance, a PO is a request. After acceptance, it is a commitment from both sides: the vendor commits to deliver, and you commit to pay.

A standard purchase order includes:

• PO number (this becomes the linking mechanism between all related documents)
• Buyer and supplier contact information
• Items or services ordered, with quantities
• Agreed prices for each item
• Payment terms
• Expected delivery dates
• Any other relevant reference numbers

The PO number deserves special attention. It is the thread that ties everything together downstream. When the invoice arrives weeks later, the PO number on the invoice is what enables your AP team to match the two documents.

What an invoice is (and what goes on it)

The invoice is the seller's move. After delivering the goods or services, the vendor sends an invoice requesting payment, along with terms regarding when the payment is due.

A standard invoice includes:

• Invoice number
• Purchase order number (the critical link back to the original authorization)
• Date of the invoice
• Buyer and supplier contact information
• Description of goods or services provided
• Unit and total prices
• Applicable taxes and discounts
• Due date and payment terms
• Bank details for payment
• Shipping and handling fees

Notice the overlap. Both documents share core fields: order details, shipping information, vendor details, and price. That overlap is deliberate. It is what makes matching possible.

How they work together: the five-step procurement flow

The purchase order vs invoice distinction makes more sense when you see where each document sits in the full procurement cycle. The workflow runs in five steps:

1. Purchase order created and sent. The buyer drafts a PO specifying what they need, at what price, and sends it to the vendor.
2. Goods or services delivered. The vendor fulfils the order. A delivery receipt or goods received note confirms what actually showed up.
3. Invoice received. The vendor sends an invoice referencing the PO number.
4. Invoice validated and reconciled with purchase order. AP compares the invoice against the original PO (and the delivery receipt). Do quantities match? Do prices match? Was everything received?
5. Invoice paid. Once validated, payment is released according to the agreed terms.

Step 4 is where the two documents earn their keep. This validation process, known as three-way matching, cross-references three documents: the PO, the delivery receipt, and the invoice. It is the single most effective control against paying for goods you never ordered or never received.

Side-by-side comparison

The purchase order creates financial control before money is spent, while the invoice ensures accuracy and accountability once payment is due.

Why your business needs both

Skip the PO and you lose pre-spend control. There is no baseline to match against when the invoice arrives. Did the vendor charge the agreed price? Did they bill for the right quantity? Without a PO on file, your AP team has no way to answer those questions systematically.

A PO creates a paper trail so you have proof of what was ordered, which you can then use to confirm that what was delivered matches correctly or bring up any errors with the supplier.

Skip the invoice and there is no formal payment request, no due date, no record of what was owed. While invoices are critical from a legal standpoint, purchase orders offer much-needed clarification and prevent conflicts. You need both sides of the equation.

Matching invoices to POs ensures you're paying only for what you ordered and received. For businesses processing dozens or hundreds of invoices per month, that matching process is the difference between controlled spend and cash leaking out through billing errors you never catch. For common red flags to watch for during matching, see our guide on detecting duplicate invoices.

Where automation fits in

The five-step procurement flow works cleanly when you process ten invoices a month. At fifty or a hundred, manually comparing each invoice line against its PO and delivery receipt becomes time-consuming and error-prone.

This is where AI invoice processing changes the equation. Automated tools extract invoice data (vendor, amounts, line items, PO numbers), match it against the corresponding purchase order, and flag discrepancies before payment is approved.

The PO number that links every purchase order to its invoice is what makes automated matching possible. Without structured data on both documents, there is nothing for software to reconcile. With it, invoice processing tools can validate in seconds what takes a human minutes per invoice.

For teams already using accounting software like Xero or QuickBooks, automation means invoice data flows directly into your ledger with the PO reference intact, keeping the audit trail unbroken from authorization to payment.

FAQ