Procure-to-pay (P2P) process flow template

What the procure-to-pay (p2p) process flow process is

P2P is the process that most often gets documented twice and never in one place. Procurement has one version in their procedure, finance has another in the accounts payable guide, and the ERP system has a third in its configuration. When the external auditor asks to walk the cycle, the question isn't whether a description exists: it's which one is authoritative.

The version that holds up is drawn around the control points: approving the requisition against a threshold, issuing the purchase order, receiving the goods, three-way matching order against receipt against invoice, and finally releasing payment with segregation of duties. Each of those points is a control the auditor tests, and each has a source system that constitutes the evidence.

The exceptions matter as much as the main path. Invoices with no order, price variances within tolerance, partial deliveries and rush purchases are where both the money and the mistakes concentrate. A diagram that shows only the clean path from requisition to payment documents the less interesting half of the process.

What this flowchart covers

In this template

• Need and requisition: who may requisition, what budget and cost center must be entered, and how the requisition is logged in the ERP system
• Threshold-based approval, with a branch for purchases that require additional sign-off from finance or an executive
• Purchase order and vendor selection, including a check on whether the vendor is approved and correctly set up in vendor master data
• Goods receipt and invoice receipt as two separate records that together form the basis for matching
• Three-way match between order, receipt and invoice, with explicit branches for a price variance within tolerance, a missing goods receipt, and an invoice with no order
• Payment release with segregation of duties between the person who approves the invoice and the person who releases payment, followed by posting and reconciliation

When to use this template

• The external auditor is walking the P2P cycle as part of ICFR testing, and you need one controlled description instead of three
• You're implementing or upgrading an ERP system and need to describe the to-be process before configuration locks it in
• Invoices get paid outside the process, and you need to see where the exception paths bypass the controls
• Approval thresholds and the sign-off hierarchy have changed and the documentation hasn't kept up
• You're training new accounts payable staff and need a diagram that shows both the main path and the exceptions

Controls documented

• ICFR: P2P cycle controls

How it works

1. Document each P2P step in a spreadsheet

   List every step from purchase requisition through invoice payment, with columns for owner, system of record, and approval gate.

2. Import the spreadsheet into QueryChart

   Paste or upload the spreadsheet; QueryChart maps rows to swimlanes by owner and to steps by order.

3. Draw the exception paths before you share the diagram

   An invoice with no order, a price variance over tolerance and a rush purchase each need their own branch with a named approver.

4. Add approval gates and route to approvers

   Mark approval-required steps; QueryChart enforces the approval workflow.

5. Publish the version as audit-ready

   Once approved, the process map is checkpointed with a version number, timestamp, and approver signature for audit evidence.

Frequently asked questions

What goes into a P2P process flow?

A complete procure-to-pay process flow covers requisition, approval, purchase order, goods receipt, invoice match, exception handling, approval, and payment — each assigned to an owner and a system of record.

How do I document P2P for SOX or SOC 2?

Document each control point as a step with an owner, evidence link, and approval gate. QueryChart's audit trail captures who approved which version, when, and what changed.

What's the difference between P2P and O2C?

P2P covers cash flowing out: requisition, order, receipt, invoice, payment. O2C covers cash flowing in: order, delivery, invoicing, collection.

What is a three-way match, and why does the auditor ask about it?

It confirms the purchase order, goods receipt, and invoice agree on vendor, quantity, and price before payment is approved.