Purchase order template: fields, approval flow, and invoice matching
Build a purchase order that records what was approved, who approved it, what the supplier may deliver, and how AP should match the invoice.
Bottom line
A useful purchase order records the approved commitment before the supplier invoice arrives. It should give the supplier clear commercial instructions and give AP enough data to compare the invoice with the order and, for physical goods, the receipt. A PO alone does not prove that the supplier delivered or that the invoice is correct.
Try Ramp →Is it right for you?
- Give every approved order a unique PO number and named requester
- Use the supplier legal name and the correct buying entity
- List quantity, unit, unit price, currency, tax, freight, and total
- State delivery location, required date, and payment terms
- Capture the account, department, project, and budget owner
- Keep approval history and change orders with the original PO
- Match the invoice and receipt evidence before payment
Copy this field structure before choosing a layout
| Block | Required fields | Why AP needs it |
|---|---|---|
| Identity | PO number, issue date, status, requester | Prevents the invoice from floating without an approved record |
| Parties | Buying entity, supplier legal name, remit and order contacts | Keeps the contract, tax record, and payment vendor aligned |
| Lines | Description, SKU or service period, quantity, unit, unit price, tax, freight | Lets AP compare invoice lines instead of checking only the total |
| Accounting | Account, department, location, project, budget owner | Preserves the coding decision made at approval |
| Delivery | Ship-to or service location, required date, receiver | Identifies who can confirm receipt |
| Terms | Currency, payment terms, total cap, renewal or cancellation terms | Defines what AP may pay without a new approval |
| Control trail | Approvers, timestamps, attachments, change-order history | Shows how the commitment changed |
Issue the PO before the supplier starts work
The request should reach the budget owner while the business can still change the quantity, scope, or supplier. A PO created after an invoice arrives documents a decision that has already happened.
Intuit describes a purchase order as the record of an intent to buy specified items and quantities. In QuickBooks Online, an accepted PO can later be added to an expense or bill, which keeps the purchasing record connected to the accounting transaction [Intuit, 2026].
Choose two-way or three-way matching by what can be received
A two-way match compares the invoice with the PO. It often suits subscriptions and services when the business has a separate service-acceptance control. A three-way match adds an item receipt, so AP compares the PO, the invoice, and evidence that goods arrived.
Ramp documents both methods. Its procurement guide says two-way matching checks the invoice against the PO, while three-way matching also requires confirmed receipt for physical goods [Ramp, 2026]. Do not force a receiving step that nobody can perform; assign the receiver when the PO is approved.
Handle changes without overwriting the approval
Price increases, extra units, changed dates, and added scope should create a visible change order. The new approval should show the old amount, the requested change, the revised total, the reason, and the approver.
AP needs an exception rule. A small difference may route to a named reviewer, while a material overbill should stop payment. The tolerance must be written by the business. It should not be inferred from whichever invoice arrived last.
Use the template as a control record, not a payment instruction
The supplier may put different bank details on an invoice. That does not make the new details valid. Verify remit changes through the vendor-master process and a trusted contact before payment.
Also separate commitment from expense recognition. The PO reserves approval and budget. The bill records what the business owes. The payment clears the approved liability. Connecting those records keeps an open PO from masquerading as a paid invoice.
How Ramp can support the handoff
Ramp Procurement supports intake forms, conditional questions, approval policies, PO customization, and invoice matching. Ramp also documents PO imports from QuickBooks and other accounting systems for matching in Bill Pay [Ramp, 2026].
Feature access and plan requirements can change. The reviewer should confirm whether the intended approval, matching, receiving, and integration features are present in the live Ramp account before a CTA is published.
Frequently asked questions
Does every purchase need a PO? The company policy should define thresholds and exceptions. Recurring, higher-value, regulated, or budget-sensitive purchases are common candidates.
Is a PO the same as an invoice? No. The PO records the buyer approved commitment. The invoice is the supplier request for payment.
What belongs in a service PO? Name the service period, deliverable, billing schedule, total cap, acceptance owner, and renewal or termination terms.
Who should close a PO? The process owner should close it after confirming that expected invoices and receipts are complete, or document why the remaining commitment is cancelled.
Can AP pay an invoice with no PO? Only under the approved exception process. AP should record who authorized the exception and whether a PO or contract should govern future purchases.