Difference Between Purchase Order and Invoice: Key Roles, Legal Weight, and How They Work Together

TL;DR: Most articles on the difference between purchase order and invoice stop at a field comparison. This one shows how each document serves a distinct function at opposite ends of the same transaction, and what breaks operationally when your team conflates the two. You'll leave with a clear framework for using both correctly, from first approval through final payment.

What is a purchase order and what is its legal purpose?

A purchase order (PO) is a formal document a buyer issues to a seller before any goods or services change hands. It specifies what's being ordered, the agreed price, quantity, delivery terms, and payment conditions. Once the seller accepts it, the PO becomes a binding contract under UCC Article 2, which governs the sale of goods in the US. That legal weight is the point: the PO locks in terms so neither party can revise them unilaterally after acceptance.

This is what separates a PO from a casual email or verbal agreement. It creates a documented, enforceable commitment on the buyer's side before money or goods move. For IT company owners managing vendor relationships, that distinction matters every time a supplier delivers the wrong spec or invoices at a different rate than agreed.

Understanding how a sales order differs from both a PO and an invoice helps clarify where the PO sits in the procurement sequence: it's the buyer's opening move, not a response to anything the seller has sent.

The difference between purchase order and invoice starts here, at timing and initiation. A PO is buyer-initiated and pre-delivery. Everything that follows, including the invoice, responds to it.

What is an invoice and when is it issued?

An invoice is a payment demand issued by the seller after goods or services have been delivered. Where a purchase order originates with the buyer before any work begins, an invoice originates with the seller once the obligation is fulfilled. That sequence matters: the PO sets the terms, the invoice calls in payment against them.

A complete invoice typically includes the seller's details, a description of what was delivered, the agreed price, payment terms (net 30 is common in B2B), and a due date. It creates a legal obligation for the buyer to pay, provided the delivery matches what the PO specified.

Timing is the sharpest distinction. A PO is issued before delivery; an invoice follows it. Confusing the two, or treating them as interchangeable, is one of the more common sources of payment disputes between buyers and sellers. If you want to understand how an invoice differs from the proof-of-payment document that comes after it, the difference between an invoice and a receipt is worth reading alongside this.

The two documents are sequential by design. One authorizes the transaction; the other closes it.

PO vs. invoice decision matrix: how the two documents compare

The table below maps the five dimensions that matter most when you're deciding which document applies — and when both are required.

Dimension	Purchase Order	Invoice
Timing	Issued before delivery	Issued after delivery
Who initiates	Buyer	Seller
Legal weight	Binding offer under UCC Article 2 once accepted	Creates a documented payment obligation
Payment trigger	No — authorizes the transaction	Yes — starts the payment clock
Dispute resolution role	Reference point for scope and price	Reference point for amount owed and due date

The sequence is fixed: PO first, invoice second. Swapping that order — or skipping one document entirely — is where PO and invoice matching breaks down and payment disputes start.

A few practical implications worth noting:

• An invoice without a corresponding PO has no locked price or scope to reference. The seller is exposed.

• A PO with no follow-up invoice leaves the buyer's accounts payable team with nothing to process. The transaction stalls.

• When the two documents disagree on quantity or price, the PO typically governs — because it was accepted first.

Understanding the purchase invoice and the payment obligations it creates clarifies why both documents need to exist and agree before payment moves. If you also work with sales orders, how a sales order differs from both a PO and an invoice covers where that third document fits in the sequence.

The next section covers what happens legally and financially when one document is missing.

How POs and invoices protect buyers and sellers differently

A purchase order protects the buyer. Once a seller accepts it, the PO becomes a binding commitment under UCC Article 2 — locking in price, quantity, delivery terms, and scope before any money moves. If the seller delivers the wrong goods or inflates the price later, the buyer has a signed document to dispute against.

An invoice protects the seller. It creates a documented payment obligation: proof that goods or services were delivered and that a specific amount is now owed. Without an invoice, a seller has no formal record to pursue if payment stalls or a client disputes the amount.

The asymmetry matters most when one document is missing. A seller who ships without a PO loses the price-lock protection the buyer had agreed to — disputes become he-said-she-said. A buyer who pays without an invoice has no audit trail, which creates problems during tax review or vendor reconciliation. Understanding the purchase invoice and the payment obligations it creates makes this clearer.

An invoice without a purchase order is a common gap in smaller IT procurement workflows. The invoice arrives, gets paid, and no one notices the missing authorization layer until an audit flags it.

What happens when an invoice does not match the original PO

A mismatch between a PO and an invoice triggers a chain of operational problems that most IT company owners only notice after cash flow has already taken the hit.

The immediate consequence is payment delay. Accounts payable teams are trained to hold invoices that don't match the originating PO on price, quantity, or scope. That hold can run days or weeks while both sides dig through email threads to find who approved what.

The second consequence is an audit flag. When the purchase invoice and the payment obligations it creates don't reconcile with the PO on record, auditors treat the gap as a control failure, not a clerical error. That distinction matters at tax time and during vendor compliance reviews.

