Purchase Order vs Invoice vs Sales Order — What's the Difference?

If you're new to B2B paperwork, the difference between a purchase order, a sales order, and an invoice can feel arbitrary. They all list line items. They all have totals. They all reference vendors and buyers. So why do we need three documents instead of one?

Because each one is a different commitment, made at a different stage, by a different party. Mixing them up costs money — either you pay too much, deliver the wrong thing, or fight with a vendor over what was agreed.

Here's the breakdown, in plain language.

The one-sentence definitions

• Purchase order (PO): a buyer's commitment to buy. Issued before delivery.
• Sales order (SO): a seller's confirmation that the order will be filled. Created after the PO arrives.
• Invoice: a seller's request for payment. Sent after delivery.

That's the whole framework. Now let's make it concrete.

The flow on a typical transaction

Acme Construction needs 50 sheets of drywall from Beta Building Supply. Here's what happens:

1. Acme sends a PO to Beta: "We commit to buy 50 sheets of 5/8" drywall at $14.50/sheet, delivered Wednesday, Net 30 terms." This is the purchase order.
2. Beta receives the PO and creates an SO internally: "OK, fulfilling order PO-2026-0142. Pick 50 sheets, schedule Wednesday delivery, invoice on completion." This is the sales order.
3. Beta delivers the drywall Wednesday morning.
4. Beta sends an invoice to Acme: "You owe $725, due 30 days from today, reference PO-2026-0142." This is the invoice.
5. Acme matches the invoice against the PO and pays.

Three documents, three distinct jobs. Each one creates a paper trail that protects against a specific kind of error.

What each document protects against

The PO protects the buyer from the seller invoicing for something they never agreed to. Without a PO, the seller's invoice price is what you owe, full stop. With a PO, you have grounds to push back: "That's not what we agreed to. Here's the PO. Send a corrected invoice."

The SO protects the seller from fulfilling the wrong order or losing track of who ordered what. It's the seller's internal source of truth. In small businesses without ERP software, the SO is sometimes sent back to the customer as an order acknowledgment.

The invoice protects both parties. It creates the formal record of the transaction for accounting, taxes, and payment terms. The buyer's AP system uses it to schedule payment; the seller's AR system uses it to track receivables.

Detailed comparison

| Attribute | Purchase Order | Sales Order | Invoice | |---|---|---|---| | Created by | Buyer | Seller | Seller | | Sent to | Seller | Internal (sometimes buyer) | Buyer | | Timing | Before delivery | After PO, before delivery | After delivery | | Purpose | Commit to buy | Trigger fulfillment | Request payment | | Binding when | Vendor accepts | Internally on creation | Always (when valid) | | Identifies | Order number, items, terms | Order number (often same as PO) | Invoice number, payment due | | Has due date | Yes (delivery date) | Yes (ship date) | Yes (payment due date) | | Counted as revenue | No | No | Yes (when accrual basis) |

Common confusion points

"Can't the invoice just be the PO?"

You'd think so, but no. Here's why:

The PO is the buyer's commitment. The invoice is the seller's claim. If they're the same document, you've collapsed the negotiation into the bill — which means anything the seller invoices is what you "agreed to."

In practice, sellers frequently invoice for slightly different amounts than the PO (extra fees, quantity adjustments, surcharges). The PO gives you the basis to push back. Without one, the conversation becomes "here's our invoice; pay it" and you have nothing to point to.

"Do I need an SO if I send invoices?"

Depends on your business.

• If you fulfill and invoice in one step (service businesses, instant-shipment retailers), the invoice alone is usually enough.
• If there's a delay between order acceptance and fulfillment (manufactured goods, scheduled installations, custom work), an SO is valuable for managing your fulfillment pipeline.
• If you have a fulfillment team separate from sales, the SO is the handoff document.

If you decide you do need them, our SO template hub has Word and Excel versions plus an online generator.

