A supplier asks for a purchase order, finance is chasing an invoice, and somewhere in the exchange the two documents get treated as the same thing. For anyone coordinating a purchase, that mix-up is easy to make and expensive to untangle.
Mismatched paperwork stalls payments, muddies the audit trail, and turns a routine transaction into a back-and-forth over which number is right. The confusion usually traces back to a simple gap: the two documents look similar but serve opposite ends of the same purchase.
This guide sorts them out. It defines a purchase order (PO) and an invoice, sets them side by side, and shows the order they move in, so a buyer or accounts payable team can keep a purchase clean from request to payment.
A purchase order is a document a buyer issues to a seller to commit to buying specific items at agreed quantities and prices. It's created before the goods or services change hands, and it records what the buyer intends to buy and on what terms.
A PO usually carries a few standard fields:
PO number: A unique identifier that lets both sides track the order through to payment.
Line items and quantities: The specific products or services and how many of each.
Agreed price and terms: The pricing both parties settled on, plus any delivery or payment terms.
In short, the PO is the buyer's record of intent to buy. It opens the transaction and gives the seller a documented commitment to fulfill.
An invoice is a document a seller issues to request payment after goods or services are delivered. Where the PO opens the purchase, the invoice comes near the end of it, once the seller has done their part.
An invoice typically includes:
Invoice number: The seller's reference for the bill.
The PO it references: The matching purchase order number, which links the request for payment back to the original order.
Amounts due and payment terms: The total owed and when it's due, such as net 30.
The invoice is the seller's request to be paid. It signals that the order has been fulfilled and that payment is now expected against the terms both sides agreed to.
The clearest way to hold the two apart is that a PO opens the transaction and an invoice closes it. They're created by different parties, at different points, for different reasons.
Who issues it: The buyer issues the PO; the seller issues the invoice.
When it's issued: The PO comes first, before fulfillment; the invoice follows, after delivery.
Its purpose: The PO commits the buyer to a purchase; the invoice requests payment for it.
Its role in the trail: The PO records what was ordered; the invoice records what's owed, and the two are matched to confirm they agree.
Read together, the pair forms a simple loop: the buyer commits, the seller delivers and bills, and the numbers on both documents are checked against each other before money moves.
The purchase order comes first, and the invoice follows once the order is fulfilled. The sequence is what keeps a purchase auditable from start to finish.
In practice the flow runs in a few steps:
The buyer issues a PO to commit to the purchase
The seller delivers the goods or services
The seller then issues an invoice that references the original PO number
Finance matches the invoice back to that PO before approving payment, which is why the order of the two documents matters as much as their contents.
POs and invoices work together in the wider procure-to-pay process so a business pays only for what it ordered and received. The link between them is what turns two separate documents into a control.
The common method is three-way invoice matching, which compares three records:
The purchase order, showing what was ordered
The invoice, showing what the supplier billed
The receiving record, showing what arrived
When all three agree on items, quantities, and prices, the invoice is cleared for payment. When they don't, the mismatch is flagged for review. Discrepancies tend to surface here first, whether it's a price that drifted from the agreed rate, a short shipment, or a duplicate bill. Matching the documents is what catches those before payment rather than after, which is the point of keeping both in the first place.
Amazon Business can help teams keep purchase orders and invoices aligned across the buying cycle, framed as tools that support the process rather than as the system of record. Each capability sits at a different point in the loop described above.
For the matching step, 3-Way Match can help reconcile a purchase order against its invoice and receipt so discrepancies surface before payment.
On the billing side, Business Credit Account–available to approved Amazon Business customers–can consolidate invoiced purchases, trimming the volume of individual invoices a team reconciles.
Before an order is placed, Guided Buying and approvals can help apply a business's own purchasing policies, which can reduce the off-policy orders that create mismatches later.
Used alongside an organization's existing finance systems, these tools can help keep the PO-to-invoice trail consistent.
POs and invoices aren't interchangeable; they're two ends of the same purchase, and matching them is what keeps spend controlled. A buyer who treats the PO as the commitment and the invoice as the bill against it has the relationship right, and the audit trail tends to take care of itself from there.
A useful next step is confirming that purchases run through a documented PO process before invoices arrive, so matching has something to check against. To see how Amazon Business can help connect purchasing and payment for your organization, contact us to learn more.
Get started today
Was this helpful?