Purchase Order

A purchase order is a buyer's document authorizing a purchase at a set price and quantity. See how it relates to rate cards and invoice matching.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Purchase Order

A purchase order is a document a buyer issues to a vendor that authorizes a purchase at a stated quantity, price and delivery term before the vendor ships or invoices. It becomes the reference point AP later checks the invoice against, but on its own it does not confirm the price is correct against the underlying contract.

1. What is a purchase order?

A purchase order is a buyer-issued document that authorizes a specific purchase: item or service, quantity, unit price and delivery date. Once a vendor accepts it, it becomes a binding commercial commitment. AP later uses it as the reference point to confirm that an incoming invoice matches what was actually ordered, at the price that was actually agreed.

Procurement systems generate a purchase order number automatically, and that number typically flows through to the vendor's invoice as a reference field. This lets AP pull up the original order during payment processing without contacting procurement directly.

A purchase order can cover a single delivery or, in a services context, a period of billing tied to a statement of work. Either way, it sets the boundary AP checks incoming charges against.

2. How does a purchase order differ from a contract?

A contract sets the ongoing terms: pricing structure, volume tiers, rebate clauses, surcharge rules. A purchase order is a single transaction issued under those terms. The contract governs many purchase orders over its term, so if the person raising the PO does not check it against the contract's current rate card, the PO can be internally consistent and still wrong.

This distinction matters because a purchase order system checks itself, not the contract. It will confirm an invoice matches the PO. It has no built-in step that confirms the PO price matches the rate card the vendor actually agreed to.

When a contract changes, a price increase, a new rebate tier, an updated surcharge schedule, someone has to update how future purchase orders are priced. If that update does not happen, every PO issued afterward carries the old, wrong number forward.

3. Why do purchase order errors cause margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A purchase order raised at an outdated or incorrect price becomes the baseline AP checks against, so the invoice can pass a routine match while still deviating from the actual contract. The error goes uncaught because the check compares two wrong numbers to each other.

This is a structural gap, not a lapse by any one person. The purchase order system and the contract repository are usually separate systems, maintained by separate teams, on separate update cycles.

Fixing it requires checking the purchase order itself against the contract terms, not just the invoice against the purchase order. That is a different check than the one most AP workflows run by default.

4. How does invoice matching use the purchase order?

Standard invoice matching compares the invoice to the purchase order and, often, the goods or service receipt. This confirms the vendor billed what was ordered, at the price stated on the PO. It does not independently confirm the PO price is the correct contract price; that check requires going back to the rate card or master agreement.

Three-way matching, invoice, PO and receipt, catches quantity errors and unauthorized charges. It was built to stop a vendor from billing for something never ordered or never received.

It was not built to test whether the PO price itself reflects a rebate clause, a volume tier, or an index escalation clause buried in the contract. Those checks sit outside the standard match and require going back to the source document.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

Does a purchase order guarantee the price is correct?

No. A purchase order guarantees the vendor was authorized to bill that price for that quantity. It does not confirm the price matches the current contract rate. A stale or wrong figure keyed onto a PO will still pass a routine invoice match.

Who issues a purchase order?

Procurement or an authorized buyer within the company issues the purchase order, typically through an ERP or procurement system, before the vendor ships goods or begins billable work.

What happens if an invoice doesn't match the purchase order?

AP flags the invoice for review rather than paying it automatically. The vendor is asked to explain the difference, or the invoice is adjusted to match the PO before payment proceeds.

Is a purchase order the same as a statement of work?

No. A statement of work defines the scope, deliverables and terms of a services engagement. A purchase order authorizes the spend against that scope. Services engagements often use both together.

Can a purchase order be changed after it's issued?

Yes, through a change order or PO revision, which most procurement systems track separately so the original and revised terms remain visible.

Does three-way matching check the purchase order against the contract?

No. Three-way matching checks the invoice against the purchase order and the receipt. It confirms consistency between those three documents. It does not test whether the PO price reflects the vendor's contract or rate card.

