ERP vs a stack of separate tools: the real cost

There is a genuine argument for building your operations from specialist tools, because each one is often better at its job than a general system's equivalent module. So why do so many growing businesses eventually consolidate?

Because the comparison everyone runs, feature against feature, measures the wrong thing. This guide shows where the real cost sits, when separate tools genuinely win, and a fair way to compare.

The cost is in the gaps, not the tools

Every boundary between two systems is a place where data has to be copied, reconciled or chased. Those hand-offs are invisible on a feature comparison and very visible in your team's week.

The joins also grow faster than the tools. Four tools have six possible connections between them; six tools have fifteen.

Key PointFeature comparisons hide the joins. Your team's week does not.

Three costs that do not appear on any invoice

Re-keying and the errors it brings

Every manual transfer costs time and carries a risk of error. The errors are the expensive part, because they surface later, usually at month-end and usually under time pressure.

No single source of truth

When two systems disagree, someone has to decide which is right. That decision is often made by whoever is most confident, and it erodes trust in every number.

Integrations that break quietly

The worst failure is not an integration that stops, because you notice that. It is one that half-works, syncing most records and silently dropping some.

Watch OutIf you cannot say when each connection last synced, and whether it worked, you have this problem. You just do not know its size yet.

The tax angle

Separate tools also matter for VAT. HMRC's VAT Notice 700/22 sets out when programs used together for Making Tax Digital must be digitally linked.

It is direct about one habit: HMRC "does not consider the use of 'cut and paste' or 'copy and paste' to select and move information, as a digital link". So a stack of tools held together by copying is not only slow; it can fall short of the VAT rules.

When separate tools genuinely win

This is not one-sided. A stack is the better shape when:

• One function is so specialised that a general module genuinely cannot do it
• You are small enough that the joins are few and manageable
• You need to move fast and cannot wait for a consolidated build
• The tools you rely on have mature, well-supported integrations, not one-off scripts

When consolidation pays off

The tipping point usually arrives when these come together: you re-key data daily, you argue about which figure is right, and you wait on reports that span more than one system.

At that point one connected system usually wins, not because it is better at any single job, but because it removes the joins. Our guides to the signs you have outgrown your accounting software and the signs you have outgrown your ERP help you check where you are.

A fair way to compare

Do not compare features. Compare the total time to a number you trust. Take one real question, such as this month's margin by product line, and count every system touched, every manual step and every reconciliation needed to answer it.

Then ask what that looks like in a connected system. Our article on why month-end should not take a week shows where that time usually goes.

Pro TipTrack re-keying time for a fortnight and add the reconciliation work at month-end. That figure is usually enough to make the decision clear.

Frequently asked

Is an ERP not just a stack of tools from one vendor?

Partly. The difference is that the modules share one set of data, so there are no joins to reconcile.

Can we keep our best tools and connect them to an ERP?

Often, yes, and it is a common middle path. The discipline is choosing which system owns each piece of data and sticking to it.

What if we consolidate and lose a feature?

It happens, so map it up front. The question is whether the lost feature costs more than the joins you remove.

See where your joins are costing you

Our free ERP Health Check asks where your system is letting you down and sends back a short report on where to focus first, with no obligation. You can also talk to our team. For independent guidance on finance systems, see the ICAEW technology resources. Microsoft describes Business Central as working with the Microsoft 365 applications you already use, such as Outlook, Excel and Teams.