The standard prevention mechanism is three-way matching: the PO, the goods receipt note, and the invoice are compared line by line before payment is released. Any variance above a set tolerance (typically 1–5% depending on company policy) routes to a human reviewer.

This is where PO and invoice matching earns its operational weight. According to the Institute of Finance and Management, manually reconciling a mismatched invoice costs significantly more than processing one that clears automatically.

Understanding the difference between purchase order and invoice is the prerequisite. If you want to see how a sales order differs from both a PO and an invoice, that context rounds out the full procurement picture.

Can you have an invoice without a PO, or a PO without an invoice?

Both documents can exist independently, but each scenario carries a different risk profile.

An invoice without a purchase order is common in informal vendor relationships, recurring service contracts, or small purchases below a set approval threshold. Many IT firms set a floor — often $500 to $1,000 — below which buyers skip the PO entirely. That works until an audit flags the spend or a vendor dispute surfaces with no paper trail to anchor it. For a closer look at the payment obligations a purchase invoice creates, the mechanics matter more than most teams realize.

A PO without a matching invoice happens most often with prepayments, deposits, or blanket orders covering future deliveries. The PO records the commitment; the invoice arrives later, sometimes in installments.

The real risk in both cases is the gap between the two documents. When purchase order vs invoice records don't align, payment delays and audit flags follow almost automatically. Understanding how a sales order differs from both helps clarify where each document sits in the approval chain.

How POs and invoices affect accounting and cash flow

A PO hits your books as an encumbrance the moment it's approved — not a payable yet, but a committed spend that reduces available budget. When the matching invoice arrives, your AP team converts that commitment into an actual liability. Miss the link between the two and you get duplicate payments, phantom liabilities, or a month-end close that takes days longer than it should.

PO and invoice matching is where most cash flow surprises originate. If an invoice references a PO number that doesn't exist in your system, someone has to chase the paper trail manually. According to the Institute of Finance and Management, manually reconciled invoices cost significantly more to process than automatically matched ones — a gap that compounds fast when you're handling dozens of vendor bills per week.

The operational fix is converting approved POs directly into bills without re-keying data. Inzo handles this inside WorksBuddy: once a PO clears approval, Inzo generates the corresponding bill, pre-populated with line items, amounts, and vendor details. Your AP team reviews rather than rebuilds.

Understanding the payment obligations a purchase invoice creates makes this workflow clearer — the PO sets the terms, the invoice triggers the obligation, and the match between them is what your auditors will check first.

What information must each document contain to be valid?

A valid purchase order and a valid invoice share some fields, but each document has its own required set. Getting either wrong creates the exact mismatch that delays payment or triggers a dispute.

A legally valid purchase order must include:

• Unique PO number

• Issue date and expected delivery date

• Buyer's legal name, address, and authorized signature

• Itemized list of goods or services with quantities and agreed unit prices

• Delivery terms and payment terms

• Applicable taxes or duties

A legally valid invoice must include:

• Unique invoice number

• Invoice date and payment due date

• Seller's legal name, address, and tax ID

• Itemized charges that match the original PO line items

• Total amount due, with taxes broken out

• Accepted payment methods

The PO number on the invoice is the link that makes three-way matching possible. If those numbers don't align, accounts payable has no clean way to confirm what was ordered versus what arrived. Understanding what a purchase invoice triggers in your payment obligations makes this checklist easier to apply in practice.

Closing

A purchase order and an invoice are sequential, not interchangeable. The PO locks in terms before delivery; the invoice calls in payment after. When they misalign on price, quantity, or scope, your accounts payable team stalls the payment and auditors flag a control gap. The fix isn't better spreadsheet tracking — it's linking the invoice to the PO at the moment of creation so the match is built in, not reconciled after the fact. Start by auditing your last five invoices: how many arrived without a corresponding PO, and how many sat unpaid while someone hunted for the original authorization?

FAQ

What is the main difference between a purchase order and an invoice?

A PO is issued by the buyer before delivery and locks in terms; an invoice is issued by the seller after delivery and triggers payment. Timing and direction of initiation are the core distinction.

When should you use a purchase order vs an invoice?

Use a PO to authorize a transaction before goods or services move. Use an invoice to request payment after delivery. Both are required for a complete transaction.

How do purchase orders and invoices differ in terms of payment terms?

A PO specifies payment conditions but does not trigger payment. An invoice includes payment terms and starts the payment clock once goods are delivered.

Can a purchase order be used as an invoice?

No. A PO authorizes a transaction; an invoice requests payment for it. Using one in place of the other leaves either the authorization or the payment record missing.

Can you issue an invoice without a purchase order?

Legally, yes. Operationally, it creates audit risk and payment delays because accounts payable teams have no locked price or scope to reference against the invoice.

What happens if an invoice amount does not match the purchase order?

Accounts payable places a hold on payment while the discrepancy is investigated. Auditors flag it as a control failure. Three-way matching (PO, receipt, invoice) prevents this.