Procure to Pay

Procure to pay (P2P) is the complete process that starts when a business decides to purchase something and ends when the supplier is paid. It covers purchasing, receiving, invoice processing, and payment in a single end-to-end workflow. The name emphasises that these stages are connected: decisions made early in the process, like whether to raise a purchase order and what price to agree, determine how smoothly the later stages of invoice matching and payment can proceed.

P2P is a useful frame for AP improvement because it reveals where breakdowns occur. Most AP problems do not originate in the AP team; they originate upstream, in purchasing decisions made without adequate documentation, in deliveries received without a goods receipt note, or in verbal agreements that were never formalised into a purchase order. A P2P perspective asks not just how invoices are processed but how the conditions for clean invoice processing are created earlier in the chain.

The stages of the procure-to-pay cycle

The P2P cycle begins with the purchase requisition: an internal request to buy something, which triggers the approval process for the commitment before a supplier is engaged. Once approved, the purchase order is raised and sent to the supplier, formally authorising the purchase at agreed terms. When the supplier delivers, a goods receipt note is created, confirming what was received. The supplier's invoice arrives and is matched against the PO and GRN. The matched invoice is approved and posted to the accounting system. Payment is released within the agreed terms.

In a well-functioning P2P process, each stage feeds cleanly into the next. The PO contains the information needed for the invoice match. The GRN provides the delivery confirmation needed for three-way matching. The matched invoice has the account codes and cost centre references needed for posting. The payment is made with the remittance advice needed for the supplier to reconcile their receivables.

Where P2P breaks down in Australian businesses

The most common P2P failure point for Australian small and medium businesses is the absence of purchase orders. When employees place orders verbally or by email without raising a formal PO, the invoice that arrives later has no reference document to match against. The AP team must either chase down confirmation that the goods were ordered, ask the approver to verify from memory, or process the invoice on trust. Each of these is slower and less reliable than a PO match.

The second most common failure point is the absence of goods receipt documentation. When deliveries are not formally recorded, three-way matching is impossible and the AP team cannot verify that goods invoiced were actually received. In industries like construction and wholesale, where short deliveries are common and supplier invoicing errors are frequent, the absence of receiving records leads to overpayments that are difficult to recover.

P2P and AP automation

AP automation addresses the latter stages of the P2P cycle: invoice capture, coding, validation, approval, and payment. For the automation to work effectively, the earlier stages need to be in reasonable order. A business where purchase orders are routinely raised and where goods receipts are recorded can achieve high straight-through processing rates because the matching and validation steps have reference data to work with. A business where these upstream stages are informal will find that AP automation surfaces and amplifies the existing process gaps rather than hiding them.