Process family
Procure-to-pay process: six templates from requisition to supplier payment
The procure-to-pay chain as six linked flowcharts: purchase requisition, purchase order, goods receipt, three-way matching, invoice approval and payment approval, with the P2P overviews, vendor onboarding and procurement alongside.
Procure-to-pay is the operational cycle that runs from an identified need to a paid supplier. This family orders six templates in the sequence the documents hand off: a requisition becomes a purchase order, the order is matched against a receipt and an invoice, and the approved invoice is released for payment. The end-to-end P2P overviews, vendor onboarding and the procurement process sit alongside the chain.
The chain starts with a coded, budget-checked requisition and ends with a dual-released bank payment. A requisition approved by value becomes a purchase order once procurement has reviewed it; the supplier delivers against that order, and the goods-in dock records what arrived through goods receipt. The invoice is then compared with the order and the receipt in three-way matching, coded and approved by value in the invoice approval step, and released in a payment run under the payment approval control. Each template picks up the document the previous one produced: PO number, GRN, matched invoice, payment proposal.
P2P fails in the gaps between documents: an order raised after the goods arrived; a receipt never posted, so the invoice is blocked; an invoice paid twice after arriving by two channels; a payment to unverified bank details. Requisition and purchase order put the budget and authority gates before the commitment; three-way matching holds an out-of-tolerance variance until it is owned; invoice approval carries the duplicate check and supplier query loop; payment approval keeps the proposal's preparer off the dual bank release. The run itself, from due dates to remittance advice, is drawn inside the full AP cycle; payment approval is its release gate.
Two overviews draw the whole cycle: the procure-to-pay flowchart and the ERP P2P flow written for SOX and SOC 2 walkthroughs. Alongside them, the full AP cycle carries the payment run and period-end accruals, vendor onboarding supplies the supplier master record and callback-verified bank details, and the procurement process starts from the same need but turns into the market: sourcing, tender, award, contract. Invoice-side controls continue in accounts payable; whether a purchase happens at all is decided under spend governance; goods receipt at a warehouse dock, with ASN and WMS, is drawn in depth under warehouse inbound.
The sequence
Step 1: Purchase requisition process flowchart
Purchase requisition process flowchart: specification and GL coding, budget check, manager and threshold approval, procurement review and an urgent fast track.
Step 2: Purchase order process flowchart
Purchase order process flowchart: requisition, budget check, approval thresholds, supplier quotes, PO issue, goods receipt, three-way match and payment.
Step 3: Goods receiving process flowchart (goods-in to GRN)
A goods receiving process flowchart for the goods-in dock: booking-in, PO paperwork check, count and damage check, carrier claim, GRN and put-away to stock.
Step 4: Three-way matching process flowchart
Three-way matching process flowchart for comparing a supplier invoice, purchase order and goods or service receipt, with tolerance controls and discrepancy handling.
Step 5: Invoice approval process flowchart
A swimlane invoice approval process template: capture, duplicate check, three-way PO match, coding, approval by value, supplier queries, posting and payment.
Step 6: Payment approval process flowchart
Payment approval process flowchart for payment-proposal preparation, supplier-bank verification, delegated approval, dual bank release, posting and reconciliation.
Also part of this family
- Procure-to-pay (P2P) process flowchart (need to payment) — Procure-to-pay process flowchart from an identified need to a paid supplier: requisition, budget and delegated-authority approval, contract check, PO issue, receipt, three-way match, no-PO exceptions and the payment run.
- Procure-to-pay (P2P) process flow template — An audit-ready procure-to-pay (P2P) process flow template (requisition through payment) with approval workflow and version control. Built for ERP teams documenting AP processes for SOX, SOC 2, and internal audit.
- Accounts payable process flowchart (full AP cycle) — Accounts payable process flowchart for the whole AP cycle: invoice intake, supplier master data, duplicate and PO checks, payment runs and month-end accruals.
- Vendor onboarding process flowchart — Vendor onboarding process flowchart with swimlanes for requester, procurement, legal, finance and security, from vendor request to approved register entry.
- Procurement process flowchart — End-to-end procurement process flowchart: need and specification, make or buy, budget approval, tender or call-off, award, contract, delivery and review.
Used in these industries
Related guides
- How to standardize a business process — How to standardize a business process across teams or sites: map the variants, separate real differences from habit, agree one flow with defined exceptions, and control the version.
- How to map a business process — How to map a business process end to end: agree the boundaries, interview the people who run it, map the as-is including exceptions, then validate it. With a live procure-to-pay example.
- How to create a purchase order process — How to design a purchase order process: separate requisition from order, put the budget check before the commitment, set thresholds from your delegation of authority, and define match tolerances.
- How to create a process flowchart — How to create a process flowchart: fix the trigger and the end state, write one action per box, turn every 'if' into a labelled decision, and close every branch. With a worked example you can step through.
- How to create an invoice approval workflow — How to build an invoice approval workflow around the three-way match: the ways three documents disagree, the different row each correction re-enters at, and lanes that keep duties apart.
- How to create a process flow diagram — A process flow diagram is three artefacts under one name. How to choose the level from what the diagram will be used for, hold that level across every box, and break a sub-process out instead of inflating one.