Someone in the warehouse notices the packing tape is running low. Six weeks later, a supplier receives payment. Between those two moments sits a whole sequence of documents, approvals and checks that most employees never see. That sequence has a name: the procure-to-pay cycle, often shortened to P2P.
Understanding it matters far beyond the purchasing department. It explains why a manager cannot simply buy something and expense it, why finance keeps asking for a PO number, and where money quietly leaks out of organisations that treat the process casually.
The cycle in one view
| Step | Document produced | Question it answers |
|---|---|---|
| 1. Need identified | Purchase requisition | Do we actually need this? |
| 2. Approval | Approved requisition | Is it budgeted and authorised? |
| 3. Supplier selection | Quotes or contract | Who supplies it, at what price? |
| 4. Order placed | Purchase order (PO) | What exactly did we commit to? |
| 5. Goods received | Goods receipt note | Did it arrive, complete and undamaged? |
| 6. Invoice received | Supplier invoice | What is the supplier charging? |
| 7. Matching | Three-way match record | Do order, delivery and invoice agree? |
| 8. Payment | Payment remittance | Has the supplier been paid on terms? |
Requisition: the internal request
A purchase requisition is an internal document. It travels from the person who needs something to the people who can authorise it. Crucially, it is not an order and creates no obligation to any supplier — a distinction that trips up newcomers constantly.
A useful requisition states what is needed, how much, when, and why. The “why” matters more than people expect: it is what allows an approver to question whether a cheaper alternative or existing stock would do the job.
Approval: separating request from authority
Approval routing usually depends on value. Small amounts stop at a line manager; larger ones climb to department heads or finance. This ladder exists to enforce a principle known as segregation of duties: the person who requests a purchase should not be the same person who approves it, and neither should be the person who releases payment.
The reasoning is not that employees are assumed dishonest. It is that a single person controlling an entire money flow has no natural error-catching mechanism. Splitting the steps means mistakes and fraud both need collusion to succeed, which is far less likely.
Supplier selection
For routine items, the supplier is already fixed by a framework agreement or a preferred-vendor list, and this step is fast. For larger or unusual purchases, buyers collect quotes and compare them.
An important point often missed by beginners: the lowest quote is not automatically the right choice. Buyers weigh total cost of ownership — delivery time, payment terms, warranty, service quality, shipping, and the cost of switching if things go wrong. A supplier who is five percent cheaper but two weeks slower can be far more expensive in practice.
The purchase order
The purchase order is the first document that leaves the company. Once the supplier accepts it, it typically becomes a binding commercial agreement. That is why POs are far more formal than requisitions and why unauthorised purchasing — buying first, paperwork later — creates real legal and accounting problems.
A complete PO specifies:
- Item description, quantity and unit price
- Delivery address and required date
- Payment terms, such as net 30
- A unique PO number used to link every later document
That PO number is the thread that ties the whole cycle together. Without it, matching becomes guesswork.
Receiving the goods
When the delivery arrives, the receiving team checks it against the PO and records a goods receipt note. They verify quantity, condition and specification. Partial deliveries, damaged items and substitutions are recorded here rather than argued about later.
This is one of the least glamorous steps and one of the most valuable. A receipt note created carelessly — signing for boxes without counting them — undermines every control that follows.
The three-way match
This is the heart of the control system. Before payment is released, accounts payable compares three documents:
- The purchase order — what was ordered.
- The goods receipt — what actually arrived.
- The supplier invoice — what is being charged.
If all three agree, payment proceeds. If they disagree, the invoice is held and investigated. The mismatches this catches are ordinary and frequent: an invoice for twelve units when ten arrived, a price that does not match the agreed rate, a delivery charge nobody authorised, or a duplicate invoice submitted by accident.
Some organisations use a two-way match for services, where there is no physical delivery to receive, and instead rely on a confirmation that the work was completed.
Payment
Approved invoices are scheduled according to their payment terms. Finance balances two competing pressures here: holding cash longer improves working capital, but paying late damages supplier relationships and can forfeit early-payment discounts.
The record is then closed, and the transaction feeds into accounting, budget reporting and supplier performance data.
Where the process commonly breaks
- Maverick spending. Employees buying outside the process, then submitting invoices after the fact. It destroys price negotiation leverage and hides real spend.
- PO created after the invoice. A retroactive PO is paperwork theatre — it matches by definition and controls nothing.
- Approval bottlenecks. When one overloaded manager approves everything, they rubber-stamp rather than review.
- Poor master data. Duplicate supplier records and inconsistent item descriptions make matching fail and enable duplicate payments.
- No exception handling. Every process needs a documented path for urgent purchases; if none exists, people invent their own workaround permanently.
Why the bureaucracy is worth it
To someone waiting for a laptop, P2P looks like obstruction. But the process delivers things that matter at scale: an audit trail for every pound spent, protection against paying for goods never received, negotiating power from consolidated volume, and reliable forecasting of committed spend.
The design challenge is proportionality. Applying a full approval chain to a box of pens wastes more in staff time than the pens cost. Mature organisations set value thresholds and use simplified routes such as purchasing cards for low-value items, reserving the full cycle for spend where the controls actually pay for themselves.
Conclusion
The procure-to-pay cycle is a chain of questions, each one asked by a different person: do we need it, can we afford it, who supplies it, did it arrive, and does the bill match reality? Once you can see the logic behind each step, the paperwork stops looking arbitrary.
If you would like to go deeper into purchasing, supply chain and financial controls, the free courses on procurement, logistics and accounting available on Cursa cover these processes in more practical detail.
