Procure-to-Pay (P2P)

Procure-to-Pay (P2P) describes the end-to-end process of acquiring goods and services from suppliers and paying for them — from requisition through purchase order, goods receipt, invoice verification and payment. P2P is the second of the four classical ERP processes (alongside Order-to-Cash, Record-to-Report and Hire-to-Retire). For ERP-bearing organisations in DACH, P2P is a major automation target: invoice processing alone typically consumes 30-60% of AP-team capacity, and AI-based document understanding has transformed the economics of automation since 2022.

P2P process stages

1. Requisition — internal request, approval routing, budget check
2. Sourcing — supplier identification, request for quotation, supplier evaluation
3. Contract negotiation — framework agreement, pricing terms, SLA
4. Purchase order — PO creation, approval workflow, transmission to supplier (EDI, e-mail, supplier portal)
5. Goods receipt — physical receipt verification, inspection, stock posting
6. Invoice receipt and verification — supplier invoice ingestion, three-way match (PO + receipt + invoice), approval routing for exceptions
7. Payment — payment scheduling, bank-file generation (SEPA), payment confirmation
8. Supplier-master maintenance — ongoing supplier-data quality, bank-detail verification, tax-ID and certification renewals

Three-way match

The classical control of P2P is the three-way match: invoice details (price, quantity, payment terms) must agree with the purchase order, and the quantity must agree with the goods receipt. Discrepancies route to manual review. Modern ERPs automate the match when all three documents align within tolerances (typically 5% price variance, 10% quantity variance), straight-through processing the rest. For service invoices and indirect spend without goods receipts, two-way match (invoice versus PO or contract) applies. Achieving high straight-through rates requires supplier data quality, accurate purchase orders and well-tuned tolerance rules. Mature P2P programmes reach 70-90% straight-through processing, freeing AP team capacity for exception handling and supplier-relationship management.

AI-driven invoice processing

Supplier-invoice processing is one of the most-automated ERP-adjacent processes. Specialist platforms (Rossum, Hyperscience, ABBYY FlexiCapture, Esker, SAP Document and Reporting Compliance, Microsoft AI Builder) extract structured data from incoming invoices — PDF, e-mail attachments, scanned paper, structured e-invoice formats — with LLM-augmented accuracy now consistently exceeding 90%. The extracted data flows directly to the ERP for three-way matching. Implementation effort: 3-9 months and 200,000-700,000 EUR for mid-market AP operations processing 50,000-500,000 invoices per year. Payback period: 12-24 months through reduced AP team size, faster invoice cycle and lower error-rate rework.

DACH-specific considerations

Three DACH-specific layers. (1) E-invoice mandate: from 2025, German B2B must be able to receive structured e-invoices (XRechnung, ZUGFeRD). P2P systems must parse these formats and feed the ERP with structured data — bypassing OCR entirely. (2) GoBD compliance: all P2P transactions and the original invoice files must be retained for 10 years in their original electronic form, with audit-trail. (3) DATEV integration: many German tax-relevant outputs flow through DATEV at month-end; the P2P pipeline must produce the right DATEV-compatible structures. Specialist tools (D.velop invoices, JustOn Invoice, sevDesk for SMB, JTL-Wawi for e-commerce-heavy SMB) handle these specifics within or alongside the ERP.

Related Topics

• Order-to-Cash
• Record-to-Report
• E-invoicing