A purchase order process that prevents surprise bills

The bills that blow up a month are rarely the ones you planned for. They are the ones nobody remembers agreeing to. A contractor's second invoice that is double the first. A software renewal that quietly jumped from $8,000 to $14,000. A shipment of parts someone on the team ordered without telling anyone. By the time the invoice lands, the money is already committed and the only question left is how to pay it. A purchase order process moves that decision to the front, where you can still say no.

What a purchase order actually is

A purchase order, or PO, is a written authorization to buy something, issued before the invoice arrives. It records what you agreed to purchase, from whom, at what price, and who approved it. That is the whole point: the commitment is documented at the moment you make it, not weeks later when the vendor asks to be paid.

Contrast that with how spending usually works on a small team. Someone decides to buy, the vendor delivers, an invoice shows up, and finance sees the number for the first time. The order and the approval happened in someone's head. A PO turns that private decision into a shared record everyone can check against before a dollar moves.

The three-way match that catches the problems

The reason a PO earns its keep is a simple control called the three-way match. Before you pay any invoice, you line up three documents and confirm they agree: the purchase order (what you agreed to buy), the receipt or goods-received note (what actually arrived), and the invoice (what the vendor is charging). When all three match, you pay. When they don't, you stop and find out why.

This one check quietly kills the most common ways money leaks out of a small company.

• Overbilling: the invoice says $12,000 but the PO says $9,000, so the extra $3,000 never slips through
• Duplicate invoices: a vendor sends the same bill twice, but there is only one PO to match it against
• Unauthorized spend: an invoice arrives with no PO behind it, which tells you nobody approved it
• Short shipments: you were billed for 100 units but the receiving note shows 80 arrived, so you pay for 80

A lightweight flow for a small team

You do not need procurement software or a purchasing department. You need a repeatable path that every committed purchase follows, and it fits in six steps.

• Request: whoever wants to buy writes down what, from whom, and roughly how much
• Approve by threshold: small amounts get a manager's yes, larger amounts go to the founder or finance lead
• Issue a PO number: the approved order gets a unique number, which is sent to the vendor
• Receive: when the goods or work arrive, someone confirms what actually showed up
• Match: the invoice is checked against the PO and the receipt
• Pay: a matched invoice drops into your normal payment run

Write your approval thresholds down so nobody has to guess. A common setup: anything under $1,000 needs one manager, anything from $1,000 to $10,000 needs a department head, and anything above $10,000 needs the founder or finance lead. The exact numbers matter less than the fact that they are written and followed the same way every time.

When a PO is worth it, and when it is overkill

Purchase orders are a tool, not a religion. Wrapping a $30 domain renewal in a formal PO wastes everyone's time and teaches the team to route around the process. Save POs for spending where the control actually pays off.

Use POs for recurring vendors where costs tend to creep, for larger one-time purchases, and for anything you commit to before you ever see a bill — inventory, contractor engagements, equipment. Skip them for small, immediate, low-risk buys and cover those with a simple expense policy and a company card instead. A clean rule is a single dollar threshold: every purchase over, say, $2,500, and every commitment to a vendor you will pay repeatedly, gets a PO. Everything below runs on the lighter expense track.

A worked example

Say your operations lead needs 500 custom units from a supplier for a product launch. She requests the order at a quoted $18 per unit, or $9,000 total. Because it clears your $2,500 threshold, it goes to the founder, who approves it, and you issue PO #1047 to the supplier for 500 units at $18.

Two things now protect you. First, the $9,000 is a known commitment. Even though no cash has moved and no invoice exists yet, your finance lead can accrue it — record the $9,000 as an expense and a payable in the month the goods arrive — so your books reflect what you owe, not just what you have paid. That is a cleaner, more honest close.

Second, when the shipment arrives, your receiving check shows only 460 units made it; 40 were damaged in transit. A week later the supplier's invoice comes in for the full $9,000. Without a PO and a receipt, you pay it, because it looks like every other bill. With the three-way match the gap is obvious: the PO says 500, the receipt says 460, the invoice says 500. You pay for the 460 you actually received, $8,280, and hold the rest until the supplier ships replacements or issues a credit. That $720 correction, and the surprise it prevents, is the entire case for the process.