01The difference in one line each
- A purchase requisition is an internal request: "may we buy this?" It goes from an employee to the people who approve spending. It commits nobody outside the company.
- A purchase order is an external commitment: "we are buying this, on these terms." It goes from the company to a supplier, and once the supplier accepts it, it is generally treated as a contract.
- A supplier invoice is the supplier's request for payment: "you owe us this." It should refer to the PO and, ideally, only arrive after delivery.
In short: the requisition asks for permission, the purchase order makes the commitment, and the invoice asks for the money.
02Side by side: requisition, purchase order and invoice
| Purchase requisition | Purchase order | Supplier invoice | |
|---|---|---|---|
| Question it answers | Should we buy this? | What exactly are we buying, from whom, on what terms? | How much do we owe, and when? |
| Created by | Employee or department | Buyer or purchasing system | Supplier |
| Audience | Internal approvers | Supplier | Accounts payable |
| Legal weight | None outside the company | Binding once accepted | Claim for payment |
| Accounting effect | None | Budget commitment (encumbrance) | Liability recorded |
| Key fields | Need, budget line, estimated cost, suggested supplier | PO number, supplier, prices, delivery date, payment and delivery terms | Invoice number, PO reference, amounts, tax, due date, bank details |
| Can be changed freely? | Yes, until approved | Only by agreement with the supplier | Only by credit note |
Two rows matter more than the others. Legal weight explains why a PO needs a tighter approval than a requisition: once sent, it is a promise. The accounting effect explains why finance cares about POs at all: an approved PO reduces the budget available before a single invoice arrives, which is the only way to see overspending coming rather than discover it at month end.
03Worked example: one purchase, from request to payment
A marketing manager needs a trade show booth package: stand rental €6,400, furniture hire €1,150, and graphics printing €980, so €8,530 before VAT.
- Requisition PR-0381. She enters the three lines, the cost centre "Events", the estimated €8,530 and two suggested suppliers. Status: submitted.
- Approval. The budget owner checks the Events budget: €40,000 for the year, €28,700 already committed, €11,300 available. The request fits, so he approves. Because it exceeds the company's €5,000 threshold for three quotes, purchasing collects quotes before ordering.
- Purchase order PO-1207. The best offer comes in at €8,210. The buyer issues the PO to that supplier at €8,210 with delivery terms and 30-day payment terms. The committed amount on the Events budget becomes €36,910.
- Receipt. After the show, the manager confirms the stand, furniture and graphics were delivered as ordered.
- Invoice INV-55120. The supplier bills €8,210 plus 20% VAT, so €9,852, quoting PO-1207. The invoice matches the order and the receipt, and is scheduled for payment on its due date.
Each document did a different job. Without the requisition, nobody would have checked the budget before the commitment. Without the PO, the supplier's price and terms would live only in an email thread. Without the receipt, the invoice would have been paid on trust.
04Purchase order vs invoice: the confusion that costs money
The PO comes first and is written by you; the invoice comes last and is written by the supplier. When the invoice arrives, the PO is your reference for what should be billed. That is the basis of three-way matching, which compares the invoice with the PO and the receipt before payment.
An invoice that arrives without a PO reverses the order: you discover the commitment when you are asked to pay for it. Some of those are legitimate (an emergency repair), but if they are frequent, your purchasing process is being bypassed and your budget reports are always late.
05When you need both, and when you can skip a step
Not every purchase needs a requisition and a PO. A sensible policy uses both above a threshold and lighter routes below it:
| Purchase | Requisition | PO | Typical route |
|---|---|---|---|
| Small, one-off, under your low-value threshold (for example $250 / €250 / £200) | No | No | Company card or expense claim, with receipt |
| Recurring item from an approved catalogue | Optional | Yes | Catalogue order, auto-approved within budget |
| Anything above the threshold | Yes | Yes | Requisition, approval, PO, receipt, invoice |
| Contracted service with fixed monthly fee | No, after the contract is approved | One blanket PO for the year | Monthly invoices matched against the blanket PO |
| Emergency (safety, outage) | After the fact, within 48 hours | After the fact | Documented exception, reviewed monthly |
The thresholds are yours to choose. What matters is that they are written down, that the system enforces them, and that the exceptions are visible.
06What a good requisition contains
- What is needed and why, in a sentence an approver can judge.
- Quantity, estimated unit cost and total, in the currency of purchase.
- The budget line or cost centre it will be charged to.
- The date it is needed by, which drives how much sourcing time is available.
- A suggested supplier or existing contract, if any.
- Attachments: a quote, a specification, or a link to the catalogue item.
A requisition missing the budget line or the need date is the one approvers send back most often. Making these two fields mandatory removes a round trip on most requests.
07From spreadsheet to system
If you are starting out, our free Purchase Request Tracker logs every request with its status and approved amount, and the free Purchase Order template gives you a clean, numbered PO with an approval block.
The limits appear quickly: the tracker and the PO are two files that do not talk to each other, the budget check is manual, and nothing stops a PO from being sent before approval. In a purchasing system the approved requisition becomes the PO, with its lines, budget and approval history attached. See purchase order software in Procura, and the next step in the chain: the purchase approval workflow.
08Requisition and PO checklist
- A written threshold above which a requisition and a PO are required.
- Mandatory fields on every requisition: need, budget line, amount, need-by date.
- Budget availability checked at approval, not at invoice time.
- No PO sent to a supplier before the requisition is approved.
- PO numbers are sequential and quoted on every supplier invoice.
- Approved POs reduce available budget immediately (commitments).
- Blanket POs for recurring contracted services.
- Emergency purchases regularised within 48 hours and reviewed monthly.