Procure-to-Pay: how it works and what to require
Proconomy Procure-to-Pay (P2P) makes the compliant buying route the easiest one, moves policy-ready requisitions through approval and writes approved purchase outcomes back to your ERP. Receipt and invoice exceptions are routed with the context needed to resolve them, rather than starting another email chain between procurement, the plant and accounts payable.
The compliant route has to be the fast route. Or people go around it.
Twenty-four purchasing situations, including the four that create most of your leakage.
Guided buying
- Catalogue purchases against a negotiated price
- Contracted supplier orders outside a catalogue
- Punch-out to a supplier site with controls intact
- Repeat orders from a previous purchase
- Blanket orders and call-offs against a framework
- Low-value purchases with a light approval path
Order to receipt
- Purchase order creation in the ERP with approved values
- Order acknowledgement and promised date capture
- Delivery schedule changes raised by a supplier
- Goods receipt against a partial delivery
- Service entry confirmation
- Returns and rejected receipts
Invoice and match
- Three-way match against order and receipt
- Price and quantity variance inside tolerance
- Variance outside tolerance routed to a person
- Invoices with no matching order
- Credit notes and corrections
- Supplier queries on payment status
Exceptions
- Emergency purchase outside the approved route
- Order against an expired agreement
- Purchase from an unapproved supplier
- Value exceeding delegated authority mid-process
- Duplicate order detection across plants
- Retrospective purchase order requests
From approved outcome. To matched invoice.
Ten mechanisms, and the ERP stays the system of record throughout.
| Mechanism | What it has to do |
|---|---|
| Guided buying | Catalogue items, contracted suppliers and preferred agreements presented ahead of open buying, so the compliant route is also the quickest one. |
| Requisitions that arrive complete | Contracted price, cost centre, delivery point, tax treatment and account assignment applied before the requisition reaches an approver. |
| Delegation of authority | Approval by value, cost centre and entity, with reminders, escalation and delegation during absence. |
| ERP write-back | The approved outcome becomes a requisition or purchase order in your ERP with the approved values, monitored for success and failure rather than assumed. |
| Order acknowledgement and schedule | Supplier acknowledgement, promised dates and schedule changes captured against the order rather than in email. |
| Receipt and service confirmation | Goods receipt and service entry against the order, including partial deliveries and rejections. |
| Three-way match with tolerance | Order, receipt and invoice matched automatically inside your tolerance, with variance outside it routed to a named person with the discrepancy shown. |
| Requester-visible status | Order status, expected delivery and open exceptions visible to the requester and the plant, which removes most status enquiries. |
| Duplicate and consolidation detection | Similar orders across plants inside a window surfaced before they are separately committed. |
| Complete purchase history | The requisition, the rule that routed it, the approvals, the order, the receipt, the match result and any exception, per transaction. |
A description of what the practice requires, not a feature list.
One purchasing engine. Different approval reality.
What guided buying has to enforce, by industry.
Automotive
Schedule-driven call-offs against framework agreements, with acknowledgement and promised dates visible against programme need.
Industrial equipment
Project purchasing and plant MRO running side by side under different approval paths without two systems.
Medical devices
Purchases restricted to suppliers approved for the specific device family, enforced at order rather than checked afterwards.
Building materials
Delivered-cost purchasing across plants, with local buying against a group agreement rather than around it.
Five questions. Starting with a deliberate write-back failure.
Silent failure is the defect that costs most and surfaces latest.
- Ask what happens when the ERP write-back fails. Silent failure is the defect that costs most and shows up latest.
- Create an order against a contracted supplier and confirm the negotiated price applies without the buyer knowing it exists.
- Show an invoice variance outside tolerance being routed, and what the approver sees.
- Ask how an emergency purchase outside the approved route is handled — blocked, or governed with a retained justification?
- Confirm the ERP remains the system of record and ask exactly which objects are written.
Definitions. Asked and answered.
No. Your ERP remains the system of record for the transaction. Proconomy governs the work around it — the buying route, the completeness of the requisition, the approval path and the exception handling — and writes the approved outcome back.
The failure is surfaced rather than silently retried into inconsistency. Write-back success and errors are monitored, and the affected purchase is visible to the people who can resolve it.
Yes, within the authority you grant. Entity and plant rules define thresholds, approvers, catalogue scope and permitted local suppliers, while group policy defines what must stay common.
Tolerance rules decide what counts as an exception. Mismatches route to the accountable owner with the order, receipt, contract and prior correspondence attached, so the resolution does not begin with an investigation.
Proconomy governs procurement execution through to the approved outcome, then writes it back to your systems of record. Payment execution stays with finance, where it belongs — the three-way match, the approval and the audit trail arrive there complete rather than being rebuilt.
Order status, expected delivery and open exceptions are visible to requesters and plant teams according to their role and entity, which removes most of the status enquiries procurement currently answers.
Procure-to-pay covers the operational span from an approved need through requisition, purchase order, receipt, invoice matching and payment. It is the transactional half of source-to-pay, and it is where most procurement administration effort sits.
Three-way matching compares the purchase order, the goods receipt and the supplier invoice before payment is approved. Where all three agree within tolerance, the invoice can be processed automatically. Where they do not, the discrepancy is routed to a person, which is the control that prevents paying for what was not received.
Guided buying presents the requester with the compliant purchasing route first — catalogue items, contracted suppliers and negotiated agreements — before open buying is offered. It reduces off-contract spend by making the correct route the easiest one rather than by policing the incorrect one.
Maverick spend is purchasing that bypasses agreed processes, suppliers or contracts. It usually reflects a process that is slower than the alternative rather than deliberate non-compliance, which is why it responds better to guided buying than to enforcement.
No. The ERP remains the system of record for the transaction. Proconomy governs the work that produces the approved outcome and writes that outcome back, with write-back success and failure both monitored.