Invoice processing is the accounts-payable loop that books a supplier invoice into the ERP after vendor, purchase order and amounts have been checked. Pexon wires extraction, three-way match and a human queue for exceptions into SAP or the finance system you already run. It is not an accounts-payable product licence; posting stays in your ledger.
The starting point
Industrial companies of about 500 people in Europe usually meet the wall the same week: supplier PDFs in a shared inbox, someone re-keying them into SAP, and a cycle time nobody can put on a slide. Invoice processing here means the posting loop — vendor, purchase order, amounts, then a ledger line — not a second product finance has to log into. We build that loop into the ERP you already run.
The invoice is not processed until the ERP has accepted it.
| Metric | Top performers | All-buyer average |
|---|---|---|
| Cost per invoice | USD 2.78 | USD 10.89 |
| Cycle time | 3.1 days | 10.9 days |
| Exception rate | 9% | 22% |
| Touchless rate | 49.2% | not in the same series |
Ardent Partners, Accounts Payable Metrics That Matter in 2025, as summarised by Corpay on 31 July 2026 (retrieved 30 August 2026). Figures are USD as published. They are a peer benchmark, not a Pexon result, and about 75% of AP departments in that research already use some automation — tooling alone does not produce the left-hand column.
What we build
01
One company code, the real mix of PDFs and scans. We use the extractor you already licensed where it is good enough — SAP Document AI is one option, not a prerequisite — and we write down which fields must hit the typical 90% auto-confirm floor before a human is skipped.
02
Vendor against master data, purchase order and goods receipt where they exist, amounts and tax as the ERP already knows them. SAP's published posting pattern is the A_SupplierInvoice OData API with blocked vendors and invalid accounts returned to an exception queue. We follow that shape, including on non-SAP ledgers that expose an equivalent posting API.
03
Low-confidence fields, missing receipts and amount breaks stay in a human queue with an owner in finance. Straight-through processing is the residue after that queue is designed, not a slider in a demo.
€4,900
We take one invoice population, write the match rules and the exception queue, and say whether the extractor you already have is enough to book into the ERP. The document is yours to keep, whether Pexon builds the loop or your existing integrator does.
All prices are net and exclude VAT.
The two-week Readiness Blueprint is fixed at €4,900 net. It maps capture, match rules and the exception queue against one invoice population in your ERP. A production use-case pilot starts from €15,000. We do not sell an accounts-payable suite licence.
Most invoice processing software is a product you log into beside the ERP. This offer books into the ledger you already run: extraction, vendor and purchase-order checks, then a posting API such as SAP's A_SupplierInvoice. The ERP remains the system of record. We do not replace Central Invoice Management or your current AP module.
A named invoice population (one company code is enough), access to the posting API or middleware your finance team already trusts, and an owner for the exception queue. Without those three, the blueprint can only describe a demo.
We do not auto-post every invoice. Low-confidence fields, blocked vendors, missing goods receipts and amount breaks go to a human. Extraction accuracy is not posting correctness. If the ERP master data cannot be queried, this is a data-foundation problem first, not an invoice project.
Next step
Thirty minutes with the architect who would actually run the engagement.