Purchase Orders, Explained: What a PO Must Include, Blanket Orders, Matching, and Numbering

You ordered 200 units at $12 each. The invoice says 220 units at $13.50. Without a purchase order on file, that invoice is just a number someone typed — and you have no document proving what you actually agreed to. That is the entire reason purchase orders exist: a PO turns a verbal "yes, send them over" into a written record of quantities, prices, and terms that your accounts payable team can check every invoice against before a dollar leaves the bank.

A purchase order is a written authorization from a buyer to a supplier to deliver goods or services at a stated price, quality level, and delivery date. It starts life as an offer to buy. Once the supplier accepts it — by countersigning, sending written confirmation, or simply shipping the goods — it becomes a legally binding agreement. The rest of this guide covers what a PO must contain, the blanket-order shortcut for repeat purchases, the two-way and three-way matching controls that stop duplicate and inflated payments, a numbering scheme that survives an audit, and exactly when your PO turns into a contract.

What Every Purchase Order Must Include​

A PO only protects you if it captures the terms you would argue about later. Every purchase order should carry these fields:

• PO number. A unique identifier for the order. More on numbering schemes below.
• Issue date and requested delivery date. The delivery date is what makes a late shipment a breach rather than an inconvenience.
• Buyer and supplier details. Legal names, billing and shipping addresses, and a contact on each side.
• Line items. One row per item: description or SKU, quantity, unit of measure, and unit price. Vague descriptions ("miscellaneous supplies") defeat the whole purpose.
• Extended totals, discounts, tax, and shipping. The math should be on the face of the document: subtotal, any early-payment discount terms, sales tax treatment, freight charges, and the grand total.
• Payment terms. Net 30, 2/10 net 30, due on receipt — whatever you negotiated, written down.
• Delivery and shipping instructions. Ship-to address, carrier or method, and who pays freight.
• Authorized signature or approval. Who approved the spend, and under what authority. For larger companies this maps to an approval matrix by dollar amount.

Small businesses often skip POs for low-value purchases, and that is reasonable: preparing a PO costs staff time without adding value to the goods themselves. The common rule is to require POs above a dollar threshold, for bulk buys, for new suppliers, for customized goods where specifications must be exact, and for anything with a long lead time where you need the supplier contractually committed.

Types of Purchase Orders​

Not every PO covers a single shipment. The four types you will encounter most:

Standard Purchase Orders​

The ordinary case: one document, one set of line items, one delivery expectation. Use these for one-off and infrequent purchases where quantities and prices are known up front.

Blanket Purchase Orders​

A blanket PO (also called a master PO) is issued once to a supplier authorizing purchases up to a ceiling amount over a period — say, $50,000 of office supplies over twelve months. Individual shipments are then made as releases against the master order, each referencing the blanket PO number, without writing a fresh PO every time.

Blankets make sense for repeat purchases of consumables, raw materials, or maintenance parts from an established vendor. They cut paperwork dramatically, but they need two guardrails: a firm expiration date and a not-to-exceed amount, plus periodic review of cumulative releases so a blanket authorization does not quietly become an open checkbook.

Contract Purchase Orders​

A contract PO references a longer-term supply agreement and fixes the commercial terms — pricing tiers, delivery schedules, service levels — for the contract's duration. Think of the blanket PO as the lightweight version for routine consumables and the contract PO as the heavyweight version for strategic supply relationships.

Planned Purchase Orders​

A planned PO is like a standard PO except the delivery dates and sometimes the exact quantities are tentative at issue time, with scheduled releases to follow. Manufacturers use these to lock in pricing with a materials supplier while finalizing production schedules.

Two-Way vs. Three-Way Matching: The Control That Pays for the Paperwork​

Issuing POs is only half the system. The payoff comes in accounts payable, when each supplier invoice is matched against the PO before payment. There are two standard versions.

Two-Way Matching​

Two-way matching compares the supplier invoice against the purchase order, checking that quantities and prices agree. It works for services and low-risk buys where there is nothing physical to receive — consulting hours, software subscriptions, freight bills. If the invoice says what the PO said, it gets approved.

Three-Way Matching​

Three-way matching adds a third document: the receiving report (goods receipt) confirming what actually arrived at your dock. Payment requires all three to agree:

1. The PO says what you ordered and at what price.
2. The receiving report says what showed up.
3. The invoice says what the supplier wants to be paid.

If the invoice claims 220 units but receiving logged 200, the invoice goes on hold until the discrepancy is resolved — a credit memo, a corrected invoice, or a short-shipment claim. This is the control that catches overbilling, short shipments, duplicate invoices, and phantom vendors. It is considered best practice for tangible goods, at the cost of an extra day or two in the approval cycle while documents are gathered.

Larger operations add a fourth check — matching against a quality inspection report — but for most small businesses, three-way matching on goods and two-way matching on services is the right split. Apply the heavier control where the dollars and the fraud risk justify it, not uniformly.

What Happens When Documents Disagree​

Mismatches need a defined tolerance and a defined owner. Common practice: auto-approve variances under a small threshold (a few dollars or a small percentage) and route anything larger to the buyer or department head for resolution. Without tolerance rules, your AP clerk spends Friday afternoons chasing $1.40 rounding differences.

