Purchase Order vs. Invoice: What's the Difference?

Two documents that look similar, flow in opposite directions, and together form the backbone of every business transaction. If you've ever stared at a purchase order and an invoice side by side and thought "these look almost identical — why do we need both?", you're not alone. Both documents list the same items, the same quantities, the same prices. Both have numbers, dates, buyer and seller details. At first glance, they appear redundant. They're not. A PO and an invoice are mirror images of the same transaction — one issued by the buyer before the purchase, one issued by the seller after delivery. Each protects a different party, records a different moment, and serves a different purpose in the accounting trail. This post walks through exactly what each document is, how they differ, when to use which, and the mistakes that happen when people confuse them. The Short Answer A purchase order is sent by the buyer to the seller to authorize a purchase. It says: "I want to buy these things, at these prices, under these terms, delivered by this date." An invoice is sent by the seller to the buyer to request payment. It says: "I've delivered what you ordered. Here's what you owe me, and here's when it's due." The PO comes first. The invoice comes after. Both describe the same transaction — just from opposite sides of the table. Side-by-Side Comparison AspectPurchase Order (PO)InvoiceIssued byBuyerSellerSent toSeller / supplierBuyerDirectionBuyer → SellerSeller → BuyerPurposeAuthorize a purchaseRequest paymentTimingBefore goods/services are deliveredAfter goods/services are deliveredLegal natureAn offer to buy; becomes a contract once acceptedA formal demand for payment; creates an account payableRequired action from recipientFulfill the orderPay the amount owedPrimary beneficiaryProtects the buyerProtects the sellerTypical document numberingPO-2026-00427INV-2026-01842 The Timing Sequence: How They Fit Together A normal business transaction follows this flow: The buyer identifies a need. A purchase requisition is raised internally and approved. The buyer issues a Purchase Order to the chosen supplier, specifying items, quantities, prices, delivery date, and terms. The supplier accepts the PO — either by signing and returning it, sending an acknowledgment, or simply beginning to fulfill. The supplier delivers the goods or renders the services. The buyer receives the goods and logs them in a Goods Received Note (GRN). The supplier issues an Invoice referencing the original PO, listing what was delivered, and stating the amount due. The buyer's accounting team performs a three-way match — comparing the PO, the GRN, and the invoice to make sure all three agree. If the match is clean, the invoice is approved and scheduled for payment according to the payment terms (Net 30, Net 60, etc.). The PO and the invoice bookend the transaction. Everything else — delivery, receiving, matching, payment — happens between them. A Worked Example Let's make this concrete. Acme Trading (the buyer) needs 200 cartons of bond paper. They've been sourcing from PaperCo for years. Step 1 — The Purchase Order. Acme's purchasing specialist creates PO-2026-00427: Buyer: Acme Trading Supplier: PaperCo Item: Bond paper, 80gsm, 500 sheets/ream, 10 reams/carton Quantity: 200 cartons Unit price: $18.00 Subtotal: $3,600 VAT (12%): $432 Grand total: $4,032 Delivery date: Within 5 business days Payment terms: Net 30 The PO is emailed to PaperCo as a PDF. Step 2 — PaperCo fulfills. PaperCo confirms receipt of the PO, packs the order, and delivers 200 cartons to Acme's warehouse on day 4. Step 3 — Acme receives. Acme's receiving team counts the cartons, inspects for damage, and logs GRN-2026-00519 confirming 200 cartons received in good condition. Step 4 — The Invoice. PaperCo issues INV-2026-01842: Seller: PaperCo Customer: Acme Trading Reference: PO-2026-00427 Item: Bond paper (same specs as on the PO) Quantity delivered: 200 cartons Unit price: $18.00 Subtotal: $3,600 VAT (12%): $432 Grand total: $4,032 Payment due: 30 days from invoice date Step 5 — The match. Acme's accounting team compares PO-2026-00427, GRN-2026-00519, and INV-2026-01842. Quantities agree (200 cartons). Prices agree ($18.00/unit). Totals agree ($4,032). The invoice is approved for payment. Two documents. Two directions. One clean transaction. What's Actually on Each Document The fields overlap significantly, which is why they're easy to confuse. But the tone and purpose are different. A Purchase Order contains: PO number and date of issue Buyer's company details (legal name, address, tax ID) Supplier's company details Ship-to address (may differ from billing) Required delivery date Line items: description, quantity, unit of measure, unit price, line total Subtotal, taxes, shipping, grand total Payment terms (to be honored later) Delivery terms (FOB, DDP, etc.) Authorized buyer signature or approval An Invoice contains: Invoice number and date of issue Seller's company details (legal name, address, tax ID) Buyer's company details Reference to the original PO number Delivery date (for reference) Line items: description, quantity actually delivered, unit price, line total Subtotal, taxes, shipping, grand total Payment due date Payment methods accepted (bank transfer details, payment links) Any early payment discount terms Both documents describe the same transaction. The PO describes it as "what we agreed to buy." The invoice describes it as "what we delivered and what you owe." Can One Replace the Other? No — and here's why. A PO without an invoice means there's no formal record of delivery or amount owed. The supplier can't get paid through normal accounting channels. The buyer's books show a commitment but no expense. An invoice without a PO is a red flag in any well-run accounting department. It means the supplier is billing for something the company never formally authorized. This is how rogue spending and supplier fraud happen — "just pay this invoice, we ordered the stuff over the phone" is exactly the conversation that controls are designed to prevent. There are exceptions. Very small transactions — petty cash, company credit card purchases, recurring utilities — often skip the formal PO process. But for any substantial B2B purchase, both documents exist, and they check each other. Related Document Types Worth Knowing Proforma invoice. A preliminary bill issued before goods are delivered, often used for customs, import declarations, or to help the buyer arrange payment in advance. It looks like an invoice but isn't a formal demand for payment — think of it as a "this is what the invoice will look like when we deliver" document. Tax invoice. The formal, tax-compliant version of an invoice, with all required tax information (VAT/GST registration numbers, tax breakdown, compliance codes). In many jurisdictions — India, Philippines, EU countries — a tax invoice is a specific legal document with mandatory fields. Sales order. The seller's internal document confirming a sale after they receive a PO. It's the mirror image of a PO on the seller's side — the same information, but used to trigger fulfillment in the seller's warehouse or production system. Quotation / estimate. A non-binding price offer sent before any formal PO is issued. It tells the buyer what the seller would charge. It does not commit either party — it's an informational document. Receipt. Proof of payment, issued by the seller after the buyer pays the invoice. Not the same as an invoice — an invoice requests payment, a receipt confirms it happened. Common Mistakes to Avoid Treating a quote as an invoice. A quotation is a price offer, not a demand for payment. Paying from a quote without an invoice means your accounting has no tax-compliant record. Issuing an invoice with no PO reference. Most large buyers will reject an invoice that doesn't reference a PO number. Always include it — it's the key that unlocks payment on the buyer's side. Using the terms interchangeably in customer communication. "Send me the invoice" when you mean "send me the quote," or "I'll send you a PO" when you mean "I'll send you the payment" — these create confusion that slows transactions and creates legal ambiguity. Sending an invoice before delivery. Unless payment in advance is the agreed term, invoicing before goods are delivered creates an awkward three-way match and often delays payment. Wait until delivery is confirmed. Accepting goods without a PO. Receiving unapproved shipments commits your company to paying for things nobody authorized. Always require a PO first — and train receiving to reject deliveries without one. How Pomanager Handles Both — Without the Duplication Here's where the design of your accounting software actually matters. In a traditional setup, the buyer creates a PO in their system. The seller receives the PO, re-keys it as a sales order in their system, eventually generates an invoice in their system. The buyer then receives the invoice and matches it against their original PO — often by hand. The same transaction data gets entered three or four times, each entry a fresh opportunity for errors. Pomanager was built around a different premise: One Transaction. Two Businesses. Zero Duplication. When a buyer using Pomanager issues a PO to a supplier also using Pomanager, the same transaction appears in the supplier's system automatically — no re-keying. The supplier can confirm, fulfill, and generate the corresponding sales invoice directly from the PO record. When the buyer receives the goods and logs the GRN, the three-way match happens inside the system without manual intervention. For buyers, the PO and Quotations modules are free forever up to 100 POs per month. For sellers, the Sales Invoicing module handles the other side of the transaction. The core value is that both modules share the same transaction data, so the buyer's PO and the seller's invoice are two views of one record — not two separate documents that have to be reconciled. If you're currently entering the same data into multiple systems, that's exactly the friction Pomanager is designed to eliminate.