Four symptoms reliably indicate the system is the constraint
A critical spreadsheet, duplicate data entry, a close slower than the period's relevance, and growth requiring proportional administrative hiring.
Dynamics 365 Business Central · Small & Mid-Market
The mid-market ERP decision
Nobody outgrows their accounting package on a particular Tuesday. It happens through a series of individually sensible workarounds until the workarounds are the process.
Abstract
The mid-market ERP decision
Summary
The difficulty in the mid-market ERP decision is knowing whether you have crossed the line, because from inside it always looks like you are one spreadsheet away from being fine.
This paper sets out four symptoms that reliably indicate the system has become the constraint, two that are commonly mistaken for it, and the scoping principle that determines whether a mid-market implementation succeeds — which has almost nothing to do with the product selected.
Key findings
Four things this paper argues
If you read nothing else, read these. The analysis that follows sets out the evidence for each.
Two common triggers are not symptoms
System age and reporting frustration. Replacing an ERP to fix a report is a very costly route to a dashboard.
Scope determines success more than product selection does
The common mid-market failure is a programme so large it produces nothing for a year, by which point the sponsor has lost patience.
The reconciliation test is the honest measure of a migration
If the new system cannot reproduce a period you have already closed and signed off, the migration is not finished.
Analysis
The argument in full
The four symptoms
A spreadsheet has become critical infrastructure. Pricing, stock, scheduling or forecasting runs in a workbook one person maintains, and everybody knows it is fragile.
The same data is entered more than once. An order goes into the quoting tool, the accounting system and the shipping platform, and reconciling them costs more than the entry did.
Month end takes longer than the period it describes remains relevant. By the time management accounts arrive, the decisions they should have informed have been made.
Growth requires proportional administrative hiring. Every additional ten clients seems to need another coordinator, which caps the business at whatever headcount it can afford.
The two that are not
System age. Plenty of businesses run perfectly well on unfashionable software that does exactly what they need. Replacing something because it looks dated is an expensive aesthetic decision, and it is more common than owners admit.
Reporting frustration. It is real, and it is frequently a data or process problem rather than a system problem. We have seen several businesses propose an ERP replacement to solve a reporting complaint that turned out to be a chart of accounts and a dimension design issue, resolvable in weeks.
- A critical spreadsheet everybody knows is fragile
- The same data entered into more than one system as routine
- A close that outlasts the relevance of the period it describes
- Growth requiring administrative hiring in proportion
- Not: system age, and not: a report somebody wants that they cannot get
Scoping so phase one pays for phase two
The most common mid-market ERP failure is not technical. It is a programme scoped so large that it consumes a year before producing anything, by which point the sponsor has lost patience and the business has lost interest.
A first phase that solves a specific, visible problem and proves itself changes the risk profile entirely. The organization gets a return before it commits further, and the second phase is authorised on evidence rather than on faith.
A supplier who cannot propose that structure is optimising for their own revenue rather than your outcome, and it is a reasonable question to ask directly during selection.
Framework
Something you can apply without us
Every paper in this series ends with a framework you can run internally. We would rather you used it and reached your own conclusion than took ours on trust.
Framework
The mid-market decision
Five steps from symptom to signed-off migration.
1
Diagnose
Test against the four symptoms. If only age or reporting applies, the answer is probably not ERP.
2
Quantify
Cost the workaround estate — the spreadsheets, the duplicate entry, the close effort.
3
Scope
A phase one that solves a visible problem and proves itself before phase two is commissioned.
4
Design
Dimensions and posting groups before go-live. Adding a global dimension afterwards means reprocessing history.
5
Reconcile
Reproduce a closed, signed-off period. Until that works, the migration is not finished.
Implications
What this means, depending on your seat
The same argument lands differently across an executive team. These are the three versions worth separating.
References
Where to check this for yourself
Microsoft's own documentation for the product behaviour described above. We would rather you verified the basis than accepted our summary of it.
01
Dynamics 365 Business Central documentation
02
Work with dimensions
03
Financial reports and account schedules
04
Data migration to Business Central
05
Dynamics 365 2026 release wave plans
On these references: each entry names a Microsoft Learn article or documentation area by title, because deep links change while titles are stable. Searching the title on learn.microsoft.com will reach the current version. Where we have cited a figure or a product behaviour, it is Microsoft's statement rather than ours; where we have given a number of our own it is labelled as such in the text.
Recognise the situation?
Send us a chart of accounts, an item list and a month of transactions. We will configure a demo with your own data and walk your finance lead through their own month end — including if it tells you not to change.
Discuss this paper Run the related checklist We reply to every message within one business day.
Keep reading
Related papers
The insurability of the mid-market
Insurers have quietly become the most effective security auditors in the mid-market. This paper examines what they ask, why, and what it means for how you prioritise.
July 5, 2026 · 13 pages · 14 min readRead
Build or buy the IT function
The instinct is to hire. It is not always right, and the reasoning matters more than the conclusion.
January 11, 2026 · 11 pages · 12 min readRead
The cost of not finding things
The cost is invisible because it is distributed: a few minutes per person per day looking for things, and nobody adds it up.
January 4, 2026 · 10 pages · 11 min readRead