"What about quotes and estimates?"

A quote (or estimate) is what comes before the PO. It's the seller saying "here's what we'd charge if you decide to order." It's not binding on either party until the buyer responds.

The flow with a quote:

1. Buyer asks for a quote: "What would 50 sheets of drywall cost?"
2. Seller sends a quote: "$14.50/sheet, valid 30 days."
3. Buyer accepts by issuing a PO that references the quote.
4. Seller fulfills, creates SO internally, then invoices.
5. Buyer pays.

Quotes are non-binding until accepted. POs are binding once acknowledged. Invoices are always binding once issued (assuming valid).

If you're on the seller side and need to send quotes, see our estimate templates.

"What if my vendor doesn't want to use POs?"

Some small vendors push back: "Just tell me what you need and I'll send the invoice." This is fine for low-stakes recurring purchases (your $80/month software subscription). It's risky for larger one-off orders.

Three approaches when a vendor resists POs:

1. Insist anyway. A reputable vendor accepts POs. If yours won't, ask why — they may have legitimate operational reasons or they may be hiding flexible pricing they don't want pinned down.
2. Use a written quote as a substitute. A signed quote serves the same protective function as a PO if the vendor commits to it in writing.
3. Pay net-zero terms (cash on delivery). If you're paying immediately, the PO matters less because there's no AP cycle to protect.

For most purchases above ~$500 with a non-trivial vendor, just send the PO. Our generator makes it 90 seconds of work.

Real examples by business type

Freelance graphic designer billing a client: invoice only. No PO from the client (most don't issue them for one-off creative work), no SO (you're solo). The invoice is the whole transaction.

Restaurant ordering produce from a wholesaler: standing PO + weekly invoices. The PO sets the agreed prices and delivery schedule; weekly invoices reference the PO as line items get delivered.

Custom furniture builder taking a client order: client signs a contract or sends a deposit (functioning as the PO), builder creates an SO to track production, then sends an invoice on delivery. Three documents, three stages.

Retailer restocking inventory: PO to the wholesaler with quantities and SKUs, wholesaler creates an SO, ships the goods, sends an invoice. Standard B2B flow.

Construction contractor running a job: client signs an estimate (sometimes called a contract); contractor sends POs to subs and material suppliers; suppliers create SOs internally; suppliers invoice the contractor; contractor invoices the client. Multiple chains overlapping.

When you only need invoices

For small service businesses doing simple work for repeat clients, the invoice alone is usually enough:

• Solo consultants billing hourly
• Freelancers on monthly retainers
• Small contractors doing one-time residential work
• E-commerce shops with instant fulfillment

In all these cases, you don't need a PO from the client because the work is small enough, the relationship is established enough, or the fulfillment is fast enough that the invoice alone covers the transaction.

You can graduate to POs when you start hitting:

• Disputes over pricing or scope
• Larger orders where mistakes get expensive
• Multiple stakeholders on the buyer side
• Audit or compliance requirements

When you need all three

You need all three documents when:

• Orders take more than a day to fulfill
• Multiple people are involved on either side
• Money is significant enough that a paper trail matters
• You're in an industry where POs are standard (manufacturing, construction, government, large B2B)

In these contexts, skipping any of the three creates real risk.

Tools to do all three

• Free PO generator — for the buying side
• PO template hub — Excel, Word, PDF, profession-specific
• Sales order generator — for the selling side
• SO template hub — Word and Excel SOs
• Invoice templates — 405+ industry-specific invoice templates
• Estimate templates — for quoting before the PO

The bottom line

Three documents, three distinct jobs:

• PO: buyer commits
• SO: seller confirms
• Invoice: seller bills

You don't always need all three — small simple transactions often need just the invoice. But when a transaction is big enough that getting it wrong costs real money, the three-document flow is what protects both sides.

Use the right tool for each stage. The free templates linked above cover the formats most small businesses need without paying for a procurement platform.