Purchase Order vs Invoice: What Each One Does and When You Need Both

A purchase order is created by the buyer before a transaction and authorizes the purchase. An invoice is created by the seller after delivery and requests payment. They describe the same transaction from opposite sides and share a PO number, which is how accounts payable confirms that what is being billed matches what was ordered and what actually arrived.

That is the whole distinction, and it is usually explained in one sentence and then forgotten. What is worth more of your attention is the machinery around it: which document creates a legal obligation, what happens when the two disagree, and why the small businesses that skip purchase orders entirely tend to discover the gap through an invoice they cannot verify.

Purchase order vs invoice: the difference in one table

Is a purchase order legally binding?

A purchase order becomes legally binding once the seller accepts it, either explicitly or by fulfilling the order. Before acceptance it is an offer to buy. That matters more than it sounds, because it means the terms you write on the PO are the terms you are offering to be held to.

So the prices, quantities, delivery date and payment terms on your purchase order are not administrative decoration. If you write net 30 and the vendor ships against that PO, you have a net 30 arrangement, whatever their invoice says. If you leave payment terms blank and their invoice says due on receipt, you have a much weaker position. The document you control is the one where you should be specific.

An invoice, by contrast, does not create the obligation. It evidences one that already exists under the agreement, whether that agreement is a signed contract, an accepted PO, or a handshake. This is why a vendor cannot invent an obligation by sending you an invoice, and why "we received an invoice so we have to pay it" is the wrong instinct.

What happens when the PO and the invoice disagree

They disagree more often than most people expect, and rarely because anyone is dishonest. Prices drift between quote and fulfilment. A partial shipment gets billed in full. An order is amended by phone and nobody updates the paperwork. The same delivery gets invoiced twice because the vendor re-ran a batch.

The control that catches all of it is the three-way match. Before an invoice is paid, someone compares three documents: the purchase order (what was agreed), the receiving record or packing slip (what actually arrived), and the invoice (what is being billed). If all three agree on item, quantity and price, the invoice clears. If any leg disagrees, payment stops until it is explained.

For services and software, where there is nothing to physically receive, a two-way match of PO against invoice is a reasonable compromise. For goods, do the third leg. It takes a minute per delivery and it is the only step that proves the thing you are paying for showed up.

Do small businesses need purchase orders?

Not always, and it is worth saying so plainly. If one person approves every purchase and you buy from a handful of vendors, a PO system is overhead with no offsetting benefit. Plenty of profitable companies run for years on quotes and invoices alone.

Four signals say it is time to start:

• More than one person can commit company money
• You buy the same categories repeatedly from the same vendors
• Vendors are asking for a PO number to process your orders
• Spend is appearing in your books with no approval trail behind it

The fourth one is the real trigger. The point of a purchase order is not the paperwork, it is the approval that has to happen before the paperwork exists. Once a commitment is authorized in advance, month-end stops producing surprises. If you are setting this up, the purchase order template has the full field list, a numbering scheme, and a worked example.

What about a purchase requisition and a sales order?

Two adjacent documents cause most of the remaining confusion.

A purchase requisition is internal. It is the request an employee makes to the person who controls the budget, asking permission to buy something. It never leaves the company. Once approved, it becomes a purchase order, which does go to the vendor. Small companies usually collapse these into one step, which is fine as long as somebody with authority is saying yes before the PO goes out.

A sales order is the mirror image of a purchase order, seen from the seller's side. Your PO arrives at the vendor and becomes their sales order, which drives their fulfilment. Same transaction, same numbers, different system. When a vendor asks you to reference their SO number, that is what they mean.

Make the PO number do its job

Everything above depends on one field. The PO number is what links the purchase order, the packing slip, the invoice and the payment into a single traceable transaction. Break that link and every invoice becomes a research project.

Three habits protect it. Put a line on every purchase order asking the vendor to reference the PO number on all invoices and packing slips, because most vendors will if you ask and most will not if you do not. Use a numbering format that is unique, sequential and readable, such as PO-2026-0001, so a gap in the sequence is visible during a year-end review. And do not let anyone hand-write a number outside the sequence for an urgent order, because the gap it leaves is indistinguishable from a lost PO.

Once the numbers are consistent, the matching itself is mechanical: pull the three documents, compare item, quantity and price, flag anything that differs. It is the sort of work that scales badly by hand and well once you have something that matches incoming invoices against the order automatically and only surfaces the exceptions. The exceptions are where the judgment is, and the judgment should stay with a person.

Where the admin actually goes

Ask an office manager what purchasing costs them and they will not say the forms. They will say chasing: raising the PO from a quote, emailing it to the vendor, following up when the delivery date slips, hunting for the packing slip when the invoice arrives, and filing all three where the match is possible at all. Much of that friction traces back to how the relationship started, which is why a clean process for onboarding a new vendor pays off on every order afterwards.

That is the layer Officeagent runs. It drafts the purchase order from the quote, routes it to whoever has to authorize that amount, sends it once approved, tracks the delivery date and chases the vendor when it slips, then matches the invoice against the PO and the receiving record and flags what does not line up. Nothing is sent, committed or paid without a person approving it, which is the only sensible control on anything spending money. If that is the part costing you the hours, see how it handles document filing, task tracking, and chasing what is late.