Purchase Order vs Invoice: What's the Difference?

A purchase order and an invoice are two halves of the same transaction, but freelancers and small businesses often treat them as interchangeable — or skip the PO step entirely. Then an enterprise client refuses to pay an invoice because there's no PO number on it, and a two-week delay turns into a two-month dispute.

This guide explains the actual difference between a PO and an invoice: who creates each one, when each gets sent, what fields go on each, how the 3-way matching workflow handles them together, and when you need a PO number on your invoice to get paid.

For the related document comparisons, see invoice vs receipt and what is a proforma invoice.

The short version

| | Purchase Order (PO) | Invoice | |---|---|---| | Who creates it | The buyer | The seller | | When | Before the work / shipment | After the work / shipment | | What it does | Authorizes the purchase, commits the buyer to pay | Requests payment for delivered goods or services | | Binding when | Seller accepts it (often via acknowledgement) | Issued, by default of acceptance | | Contains | Buyer's PO number, line items, quantities, agreed prices, delivery instructions | Invoice number, line items, totals, payment terms, due date | | Triggers | The work / shipment | The payment |

A purchase order is the buyer saying "I am committing to buy this." An invoice is the seller saying "I delivered, now pay me." The PO comes first; the invoice follows.

What a purchase order is

A purchase order is a document the buyer creates and sends to the seller before any work happens or any goods ship. It authorizes the transaction internally on the buyer's side and commits them to pay if the seller delivers what was ordered.

A typical PO contains:

PO number — unique to that buyer's procurement system (e.g., PO-2026-04521)
Buyer info — company, ship-to address, billing address, AP contact
Seller info — your company name and address
Line items — exactly what the buyer is ordering, with quantities and agreed unit prices
Subtotal, tax, total
Delivery / completion date — when the buyer expects the goods or service
Payment terms — typically the buyer's standard term (often Net 30 or Net 45)
Authorization signature or approval — proof the PO was approved internally

Once the seller accepts the PO (formally with an acknowledgement, informally by starting the work), the PO becomes a binding contract.

The key thing about a PO: it's the buyer's commitment to pay if you deliver what was ordered. If you ship something different — different items, different prices, different quantities — the PO doesn't cover it and the buyer can refuse to pay.

What an invoice is

An invoice is a document the seller creates and sends to the buyer after the work is done or the goods are delivered. It requests payment for what was provided.

A typical invoice contains:

Invoice number — unique to the seller's system (e.g., INV-2026-0142)
Buyer info — same as PO
Seller info — your business, bank details for payment
Line items — what was actually delivered, matching the PO line items
Reference to the PO number — usually a PO # field near the top
Subtotal, tax, total
Payment terms and due date

For a deeper walkthrough of the invoice itself — the 8 required fields, formats, common mistakes — see how to make an invoice. For the basic definition, what is an invoice.

Who creates what, when

The workflow for a typical B2B transaction:

Buyer's purchasing team needs something. They identify the need internally.
Buyer issues a PO. Their procurement system generates the document, the buyer's manager approves it, and it gets sent to you (the seller).
You acknowledge the PO. Often formally (signed acknowledgement), sometimes implicitly by starting the work.
You deliver the goods or service. Per the terms on the PO.
You issue an invoice. With the PO number referenced on it.
Buyer's AP team matches the invoice to the PO. If the invoice matches what was authorized, they pay. If not, it gets kicked back.
Buyer pays. ACH, wire, or check, typically within the stated payment terms.

The PO and the invoice are not redundant — they serve different functions in the buyer's internal controls. The PO authorizes the spend; the invoice requests the payment for the authorized spend.

The 3-way match (and why your invoice may bounce)

Large buyers — enterprises, government, hospitals, universities — use a process called "3-way matching" to approve invoices. The three documents that have to match:

The purchase order — what was authorized
The receiving report — what was actually delivered (warehouse confirmation, signed delivery doc, milestone signoff)
The invoice — what the seller is billing for

If all three line up — PO says 100 widgets at $5 each, receiving confirms 100 widgets arrived, invoice bills 100 widgets at $5 each — the invoice gets paid. If any field is off, the invoice gets rejected and routed back for resolution.

Common ways an invoice fails 3-way matching:

Missing PO number. Top reason for rejection. The AP system can't even find the matching PO to compare against.
Wrong PO number. Sometimes a typo, sometimes the buyer changed POs mid-project and you're referencing the old one.
Line items don't match. Invoice says "homepage redesign — $5,000"; PO says "web design services — $5,000." Even if the dollar amount matches, an automated system may not match the line items.
Quantity or rate mismatch. PO authorized 40 hours at $150/hr; invoice bills 45 hours. You need a PO amendment, not just a higher invoice.
Tax differs. Invoice charges sales tax not on the PO. Some buyers are tax-exempt and the PO won't have tax.
Late delivery. Receiving report says you delivered after the PO's required date. Sometimes the buyer can pay anyway; sometimes it triggers a discount or refusal.

If your invoice bounces in 3-way match, the buyer's AP team usually emails you to fix it. Respond fast — every day delayed is a day the original payment is delayed.

When you need a PO number on your invoice

Three rough categories of clients:

Clients who always require a PO

Enterprise companies with formal procurement processes
Federal and state government agencies
Universities, hospitals, large nonprofits
Most Fortune 500 companies

For these, never start work without a PO number in hand. Send a written request for the PO before you start; "I'll send the invoice when I'm done" without a PO is how you end up unpaid for 90 days while procurement figures it out.

Clients who use a PO sometimes

Mid-size companies (50-500 employees)
Tech startups past Series B
Established law firms, marketing agencies, financial services

