Compared with Excel consolidation
Consolidating Xero entities in Excel vs using software
30 August 2026Draft — noindex, not in sitemap
Excel is the right answer for a small, stable, single-currency group, and stops being the right answer once entities are added and removed regularly, currencies are involved, or more than one person needs to trust the output. That is a narrower boundary than most software vendors will tell you and a wider one than most spreadsheet-committed controllers will admit, and the deciding factors are structural rather than about time saved.
When is Excel genuinely the better choice?
Excel wins when four conditions hold together.
The group is small and structurally stable — around three to five entities, with no acquisitions or closures expected this year. Every entity reports in the same currency. Intercompany activity is light or absent. And one person owns the workbook, understands it fully, and is not going anywhere.
Under those conditions a spreadsheet consolidation is fast, transparent, free, and completely auditable by the person running it. There is no integration to maintain, no vendor dependency, no monthly cost, and no data leaving your control. A controller who has built a clean workbook and reconciles it every month is producing correct numbers, and switching them to software buys very little.
It is worth saying plainly, because most comparison pages on this topic are written to reach the opposite conclusion regardless of the facts. If your group looks like the description above, you probably do not need to buy anything.
What actually breaks first?
Structural change breaks a spreadsheet before volume does. A workbook built around a fixed set of entities has that set encoded in ranges, formulas and tab references, and every acquisition, closure or migration violates the assumption.
The failure is undramatic, which is what makes it dangerous. An entity is added and the summary sheet keeps summing the old range, so the group total quietly excludes it. Nobody sees an error because there is no error — the arithmetic is correct on the wrong inputs. It surfaces a quarter later when someone reconciles a total that has never been questioned before.
Currency is the second break point. Once translation is involved, you need average rates for the P&L, closing rates for the balance sheet, a translation reserve absorbing the difference, and — the part that is almost never built into a workbook — the rates stored against the period they were used in, so a restatement reproduces. A spreadsheet pulling live rates will produce a different September every time September is re-run.
Key-person risk is the third. A workbook that only one person fully understands is a business continuity issue disguised as a productivity one, and it typically becomes visible at the worst possible moment.
Is the time saved the real argument?
Not usually, despite it being the headline every vendor leads with. The industry figures quoted for manual consolidation — hours per entity, closes stretching from five days to fifteen — trace back to a small number of vendor-published claims that cite each other, and the most-cited independent benchmark is a self-reported survey now around nine years old.
The honest version is that time savings are real but modest for a small group and only become compelling at scale. If you have four entities and a workbook that works, you are not losing days a month.
The stronger argument is about confidence rather than speed. A spreadsheet consolidation produces a number. It does not readily tell you which entities contributed to a movement, whether an account went unmapped this month, whether an entity is still posting into a period you closed six weeks ago, or whether the same figure would reproduce if you re-ran it. Those questions get answered by hand, if they get asked at all.
That is the actual trade: not hours, but whether you can interrogate the number you just published. Our guide on measuring when a close actually finished covers one version of that question in detail, and the method works in a spreadsheet too.
What does software not solve?
Software does not fix a chart of accounts nobody has mapped, and it does not make judgements for you.
Mapping still has to be done and maintained. New accounts appear every month in every entity, and a tool that maps them automatically is guessing. The work moves from re-doing the mapping each period to maintaining it once, which is a genuine improvement and not the same as elimination.
Acquisition accounting stays manual. Purchase price allocation, goodwill, impairment testing, non-controlling interests — none of these can be derived from Xero data, because the inputs are not in the ledger. Any tool claiming to automate them from your Xero organisations is overselling.
And intercompany eliminations vary considerably between products. APBuddy Reporting does not currently perform automated eliminations — it is on our roadmap, not in the product today. If your group has material intercompany trading and needs statutory consolidated accounts rather than management reporting, that is a genuine gap and you should evaluate tools that do it now. Several established Xero consolidation products handle eliminations, and we would rather you knew that before a trial than after one.
How do the two approaches compare on the things that matter?
| Excel | Reporting software | |
|---|---|---|
| Cost | None beyond time | Monthly subscription |
| Transparency | Complete, if you built it | Depends on whether the tool shows its workings |
| Adding an entity | Manual rework, easy to get silently wrong | Connect and map |
| Multi-currency | Possible, rarely done correctly | Usually built in |
| Rate reproducibility | Almost never built | Should be — verify it |
| Drill-down to entity | Manual | Expected |
| Intercompany eliminations | Manual either way | Varies by product |
| Acquisition accounting | Manual | Manual |
| Key-person risk | High | Lower |
The rows that decide it for most groups are adding an entity, multi-currency, and drill-down. The rows people expect to decide it — cost and time — rarely do.
How should you actually decide?
Ask three questions about the next twelve months rather than the last one.
Will your entity list change? If you expect an acquisition, a closure or a migration, the maintenance cost of keeping a workbook correct across that change is the cost you are really weighing, and it is concentrated in exactly the months you have least capacity.
Will more than one person need to rely on the output? A workbook that one person trusts is different from a report a board relies on. The second needs to be reproducible by someone other than its author.
Can you currently answer “why did this move?” without rebuilding anything? If a group figure changes and you cannot expand it to the entities behind it within a few minutes, you are producing numbers you cannot defend under questioning, whatever tool generated them.
If all three answers are comfortable, stay in Excel. Genuinely. The worst outcome here is a group that buys software, keeps the spreadsheet running alongside it because nobody trusts the new numbers yet, and now maintains two consolidations instead of one.