Why would a purchase order be raised at the wrong price?

A buyer can key a price manually instead of pulling it from the vendor's current rate card, or reference an expired price file. The PO system has no built-in check against the contract terms.

What documents should a purchase order be checked against?

The vendor's rate card, the master contract, and any active rebate clause or minimum volume commitment. These sit outside the PO system and require a separate compliance check.

1. What is a purchase order?

A purchase order is a buyer-issued document that authorizes a specific purchase: item or service, quantity, unit price and delivery date. Once a vendor accepts it, it becomes a binding commercial commitment. AP later uses it as the reference point to confirm that an incoming invoice matches what was actually ordered, at the price that was actually agreed. Procurement systems generate a purchase order number automatically, and that number typically flows through to the vendor's invoice as a reference field. This lets AP pull up the original order during payment processing without contacting procurement directly. A purchase order can cover a single delivery or, in a services context, a period of billing tied to [a statement of work](/glossary/statement-of-work). Either way, it sets the boundary AP checks incoming charges against.

2. How does a purchase order differ from a contract?

A contract sets the ongoing terms: pricing structure, volume tiers, rebate clauses, surcharge rules. A purchase order is a single transaction issued under those terms. The contract governs many purchase orders over its term, so if the person raising the PO does not check it against the contract's current rate card, the PO can be internally consistent and still wrong. This distinction matters because a purchase order system checks itself, not the contract. It will confirm an invoice matches the PO. It has no built-in step that confirms the PO price matches the rate card the vendor actually agreed to. When a contract changes, a price increase, a new rebate tier, an updated surcharge schedule, someone has to update how future purchase orders are priced. If that update does not happen, every PO issued afterward carries the old, wrong number forward.

3. Why do purchase order errors cause margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A purchase order raised at an outdated or incorrect price becomes the baseline AP checks against, so the invoice can pass a routine match while still deviating from the actual contract. The error goes uncaught because the check compares two wrong numbers to each other. This is a structural gap, not a lapse by any one person. The purchase order system and the contract repository are usually separate systems, maintained by separate teams, on separate update cycles. Fixing it requires checking the purchase order itself against the contract terms, not just the invoice against the purchase order. That is a different check than the one most AP workflows run by default.

4. How does invoice matching use the purchase order?

Standard invoice matching compares the invoice to the purchase order and, often, the goods or service receipt. This confirms the vendor billed what was ordered, at the price stated on the PO. It does not independently confirm the PO price is the correct contract price; that check requires going back to the rate card or master agreement. Three-way matching, invoice, PO and receipt, catches quantity errors and unauthorized charges. It was built to stop a vendor from billing for something never ordered or never received. It was not built to test whether the PO price itself reflects [a rebate clause](/glossary/rebate-clause), a volume tier, or [an index escalation clause](/glossary/index-escalation-clause) buried in the contract. Those checks sit outside the standard match and require going back to the source document. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

Does a purchase order guarantee the price is correct?

No. A purchase order guarantees the vendor was authorized to bill that price for that quantity. It does not confirm the price matches the current contract rate. A stale or wrong figure keyed onto a PO will still pass a routine invoice match.

Who issues a purchase order?

Procurement or an authorized buyer within the company issues the purchase order, typically through an ERP or procurement system, before the vendor ships goods or begins billable work.

What happens if an invoice doesn't match the purchase order?

AP flags the invoice for review rather than paying it automatically. The vendor is asked to explain the difference, or the invoice is adjusted to match the PO before payment proceeds.

Is a purchase order the same as a statement of work?

No. A statement of work defines the scope, deliverables and terms of a services engagement. A purchase order authorizes the spend against that scope. Services engagements often use both together.

Can a purchase order be changed after it's issued?

Yes, through a change order or PO revision, which most procurement systems track separately so the original and revised terms remain visible.

Margin Drift Resources