Invoice Generator Studio

Invoice vs Purchase Order: What's the Difference?

A purchase order and an invoice bracket the same transaction from opposite ends. The purchase order comes from the buyer before anything is delivered and authorizes the purchase; the invoice comes from you, the seller, after delivery, and requests payment. If you sell to larger companies, understanding how the two connect is the difference between getting paid on time and watching an invoice sit in limbo.

This guide covers what a PO contains and why bigger clients insist on one, how their accounts-payable team matches your invoice against the PO before releasing payment, and the practical routine — PO first, PO number on the invoice, bill exactly what was authorized — that keeps a freelancer or small supplier out of the exception queue.

What a purchase order does

A purchase order, or PO, is issued by the buyer before anything is delivered. It says: we authorize this purchase — these items or services, at these prices, in these quantities, by this date. Every PO carries its own reference, something like PO-4712, and that number becomes the thread that ties the whole transaction together.

Inside the buying company, a PO is the visible end of an approval process. Before it reached you, someone requested the spend, a manager or budget holder signed off, and the finance system committed the money. That makes a PO a strong signal you will actually be paid — the budget for your work already exists.

In many countries, a PO you accept — by confirming it, or simply by starting the work — can form a binding contract on the terms it states. Read it before you begin, especially the prices, quantities, and any terms attached in the fine print, and query anything that doesn't match what you quoted.

What an invoice does

An invoice travels in the opposite direction. It comes from you, the seller, after the goods are delivered or the work is done: it itemizes what was delivered and asks for payment by a stated due date, with the details the buyer needs to pay you.

When a PO exists, the most important field on your invoice after the amount is the PO number. Quote it prominently — in its own field, or directly under your invoice number — because it's what lets the buyer's systems connect your request for payment to their authorization to spend.

Why larger companies require a PO

Once a business grows past a handful of people, spending has to be approved before it happens, not discovered on invoices afterwards. A PO system forces every purchase through sign-off first, commits the budget, and leaves an audit trail. Many companies run a strict no-PO, no-pay policy: an invoice that arrives without a valid PO number gets rejected or parked, however legitimate the work was.

It's also fraud protection. Fake and inflated invoices are a common scam, and checking every incoming invoice against a pre-approved PO makes them far easier to catch. So when a client insists on a PO, it isn't bureaucracy aimed at you — it's how their whole payment pipeline works.

How accounts payable matches your invoice

Two-way matching compares your invoice against the PO: same supplier, same items, same prices, same quantities. Three-way matching adds a third document — the goods receipt or delivery confirmation logged when your shipment arrived or your work was accepted. Only when the documents agree is the invoice approved for payment.

A concrete example: the PO authorizes 20 hours at $100 an hour. You invoice 24 hours. Your $2,400 invoice doesn't match the $2,000 PO, so it drops into an exception queue where a human has to investigate — often days or weeks of delay over a $400 difference. Some AP teams tolerate small variances, perhaps 1-2% or a fixed amount, but you can't count on that.

The same thing happens with a missing or mistyped PO number. The system can't find the matching authorization, so your invoice lands in no one's queue and sits unpaid without anyone ever deciding to reject it. When a supplier complains that a big client lost their invoice, an unmatched PO number is often the real story.

Get the PO first, then invoice against it

When a client says "send us your invoice referencing the PO number," the working sequence is simple: get the PO before you start, check it against your quote, do the work, then invoice exactly what the PO authorizes with the PO number quoted on the invoice.

Bill precisely what the PO covers — matching descriptions, matching amounts, same currency. If the scope grew mid-project, don't just add lines to the invoice; ask for a revised or additional PO first, or the extra amount will fail matching. And if a large client hasn't mentioned a PO at all, ask before you invoice — one email asking whether they need a PO number can save you a full billing cycle.

Everything else about the invoice stays normal: a unique invoice number like INV-014, your details and the client's, clear line items, a due date such as Net 30, and VAT, GST, or sales tax if you're registered to charge it where you operate. The PO number is an addition to a proper invoice, not a substitute for one.

At a glance

Purchase order: issued by the buyer, before delivery, authorizes the purchase and commits the budget, and fixes the agreed items, quantities, and prices. Invoice: issued by the seller, after delivery, requests payment against that authorization, and quotes the PO number so the two can be matched. PO first, invoice second — and payment only once they agree.

Frequently asked questions

Is a purchase order the same as an invoice?

No. A purchase order is issued by the buyer before delivery to authorize a purchase, while an invoice is issued by the seller after delivery to request payment. In a PO-based transaction, the invoice should quote the PO number so the buyer can match the two.

Which comes first, the purchase order or the invoice?

The purchase order comes first. The buyer issues the PO to authorize the purchase, the seller delivers the goods or completes the work, and then the seller sends an invoice referencing that PO.

Do I need a purchase order to invoice a client?

No — many small businesses and individual clients don't use POs at all, and an invoice on its own is fine. But if the client runs a PO system, an invoice without a valid PO number will usually be rejected or left unpaid, so ask for the PO before you start the work.

Is a purchase order legally binding?

In many countries a purchase order becomes a binding contract once the seller accepts it, whether by confirming it or by starting the work. The details depend on your jurisdiction and the terms attached to the PO, so read it carefully before you accept.