Statutory vs Management Accounts: Two Mappings, One Xero Ledger
Your board pack and your statutory accounts don't need to match line for line. But you do need to be able to explain the difference.
The finance manager sends the board pack on the 8th. People costs are 31% of revenue. Three months later the auditors' draft statutory accounts land, and the board notices that "cost of sales" has gone up while "people costs" never appeared at all. Nobody did anything wrong. The same wages accounts were simply grouped two different ways, by two different files, and nobody could show how one turned into the other.
That's the gap between statutory vs management accounts. They come from the same Xero ledger and should arrive at the same profit, but they group the accounts for different readers. The fix isn't a better layout. It's two independent mappings over one ledger, checked against each other every time they run.
Why management accounts ≠ statutory accounts in more detail
It's tempting to treat management accounts as a more granular version of the statutory P&L. They aren't. They answer a different question.
Statutory accounts follow the accounting standards. Under IFRS, SFRS(I), FRS 102 and their cousins, expenses are classified by function (cost of sales, distribution, administrative expenses) or by nature, with finance costs and tax shown separately. The reader is a shareholder, a lender, a tax authority or an auditor, once a year.
Management accounts follow how the business is run. Expenses sit where someone is accountable for them: people costs, occupancy, marketing, technology. Revenue might be shown net of card fees and delivery commissions. EBITDA, contribution per outlet and prime cost appear because the board steers by them. The reader is the owner or the board, every month.
Here's how the same five accounts might land in each view (invented, as always):
| Xero account | Management view (Tier 1 → Tier 2) | Statutory view (Line → Note) |
|---|---|---|
| Wages – Kitchen | People costs → Kitchen labour | Cost of sales → Direct labour |
| Wages – Head office | People costs → Central staff | Administrative expenses → Staff costs |
| Card processing fees | Net sales → Payment fees | Administrative expenses → Bank charges |
| Depreciation – Fit-out | Below EBITDA → Depreciation | Administrative expenses → Depreciation |
| Bank loan interest | Below EBITDA → Interest | Finance costs → Interest on borrowings |
Neither column is wrong. Each one is a complete, two-level map of the same accounts. And both have to add up to the same net profit.
What Xero gives you for statutory vs management accounts
Xero has more here than people expect, which is part of why the problem sneaks up.
Report codes give you one default hierarchy. Where your region has them, every account carries a report code that decides where it appears by default in Xero's financial report layouts. Many accounts can share a code, which is a grouping. But it's Xero's list of codes, not yours, and each account has one. When users asked to define their own report code structure, Xero's community manager replied in July 2025 that a fully bespoke solution "is not in the pipeline".
The layout editor gives you a second view, per report. You can regroup accounts, add formula rows and save the result as a custom report. That's a genuine management view, and for one organisation with a stable chart it can be enough. We walked through it in Xero custom reports: 4 ways to build them.
But a layout is an arrangement, not a mapping. The grouping lives inside a saved report. The P&L and the balance sheet are arranged separately, and a monthly pack and a year-to-date pack may each carry their own copy. There's no single table that says "this account goes here in the board's view and there in the statutory view", so nothing to review, version or hand to an auditor.
Saved layouts don't reliably follow the chart. Users on Xero's ideas forum report that custom reports don't update when the chart of accounts changes: a moved account still shows in the old place, a new one has to be added by hand. A new account landing in one view's default section and not the other is exactly how two views start to drift.
Nothing reconciles one view to the other. Two saved layouts can both be internally consistent and still disagree, because one dropped an account or picked up a reclassification the other didn't. Xero won't tell you.
Tracking categories are a different axis. They split transactions by department or outlet; they don't regroup accounts. Useful inside a management view, and limited to two active categories, as we covered in the tracking category limit.
The method: two independent mappings over one ledger
The build we use is simple to describe and fiddly to get right.
- Pull the trial balance once. Every account, every period you need, from Xero. One set of numbers feeds everything.
- Keep one account map with both views side by side. One row per account. Columns for the management Tier 1 and Tier 2, and separately for the statutory line and note. Each view is complete on its own; neither is derived from the other.
- Render each view from its own columns. The board pack reads the management columns. The statutory schedules read the statutory columns. Neither layout knows the other exists.
- Prove both views tie to Xero. Each view's net profit equals Xero's net profit for the period, and each balance sheet balances. Every run, not at year-end.
- Reconcile the views to each other by line. Management EBITDA to statutory operating profit, with every difference named: depreciation, interest, a management-only accrual.
The independence matters most. In one group pack we built, the account map already carried a chart-of-accounts tier, management tiers and a statutory layout as separate columns. When the group's lender asked for figures arranged a third way, that became another pair of columns in the same table. The board pack, which the directors had read in the same shape for years, didn't move a line.
Where the difficulty actually lives
Every new account needs a home in both maps
The single most common failure is an account that's mapped in one view and not the other. A bookkeeper adds "Wages – Weekend casuals" in March. The management view picks it up because someone remembered; the statutory schedule doesn't, and the gap surfaces at year-end as an unexplained difference.
The fix is mechanical. Every run lists any account with activity that's missing a mapping in either view, with the amount. For a multi-outlet operator we report for, that's an unmapped block at the foot of every tab, signed so that net profit plus the unmapped total always equals Xero's net profit. A blank is visible the month it appears, not the month someone asks why the numbers are light.
Some accounts sit on the wrong side of their section
An exchange gain booked to an expense account, or a tax recovery posted in an income-natured section. In one view it sits comfortably; in the other it lands in a section of the opposite sign and, added naively, increases a cost it should reduce.
Keep the sign explicit. A sign column in the map (1 or −1), or a nature carried by each section, means the view adds the account the right way round. And because the views tie to the same net profit every month, a sign error shows up as a difference straight away instead of hiding inside a subtotal.
Some differences aren't mapping at all
Regrouping can't explain everything. Management accounts might accrue a bonus monthly where the statutory accounts book it at year-end. They might show rent as a cash cost where the lease standard turns it into depreciation and interest. These aren't the same accounts grouped differently; they're different numbers.
Don't hide them in the map. Book them as named management adjustments, shown on their own lines in the reconciliation between the two views. The board sees "statutory operating profit, plus bonus phasing, plus lease adjustment, equals management EBITDA", and an auditor can follow it.
The management layout has formula lines the ledger doesn't
Net sales after payment fees, prime cost, EBITDA, labour as a percentage of sales. These are calculations on mapped lines, not accounts. For one multi-outlet operator the management structure lives in a config sheet: a Mapping tab that sends each account to a section and subsection, and a Structure tab that lists the lines in order, with formula rows referring to other lines by name. Changing a KPI definition is an edit to one row, not a rebuild, and the statutory side is untouched. We go further into those calculations in the Xero KPI dashboard.
The statutory view will change under you
Standards move. IFRS 18, effective for annual periods beginning on or after 1 January 2027 where it applies to you, sorts the P&L into operating, investing and financing categories, adds required subtotals, and asks for any management-defined performance measure used in public communications to be reconciled to them. That's a new statutory map, not a new chart of accounts. With independent mappings, it's new columns. With one shared layout, it's a fight over whose lines win.
Codes or names
A map keyed on account codes survives a bookkeeper tidying up names; a map keyed on names catches a code that's been reused for something else. Either works if the unmapped check runs every time. We weighed the trade-off in multi-entity Xero reporting, where several charts of accounts make it sharper still.
What a reliable build looks like
- One ledger pull. Both views come from the same trial balance, fetched once per run.
- One account map, two independent views. Two levels each, side by side, owned by named people: management by the FD, statutory by whoever prepares the accounts.
- No orphans. Any account with activity and no mapping in either view is listed, with its amount, on every run.
- Explicit signs. Accounts that sit against their section's nature are flagged in the map, not fixed in a formula.
- Two tie-outs. Each view agrees to Xero's net profit and balance sheet for every period shown.
- A bridge between views. Management EBITDA reconciles to statutory operating profit, with mapping differences and management adjustments on separate, named lines.
- Room for a third view. A lender covenant pack, an IFRS 18 layout, a parent's group reporting format: each is another set of columns, not a change to the existing two.
Where Cheetah fits
Cheetah builds custom reports on Xero, and this pattern runs through a lot of them: a board pack, a statutory schedule and sometimes a lender view, all from one account map kept in a sheet you can edit. We set up the map with you, build the unmapped checks and tie-outs, and add the bridge between views so the question "why doesn't the board pack match the accounts?" has a one-page answer. Reports arrive as a Google Sheet with an Excel download and refresh from Xero on a schedule.
If your management accounts and statutory accounts are maintained in different files by different people, Cheetah is worth a conversation. For what a full management pack should contain, see management accounts from Xero.
The short version
Statutory vs management accounts isn't a choice of detail. It's two complete groupings of one ledger, for two different readers, and they drift apart the moment they live in two layouts. Xero gives you one default hierarchy and saved layouts per report, but no mapping that holds both views and no check that they agree.
Keep one account map with independent columns for each view, list every unmapped account on every run, tie both views to Xero, and bridge them line by line. For the ways to build the reports themselves, see Xero Custom Reports: 4 Ways to Build Them in 2026.
Frequently asked questions
- What is the difference between statutory accounts and management accounts?
- Statutory accounts are the annual financial statements the law requires, laid out the way the accounting standards say: cost of sales, distribution costs, administrative expenses, finance costs. Management accounts are monthly internal reports laid out the way the business is run: people costs, occupancy, marketing, contribution by outlet, EBITDA. Both come from the same ledger and should arrive at the same net profit. They group the accounts differently.
- Can Xero produce a statutory view and a management view of the same accounts?
- Partly. Xero's report codes give each account one default position, and the layout editor lets you regroup accounts in a saved custom report, so you can keep one layout for each view. What Xero doesn't give you is a mapping table that holds both views side by side, a check that every account lands somewhere in both, or a reconciliation between the two. Xero said in July 2025 that user-defined report codes are not in the pipeline.
- Should management accounts reconcile to the statutory accounts?
- Yes. Both views are built from the same trial balance, so their net profit should agree for the same period. Where management figures differ on purpose, for example a monthly bonus accrual or rent shown as a cash cost, the difference should appear as a named reconciling item rather than be buried in a regrouping.
- Why keep two mappings instead of changing the chart of accounts?
- Because each view changes for different reasons. The board wants a new KPI line; the auditor wants a reclassification; a new accounting standard such as IFRS 18 changes the statutory categories. If both views hang off the account names or one layout, every change to one risks breaking the other. Two independent mappings over one ledger let each move on its own.
A finance professional turned product builder, Jarvin has built hundreds of reports by hand and knows what financial and operational reporting demands: customisability, auditability, scalability, and security. Having automated that work reliably, he's now helping advisory firms and finance teams do the same.