For these, ask before starting. "Will this engagement have a PO?" If yes, get the PO number before you invoice. If no, proceed normally.

Clients who never use a PO

Solo entrepreneurs and small businesses
Most freelance clients
Many service businesses (creative agencies under 50 people, etc.)

For these, no PO is fine. You can still include a PO #: field on your invoice with a value like n/a or just omit the field entirely.

How to include a PO on your invoice

If the client gave you a PO, put it on your invoice in a way that's impossible to miss:

Invoice #2026-0142
Date: May 16, 2026
PO #: PO-2026-04521
─────────────────────────────
Bill To: Acme Industries LLC
         123 Corporate Way
         Chicago, IL 60601

Place it in the header block, next to the invoice number and date. Match the exact PO number format from the client's document — PO-2026-04521 is different from PO2026-04521 or 2026-04521 in an automated AP system.

If the project has multiple POs (some big projects break into phases with separate POs per phase), reference only the PO that this invoice corresponds to. Don't list all the POs you've ever had with the client.

Industries that use POs vs those that don't

A rough sketch of where you'll encounter PO workflows:

| Industry | PO usage | |---|---| | Manufacturing / wholesale | Always | | Government contracting | Always | | Hospitals / healthcare systems | Almost always | | Universities / higher ed | Almost always | | Enterprise software vendors | Almost always | | Construction (sub-contractors) | Often | | Marketing / advertising agencies | Sometimes (for media buys yes, for retainers often no) | | Freelance creative (design, writing) | Rare for individuals; common for enterprise clients | | Consulting (small firms) | Mixed | | Personal services (lawyers, accountants for individuals) | Rare | | Restaurant / retail B2C | Never |

The rule of thumb: the larger and more bureaucratic the buyer, the more likely they require a PO. Tiny clients don't have a procurement process; large clients can't function without one.

What if the client wants you to use their invoice portal?

Some enterprise clients require vendors to submit invoices through their portal — Coupa, SAP Ariba, Tradeshift, Tungsten, or similar. The portal handles PO matching automatically.

If a client uses one of these, use the portal. Don't email a PDF and hope it gets processed. The portal upload is the only way to get paid in most cases.

The downsides:

You lose control of formatting
You may not get notification when the invoice is approved or paid
The portal may require additional fields you don't track (cost center, GL code, project code)

Keep your own copy of the invoice with the PO number, and track payment through the portal's status page or by following up with the client's AP contact.

A worked example

Let's say you do a $10,000 web design project for a corporate client:

Day 1. You and the client sign a Statement of Work (SOW). The SOW says "client will issue a PO within 5 business days; work begins on receipt of PO."
Day 4. Client's procurement sends PO-2026-08231 for "Web design services per SOW, $10,000, completion by July 1, 2026, Net 30 payment terms."
Day 5. You acknowledge the PO via email. Work starts.
Day 45. Project complete. Client signs off on delivery.
Day 46. You issue invoice INV-2026-0142 with PO #: PO-2026-08231 referenced in the header, line item matching the SOW description ("Web design services per SOW"), $10,000 total, Net 30 from invoice date.
Day 47-50. Client's AP runs 3-way matching: PO 08231 matches receiving signoff matches invoice — all aligned. Invoice queued for payment.
Day 76 (Net 30 from invoice). Payment hits your bank.

If you'd skipped the PO and just sent the invoice cold on Day 46, the most likely outcome would be: client's AP rejects the invoice on Day 50, you spend a week tracking down the right procurement contact, they issue the PO retroactively on Day 60, you re-issue the invoice on Day 61, payment hits on Day 91. A month later than the PO-first path.

FAQ

Does every invoice need a PO?

No. POs are common in B2B procurement workflows (enterprises, government, large institutions) but not required for most freelance or small business work. Ask the client whether their process requires a PO before starting; if yes, get the PO number before doing the work.

Can a PO and an invoice be the same document?

No. They serve different roles — POs authorize the transaction before work happens (created by the buyer), invoices request payment after work is done (created by the seller). They contain similar information but exist for different purposes in the procurement process.

What if my invoice doesn't match the PO exactly?

The invoice will get rejected in 3-way matching. Common reasons: extra hours not authorized, different line item descriptions, tax mismatch, late delivery. The fix is either (a) issue a PO change order from the buyer's side, then re-invoice, or (b) revise your invoice to match the PO. Don't expect the buyer's AP team to "just process it."

Can I issue an invoice without a PO?

Yes, if the client doesn't use POs. Many freelance and small business clients pay invoices with no PO at all. For larger clients with procurement processes, sending an invoice without a PO is the #1 cause of payment delays.

What's the difference between a PO and a sales order?

A purchase order is generated by the buyer; a sales order is generated by the seller in response to a PO (essentially confirming "yes, we'll fulfill this PO"). For freelancers, sales orders are rare — an acknowledgement email serves the same purpose informally.

What if the client never sends the promised PO?

Stop work until you have one. Sending an invoice for unauthorized work to a buyer that requires POs almost always results in non-payment. If you've already done significant work without a PO, work with the client's procurement team to issue a retroactive PO — uncomfortable but standard.

Do POs expire?

Yes. Most POs have a "valid through" or "completion by" date. If you deliver after that date, the PO may need an extension before AP will pay the invoice. Check the date on the PO when you receive it.

Can I include multiple POs on one invoice?

Generally no — one invoice should reference one PO, matching line items. If a project spans multiple POs (e.g., quarterly phases), issue separate invoices, one per PO. Combining POs on one invoice causes 3-way match failures.