Spreadsheet accounting: when Excel starts costing more than a system
Signs your spreadsheets can no longer handle the job: stock doesn't match reality, reports take days, several people edit the same file. How to work out what Excel really costs and what moving to a system changes.
Excel is a good tool, and almost every accounting process starts there. The problem isn't spreadsheets as such — it's the point where the workload outgrows them. That point never arrives suddenly: first there's a second copy of the file, then a reconciliation done “just in case”, then an employee who spends half a day pulling numbers together by hand. Below are the signs that this point is already behind you, and a way to work out what spreadsheets actually cost.
Six signs your spreadsheets can no longer cope
Two or three matches are enough to start thinking about it. Five or more, and spreadsheets already cost more than a system would — that expense simply isn't a separate line in your budget.
- Stock levels in the file don't match reality, and the gap only surfaces at inventory count
- Several people maintain the same file, and copies named something like “final_v2_actual” have appeared
- Pulling together a report for management takes hours or days rather than minutes
- Data gets entered after the fact — in the evening or at the end of the week, from memory and scraps of paper
- Nobody can say who changed a particular figure, or when
- There's one employee the file depends on: only they know how the formulas work
What “free” Excel actually costs
Spreadsheets look free because nobody invoices you for them. But staff time is paid for, and errors in stock levels cost you purchases and penalties. A simple way to estimate: count the hours spent handling data manually and multiply by an hourly rate.
| Done by hand | Hours per month | What it costs |
|---|---|---|
| Reconciling stock and chasing discrepancies | 16 | hours × hourly rate |
| Assembling monthly reporting | 12 | hours × hourly rate |
| Moving data between files and departments | 8 | hours × hourly rate |
| Recovering data after an error or a corrupted file | 4 | hours × hourly rate |
The hours shown are typical for a company of 20–50 people — replace them with your own. Even at those figures it adds up to roughly 40 hours a month: one employee's working week spent not on the work itself but on reconciling data. Over a year, about six weeks.
On top of that come the costs that are harder to quantify but usually trigger the decision to change something: buying stock that was already in the warehouse, a penalty over an expired document, a dispute with a counterparty where you have no data to back up your position.
What changes when you move to a system
A system doesn't solve the problem of storing data — Excel handles that. It solves four different ones.
- A single version of the data. No file copies, no question of which one is current
- A change history. You can see who entered a figure and when, and any discrepancy can be traced
- Access rights. The warehouse sees its own data, accounting sees theirs, management sees the whole picture
- Reports on demand. The data is already structured, so reporting is opened rather than assembled
One side effect rarely considered in advance: once data is entered at the moment of the operation rather than after the fact, it becomes trustworthy. That is usually the point at which it turns out the real numbers differed from the ones in the spreadsheets.
What it costs and how long it takes
The cost of an accounting system depends on the number of processes and roles, not the number of employees. Rough timelines:
| Scope | What's included | Timeline |
|---|---|---|
| A single process | Inventory or time tracking: reference data, operations, reports | 4–8 weeks |
| Several linked processes | Stock plus purchasing plus reporting, shared reference data | 2–4 months |
| A system with integrations | Data exchange with 1C, exports, mobile workplaces | from 3 months |
We quote after going through the task: in accounting systems the price is set by the complexity of the logic rather than the number of screens — how balances are calculated, what happens on a return, who is allowed to change what.
How to switch without stopping work
The main fear about switching is having to halt day-to-day operations or lose the data accumulated so far. Neither is necessary if you go process by process.
- 1Start with one process — the one where discrepancies appear most often. Usually stock or time tracking
- 2Migrate reference data and current balances from the spreadsheets. Full history isn't essential: a starting point is usually enough
- 3Run in parallel for one cycle — a month or a quarter. Spreadsheets keep going and the figures are checked against the system
- 4Retire the spreadsheets for that process once there are no discrepancies left between them and the system
- 5Add the next process, building on reference data that's already populated
When you shouldn't switch
If one person handles the accounting, volumes are low and discrepancies don't arise, spreadsheets are doing their job and custom development won't pay off. It starts to make sense when several people work with the data at once, when errors carry a real price in purchases and penalties, or when the data has to be produced on demand — for an inspection, a dispute with a counterparty, an investor.
FAQ
How is a system better than Excel if the data is the same?
The data isn't the whole story. A system gives you one current version instead of file copies, a change history, access rights per role and ready-made reporting. Excel can imitate all of it, but only while a single person works with the file.
How much does developing an accounting system cost?
The cost depends on the number of processes and the complexity of the calculation logic, so we quote after going through the task. Scope is driven not by headcount but by how many processes are automated and which systems need to exchange data.
How long does moving from spreadsheets to a system take?
A single process — 4–8 weeks of development plus one cycle running in parallel for verification. Several linked processes — two to four months. Your operations don't need to stop during that time.
What happens to the data already in the spreadsheets?
Reference data and current balances are migrated into the system. Full history is rarely transferred: more often a starting point is fixed and the old files are kept as an archive.
Could we buy an off-the-shelf system instead of building one?
If your processes are standard, an off-the-shelf product is usually cheaper and worth looking at first. Custom development makes sense when the process differs from the typical one enough that you'd have to modify the product or reshape your work around it.