Procure-to-Pay Cycle

The procure-to-pay (P2P) cycle is the end-to-end business process from the identification of a need for goods or services through to payment of the supplier invoice. It encompasses procurement and accounts payable as connected stages of the same process, rather than treating them as separate departmental functions. Understanding the full P2P cycle is important because failures at any stage -- poorly defined purchase requisitions, inadequate purchase orders, missing goods receipts, or slow AP processing -- create problems that manifest as cost, delay, or risk at later stages.

The stages of the P2P cycle are: (1) Needs identification -- a department identifies a requirement for goods or services; (2) Purchase requisition -- the need is formally requested through an internal approval process; (3) Purchase order -- an approved requisition generates a PO that is sent to the supplier; (4) Goods or service delivery -- the supplier delivers, and the receiving party confirms through a goods receipt or service acceptance; (5) Invoice receipt -- the supplier's invoice arrives in the AP system; (6) Invoice matching -- the invoice is matched against the PO and goods receipt; (7) Approval -- the matched invoice is approved for payment; (8) Payment -- funds are transferred to the supplier.

Where P2P failures occur

The most common P2P failure is the missing purchase order: goods or services are ordered verbally or informally, delivery occurs and is accepted, and the invoice arrives without a PO reference. This produces an AP exception that requires retroactive PO creation or manual approval -- both of which add processing time and cost, and remove the pre-commitment control that the PO was designed to provide. The fix is a culture and process change that requires operational managers to raise POs before authorising purchases, supported by a PO approval process fast enough that pre-ordering does not cause operational delays.

The second common failure is the missing goods receipt. In a three-way match environment, the goods receipt is the confirmation that delivery has occurred. Without it, the invoice has no delivery confirmation to match against. Missing GRNs occur when the receiving process is informal (verbal confirmation from the site that goods arrived), when goods receipts are recorded on paper and not entered in the system, or when the person who received the goods is not aware of the need to create a system record. Building GRN recording into the operational workflow -- as a required step before work continues -- is the process fix, supported by system controls that prevent invoice payment without a corresponding GRN.