Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 36 ยท Business Processes

Procure to Pay (P2P)

Learn the procure-to-pay process step by step: requisition, purchase order, goods receipt, invoice verification, three-way match and payment, with a runnable matching example.

If order to cash is how a company earns money, procure to pay (P2P) is how it spends it. P2P begins when someone in the company needs something and ends when the supplier is paid. It covers purchasing, receiving, accounts payable and treasury. Done well, it ensures the company buys what it needs at the agreed price, pays only for what arrived and pays on time, neither too early (cash tied up) nor too late (angry suppliers, lost discounts).

This lesson explains each step, the documents, the controls and the classic three-way match.

The steps

flowchart LR
  A["Requisition"] --> B["Approval"]
  B --> C["Purchase order"]
  C --> D["Goods receipt"]
  D --> E["Supplier invoice"]
  E --> F["Three-way match"]
  F --> G["Payment"]

From need to payment.

  1. Purchase requisition. An employee asks for goods or services. It is a request, not a commitment.
  2. Approval. Based on amount, cost centre and category; larger spend needs higher approval.
  3. Purchase order (PO). A legally meaningful order sent to a chosen vendor at agreed prices and terms. Often created from a quotation or a framework contract.
  4. Goods receipt (GR). The warehouse confirms what actually arrived, which updates stock and creates an accrual in the ledger.
  5. Invoice receipt. The vendor's invoice is entered (manually, scanned or received electronically).
  6. Invoice verification / matching. The invoice is checked against the PO and the goods receipt.
  7. Payment. On the due date according to payment terms (for example "net 30" or "2/10 net 30").

Accounting entries

Step Debit Credit
Goods receipt Inventory Goods received / invoice received (accrual)
Invoice verified Goods received / invoice received Accounts payable
Payment Accounts payable Bank

The accrual account is cleared when the invoice arrives. If the invoice never arrives, the balance shows that goods are owed for.

The three-way match

The central control in P2P is comparing three documents:

  • the purchase order (what we ordered and at what price),
  • the goods receipt (what we received),
  • the invoice (what the vendor charges).

If quantity and price agree within tolerance, the invoice is approved. If not, it is blocked for review. This prevents paying for goods that never came or for prices that were not agreed.

Python Three-way match

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The first result blocks the invoice because we were billed for 100 but received 96. After the missing goods arrive, the same invoice matches.

Payment terms and early-payment discounts

Terms like 2/10 net 30 mean a 2% discount if paid within 10 days, otherwise the full amount is due in 30 days. Taking the discount is equivalent to earning a high annual return on cash.

Python Value of an early-payment discount

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

About 37%: paying 20 days earlier for a 2% discount is usually worth it if you have the cash.

Controls and common problems

  • Segregation of duties: the person who raises a PO should not approve the invoice or release the payment (see key terms).
  • Vendor master data control: fake or changed bank details are a common fraud route, so changes need verification.
  • Maverick spend: buying outside the process. Fixed with easy catalogues and clear policy.
  • Duplicate invoices: the same invoice entered twice. Systems check vendor + invoice number + amount.
  • Non-PO invoices: utilities, rent and similar items are often paid without a PO, so they need their own approval route.
Python Duplicate invoice detection

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Metrics

Useful P2P measures include cycle time (requisition to payment), the percentage of spend under contract, the first-pass invoice match rate (invoices that needed no manual work), days payable outstanding and cost per invoice processed.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. Which three documents are compared in a three-way match?

    The three-way match compares what was ordered, what was received and what was billed.
  2. 2. What does a goods receipt typically do in the ERP?

    Receiving goods increases inventory and books an accrual until the invoice arrives.
  3. 3. Terms '2/10 net 30' mean

    It is a 2 percent early-payment discount for paying within 10 days, with full payment due at 30 days.
  4. 4. What is maverick spend?

    Maverick spend bypasses contracts and approvals, reducing control and bargaining power.
  5. 5. Why are changes to vendor bank details tightly controlled?

    Fraudsters try to redirect payments by changing bank accounts, so changes need verification.

Summary

  • P2P runs from requisition and approval to PO, goods receipt, invoice matching and payment.
  • The three-way match is the main control against paying wrongly.
  • Payment terms and discounts affect cash and cost.
  • Segregation of duties, vendor master control and duplicate checks reduce fraud and error.

Next: Record to Report