Purchase-to-Pay (P2P) is the operational end-to-end process from purchase requisition to supplier payment — procurement, goods receipt, invoice verification and finance in a single bracket. Contrary to the common P2P/S2P conflation, P2P is the transactional subset starting at requisition; Source-to-Pay (S2P) starts earlier with demand strategy, sourcing and contract. From over 1,200 Dreher Consulting engagements we know this shortcut produces the wrong project scope — a P2P suite gets bought while the breakpoints sit at the three-way match and supplier master-data care. We recommend setting up P2P in five phases with a named process owner, before the tool discussion starts.
What Is Purchase-to-Pay? Definition and Distinction from Source-to-Pay and Procure-to-Pay
Purchase-to-Pay is the transactional end-to-end process from purchase requisition to supplier payment. Source-to-Pay is the strategic super-process including sourcing and contract. Procure-to-Pay is a lightly extended Purchase-to-Pay with procurement policy. Mixing the three layers scopes tool projects incorrectly.
P2P covers all operational activities from requisition through purchase order, goods receipt, three-way match, to supplier payment. The APQC Process Classification Framework separates Section 4 „Procure materials and services" into 4.2 „Develop sourcing strategies", 4.3 „Order materials and services" (the P2P core) and 4.4 „Manage suppliers". This distinction disappears in most vendor blogs.
The CIPS Procurement and Supply Cycle is complementary: P2P covers the operational order-to-payment leg; S2P covers the full cycle including sourcing strategy and supplier evaluation. Buying a P2P suite when you actually need S2P programmes a master-data break between supplier qualification and order execution.
Three terms managing directors should keep separate:
- Purchase-to-Pay (P2P) — the transactional execution strand from requisition to payment, four to seven phases.
- Source-to-Pay (S2P) — the strategic super-process including sourcing, contract and supplier evaluation, covered in our source-to-pay wiki entry.
- Procure-to-Pay — a lightly extended P2P with demand analysis and procurement policy; the drift belongs in the requirements specification, not in the discussion afterwards.
In Porter's value chain (Porter, Competitive Advantage, 1985), P2P is the horizontal interlocking of Inbound Logistics with procurement and payment settlement — the strand where vertical line organisations most often break.
Why Purchase-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 pressure a continuous Purchase-to-Pay. Anyone still measuring procurement, goods receipt and invoice verification in isolation in 2026 loses steering authority over the procurement base.
First, the e-invoicing mandate tightens the invoice phase. The BMF e-invoicing FAQ and the second BMF letter of 15 October 2025 fix the stages: receive since 1 January 2025, send from 1 January 2027 for firms above 800,000 EUR revenue, full mandate from 1 January 2028. Permitted EN 16931 formats are XRechnung and ZUGFeRD from version 2.0.1.
Second, adoption still has room. According to the Bitkom e-invoicing survey, only 8 percent of firms with 20+ employees still invoice exclusively on paper (down from 14 percent five years ago); among senders of structured formats, EDI dominates (57 percent) ahead of ZUGFeRD (45 percent) and XRechnung (26 percent). From our experience, the receive-and-process logic is decided at three points — DMS integration, ERP document logic, three-way-match capability.
Third, S/4HANA modernisation plans press on the process. The DSAG Investment Report 2026 shows 38 percent of DACH SAP users report rising IT and SAP investment budgets for 2026. Every migration is effectively a P2P architecture decision — even if filed as an ERP project.
The P2P Method at a Glance — Five Phases, One Owner
We set up Purchase-to-Pay in five phases — requisition, purchase order, goods receipt, invoice verification with three-way match, payment and discount realisation. A single P2P owner runs across all five. Without that role you get functional boundaries instead of a continuous procurement chain.
In our vendor-neutral process and ERP consulting the following five-step approach has proven itself:
- Phase 1 — Purchase requisition. Demand notification from a business unit or planning, four-eyes approval, link to procurement policy and supplier release list. The maverick-buying ratio is decided here. From over 1,200 engagements we know the loss points — usually in the gap between procurement policy and supplier master data.
- Phase 2 — Purchase order. Transfer to the supplier, order confirmation, master-data synchronisation. In the Mittelstand this phase decides whether direct procurement, indirect procurement and capital goods run in the same workflow or need separate paths.
- Phase 3 — Goods receipt. Quantity and quality check, link to warehouse and planning, goods-receipt posting. In machinery with milestone payments and split goods receipts this phase is more complex than in trade or consumer goods.
- Phase 4 — Invoice verification and three-way match. Incoming invoice meets purchase order and goods receipt; OCR, validation rules, escalation workflow. Touchless-invoice processing — automated handling without manual intervention — is the central maturity indicator here; the Hackett Group Digital World Class Matrix documents markedly higher touchless rates and shorter cycle times at leading AP platforms.
- Phase 5 — Payment and discount realisation. Approval workflow, payment run, posting and feedback into the KPI chain Cost-per-Invoice, Touchless Rate, Maverick Ratio, Discount Realisation. Only when this chain is closed does P2P become a steering basis rather than a string of functional reports.
A P2P owner must stand above all five phases. SAP Signavio defines the Business Process Owner with end-to-end responsibility, change-approval authority and compliance accountability. Without it P2P remains a diagram — not a process.
Practice Example: Kitchen Manufacturer, 320 Million EUR Revenue, 38 Percent Without Three-Way Match (Anonymised)
At a southern-German kitchen manufacturer with 320 million EUR revenue we separated P2P from the super-process Source-to-Pay and pulled 14 percent of cycle time out of the procurement strand without any new suite — through unified supplier master data, a named P2P owner and an ERP-native three-way match.
We have, in numerous projects with kitchen-manufacturer and machinery clients in the DACH Mittelstand — each with 150 to 800 employees — observed that three-way-match breaks and maverick buying appear together and rarely yield to a new tool when the process-owner role is missing. It is regularly the same three breakpoints that surface.
The manufacturer with around 320 million EUR revenue 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 supplier file in Excel and four approval paths. Supplier master data was maintained multiple times in ERP, DMS and CRM; every order required manual reconciliation of which record was currently valid.
We worked the case in over twelve workshops: ERP transaction analysis, swim-lane modelling of the requisition and invoice-verification leg, identification of breakpoints. Three were typical: duplicate supplier master data, missing three-way-match integration in the ERP standard module, manual invoice reconciliation for 38 percent of invoices.
The solution was not a new system. Management named a P2P owner with end-to-end authority who, with procurement and finance, consolidated supplier master data and activated the three-way match in the existing ERP module. The maverick ratio fell from 22 to 9 percent, procurement cycle time dropped by 14 percent. The clean separation from the super-process Source-to-Pay was written into the target model; the system update followed only afterwards.
What Most P2P Guides Won't Tell You
Three points rarely spelled out in P2P guides — yet from over 1,200 Dreher engagements the decisive difference between success and abandonment. Whoever does not clarify them builds a new suite on an old bottleneck.
1. P2P Is the Subset, S2P the Super-Process — Conflating Them Produces Master-Data Breaks
In many ERP-selection projects, P2P and S2P are used as synonyms — usually because the tool vendors blur the terms. APQC PCF separates the layers: 4.2 sourcing strategies vs. 4.3 order materials. Solving S2P problems with a P2P project buys an order-execution module while the breakpoints sit in supplier qualification, contract attachment and demand strategy.
2. The Drift Purchase-to-Pay vs. Procure-to-Pay — Narrow vs. Lightly Extended
P2P denotes the narrow order-to-payment cycle from requisition; Procure-to-Pay is lightly extended with demand analysis and procurement policy. Most top-10 articles equate the two without evidence. We reserve „Purchase-to-Pay" for the narrow execution strand and use „Procure-to-Pay" only where procurement policy and pre-qualification are in scope.
3. Three Breakpoints No Tool Fixes
From Dreher experience, more than half of P2P loss points arise at functional boundaries, not within a function. First, demand-to-requisition: if procurement policy is not linked to the supplier release list, maverick buying emerges. Second, order-to-goods-receipt: without clean quantity and quality checks no robust three-way match. Third, invoice-to-payment: without OCR and validation rules no touchless rate. We work these three breakpoints in a process-mining workshop with swim-lanes — before any new system is selected.
Our take
Purchase-to-Pay is an organisational, not a tool, topic. Whoever names the owner, analyses the breakpoints and consolidates supplier master data has done the hard 80 percent of the work. Tool selection afterwards is the comparatively easy part.
Application Across Dreher Industries
P2P scope differs across mechanical engineering, variant manufacturing and consumer-goods trade. We calibrate the five phases industry by industry — milestone payments and split goods receipts in project business, variant steering in machinery, volume and EDI in trade.
In plant and mechanical engineering P2P runs over months; invoicing follows project progress with milestone and split goods-receipt invoicing — the order-to-goods-receipt transition is, in our experience, the most frequent weak point. In variant manufacturing, bill-of-materials and configuration master data dominate; the supplier release list must be kept at variant level. In food and consumer-goods trade, batch traceability and EDI dominate; P2P runs in days, not weeks. The Trovarit study ERP in Practice 2024/2025 with over 1,700 DACH users confirms: interfaces between procurement, logistics and finance are rated better than in 2022 but remain the central maturity criterion.
Frequently Asked Questions
Purchase-to-Pay is the transactional end-to-end process from purchase requisition to supplier payment and typically covers four to seven phases. Source-to-Pay is the strategically extended super-process including sourcing strategy, supplier selection, contract negotiation and supplier evaluation. APQC PCF separates 4.2 sourcing strategies from 4.3 order materials precisely for this reason. Equating the two wrongly scopes a P2P project to the order phase and overlooks the strategic breakpoints upstream. Separate the two layers in writing before drafting any requirements specification.
From over 1,200 engagements we recommend placing the P2P owner organisationally in procurement or in a cross-functional Head of Procurement Operations role reporting directly to the management board. The decisive point is end-to-end authority: the owner must approve changes to supplier master data, the order-release workflow, three-way-match rules and the 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 P2P.
Not strictly. The BMF FAQ has required receive capability for XRechnung and ZUGFeRD from version 2.0.1 since 1 January 2025; the send mandate applies from 1 January 2027 above 800,000 EUR revenue, with the threshold falling away on 1 January 2028. In most Mittelstand firms below that threshold we recommend bringing receive-and-process logic into the existing ERP-DMS pairing rather than a separate AP suite. A cleanly configured three-way match in the ERP standard module covers most 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 P2P owner, what do the five phases look like today, where are the three typical breakpoints? Skip it and you build a diagram nobody runs.
To deepen these topics, see our process management services and our ERP consulting practice. Complementary wiki entries: source-to-pay, process owner and process mining. Current practice notes are in our Insights; book a first conversation via the contact page.
30 minutes with Dreher Consulting
A structured pre-clarification of your Purchase-to-Pay setup — the five phases, the P2P owner and the three typical breakpoints at the three-way match and supplier master data, vendor-neutral and drawn from over 1,200 projects in the DACH Mittelstand.
