Häufig gestellte Fragen
What exactly does Procure-to-Pay (P2P) mean?
Procure-to-Pay refers to the end-to-end digitally mapped procurement process that links an identified demand via purchase requisition, approval, purchase order, goods receipt and invoice verification through to payment to the supplier. The term thus captures an organisation's operational procurement chain as one coherent, largely automatable flow. In the ERP context, P2P stands for all steps being based on shared master data, being logged without gaps and interlocking without media discontinuities. The goal is not the cheapest individual purchase, but a traceable, auditable and efficient overall process.
What is the difference between Procure-to-Pay and Order-to-Cash?
Procure-to-Pay concerns the spending side of a company and describes the path from an identified demand via the purchase order through to payment to the supplier. Order-to-Cash mirrors this on the revenue side, covering the sales process from the customer order via delivery and invoicing through to receipt of payment. Both process chains access the same data pool in the ERP but concern opposing flows of money. In practice they are often considered together, because jointly they map an organisation's complete end-to-end financial cycle.
What is the three-way match in invoice verification?
The three-way match compares, line by line, the three central documents: purchase order, goods receipt or delivery note, and incoming invoice. If quantity, price and terms agree across all three documents, the invoice is automatically released for payment; only in the event of discrepancies does the case go to a responsible person for clarification. The procedure is designed to ensure that only what was actually ordered and delivered is paid for, and at the agreed prices. It thus constitutes a key control against posting errors, duplicate payments and unjustified claims.
Do you need a dedicated tool for P2P, or is the ERP module sufficient?
For many companies, the ERP's integrated purchasing and finance module covers the Procure-to-Pay process completely, because purchase orders, goods receipts and invoices are based on the same master data anyway. Specialised P2P solutions are worthwhile above all with high procurement volumes, many suppliers, complex approval paths or extensive catalogue integration via punchout standards such as OCI or cXML. In both cases it is important that common interfaces such as REST API, EDIFACT or OData as well as electronic invoice formats are supported directly, in order to avoid expensive in-house development. The decision should be guided by the actual automation needs rather than being made across the board.
What role does the e-invoicing mandate play in the P2P process?
Since 1 January 2025, companies in domestic German B2B transactions must be able to receive electronic invoices; for issuing them, staggered transition rules apply, so the issuing obligation takes effect from 2027 for companies with more than 800,000 euros in prior-year turnover and from 2028 for all remaining companies. An e-invoice within the meaning of the law complies with the European standard EN 16931, which is met, for example, by the XRechnung format and by ZUGFeRD from version 2.0.1. In the P2P process this primarily affects invoice verification, as structured data makes the automated matching against purchase order and goods receipt easier. The exact deadlines and profiles should be checked against the current requirements of the German Federal Ministry of Finance, as transition rules vary.
How do Procure-to-Pay and Source-to-Pay differ?
Procure-to-Pay covers the operational handling from purchase requisition through to payment, and thus presupposes suppliers that have already been selected and terms that have already been negotiated. Source-to-Pay covers this area as well but starts earlier, adding the strategic steps such as demand analysis, supplier search, tendering, negotiation and contract management. Put simply, P2P is the operational core, while Source-to-Pay includes the upstream strategic purchasing. Which scope makes sense depends on how complex an organisation's procurement, supplier structure and regulatory requirements are.
How does an end-to-end P2P process help against maverick buying?
Maverick buying refers to purchases made outside defined processes and framework agreements, also known as wild buying or off-contract buying. Such transactions lead to missed price advantages, inconsistent supplier structures and poorer traceability. An end-to-end P2P process with clear approval paths, embedded catalogues and system-supported authorisations channels orders into regulated paths and makes workarounds visible. As a result, agreed terms can be used more consistently and spend transparency increases, which indirectly contributes to cost control.