Purchase Order vs Invoice: The Full Document Flow Every Operations Team Needs to Understand
Most people know that a purchase order is what you send to a supplier and an invoice is what they send back. But the practical difference — and why both documents matter — is something a lot of operations and finance teams are fuzzy on.
That fuzziness creates real problems. Orders placed without POs. Invoices paid without checking what was actually received. Disputes with suppliers that take weeks to resolve because neither side has clean documentation.
Here's the full picture.
The Procurement Document Chain
A mature procurement process involves five documents, each with a specific purpose:
1. Purchase Requisition An internal request to buy something. Raised by whoever needs the goods (warehouse, production, office). It's not a commitment to buy — it's a request for authorization. The difference between a requisition and a PO matters for financial control: the requisition is how you catch unauthorized purchases before they happen, not after.
2. Purchase Order (PO) The formal document issued to a supplier. The PO specifies: what you want, how many, at what price, delivered where, by when. When a supplier receives and accepts your PO, you have a legally binding agreement. This is your commitment to buy.
3. Goods Received Note (GRN) Created at your warehouse when goods arrive. Records what was actually received — product, quantity, condition, date. This is your record of what the supplier actually delivered. GRNs are the document most businesses underinvest in, and it shows up as reconciliation problems later.
4. Supplier Invoice The supplier's billing document. States what they expect to be paid for, and by when. An invoice should reference the original PO number to allow matching.
5. Payment The actual transfer of funds, once the invoice has been validated.
The Purchase Order in Detail
A PO is a financial commitment. Creating one says: "We are authorized to spend this amount, with this supplier, for these goods."
That's why PO approval workflows exist — not to create bureaucracy, but to ensure that financial commitments are authorized before they're made. An unauthorized purchase discovered after the fact is significantly harder to manage than one caught before the PO goes out.
What a PO should include:
- Your company details and PO number
- Supplier details
- Itemized list: product code, description, quantity, unit price, total
- Delivery address and expected delivery date
- Payment terms
- Authorized signature or digital approval
What happens when you don't use POs: You lose the paper trail that connects what you authorized to what you received and what you paid. Disputes with suppliers become harder to resolve. Three-way matching — the AP control that prevents overpayment — requires a PO to match against.
The Invoice in Detail
An invoice is a payment request. The supplier creates it and sends it to you after (or sometimes alongside) delivery.
What a supplier invoice should include:
- Supplier's details and invoice number
- Your company details
- Reference to the original PO number
- Itemized list matching what was delivered
- Payment terms and due date
- Bank details for payment
What to check on every invoice:
- Does it reference a valid PO?
- Do the items, quantities, and prices match the PO?
- Do the quantities match what was received per your GRN?
- Is the due date correct per agreed payment terms?
If all three match — this is the three-way match — payment can proceed. If anything doesn't match, it goes to review.
Common Confusions and Their Consequences
"We don't really use POs — we just order informally and pay the invoice."
This means you have no documented authorization for the purchase. You can't verify whether the invoice matches what you agreed to buy. You can't run three-way matching. If there's a dispute, you have no documentation of what was agreed. Your financial controls are essentially absent for those transactions.
"We sometimes pay an invoice and then raise the PO afterward."
This is a retroactive PO — created to justify a payment that's already happened. It provides no financial control; it's just documentation of a decision that was already made without oversight. The control value of a PO comes from having it before the commitment is made.
"The invoice came in and we paid it, then realized the price was wrong."
Without a PO to check against, this is a predictable outcome. Recovering an overpayment from a supplier is time-consuming and sometimes impossible. The PO-to-invoice check catches it before payment.
Credit Notes: The Document You Also Need to Know
When something is returned, or an invoice was issued incorrectly, the supplier should issue a credit note. A credit note is essentially a negative invoice — it reduces what you owe (or creates a credit balance on the account).
Tracking credit notes properly is important because:
- They need to be matched against the original invoice
- They affect your accounts payable balance
- They need to be applied before you pay the net amount due
- If a credit note isn't tracked, you might pay the original invoice in full and then "forget" about the credit — effectively paying twice
Credit note management gets messy quickly without a system that connects them to the original transactions.
The System That Makes This Clean
The document flow above is straightforward in theory. In practice, it breaks down when procurement, warehouse, and finance are working from different systems or tracking documents in different places.
When everything lives in one platform — POs raised, approved, and sent from the same system where GRNs are recorded and invoices are matched — the chain is unbroken. Matching is automatic. Discrepancies are flagged immediately. Payment is only triggered when the three-way match passes.
Sevenledger manages the complete procurement document chain — from purchase requisition through PO approval, GRN, invoice matching, and payment — in one connected inventory and financial operations platform.