Purchase Order vs Invoice: What's the Difference?

Purchase orders and invoices get confused constantly, and it's easy to see why—both list goods or services, both show prices, and both travel between a buyer and a seller. But they do opposite jobs at opposite ends of a transaction. One authorizes a purchase; the other requests payment for it.

Here's the mental model that clears up almost all the confusion, and it's worth committing to memory: the buyer sends the purchase order, and the seller sends the invoice. A purchase order goes out from the company doing the buying, giving the green light to a purchase before it happens. An invoice comes back from the company doing the selling, asking to be paid after the work is delivered. Get that direction straight and everything else falls into place.

Understanding the distinction matters because mixing the two up causes real billing problems—payments that stall because an invoice is missing a required reference number, work started before it was actually authorized, or a business assuming every client wants a formal purchasing process when most don't. If you're a freelancer, consultant, or small business owner, the good news is that you'll spend most of your time on the invoice side, and many of you will rarely encounter a purchase order at all.

This guide explains exactly what each document is, walks through how they work together in a typical purchasing workflow, shows when purchase orders are used (and when they're safely skipped), and covers what to do when a client insists on one. By the end, you'll know precisely which document you need, when, and why.

What Is a Purchase Order?

A purchase order (PO) is a document the buyer creates and sends to the seller to officially authorize a purchase. It's a formal way of saying, "Yes, we want this, at this price, on these terms—please proceed." It's created before the goods or services are delivered, and it serves as the buyer's commitment to pay once their conditions are met.

A purchase order spells out the specifics of what's being bought: the items or services, the quantities, the agreed pricing, delivery details, and the payment terms. Crucially, every purchase order carries a unique PO number. That number becomes the thread that ties the whole transaction together—it gets referenced on delivery paperwork and, later, on the seller's invoice, so the buyer's accounting team can match everything up and confirm the bill matches what was actually authorized.

A simple example makes it concrete. Imagine a mid-sized company hiring a marketing agency for a quarter of social media management. The company's procurement team issues PO #4521, which authorizes "Q3 social media management services — $6,000, payable Net 30." That document tells the agency three things: the work is approved, the price is agreed at $6,000, and payment will follow 30 days after invoicing. The agency can now begin with confidence, knowing the spend has been formally sanctioned by someone with authority to approve it.

That last point is the real purpose of a purchase order: internal control. In larger organizations, the person requesting work isn't usually the person who controls the budget. A purchase order forces a purchase to be reviewed and approved before any money is committed, which prevents unauthorized spending and creates a clean paper trail. The PO then acts as a reference point throughout the transaction, from delivery all the way to payment.

What Is an Invoice?

An invoice is a document the seller creates and sends to the buyer to request payment for goods delivered or work completed. If the purchase order opens a transaction, the invoice closes it. It's sent after the work is done, and its core job is to say, "Here's what was delivered, here's what you owe, and here's how and when to pay."

An invoice itemizes the goods or services provided, shows the amount due, and states the payment terms and accepted payment methods. It also carries its own unique invoice number for the seller's records. When the transaction began with a purchase order, the invoice should reference that PO number, so the buyer can match the invoice against the authorization and approve it for payment quickly. (For a full breakdown of what every invoice should contain, see our Invoicing Guide and How to Make Invoices.)

Continuing the earlier example: once the marketing agency finishes the quarter's work, it sends an invoice that lists "Q3 social media management — $6,000," states payment is due in 30 days, and prominently references PO #4521. Because the invoice points back to the original purchase order, the client's accounts payable team can instantly confirm the amount matches what was authorized and release payment without back-and-forth.

The essential thing to remember is that an invoice requests payment—it does not authorize the purchase. The authorization, when one is required, already happened via the purchase order. The invoice simply collects on a commitment that was made earlier. This is why an invoice on its own can't approve a purchase, and why, in PO-based environments, a seller shouldn't begin work on the strength of an invoice they've issued. The approval flows the other direction.

Purchase Order vs Invoice: Side by Side

With both documents defined, here's how they compare directly across every dimension that matters.

	Purchase Order	Invoice
Who creates it	The buyer	The seller
Who receives it	The seller	The buyer
When it's sent	Before goods/services are delivered	After goods/services are delivered
Purpose	Authorizes and confirms a purchase	Requests payment for the purchase
Requests payment?	No	Yes
Authorizes spending?	Yes	No
Includes pricing	Yes	Yes
Includes payment terms	Yes (sets them)	Yes (restates them)
Carries a unique number	PO number	Invoice number
Typical users	Larger companies, procurement teams, government	Every business that sells, including freelancers

Read the first two rows together and the whole relationship snaps into focus. The buyer creates the PO and sends it to the seller; the seller creates the invoice and sends it to the buyer. The documents flow in opposite directions because they serve opposite parties—the PO protects the buyer by controlling spending, while the invoice serves the seller by collecting payment. They overlap on the details (both list items, prices, and terms) precisely so the invoice can be matched against the PO at the end.

The Typical Purchasing Workflow

Purchase orders and invoices aren't competitors—they're sequential steps in the same process. Seeing the full lifecycle of a transaction shows exactly where each one fits and why the order matters.

A complete purchasing workflow generally runs like this:

Quote (optional) → Purchase Order → Goods or Services Delivered → Invoice → Payment → Receipt

It begins, often, with a quote: the seller proposes pricing for the work the buyer is considering. (A quote is optional and isn't always part of the process—see Quote vs Invoice for more.) If the buyer decides to proceed, they issue a purchase order, formally authorizing the purchase at the agreed price and terms and assigning it a PO number. With the PO in hand, the seller delivers the goods or completes the services. Once delivery is done, the seller sends an invoice requesting payment and referencing the PO number. The buyer then makes payment according to the terms. Finally, the seller may issue a receipt confirming the payment was received, which closes the loop. (A receipt is distinct from an invoice—see Invoice vs Receipt.)

Two things are worth noticing in this sequence. First, the purchase order always comes before the invoice, because you authorize a purchase before you bill for it—an invoice that arrives before any authorization is exactly the kind of thing a PO process is designed to catch. Second, the quote and the receipt are bookends that don't always appear: plenty of transactions skip the quote, and not every business issues a formal receipt. The non-negotiable core for a sale is simply that something is delivered and then invoiced and paid. The purchase order is layered on top when the buyer's internal controls call for it.

When Do Businesses Use Purchase Orders?

Purchase orders are most common in organizations large or structured enough that spending needs formal controls. If the person ordering the work isn't the person who owns the budget, a PO process is what keeps purchasing accountable.

You'll most often see purchase orders in corporate purchasing, where procurement departments manage spending across many teams and require a PO for any significant outlay. They're standard in manufacturing and wholesale, where businesses order materials and inventory in bulk and need precise records of what was ordered at what price. Government contracts almost always require purchase orders, since public spending demands a rigorous, auditable trail. Construction uses them heavily to manage materials and subcontractors across complex, multi-vendor projects. And broadly, large organizations of any kind tend to run PO-based purchasing simply because their scale makes informal buying too risky to control.

The common thread is accountability at scale. A purchase order separates the act of requesting a purchase from the act of approving it, creates a documented authorization before money is committed, and gives the finance team a reference to match invoices against so they never pay for something that wasn't sanctioned.

This is also exactly why many small businesses and freelancers never receive a purchase order at all. When you're working with a solo founder, a small agency, or an owner-operated business, the person hiring you is usually the same person who controls the money and approves the spend. There's no separation of duties to enforce, so there's no need for the formal authorization step a PO provides. A simple agreement or an accepted quote does the same job with far less overhead. If you've been invoicing happily for years without ever seeing a purchase order, that's completely normal—it just reflects the size and structure of your clients.

Types of Purchase Orders

Not all purchase orders look the same. Larger buyers use a few different types depending on whether a purchase is one-off, repeated, or spread over time. You don't need to memorize these, but recognizing them helps you understand what a client means when they reference a particular PO—and how to invoice against it correctly.

A standard purchase order is the most common and the one most people picture: a single, specific order for a defined set of goods or services at a set price, used once and closed when fulfilled. Our running example—PO #4521 for a quarter of social media work—is a standard PO.

A blanket purchase order authorizes multiple deliveries or repeated purchases over a period of time under one PO number, often up to a set total value. A client who'll need ongoing work across several months might issue a single blanket PO rather than a new one each time, and you invoice against it as you go until the authorized amount is used up. These are common for recurring or high-frequency purchases.

A contract purchase order establishes the terms of a buying relationship—pricing, conditions—without committing to specific quantities upfront; individual orders are then placed against it later. A planned purchase order specifies the items and pricing but leaves delivery dates to be confirmed closer to the time. Both are tools larger organizations use to lock in terms while keeping flexibility.

The practical point for a seller is simple: when a client gives you a PO, note whether it covers a single job or a series of them, and whether it has a total spending cap. With a blanket PO especially, keep track of how much of the authorized amount you've already invoiced, so you don't bill past the limit and trip the buyer's matching checks. When in doubt, ask the client's accounts payable contact how they'd like work invoiced against the PO—they deal with this constantly and will happily tell you.

When Can You Invoice Without a Purchase Order?

For most freelancers and small businesses, invoicing without a purchase order is the default, not the exception. A PO is the buyer's internal tool; if your client doesn't use one, you simply don't need it to bill them.

Freelancers, consultants, and agencies working with small and mid-sized clients can almost always invoice directly. The engagement is typically agreed through a proposal, a signed contract, or an accepted quote, and that agreement is the authorization—an invoice referencing it is enough to get paid. Small business clients generally don't run procurement departments, so they neither issue POs nor expect them. And with repeat customers, an established relationship and a track record of paid invoices make formal purchase orders unnecessary; you both already know the terms.

The principle is straightforward: a purchase order exists to authorize spending within an organization that requires internal sign-off. When that requirement doesn't exist—because the client is small, or because you've agreed terms another way—the PO is simply unnecessary. What does matter in these cases is that you have some clear record of what was agreed before you start work: a signed quote, a contract, or even a confirming email. That agreement plays the same role a PO would, protecting both sides on scope and price. To make getting paid as smooth as possible, focus instead on clear payment terms and making it easy to pay—covered in How to Get Paid Faster.

What to Do If a Customer Requires a Purchase Order

Sooner or later, especially as you take on larger clients, you'll hear "Do you have our PO number?" When a client's process requires a purchase order, working with that process—rather than around it—is the key to getting paid on time.

Wait for the PO before starting work. This is the most important rule, and the one most often broken. If a client requires a purchase order, that PO is your authorization to proceed and their commitment to pay. Starting work before it's issued means you're working without approval—and if the spend is never formally authorized, you may struggle to get paid for it. Politely confirm the PO is in hand before you begin. A short note like "Happy to get started as soon as the purchase order comes through—just send it over whenever it's ready" keeps things moving without overstepping.

Reference the PO number on your invoice. Once you have the purchase order, put its number clearly on every invoice for that work. In PO-driven organizations, accounts payable will not pay an invoice they can't match to an authorizing PO—a missing PO number is one of the most common reasons invoices get stuck. Place it prominently so it's impossible to miss.

Make sure your invoice matches the PO. Large buyers use a process called three-way matching, where accounts payable checks that the purchase order, the record of what was delivered, and the invoice all agree before releasing payment. If your invoiced amount, quantities, or description don't match the PO, the invoice gets flagged and payment stalls. So bill exactly what the PO authorized. If the work legitimately grew beyond the original scope, don't simply invoice more—ask the client to amend the PO or issue a new one first, then invoice against the updated authorization.

Following these practices is the difference between a smooth payment and weeks of delay. Most PO-related payment problems come down to a missing number or a mismatch, both entirely preventable. When you create an invoice, you can reference the relevant purchase order number right on it and customize the fields so everything the client's AP team needs is present from the start—which keeps your invoices moving through their system instead of landing in an exceptions queue.

Purchase Orders vs Quotes

Purchase orders are also frequently confused with quotes, because both appear early in a transaction and both list prices. But they come from opposite parties and carry opposite weight.

A quote is created by the seller. It's a proposal: "Here's what I'd charge to do this work." A quote presents pricing for the buyer to consider, but on its own it commits no one to anything—it's an offer, an invitation to proceed.

A purchase order is created by the buyer. It's an acceptance and an authorization: "Yes, we want this, and we're approving the spend." Where a quote offers a price, a PO commits to one. In a typical flow, the seller sends a quote, and if the buyer agrees, they respond by issuing a purchase order that authorizes the purchase—often at the price the quote proposed.

So the direction of travel is reversed between the two. A quote flows from seller to buyer as a proposal; a purchase order flows from buyer to seller as an authorization. Keeping straight who creates each document is the fastest way to never confuse them. For more on quotes and their close cousin the estimate, see Quote vs Invoice and Estimate vs Quote.

Common Mistakes

A few avoidable errors cause most of the trouble around purchase orders and invoices.

Starting work before receiving a required PO. If a client's process requires a purchase order, beginning work without it means proceeding without authorization—and risking not getting paid if the spend is never formally approved. Always confirm the PO is issued before you start.

Forgetting the PO number on invoices. When a transaction has a purchase order, leaving its number off your invoice is one of the surest ways to delay payment. The buyer's accounts payable team relies on that number to match and approve the bill; without it, your invoice stalls.

Treating an invoice as purchase approval. An invoice requests payment; it doesn't authorize the purchase. Sending an invoice doesn't mean the spend has been approved on the buyer's side, and in a PO environment, work should be authorized before it's billed, not the other way around.

Assuming every customer uses purchase orders. Most small businesses and individual clients don't issue POs and would be puzzled if you asked for one. Don't build your billing process around purchase orders by default—use them only with the clients who actually require them, and invoice directly for everyone else.

Confusing quotes with purchase orders. Remember that a quote is the seller's proposal and a PO is the buyer's authorization. Treating an accepted quote as a binding purchase commitment—or vice versa—leads to misunderstandings about what's actually been approved.

Frequently Asked Questions

Do I always need a purchase order?
No. Purchase orders are tools used by buyers—typically larger or more structured organizations—to control internal spending. If your client doesn't require one, you don't need it to invoice them. Many freelancers and small businesses operate entirely without purchase orders, relying on signed quotes, contracts, or simple written agreements instead.

Can I invoice without a PO?
Yes, in most cases. Unless your client specifically requires a purchase order, you can send an invoice based on whatever you agreed—a proposal, contract, or accepted quote. The invoice requests payment regardless of whether a PO exists. The only time you genuinely need a PO is when the client's own payment process requires one before they'll pay.

Who creates the purchase order?
The buyer. This is the single most important fact to remember: the purchasing party generates and sends the purchase order to authorize the spend, while the selling party generates and sends the invoice to request payment. Buyer sends the PO; seller sends the invoice.

Is a purchase order legally binding?
Generally, once a seller accepts a purchase order, it forms a binding agreement between the two parties on the terms it specifies—which is part of why POs are valued for creating a clear record. That said, the exact legal status depends on the circumstances and jurisdiction, so this isn't legal advice; if a specific contract matters to you, it's worth confirming with a qualified professional.

What happens if the PO amount changes?
If the scope or cost of the work changes after a purchase order is issued, the purchase order usually needs to be amended or reissued to reflect the new amount before you invoice for it. Invoicing more than the PO authorized will cause the bill to fail the buyer's matching checks and stall. The right move is to ask the client to update the PO first, then invoice against the revised authorization.

Should my invoice reference the PO number?
Absolutely, whenever a purchase order exists. Including the PO number lets the buyer's accounts payable team match your invoice to the authorized purchase and approve it quickly. A missing PO number is one of the most common reasons invoices get delayed in larger organizations, so make it prominent on the invoice.

Conclusion

Purchase orders and invoices are two halves of the same transaction, working in opposite directions. A purchase order authorizes a purchase: it's created by the buyer, sent before delivery, and used to control spending and commit to payment. An invoice requests payment: it's created by the seller, sent after delivery, and used to collect on what was agreed. The phrase to keep is simple—the buyer sends the purchase order, and the seller sends the invoice.

Together, when both are used, they create a smooth, well-documented purchasing process: the PO sets out what's authorized, and the invoice—referencing that PO—collects on it, with the two matched at the end to confirm everything lines up. That structure is why larger organizations rely on purchase orders so heavily.

For most freelancers and small businesses, though, the practical takeaway is reassuring: you can run a healthy business invoicing without purchase orders, because your clients usually don't require them. Understanding how POs work simply prepares you for the moment a larger client does—so that when someone asks for your PO number, you know exactly what to do. Whatever side of the table your clients sit on, clear invoicing is what gets you paid.

Ready to invoice with confidence? Create professional invoices—referencing purchase order numbers whenever a client requires them—track their status, and accept online payments with Invoice Generator.