Purchase Order Numbering That Survives an Audit​

You assign your own PO numbers, and the only hard requirements are uniqueness and a sequence a stranger can follow two years later. A good scheme also embeds enough context to sort and search without opening files:

• Sequential with a year: PO-2026-0001, PO-2026-0002. Simple, gap-detectable, and all most small businesses need.
• Department or project coded: PO-MFG-2026-0142 for manufacturing, PO-IT-2026-0031 for IT. Useful once multiple teams issue orders.
• Branch coded: NYC/PO/26/000321 for multi-location operations.

Three rules keep any scheme healthy: never reuse a number (voided POs stay in the sequence marked VOID, so gaps have explanations), reset or roll the sequence on a documented schedule, and require the PO number on the supplier's invoice — that reference is what lets AP match invoices to orders without detective work. Invoice without a PO number goes back to the supplier or into an exception queue, not into the payment run.

When Does a Purchase Order Become Legally Binding?​

Until the supplier accepts it, your PO is an offer — and you can generally modify or cancel it. The moment the supplier accepts, it becomes a contract. For the sale of goods, UCC Article 2 governs in every state except Louisiana, and it is deliberately flexible about what counts as acceptance:

• Written acceptance. The supplier countersigns the PO or sends an acknowledgment confirming the terms.
• Acceptance by performance. The supplier ships conforming goods. Loading the truck and handing the shipment to a carrier accepts the offer even without a signature.
• Written confirmation between merchants. Under UCC 2-207, an acceptance counts even if the supplier's form adds different terms — the notorious "battle of the forms," where the extra terms may or may not become part of the contract depending on materiality and objection.

Two practical consequences follow. First, treat every PO as a potential binding agreement from the moment it leaves your hands: put your real terms on it, because the supplier's shipment can lock them in. Second, if you need to cancel, do it before acceptance — after the goods ship, cancellation is a breach to be negotiated, not a right to be exercised. For services rather than goods, common-law contract rules apply instead of UCC Article 2, and a separate services agreement usually fits better than a goods-shaped PO form.

Recording POs in Your Books​

A purchase order itself is generally not a journal entry — it is a commitment, not yet a transaction. Nothing hits the general ledger until goods arrive or services are performed. What the PO gives your bookkeeping is the reference trail: when the goods arrive and the invoice follows, you book the actual liability with the PO number attached so the three-way match is documented in the ledger itself.

In a plain-text ledger, the flow looks like this. The receiving event and the invoice each get their own entry, and the PO number travels in the narration or a metadata tag so a later review can tie all three documents together:

2026-10-22 * "Acme Supply" "Widget shipment received - PO-2026-0142"
  receiving:goods-in-transit:acme                      200 WIDGET @ 12.00 USD
  liabilities:accrued-receiving:acme
 
2026-10-25 * "Acme Supply" "Invoice INV-8810 against PO-2026-0142 (3-way matched)"
  liabilities:accrued-receiving:acme                   200 WIDGET @ 12.00 USD
  expenses:cost-of-goods-sold:widgets
  liabilities:accounts-payable:acme              -2,400.00 USD

Accruing on receipt rather than on invoice keeps the expense in the right period when the invoice arrives late. If the invoice had claimed 220 units, the mismatch against the 200-unit receiving entry would be visible before anything was paid — which is exactly the control the previous sections describe, expressed as ledger entries. Businesses that post invoices straight to expense with no receiving step are effectively running zero-way matching: the invoice is the only document, and whatever it says goes.

For blanket POs, keep a running schedule of releases against the master authorization — a simple list of release numbers, dates, and amounts deducted from the ceiling — and reconcile it when each invoice arrives so the blanket total never drifts past its cap unnoticed.

Common Purchase Order Mistakes​

• Approving invoices with no PO to match against. Every unmatched invoice is a payment decision made on trust. Route them through an exception approval at minimum.
• Letting blanket POs run without ceilings or expiry dates. An open-ended authorization is a budget line with no bottom.
• Skipping the receiving step. Booking supplier invoices directly to expense without confirming delivery means you pay for short shipments and phantom deliveries.
• Vague line items. "Services rendered" on a PO matches any invoice the supplier cares to send. Quantities, rates, and specifications belong on the document.
• Reusing or skipping PO numbers. Gaps and duplicates destroy the audit trail. Void, never delete.
• Treating the PO as the booking event. Recording expense when the PO is issued overstates liabilities and pulls costs into the wrong period. The PO is a commitment; receipt and invoice are the events.

Putting It Together​

Start with a threshold policy: POs required above a set dollar amount, for new suppliers, and for anything customized or time-critical. Issue standard POs for one-offs, blanket POs with firm ceilings for repeat consumables, and require PO numbers on every supplier invoice. Match services two ways and goods three ways, with written tolerance rules for small variances. Number sequentially with the year embedded, void rather than delete, and remember that the document becomes a contract when the supplier accepts — by signature or by shipment. The paperwork feels like overhead until the first invoice arrives claiming more than you ordered; that is the day the system earns its keep.