Procure-to-pay, usually shortened to P2P, is the process that runs from deciding to buy something through to paying the supplier for it. It covers the requisition, the purchase order, receiving, invoice processing, and payment. Sourcing and contracting sit upstream of it, inside the broader source-to-pay process.
Most companies treat P2P as an ordering workflow. The money says otherwise: the expensive part is the last mile, where invoices meet the records the earlier steps left behind.
Five steps, and each one leaves a document
A requisition records the need. The purchase order records the agreement. The goods receipt records the delivery. The invoice records the supplier's claim, and the payment closes it out. Each step exists to leave evidence, and that evidence is exactly what three-way matching later compares. A sloppy document at any step becomes a stopped invoice three steps later. The end-to-end walkthrough covers each handoff.
The last mile carries most of the cost
Ordering is fast and receiving is routine. The labor concentrates where invoices fail their checks and become exceptions, because every failed check needs investigation, and investigation needs people. A P2P transformation that ignores exception resolution optimizes the cheap steps and leaves the expensive one untouched.
P2P spans more systems than any one team owns
The requisition may live in a P2P suite, the order and payment in the ERP, receiving in a warehouse system, and the supplier conversation in email. The process works only when those records agree, and nobody owns all of them. That spread is why P2P bottlenecks form at handoffs, and why fixing them from inside any single system keeps failing.
Measure P2P by touchless flow, and treat exceptions as the leak
The health metric that matters is the share of transactions that run end to end with no one touching them, covered in touchless invoice processing. Everything a person has to touch is either a judgment call or a leak. Best practice today is to expect the leaks to resolve autonomously, end to end, and to reserve people for the judgment.
Fragment automates the exception-heavy last mile of P2P on top of the systems you already run. See how it works or request a demo.