1.5 · Order, receipt, invoicing: the P2P cycle

Level 1 · Purchasing Process

1.5Order, receipt, invoicing: the P2P cycle

Goal: Execute a locked P2P cycle: no purchase without PO, no receipt without control, no payment without three-way matching.
Estimated time: 12 min · self-paced reading · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • Locked P2P: validated requisition, written PO, confirmation, controlled receipt, matching, payment.
  • Three-way before paying: invoice = PO = receipt, otherwise block.
  • Immediate written reservations: precise and photographed, otherwise recourse lost.

Running mini-case — Nadia and the invoice that does not pass

Nadia receives a packaging invoice 15% above the PO: list price instead of negotiated price, plus two cartons missing on the GRN. Thanks to receipt tick-off and three-way matching, she blocks, gets a credit note and pays on due date. Without a written PO or control, the gap would have gone unnoticed.

Final episode of cases 1.1-1.4 — Nadia locks the cycle through to payment.

1. The Procure-to-Pay cycle

The P2P (Procure-to-Pay) links: validated internal purchase requisition (PR) (budget control), purchase order (PO) sent to supplier (references, quantities, prices, lead time, place), confirmation from supplier (validates price and lead time — demand it, without it the order commits no one), then receipt.

On receipt, check: count quantities against GRN, apparent condition, conformity. Record receipt: this too-often botched gesture is legally and financially decisive for recourse.

Then comes invoicing and payment at agreed due date — neither before (cash) nor after (relationship, penalties). ERPs automate this flow, but logic remains identical from notebook to integrated system.

2. Three-way matching

Before paying, check that invoice matches purchase order (what was ordered at agreed prices) and goods receipt / GRN (what was actually received). That's three-way matching.

If all three agree, pay; otherwise block and handle gap (missing quantity, different price, unordered goods). It's the main protection against invoicing errors, duplicate invoices and fraud.

Control only works if upstream was done: no written PO or no receipt control, and matching becomes impossible — you then pay blindly.

3. Reservations and golden rules

Reservations on delivery must be immediate, precise and written on carrier's note: "2 cartons missing of 10", "carton #3 crushed" — never "subject to unpacking", worthless. After signing without reservation, it's often too late, especially vis-à-vis carrier.

Three golden rules: no purchase without PO (even simple), no receipt without control, no payment without matching. Held, P2P protects cash and provides clean, exploitable purchasing data.

Complete with anti-fraud hygiene: any bank details change is verified via independent channel (call known number), never by replying to the message announcing it.

Common misinterpretation: “Matching is paperwork for suspicious people.” No: it mostly intercepts involuntary errors (list price, quantity, forgotten discount) — trust without control means paying blind.
The locked P2P cycle Each step feeds the next control: the chain of evidence Purchase requisition ValidationPurchase order +confirmationReceipt Control +reservationsInvoice 3-way match→ payment
Each step feeds the next control: the chain of evidence
Text version of the diagram (SEO / screen readers / translation): 1) Order: validated requisition, written PO, supplier confirmation. 2) Receipt: check against GRN, immediate written reservations. 3) Invoice: three-way matching then payment on due date. Lesson: each step feeds the next control.

The lighter side — paperwork that pays

undefined
undefined
undefined
undefined
undefined
undefined

Moral: three-way, zero blind trust — and one photo beats a thousand subject-tos.

🔎 Concrete example — The invoice that doesn't pass

An invoice arrives at €1,150 for a €1,000 order. Matching reveals: price non-conforming to PO (list price instead of negotiated) and 2 units missing on GRN. Invoice is blocked, supplier corrects and issues credit.

Reading: without PO and without counting, gap would have gone unnoticed and been paid.

Lesson: P2P first intercepts involuntary errors, far more frequent than fraud.

Section vocabulary

P2P (Procure-to-Pay)
Full process purchase → payment: requisition → PO → confirmation → controlled receipt → invoice → matching → payment.

Simple example: Nadia's requisition-PO-GRN-invoice chain is archived complete.

What it is not: ordering by phone with no trail then paying on invoice alone.

Reflex: every purchase follows the chain, on paper as in ERP.

Purchase requisition (PR)
Validated internal request before commitment: budget control point.

Simple example: production validates its packaging requisition before Nadia orders.

What it is not: committing spend then regularising afterwards.

Reflex: no PO without validated requisition.

Order confirmation
Supplier's acknowledgement validating references, price and lead time; without it, order commits no one on lead time.

