Explainer
I have sat on the client side of enough purchase to pay projects to know the software is the easy part. Here is what procure to pay software actually does, what the UK e invoicing mandate means for it, and how I would pick one.
By Christopher Fagan, Managing Partner, PEF Consulting Partners
Delivered for and alongside
















Procure to pay is the chain of events between someone in your business needing something and your bank paying for it. Written out, it has seven links: a requisition or intake request, an approval against budget and policy, a purchase order sent to the supplier, a goods receipt or confirmation that the service was delivered, an invoice, a match of that invoice against the order and the receipt, and a payment run with a remittance back to the supplier.
Every ERP can do each link. What procure to pay software does is make the chain hold for the people who only touch it occasionally. The requester who buys once a quarter gets a guided form or a catalogue rather than a blank purchase order screen. The approver gets a mobile notification with the budget position on it. The supplier receives the order electronically and can flip it into an invoice without retyping. The payables team sees exceptions only, because clean matches post themselves.
The failure modes are just as predictable. Orders raised after the invoice arrives, so the system records history rather than controlling spend. Receipts never entered, so every invoice blocks. Approval chains so long that people buy on a card and claim it back. Supplier records duplicated across entities. A procure to pay tool does not fix any of these on its own; it exposes them. That is useful, provided someone owns the process design, which is the point I keep returning to in our procurement software selection work.
The honest answer is that the boundary is movable, and vendors on both sides have an interest in where you draw it. SAP, Oracle, Microsoft, NetSuite, Unit4 and Sage all ship purchasing and payables that are adequate for a disciplined finance team buying from a stable supplier base. If trained buyers raise most orders, invoices arrive in modest volume and suppliers are content to email PDFs, you may not need anything else, and I have told clients exactly that.
Specialist procure to pay earns its keep in five situations:
Where the boundary sits also decides the integration. In most designs the ERP stays the system of record for the general ledger, the supplier master and the payment run, while the P2P tool owns requisitions, orders, receipts and invoice approval, posting approved invoices back for payment. Some firms keep the three way match in the ERP; others move it into the P2P tool so exceptions are handled where the receipt lives. Neither is wrong, but you must choose, and the integration design follows from that choice. Payables automation on its own, without the buying side, is a narrower decision I cover in a separate guide.
For years UK buyers could treat e invoicing as a European complication. That ended in November 2025. HMRC and the Department for Business and Trade ran a consultation between February and May 2025, took 342 responses, and published the outcome on 26 November 2025: the UK will introduce mandatory e invoicing for all VAT invoices from 2029, with an implementation roadmap to follow at Budget 2026 and detailed design work with stakeholders from January 2026.
The response is worth reading for what it rules out as much as what it rules in. The government’s preferred model is decentralised, so invoices move between service providers rather than through a single state platform. Real time reporting to HMRC will not be introduced alongside the 2029 mandate, though the case for it later is left open. No standard has been chosen: the government says it will develop standards that allow interoperability, weighing an existing standard against a UK specific one. Businesses below the VAT threshold that choose not to register will not be obliged to adopt it.
The public sector is already further along. Bodies covered by the Procurement Act 2023 must accept e invoices that comply with BS EN 16931, and NHS Supply Chain requires its suppliers to invoice through the Peppol network. If you sell to or buy from the public sector, structured invoices are part of your present, not your future.
Any platform you sign for in 2026 or 2027 will be live in 2029. Ask every vendor how it receives structured invoices today, whether it runs or partners with a Peppol access point, how it archives invoices for VAT inspection, and how it will handle the standard once HMRC names one. Basware and GEP both market e invoicing compliance across many countries; the question is whether the UK specifics are on their roadmap or merely assumed.
The supplier portal is where good intentions meet supplier patience. On SAP Business Network a standard account is free, while an enterprise account becomes chargeable once a supplier passes five documents and 50,000 US dollars with one buyer in a rolling year; it then pays an annual subscription set by document count plus a transaction fee of 0.155 per cent of volume, or 0.35 per cent where service entry sheets are used, capped at 20,000 US dollars per buyer relationship a year. Coupa’s basic supplier account is free, with paid tiers at 549 and 4,800 US dollars a year for a verified badge and reporting. Your suppliers will ask about this in week one, so know the answer and decide whether you will mandate the portal or let the long tail keep emailing PDFs.
Three way matching, order against receipt against invoice, is the control that justifies the whole system, and it is where tolerances matter. Too tight and every freight charge blocks; too loose and overbilling slips through. Services need a different pattern, usually a two way match against an approved service entry or timesheet, because there is no goods receipt. Set tolerances by category, not globally.
Fraud is now a design requirement rather than an audit afterthought. The controls I expect to see are segregation of duties enforced in the workflow, independent verification of any change to supplier bank details, duplicate invoice detection across entities, and monitoring of unusual patterns. The vendors have moved here: Coupa’s SpendGuard describes more than 25 alert types across invoices, expenses and payments, Medius markets fraud and risk detection across the payables lifecycle, and Basware sells AP Protect alongside audit and recovery. Use these, but do not let them replace the phone call to a known contact before bank details change.
The field divides by where each vendor started. Coupa, SAP Ariba, Ivalua, Jaggaer and GEP sell procure to pay as part of a source to pay suite, so you buy the buying side with sourcing, contracts and supplier management on the same platform. Basware and Medius came from invoices and payables and have grown procurement modules around that core. Proactis serves UK service led organisations and public bodies with its Rego platform. Zip is a newer intake and orchestration layer that routes requests across the systems you already have, naming SAP Ariba, S/4HANA, Oracle and Workday among its connections. Precoro serves smaller businesses.
Published prices are rare. Precoro lists a Core plan from 499 US dollars a month and an Automation plan from 999 US dollars a month, both billed annually, plus an AP Module from 499 US dollars a month, with enterprise pricing on request and payment accepted in pounds (checked November 2026). SAP’s website carries a store listing for its SAP Strategic Procurement package at 2,420 US dollars a month per block of one user on contracts of 3 to 36 months, but that is the sourcing and contracts side, and real Ariba estates are negotiated. Coupa, Ivalua, Jaggaer, GEP, Basware, Medius, Proactis and Zip do not publish buyer prices at all.
What drives the quote is consistent: annual spend under management, invoice volume, the number of requesters and approvers, the modules switched on, the legal entities and ERPs to connect, and the countries whose tax rules you need. Implementation is priced separately, almost always by a partner rather than the vendor, and supplier enablement is often a further line. I normalise all three before comparing quotes, because a low subscription with an expensive partner is not a low price. For the two largest suites, see Coupa explained and SAP Ariba explained.
Start with the spend, not the software. Pull twelve months of invoices and classify them: how many had a purchase order before the invoice date, how many suppliers account for 80 per cent of value, how many invoices were under £500, how many legal entities and currencies are involved. That analysis tells you whether your problem is control, efficiency or visibility, and each points to a different tier.
Then write the boundary with the ERP down on one page, including who owns the supplier master and where the match happens. Shortlist three vendors from the right tier and make them demonstrate your scenarios on your data, including a supplier onboarding, an invoice without a purchase order and a change of bank details. Score the integration approach as hard as the user interface. Get the roadmap commitment on UK e invoicing in writing.
Running the software procurement for the National Grid separation taught me that the commercial structure matters as much as the product: what happens to the subscription when spend grows, what the partner’s day rate looks like in year three, and what exit terms you hold. Build those into the evaluation, not the negotiation.
If you want independent help, we work in two ways: as assurance alongside your team and whichever integrator you choose, or by running the selection and implementation ourselves. We hold no reseller or referral arrangement with any vendor on this page, and our fees are published plainly on our pricing page.
Related reading: Independent procurement software selection, Accounts payable automation explained, Coupa explained for UK buyers, SAP Ariba explained, Basware explained, Procurement consultancy.
Procure to pay software manages the cycle from a request to buy something through approval, purchase order, goods or service receipt, invoice matching and payment. It usually adds guided buying, catalogues, a supplier portal and invoice capture on top of an ERP, which remains the system of record for the ledger and the payment run. Its purpose is to make occasional buyers follow the process and to let clean invoices post without manual handling.
No. Accounts payable automation covers the invoice side only: capture, coding, matching, approval and preparation for payment. Procure to pay starts earlier, at the request and purchase order, so that invoices arrive against an approved order and match automatically. Basware and Medius grew from the payables side and now offer buying modules; Coupa, SAP Ariba, Ivalua and Jaggaer sell procure to pay inside wider source to pay suites.
Yes. On 26 November 2025 the government confirmed that the UK will introduce mandatory e invoicing for all VAT invoices from 2029, following an HMRC and Department for Business and Trade consultation. The model is decentralised, real time reporting is not part of the 2029 mandate and the standard has not yet been chosen. An implementation roadmap was promised at Budget 2026. Public bodies already have to accept e invoices to BS EN 16931.
Most vendors do not publish prices. Precoro is an exception, listing plans from 499 US dollars a month billed annually with enterprise pricing on request. Coupa, SAP Ariba, Ivalua, Jaggaer, Basware, Medius and Zip quote based on spend under management, invoice volume, users, modules, entities and integrations. Implementation by a partner and supplier enablement are charged separately and can exceed the first year subscription, so compare all three together.
Yes, and for groups that is often the main reason to buy it. The procure to pay layer gives every entity one buying experience and one spend view while each ERP keeps its own ledger, supplier master and payment run. The integration has to map suppliers, accounts, cost centres and tax codes for each ERP, so the number of ERPs is one of the biggest drivers of both the quote and the implementation effort.
Deciding where your ERP should stop? Send me your invoice data and your ERP, and I will tell you which tier of procure to pay software you actually need.
Book a confidential conversation
Independent, client side help on the systems around ERP and CRM: LIMS selection, MES selection, eQMS selection, Computer system validation, HRIS selection and implementation, Payroll implementation, Workday HCM, SAP SuccessFactors, Oracle HCM, Procurement software selection, EAM software selection, WMS selection, Power BI consultancy, and ERP implementation itself. For our fees see pricing.
Written by Christopher Fagan
Managing Partner, PEF Consulting Partners
Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.
Where next