Procure-to-Pay is the operational procurement strand from purchase requisition to supplier payment — extended by requisition policy, supplier pre-qualification, three-way match and maverick-buying control. Contrary to common term-mixing, Procure-to-Pay is neither a synonym for Purchase-to-Pay nor identical to Source-to-Pay: it is the compliance layer between them. From over 1,200 Dreher engagements we have learned this distinction separates a clean requirements specification from master-data chaos. We recommend setting up Procure-to-Pay in six phases with a named owner — before the tool discussion begins.
What is Procure-to-Pay? Definition and distinction from Source-to-Pay and Purchase-to-Pay
Procure-to-Pay is the operational procurement process from requisition policy to supplier payment — including supplier pre-qualification, compliance check, three-way match and maverick control. Source-to-Pay is the strategic super-process including sourcing. Purchase-to-Pay is the bare transaction from requisition. Mixing the three layers scopes tool projects incorrectly.
Procure-to-Pay covers all operational activities from a policy-compliant requisition through compliance check, purchase order, goods receipt and three-way match to supplier payment. Methodologically, the APQC Process Classification Framework separates, in its procurement section, "Develop sourcing strategies" (4.2, Source-to-Pay precursor), "Order materials and services" (4.3, Purchase-to-Pay core) and "Manage suppliers" (4.4, the compliance layer). Procure-to-Pay binds 4.3 with 4.4 — the layer that disappears in the top-10 consensus.
The CIPS Procurement and Supply Cycle maps the same flow across thirteen stages: the operational procurement stages correspond to the Procure-to-Pay strand, the upstream market-analysis and sourcing stages belong to Source-to-Pay, and the narrow Purchase-to-Pay begins with the requisition.
Three terms managing directors should keep separate:
- Source-to-Pay (S2P) — the strategic super-process including market analysis, sourcing strategy, supplier selection and contract negotiation, covered in our source-to-pay wiki entry.
- Procure-to-Pay (P2P-Procure) — the operational strand with requisition policy, supplier compliance, three-way match and maverick control, six to eight phases.
- Purchase-to-Pay (P2P-Purchase) — the bare transactional subset from requisition onwards, four to seven phases, covered in our purchase-to-pay wiki entry.
In Porter's value chain (Porter, Competitive Advantage, 1985) Procure-to-Pay interlocks the procurement support activity with Inbound Logistics — the strand where vertical line organisations most often break.
Why Procure-to-Pay matters in the DACH Mittelstand in 2026
The German e-invoicing mandate 2025/2027/2028, S/4HANA modernisation plans and rising maverick-buying ratios increase the pressure on a continuous Procure-to-Pay strand. Anyone still running requisition policy, supplier compliance and three-way match in isolation in 2026 loses control of indirect spend.
First — the e-invoicing mandate tightens the invoice phase. The BMF e-invoicing FAQ and the BMF letter of 15 October 2025 fix the stages: receive mandate since 1 January 2025, send mandate from 1 January 2027 for firms above 800,000 EUR prior-year revenue, full mandate from 1 January 2028. Permitted EN 16931 formats are XRechnung and ZUGFeRD from version 2.0.1.
Second — format adoption still has room. The Bitkom e-invoicing study 2026 shows that only 8 percent of firms with 20 or more employees still invoice exclusively on paper, and 59 percent of digitally sending firms use e-invoice standards; among senders, EDI dominates at 71 percent, followed by ZUGFeRD or Factur-X at 27 percent and XRechnung at 5 percent. From our experience, receive-and-process logic is decided at three points — inbound DMS, ERP document logic and three-way-match capability.
Third — S/4HANA modernisation plans press on the process. The DSAG Investment Report 2026 (around 198 SAP users across D/A/CH) shows 38 percent of DACH SAP users report rising IT and SAP budgets for 2026. Every migration is effectively a Procure-to-Pay architecture decision — even when it is filed as an ERP project.
The Procure-to-Pay method at a glance — six phases, one owner
We set up Procure-to-Pay in the DACH Mittelstand in six phases — requisition policy, supplier pre-qualification, purchase order, goods receipt, invoice verification with three-way match, payment and discount realisation. A single Procure-to-Pay owner runs across all six. Without that role the compliance layer is just a diagram.
In vendor-neutral process and ERP consulting the following six-step approach has proven itself:
- Phase 1 — Requisition policy and demand. Demand notification, four-eyes approval, catalogue obligation for indirect spend, link to the supplier release list. The maverick-buying ratio is decided here — the central difference from a bare Purchase-to-Pay.
- Phase 2 — Supplier pre-qualification and compliance check. Master-data maintenance, credit and supply-chain due-diligence check, approval before the first order. The APQC category "Manage suppliers" anchors this layer; it is absent in Purchase-to-Pay.
- Phase 3 — Purchase order. Transfer to the supplier, order confirmation, master-data synchronisation.
- Phase 4 — Goods receipt. Quantity and quality check, warehouse and planning link, goods-receipt posting. Far more complex in machinery with milestone payments than in trade.
- Phase 5 — Invoice verification and three-way match. Invoice meets purchase order and goods receipt; OCR, validation, escalation. According to the Hackett Group P2P Digital World Class Matrix 2025, leading platforms reach markedly higher touchless rates and productivity in invoice processing.
- Phase 6 — Payment and discount. Approval, payment run, feedback into the KPI chain: maverick ratio, catalogue hit rate, cost-per-invoice, touchless rate. Only when this chain is closed does Procure-to-Pay become a basis for control.
A Procure-to-Pay owner must stand above all six phases. SAP Signavio defines the Business Process Owner with end-to-end responsibility, change approval and compliance accountability. Without this role Procure-to-Pay remains a term from a vendor glossary.
Practice example: kitchen manufacturer, 320 million EUR revenue, maverick ratio from 22 to 9 percent (anonymised)
At a southern-German kitchen manufacturer with 320 million EUR revenue we set up the Procure-to-Pay compliance layer cleanly — requisition policy, catalogue obligation, supplier pre-qualification — and reduced the maverick ratio from 22 to 9 percent without any new suite. The three-way-match gap fell in parallel from 38 to under 10 percent.
Across numerous projects with kitchen-manufacturer and machinery clients in the DACH Mittelstand (150 to 800 employees), we have observed that maverick buying and three-way-match breaks routinely appear together — and rarely yield to a new tool when the requisition policy is not linked to the supplier release list. From our experience, the compliance layer collapses where master data is held three times over between procurement, planning and finance.
The 320 million EUR kitchen manufacturer had called us in because 38 percent of incoming invoices were booked without a three-way match and the maverick ratio sat at 22 percent. Procurement ran on an ERP standard module, a separate Excel supplier file and four parallel approval paths. Master data was held in ERP, DMS and CRM; every indirect order needed manual reconciliation to establish which record was currently valid.
We worked the case in several workshops: ERP transaction analysis, swim-lane modelling of the demand, requisition and invoice-verification strand, breakpoint identification. Three were typical: duplicate supplier master data, missing catalogue obligation for indirect orders, manual reconciliation for 38 percent of invoices.
The solution was not a new system. Management named a Procure-to-Pay owner with end-to-end responsibility who consolidated the supplier master data, rolled out the catalogue obligation across 80 percent of indirect orders and activated three-way match in the existing ERP module. The maverick ratio fell from 22 to 9 percent, the three-way-match gap from 38 to under 10 percent, cycle time dropped 14 percent. The clean separation from the parent Source-to-Pay was written into the target model; the system update followed afterwards.
What most Procure-to-Pay guides won't tell you
Three points rarely spelled out in Procure-to-Pay guides — yet from over 1,200 Dreher engagements they are the decisive difference between success and abandonment. Contrary to the common vendor narrative, Procure-to-Pay is neither a super-process nor a synonym — it is the compliance middle layer.
1. Procure-to-Pay is the middle layer, not the super-process
In the top-10 consensus many articles place Procure-to-Pay wrongly above Purchase-to-Pay and ignore Source-to-Pay entirely. Methodologically, the APQC framework separates the three layers cleanly: "Develop sourcing strategies" (Source-to-Pay domain), "Order materials and services" (Purchase-to-Pay core) and "Manage suppliers" (the compliance layer that Procure-to-Pay additionally carries). Solving Source-to-Pay problems with a Procure-to-Pay project buys the wrong suite — and overlooks that the strategic sourcing layer sits a step above.
2. Three disciplines that Purchase-to-Pay does not contain
Procure-to-Pay extends Purchase-to-Pay by exactly three disciplines: requisition policy with catalogue obligation, supplier pre-qualification and compliance check before the order, and active maverick-buying control via KPI loops. Anyone who does not write these into the tool scope actually means Purchase-to-Pay and can choose a leaner suite. The distinction belongs in the requirements specification, not in the discussion afterwards.
3. Three breakpoints no tool fixes
From Dreher experience, more than half of Procure-to-Pay loss points sit between the disciplines, not within. First, requisition-policy-to-requisition: without catalogue linkage no maverick protection. Second, pre-qualification-to-order: without a compliance check no reliable supplier master. Third, goods-receipt-to-invoice: without three-way-match integration no touchless rate. We work these three breakpoints in a process-mining workshop with swim-lanes — before any new system is selected.
Our take
Procure-to-Pay is an organisational and compliance topic, not a tool topic. Naming the owner, linking requisition policy to the supplier release list and analysing the three breakpoints is the hard part of the work.
Application across Dreher industries
Procure-to-Pay scope differs between mechanical and plant engineering, variant manufacturing and consumer-goods trade. We calibrate the six phases industry by industry — milestone payments in project business, variant-level supplier release in machinery, EDI and batch traceability in trade.
In plant and mechanical engineering Procure-to-Pay runs over months; invoicing follows project progress with milestone splits. We see recurring weakness at the requisition-to-order transition. In variant manufacturing the supplier release list must be maintained at variant level. In food and consumer-goods trade, batch traceability and EDI integration dominate; Procure-to-Pay runs in days, not weeks. The Trovarit study "ERP in Practice 2024/2025" (over 1,700 DACH users) puts vendor service quality under scrutiny — the interfaces between procurement, planning and finance remain the central maturity criterion.
Frequently asked questions
Procure-to-Pay is the operational procurement strand from requisition policy to supplier payment, extended by supplier pre-qualification, compliance check, three-way match and maverick-buying control. Purchase-to-Pay is the bare transactional subset from requisition onwards — without an active compliance layer. Source-to-Pay is the strategic super-process including market analysis, sourcing strategy and contract negotiation. The APQC framework separates sourcing strategies, order materials and manage suppliers for exactly this reason. Equating the three layers wrongly scopes a Procure-to-Pay project to the order phase and overlooks the compliance gap.
From over 1,200 engagements we place the Procure-to-Pay owner in procurement or a cross-functional Head of Procurement Operations role with a direct reporting line to the management board. The decisive point is end-to-end authority over the compliance layer: the owner must approve changes to requisition policy, supplier master data, catalogue obligation, three-way-match rules and payment run. SAP Signavio defines the Business Process Owner with exactly this responsibility. A fragmented owner structure across procurement, goods receipt and finance does not work for Procure-to-Pay.
Procure-to-Pay extends Purchase-to-Pay by three disciplines: first, requisition policy with catalogue obligation for indirect orders; second, supplier pre-qualification with compliance check before the first order; third, active maverick-buying control through KPI loops. The APQC framework anchors the compliance layer in Manage Suppliers — absent from the narrow Purchase-to-Pay term. In the anonymised kitchen-manufacturer case this layer reduced the maverick ratio from 22 to 9 percent. Anyone who does not write the three disciplines into the tool scope actually means Purchase-to-Pay.
Not strictly. The BMF FAQ has required receive capability for XRechnung and ZUGFeRD from version 2.0.1 since 1 January 2025; from 1 January 2027 the send mandate applies above 800,000 EUR prior-year revenue, and from 1 January 2028 the threshold falls away. Below 800,000 EUR we bring receive-and-process logic into the existing ERP-DMS pairing rather than buying a separate AP suite. A cleanly configured three-way match plus a catalogue obligation for indirect orders covers a large part of the touchless-invoice promise — without an additional licence.
Next steps
Before any tool or requirements-specification discussion, a brief up-front clarification pays off: who is the Procure-to-Pay owner, what do the six phases look like today, and where are the three typical breakpoints between requisition policy, pre-qualification and three-way match? Skip it and you build a diagram nobody runs.
To deepen these topics, see our process management services and our ERP consulting practice. We also recommend the wiki entries on source-to-pay, purchase-to-pay and process mining. Current case studies are in our insights; arrange a first conversation via the contact page.
30 minutes with Dreher Consulting
A structured pre-clarification of your Procure-to-Pay strand — owner role, six phases and the three breakpoints between requisition policy, pre-qualification and three-way match, vendor-neutral and drawn from over 1,200 projects across the DACH Mittelstand.
