ERP or Simple Accounting Software? The Criteria That Actually Decide

This is written for the managing director with a system quotation on the desk, and for the finance manager who has to say whether the spend is justified. The aim is to move the decision away from which brand is better, and towards three sharper questions: what is broken today, what does integration actually fix, and what is the full cost of the change.

The real difference is scope, not reporting

Accounting software records a financial event after it happens: a voucher is entered, the ledger updates, reports are produced. An integrated system runs the operating process as it happens — requisition, purchase order, goods receipt, production, sale and return all live in one database, and the accounting entry is their by-product.

The consequence fits in one sentence: in the first model the accountant re-enters data; in the second, data is captured once at the point it occurs. Wherever you see re-keying, you are looking at a primary source of error and delay.

The criteria that actually decide

• Number of data-generating points. If purchasing, stores, production and sales each produce independent data and someone must stitch it together, you need integration.
• Costing complexity. Job-order or multi-stage production with variable wastage is not controllable without a costing module. The logic is in production costing.
• Need for control before the fact. If you want purchases blocked without approval, or sales blocked to an overdue customer, you need workflow, not reports.
• Multiple entities or branches. Consolidating several sets of books in spreadsheets costs more over time than a system does.
• Item volume and variety. Several thousand SKUs across multiple warehouses is the practical ceiling of simple packages.

Total cost of ownership

Take the last line seriously. In the projects I have watched closely, the real cost was the months in which the finance manager and the stores supervisor sat in implementation meetings while their own work fell behind.

Signals that it is time to upgrade

1. The monthly close takes more than two weeks.
2. System stock chronically disagrees with physical counts.
3. One figure — monthly sales, say — appears differently in two reports.
4. Pricing decisions rest on a mental estimate of cost.
5. Key information lives in employees' personal files and leaves when they do.
6. The number of bridging spreadsheets exceeds the number of system reports.
7. Answering a simple management question takes several people several days.

Three or more of these and integration really is your problem. Only number three, and your problem is coding and entry discipline.

The middle path

Between a single-user accounting package and a full ERP lies a wide range of integrated finance and trading systems covering purchasing, sales, inventory, treasury and payroll with optional modules. For a large share of mid-size companies this level is sufficient, at far lower cost and risk.

Decision checklist before signing

1. Write down today's three main problems and mark which are solved by software and which by process change.
2. Draw your current purchasing, inventory, production and sales flows; if you cannot, you are not ready to implement.
3. Assess master data quality: items, customers, suppliers, opening balances.
4. Demand a demo run on your own data, not the vendor's sample set.
5. Speak to three current customers in a similar industry about post-go-live support.
6. Budget three-year total cost, not purchase price.
7. Put data ownership, export formats and future migration rights into the contract.
8. Set a realistic timeline with a pilot phase and a parallel run.
9. Name an internal project owner; projects without one fail.
10. Write the migration and balance-validation plan in advance — see migrating data to new software.

If you decide not to upgrade yet

Staying put is a sound decision provided you do three things: fix the chart of accounts, write down and standardise entry procedures, and build monthly management reports from the data you already have. Many companies have deferred a system change by years on the strength of those three steps alone.

Key takeaways

• The ERP difference is scope and where data is captured, not report count.
• Decide on process complexity and data-generating points, not headcount.
• Licence price is a small share of total cost; manager time is the biggest hidden item.
• An integrated system will not fix a broken process, only accelerate it.
• A phased path is the lowest-risk route for most mid-size companies.