Seven signs your business has outgrown its accounting software

1. Your month-end close is measured in weeks

A close that runs past day ten is usually not a discipline problem. It is a reconciliation problem — sub-ledgers that do not tie, inventory valued in a spreadsheet, intercompany entries assembled by hand. When the close depends on one person's workbook, the software has stopped being a system of record.

2. The real numbers live in spreadsheets

Ask where the management pack comes from. If the answer is an export plus four spreadsheets plus a person, you are paying for an accounting package and running a spreadsheet ERP alongside it. The spreadsheet is the actual system; it just has no audit trail, no access control and no backup discipline.

3. Inventory on the screen and inventory on the shelf disagree

Persistent variance you investigate but never eliminate usually means transactions are recorded after the fact rather than at the point they happen. That is a capture problem — it wants barcode capture at the shelf, which needs a system that can accept it.

4. You cannot answer "what did this job actually cost?"

If gross margin is only knowable at company level and not per job, product, customer or site, you are flying on aggregate. Businesses in this state routinely discover, on getting dimensional reporting for the first time, that a meaningful slice of revenue is loss-making.

5. Approvals happen in chat

Purchase approval by group chat message works until an auditor asks for the approval trail, or until someone approves something they should not have. An enforced approval matrix is not bureaucracy — it is the control that lets you delegate spending safely.

6. Adding an entity or a location is a project

If opening a second registered company or a third warehouse means another instance, another chart of accounts and a manual consolidation, the system is capping your structure. Growth decisions should not be constrained by bookkeeping architecture.

7. A compliance change would take months

This is the current one. BIR EIS requires structured JSON, digital signing and system-to-system transmission within three days. If your reaction to that is "our software cannot do that and the vendor has no roadmap," the compliance deadline has just become an ERP deadline. See the four-question checklist for whether it applies to you.

Three signs that are not ERP problems

Replacing software will not fix these, and doing so is expensive:

• Nobody follows the process. A new system enforces process, but only where the process was agreed. Undefined processes produce the same chaos on better software.
• The data is wrong. Migration moves data; it does not clean it. Bad master data arrives intact on day one.
• One person is overloaded. Sometimes the answer is a hire, not a licence. Automation helps when the work is repetitive and rule-based — not when it needs judgement.

Questions to ask before you shop

What a realistic timeline looks like

A single-entity scope on Business Central goes live in 10 working days with BC-KickStart, because roughly 70% of the configuration is pre-built. Multi-entity, manufacturing or heavy integration work is phased over longer. The variable is not the software — it is how much of your operation is genuinely unlike everyone else's.

If you want a concrete read rather than a sales call, the 5-minute assessment maps how your business runs to the modules that fit it and shows the result on screen.