Xero Budget vs Actual Reports: Why the Native One Falls Short (And What Good Looks Like)
Two columns, one variance, a lot of quiet frustration.
Every month, somewhere in the world, a finance manager opens Xero, runs the Budget vs Actual report, stares at it for ten seconds, exports it to Excel, and rebuilds the whole thing by hand. I've watched this happen more times than I can count.
The native report isn't broken. It's just not enough. Once you need anything beyond "here's the budget, here's actuals, here's a variance column," you run out of road very quickly.
This post is about why that happens — and what a Xero budget vs actual report should actually look like if it's going to be useful for running a business.
Where Xero's native budget vs actual report stops being useful
Xero gives you a Budget Manager, and a Budget Variance report. That's it. For basic check-ins it's fine. But for actual management reporting, a few limits bite fast:
You can only compare against one budget at a time. No scenario comparison. No "budget vs reforecast vs actuals" side by side. If you run a rolling forecast, you're going to be exporting.
The layout is the P&L layout. You can't regroup accounts, add calculated rows like Gross Profit % or EBITDA margin, or insert subtotals where they actually make sense for your business. You're stuck with the chart of accounts' order.
Tracking categories don't play nicely with budgets. You can build budgets per tracking category, but reporting variance across a whole portfolio of locations or divisions gets clunky fast — and consolidating those views into one report is a manual job.
No variance commentary. Every real management pack has a "Why?" column. Xero's report doesn't have a place for it, so people paste the report into a Google Doc or Word doc and write commentary there. Now you have two artifacts that need to stay in sync.
No YTD budget vs YTD actual vs full-year forecast in one view. This is the view most boards want. You have to stitch it together.
Multi-entity? Forget it. If your group has three entities on Xero, you're running three separate budget vs actual reports and reconciling them in a spreadsheet.
None of this is a dealbreaker for a simple business. But the moment someone — a CEO, a board, an investor — asks a real question about variance, you're back in Excel.
What a good Xero budget vs actual report actually looks like
Over the years I've built and rebuilt dozens of these. The good ones share a handful of traits:
1. A layout that matches the business, not the chart of accounts. Revenue grouped by stream. Cost of sales broken down the way operators actually think about it (ingredients, packaging, delivery commissions, etc. in F&B — or COGS by category in retail). Opex grouped by function — people, premises, marketing, tech — not alphabetically by account name. Gross profit, contribution margin, EBITDA as calculated rows with the margin shown in the next column over.
2. Multiple comparison columns that make sense together. At a minimum: Current month actual, current month budget, variance $, variance %. Then YTD actual, YTD budget, YTD variance. Then full-year forecast vs full-year budget. Twelve columns done right is more readable than six columns done wrong.
3. Variance thresholds and flagging. Not every variance matters. A good report surfaces only the lines that moved meaningfully — say, anything more than 10% or $10k off budget — and leaves the noise alone. Colour, a flag column, whatever works. The point is the eye should land on what matters.
4. A commentary column that lives with the numbers. Not in a separate doc. The "why" belongs next to the variance it's explaining. When the numbers update, the commentary column stays put so you can update it in place.
5. Multi-entity consolidation with eliminations. If your group has three entities, you want one consolidated budget vs actual, not three reports. Inter-company transactions eliminated. FX translated if relevant. Tracking categories rolled up or filtered however the reader needs it.
6. A rolling forecast view. Budget is a once-a-year thing. Forecast should update monthly. The best budget vs actual reports quietly become rolling forecast reports — actuals for the months that have closed, forecast for the months that haven't, and a running comparison against the original budget so you can see how the year is drifting.
7. Tracking category slicing. Budget vs actual by location. By department. By revenue stream. Same report, different cut. Not three reports glued together.
8. Drillable to the source. A variance is a question, not an answer. Good reports let you click through from the line to the transactions that moved it. If someone has to ask "why is payroll $23k over?", the answer should be one click away, not a half-day investigation.
Why most finance teams settle for less
Because building all of the above takes real time, and the people most equipped to build it are the same people who should be doing judgment work instead of formula plumbing.
I wrote about this a while back in What I Learnt Building 100+ Reports by Hand — the infrastructure of a good report (data layer, logic layer, output layer) is almost always underinvested in. Finance teams end up with a fragile spreadsheet that only one person understands, breaks when the chart of accounts changes, and quietly rots over the course of a year.
So the compromise ends up being: run the native Xero report, manually paste it into the "nice" template, add the commentary by hand, and do it all over again next month. Three to five hours a client or entity, every month, forever.
The Cheetah way
Cheetah is effectively that "nice" template, except the pasting is automated. We pull from the Xero programmatically, apply your group's logic (whatever the grouping, whatever the calculated rows, whatever the consolidation rules), and output a Google Sheet on demand. The sheet is auditable — every cell traces back to the transactions that built it — so finance teams don't lose control of the numbers.
The point isn't that Cheetah is the only way to get a decent budget vs actual report out of Xero. You can build it yourself in Excel, or use Fathom, or Syft, or Spotlight — all of which have their place. The point is that whichever path you pick, the eight traits above are what you should be measuring the output against. If your current report doesn't have most of them, you're leaving insight on the table every month.
If you're one of the finance managers rebuilding budget vs actual by hand every month, Cheetah is probably worth twenty minutes of your time. And if not, at least steal the checklist.
Related reading: Management Accounts from Xero: What They Should Look Like (And Why They Rarely Do) and Creating Custom Reports from Xero in 2026.
Jarvin is a product builder who's spent years deep in the worlds of finance and software. From his years of building reports manually, he understands the unique needs of businesses in financial and operational reporting – security, auditability, scalability, and most importantly, customisation.
He has built hundreds of the most complex reports the hard way, figured how to automate them reliably, and is now on a mission to help businesses and advisory firms do the same.