Purchase Order vs Invoice: What Is the Difference and Why It Matters

Purchase orders and invoices look similar, list similar things, and travel between the same two parties, which is exactly why they get confused. But they do opposite jobs at opposite ends of a purchase, and treating one as the other is how businesses overpay, pay twice, or pay for things they never approved. Understanding the difference is the foundation of any clean buying process. This guide lays out what each document is, who issues it, and why matching them matters.

What a purchase order is

A purchase order, or PO, is issued by the buyer before a purchase. It is an authorization to buy: it names the vendor, the items or services, the quantities, the agreed price, and a PO number. When the buyer sends it and the vendor accepts, it becomes a record both sides agreed to in advance. The key word is before. A PO commits the buyer to a purchase on agreed terms and puts the approval on record ahead of any money changing hands.

What an invoice is

An invoice is issued by the vendor after delivering the goods or services. It is a request for payment: it lists what was provided, references the PO number when there is one, states the amount due, and sets payment terms. The key word is after. An invoice says the work is done, here is what you owe, and please pay by this date. It is the vendor's side of the same transaction the PO started.

The core differences at a glance

• Who issues it: the buyer issues the PO; the vendor issues the invoice.
• When: the PO comes before the purchase; the invoice comes after delivery.
• Purpose: the PO authorizes and commits to the purchase; the invoice requests payment for it.
• What it proves: the PO proves the purchase was approved; the invoice proves payment is now due.

Same transaction, two documents, opposite directions: one opens the commitment, the other closes it.

Not every invoice has a purchase order to pair with. When one arrives without an order behind it, accounts payable handles it down a separate path, covered in non-PO invoice vs PO invoice.

Why matching the two matters

The reason both documents exist is so you can match them. Before paying an invoice, you compare it to the purchase order that authorized the purchase, and to the receipt that confirms delivery. This is three-way matching, and it is what stops the expensive mistakes: an invoice with no matching PO is unauthorized and gets flagged, an invoice for more than the PO agreed gets caught, and a duplicate invoice cannot be paid twice because the PO has already been matched. Without the PO, accounts payable has nothing to check an invoice against and is paying on trust. Running that comparison at volume is exactly what invoice matching automation handles.

How they work together in practice

A clean cycle runs PO first, invoice last. The buyer issues an approved purchase order. The vendor delivers and sends an invoice referencing that PO. Accounts payable matches the invoice to the PO and the goods receipt, and only then schedules payment, the check known as three-way matching. A purchase order system keeps the PO numbered, approved, and open until the matching invoice arrives, so the two documents line up automatically and only genuine exceptions need a human. The PO is not paperwork for its own sake; it is the control that makes the invoice safe to pay.

Frequently asked questions

Both documents have to be readable as data before any of that matching can happen, and that is where most teams still lose the hours. Turning a supplier PDF into fields is a different job from template-based scanning, a distinction laid out in purchase order OCR vs AI extraction. Finance teams that keep their ledger in the cloud usually want the captured order to land where the bills already sit, so they push purchase order data into Xero or the equivalent in Sage and match against it there.

Can you have an invoice without a purchase order? Yes, and it happens often for small or ad hoc spend, but it removes your ability to verify the charge was approved. PO-backed invoices are far safer to pay.

Does the invoice have to reference the PO? It should. The PO number on the invoice is what lets accounts payable match the two quickly instead of hunting for the authorization.

Which comes first, the PO or the invoice? The purchase order always comes first. It authorizes the purchase; the invoice requests payment after delivery.

Is a purchase order a contract? Once the vendor accepts it, a PO is generally a binding agreement to buy on the stated terms, which is part of why it carries weight in a dispute.

Put it together

A purchase order authorizes a purchase before it happens; an invoice requests payment after it is delivered. The buyer issues one, the vendor the other, and matching them, with the goods receipt, is what keeps you from overpaying or paying twice. Get the order right, PO first and invoice last, and the rest of accounts payable gets a lot simpler. When the POs arrive as PDFs and someone retypes them before any matching can start, purchase order line item extraction turns those documents into match-ready data first.