If you run Exact Online, AFAS, Dynamics 365 Business Central, or Moneybird, you already have a tool that creates purchase orders, records invoices, and tracks payments. So a fair question is: why would a mid-size company add a separate procurement platform on top of that?

It is a question worth taking seriously, not dismissing. ERPs are powerful, and "buy another tool" is not always the right answer. This piece lays out what an ERP purchasing module does well, where it tends to stop, and how to tell whether that gap is costing you enough to close.

What your ERP does well

An ERP is the financial and operational backbone. For purchasing, that means it handles the transactional core competently: it can raise purchase orders, post supplier invoices, run two or three way matching at the order level, manage the general ledger, and keep your accounts payable in order. It is the system of record for what was bought and what was paid.

For many companies, especially those buying a stable set of goods through a clean order-to-invoice flow, that core covers the day-to-day. If your purchasing is mostly repeat orders against known suppliers and your finance team is happy, you may not need anything else, and you should be skeptical of anyone who insists otherwise.

Where the ERP purchasing module tends to stop

The gap shows up not in the transaction, but in everything around it. ERPs are built to record what happened. They are not built to manage the relationships, contracts, and decisions that happen before and between transactions.

Contracts are not really managed. Most ERP purchasing modules treat a contract as a reference number, not as a living document with clauses, obligations, renewal dates, and price terms. The ERP knows you have an agreement. It does not read it, track its renewal, or check invoices against its terms. That is why World Commerce and Contracting research has consistently tied poor contract management to value leakage of around 9% of annual revenue, even in companies with capable ERPs.

Renewals slip through. An ERP will not warn you ninety days before a contract auto-renews on terms you meant to renegotiate. The renewal date, if it exists at all, sits in a custom field nobody monitors. The Aberdeen Group found that best-in-class companies proactively renew about 56% of their contracts, against 25% for everyone else. The rest auto-renew or lapse, often unintentionally. An ERP does little to move you into the first group.

Invoice matching stops at the order, not the agreement. ERP matching typically confirms that an invoice matches a purchase order. It does not confirm that the invoice matches what your contract actually entitles you to: the agreed unit price, the volume discount, the tolerance band. The gap between PO-level matching and contract-level matching is exactly where overbilling hides.

Spend visibility is fragmented. ERPs report on what flows through them. The off-contract purchases, the credit card buys, the supplier paid under three slightly different names: these blur the picture. Tail spend, the long tail of small purchases scattered across many suppliers, is where maverick buying concentrates, and McKinsey has estimated that maverick spend can account for 20% to 30% of indirect spend leakage. ERPs rarely surface it cleanly.

Sourcing and supplier risk are out of scope. Running an RFP, scoring suppliers, tracking vendor risk over time: these are not what an ERP is for, and bolting them on through spreadsheets recreates the original problem.

The real question: replace or integrate?

Here is the framing that actually matters. A dedicated procurement platform is not a replacement for your ERP, and you should distrust any vendor who positions it that way. Your ERP remains the financial system of record. The right procurement tool sits alongside it and connects to it.

That connection is the whole point. A procurement platform that integrates with Exact Online, AFAS, Dynamics 365 Business Central, or Moneybird can pull invoice and vendor data out of the ERP, enrich it with contract intelligence and risk scoring, and feed insight back. The ERP keeps doing what it is good at, the recording. The procurement layer does what the ERP was never built to do: read contracts, watch renewals, match invoices against agreed terms, and surface spend the ledger hides.

Think of it as division of labour, not duplication. The ERP answers "what did we pay." The procurement platform answers "should we have paid that, and what is coming up that we need to act on."

How to tell if the gap is costing you

You probably have an ERP-shaped gap if several of these are true:

• You cannot quickly list which contracts renew in the next quarter without opening the agreements one by one.

• Your invoice matching confirms the order but not the contracted price or discount.

• A meaningful share of your spend happens off-contract or on cards, invisible to the ERP's reporting.

• You have no running view of supplier risk, just whatever someone last noted.

• Sourcing events and RFPs happen in email and spreadsheets, outside any system.

If three or more land, the gap is not theoretical. It is leaking value that your ERP, by design, will not catch.

A measured way to decide

You do not have to choose between loyalty to your ERP and adding a tool. The two coexist by design. A practical test:

1. Pick the one purchasing question your ERP cannot answer well today. For most mid-size companies that is "which contracts need attention before they renew" or "are we being billed what we agreed."

2. Quantify one instance of getting it wrong. A single overlooked renewal or unchecked overbill on a meaningful contract usually exceeds a year of procurement software cost.

3. Require any tool you trial to integrate with your specific ERP. If it cannot read your invoice and vendor data, it will recreate the silo you are trying to remove.

The honest conclusion: an ERP is necessary and not sufficient. It runs the transaction. It does not manage the contract, the renewal, the risk, or the savings around the transaction. For a mid-size company, that surrounding layer is usually where the recoverable money sits.

Frequently asked questions

Can't my ERP do everything procurement software does? For the transactional core, often yes. For contract management, renewal tracking, contract-level invoice matching, supplier risk scoring, and clean spend visibility, usually no. ERPs are built to record transactions, not to manage the contracts and relationships around them.

Will procurement software replace my ERP? No, and it should not try to. Your ERP stays the financial system of record. A good procurement platform integrates with it, adding the contract, renewal, matching, and analytics layer the ERP was not designed for.

Does procurement software integrate with Exact Online or AFAS? It should. Integration is the entire value of the model: the procurement platform reads invoice and vendor data from your ERP, enriches it, and feeds insight back. Without integration, you are adding a silo rather than removing one. ProcuHelp connects with Exact Online, AFAS, Dynamics 365 Business Central, and Moneybird.

How do I know if my ERP's purchasing module is enough? Ask what it cannot tell you. If you cannot easily see upcoming renewals, confirm invoices against contracted terms, or surface off-contract spend, those gaps are where a procurement layer pays for itself.

ProcuHelp adds the contract, renewal, and matching layer your ERP was never built for, and connects to Exact Online, AFAS, Dynamics 365 Business Central, and Moneybird so your financial system of record stays exactly where it is.

Sources: World Commerce & Contracting (contract value leakage research); Aberdeen Group (proactive contract renewal benchmarks); McKinsey (maverick spend leakage estimates).