Simple example: Nadia chases until price and lead time are confirmed in writing.

What it is not: treating the sent PO as a supplier commitment.

Reflex: demand confirmation, otherwise the order commits no one.

Three-way matching
Check before payment: invoice = PO (ordered, agreed prices) = receipt (received); protection against errors and fraud.

Simple example: the invoice 15% above PO is blocked before payment.

What it is not: paying on invoice alone without comparing.

Reflex: no payment without triple agreement.

Reservations on delivery
Immediate precise written mentions of anomalies on receipt; condition recourse, especially against carrier.

Simple example: 2 cartons missing of 10, carton #3 crushed — photos attached, in the driver's presence.

What it is not: signing quickly with a vague “subject to unpacking”.

Reflex: immediate, precise, written and photographed reservations.

In practice — Lock your order → receipt → payment cycle

  1. Ensure every purchase has a written PO (references, quantities, prices, lead time) and demand supplier confirmation.
  2. On each delivery, physically count against GRN; note reservations immediately and in writing if anomaly.
  3. Before each payment, do three-way matching: does invoice match ordered (PO) and received (GRN)? Block any gap.
  4. Pay at agreed due date and archive complete chain PR → PO → GRN → invoice.
Your P2P cycle is locked: no purchase without PO, no receipt without control, no payment without matching.

Ready-to-say script — log reservations in front of the driver (30 s)

“I tick off before signing: two cartons missing of ten and number three crushed — I note it precisely here with photos, in your presence. Nothing against you: without immediate written reservations, no recourse is possible.”

Say calmly at each doubtful delivery; timestamped photos and written notice to the supplier the same day.

Copy-paste template — receipt control + 3-way

PO No.: _______________ | GRN No.: _______________ | INVOICE No.: _______________
TICK-OFF (quantities / condition / conformity): _______________
WRITTEN RESERVATIONS (precise + photos): _______________
3-WAY (invoice = PO = received? yes/no, gap): _______________
DECISION (pay / block + reason + credit requested): _______________

Small business / tight budget

Notebook or spreadsheet: one simple PO per purchase, pen tick-off, payment after verification.

Algeria SME

On imports: check when stripping the container, photos of seal and cartons, reservations on the forwarder's note.

Bank details and fraud

Every bank-details change checked by calling the known number — never by replying to the announcing message.

Separation of duties

As soon as possible: whoever orders is not whoever receives nor whoever pays.

✓ Best practices

  • Photograph anomalies on receipt with timestamp: a photo beats a long description.
  • Notify supplier in writing same day if gap: claim deadlines run fast.
  • Separate roles (order, receipt, payment) as soon as possible: separation prevents internal fraud.

✗ Common pitfalls

  • Signing carrier's note without checking: a delivery signed without reservation is presumed conforming.
  • Paying on invoice alone without matching: you pay errors, duplicates and gaps unknowingly.
  • Using vague "subject to" mention: generally without legal value, prefer precise description.

Key takeaways

  • P2P cycle: PR → PO → confirmation → controlled receipt → invoice → matching → payment.
  • Three-way matching before any payment: main protection against errors and fraud.
  • Immediate, precise written reservations: afterwards, often too late.
  • Three golden rules: no purchase without PO, no receipt without control, no payment without matching.

48h Challenge — apply tomorrow

Lock 1 upcoming delivery: demand supplier confirmation, tick off against the GRN with photos, then match before paying. Archive the requisition, PO, GRN, invoice chain.

Section exit checklist
  • I can name the three golden rules of P2P.
  • I can write a precise, valid reservation.
  • I have done a three-way match before payment.
Self-rating 1-5: no payment without matching?Self-rating 1-5: are my receipts controlled and logged?

Frequently asked questions

Isn't matching useless paperwork when you trust?

No: trust without control is exposure. Matching intercepts mainly involuntary errors (list instead of negotiated price, different invoiced quantity, forgotten discount) that otherwise go unnoticed. Companies systematising it discover gaps representing a significant percentage of purchases.

What if delivery doesn't match?

Check before signing carrier's note, make precise written reservations, photograph, then notify supplier in writing same day asking for solution (replacement, complement, credit) with deadline. On unpacking, check contents against GRN and PO and alert immediately if gap.

Check your understanding

What must be demanded after sending the purchase order?

Additional resources (optional, to go further)

Level 1 examFresh, harder questions to test what you've learned