Who it's for: anyone who builds, checks or presents monthly management accounts or a board pack in a SaaS or tech finance team.
What you'll get: a page-by-page layout for monthly management accounts and a quarterly board pack, a build checklist, a worked example with a reclassification journal, where AI helps, and a one-slide pitch for improving your pack.
Reading time: about 12 minutes. Have last month's pack open next to it.
Why the layout matters
Management accounts are the main way finance tells the business what happened. If the numbers are right but the pack is hard to read, people skim it, miss the point and ask the same questions in the meeting. A steady, logical layout means readers know where to look, and you spend less time each month deciding what goes where.
Key terms
- Management accounts: internal monthly financial reports for the leadership team. There's no set format, unlike statutory accounts filed at Companies House.
- Board pack: the set of papers sent to directors before a board meeting. Usually built from the management accounts plus forward-looking items.
- Budget vs actual (BvA): a comparison of what happened against what was planned, with the difference (variance) shown.
- EBITDA: earnings before interest, tax, depreciation and amortisation. A rough measure of operating profit before non-cash charges.
- Net burn: how much cash the business used in the period, after cash coming in.
- Runway: how many months the cash would last at the current burn.
- Materiality threshold: the size of variance that needs explaining. Many teams use a mix, such as more than £10,000 and more than 10%.
Monthly management accounts: the page order
A common approach is to lead with what the reader most needs, then go into detail. Most monthly packs fit in 8 to 12 pages.
| Page | What goes on it | Where AI helps |
|---|---|---|
| 1. Summary | Five to eight headline numbers, three to five bullet points on what changed, and any decisions needed | First draft of the bullets from the detailed pages |
| 2. KPIs | ARR, ARR bridge, net revenue retention, gross margin, cash, net burn, runway, headcount | Checking KPIs tie to the source reports |
| 3. P&L | Month and year to date, actual vs budget and vs last year, with variances | Flagging variances above threshold |
| 4. Variance commentary | Short reasons for each material variance, with what happens next | Drafting commentary for you to correct |
| 5. Balance sheet | This month vs last month and vs year-end, with key movements | Listing large movements to explain |
| 6. Cash flow | Cash bridge from opening to closing, linked to the forecast | Building a first-pass cash bridge |
| 7. Headcount | Actual vs budget by department, starters and leavers, open roles | Reconciling HR list to payroll |
| 8. Appendix | Department costs, aged debtors, deferred revenue roll-forward, accounting notes | Formatting and consistency checks |
Rule of thumb: if someone reads only page 1, they should still know whether it was a good month and what needs their attention.
The quarterly board pack: what's added
Board packs cover the same ground at a higher level, plus items that look forward. A typical order:
- CEO or CFO letter: one page on the quarter, in plain words.
- Financial summary: quarter and year-to-date P&L, KPIs and cash, against budget and latest forecast.
- Forecast and runway: full-year outlook, cash runway and the main assumptions behind it.
- Revenue and customers: ARR bridge, retention, pipeline (often supplied by sales, checked by finance).
- Risks and issues: what could go wrong and what's being done about it.
- Decisions and approvals: anything the board is asked to approve, clearly labelled.
- Appendix: full financial statements, department detail and any compliance items, such as filing deadlines.
The board usually wants trends and decisions, not every line. Keep the detail in the appendix so it's there if asked for.
Building the pack, step by step
| Step | What "done" looks like | |
|---|---|---|
| ☐ | Confirm the period is locked in the ledger | No postings can change the month without approval |
| ☐ | Export the trial balance and map it to pack lines | Every account is mapped; mapping total equals the trial balance total |
| ☐ | Check the account mapping for anything new | New accounts created this month are mapped to the right pack line |
| ☐ | Load budget and last year's numbers on the same mapping | Budget and prior year use the same lines as actuals |
| ☐ | Review cost classification (cost of sales vs operating costs) | Any miscoded items reclassified with a journal before the pack is built |
| ☐ | Update KPIs from their sources | ARR agrees to the billing system or ARR schedule; cash agrees to the bank reconciliation |
| ☐ | Run the tie-out checks | P&L profit agrees to the ledger; balance sheet balances; cash on the cash flow page equals cash on the balance sheet |
| ☐ | Write variance commentary | Every variance above threshold has a reason and, where useful, an action |
| ☐ | Write the summary page last | Headlines match the detailed pages |
| ☐ | Get a second-person review | Reviewer has checked tie-outs and commentary and signed off |
| ☐ | Issue on the agreed day, as a locked file | Pack sent, version number and date on the cover |
AI shortcut: give an approved AI tool this month's mapped trial balance and last month's, and ask it to list every pack line that moved by more than your threshold, with the accounts behind each movement. You get a ready-made list of what the commentary needs to cover. Check its arithmetic against the pack before relying on it.
Worked example: MonthEndClub Co Ltd, October
MonthEndClub Co Ltd is a fictional UK SaaS company. While building the October pack, the finance team spots that £6,000 of third-party tools used to run the live product (monitoring and database services) were coded to research and development. Under the company's policy, costs of running the live service sit in cost of sales.
Step 1: post the reclassification journal before the pack is built.
| Account | Dr | Cr |
|---|---|---|
| Cost of sales: third-party hosting tools | £6,000 | |
| Research and development: software subscriptions | £6,000 |
EBITDA doesn't change. Gross margin does: cost of sales goes from £80,520 to £86,520, and R&D from £216,000 to £210,000. Gross margin drops from 80.5% (£331,480 ÷ £412,000) to 79.0% (£325,480 ÷ £412,000). That's why classification is checked before the pack is built, not after.
Step 2: the P&L page (October, month only).
| £ | Actual | Budget | Variance |
|---|---|---|---|
| Revenue | 412,000 | 400,000 | 12,000 |
| Cost of sales | (86,520) | (80,000) | (6,520) |
| Gross profit | 325,480 | 320,000 | 5,480 |
| Gross margin | 79.0% | 80.0% | (1.0) pts |
| Sales and marketing | (230,000) | (240,000) | 10,000 |
| Research and development | (210,000) | (205,000) | (5,000) |
| General and administrative | (95,000) | (93,000) | (2,000) |
| Total operating costs | (535,000) | (538,000) | 3,000 |
| EBITDA | (209,520) | (218,000) | 8,480 |
Favourable variances are shown as positive, adverse in brackets. State your sign convention on the page; mixed conventions are one of the most common causes of confusion in a pack.
Step 3: the KPI page (extract).
| ARR bridge, October | £ |
|---|---|
| Opening ARR, 1 October | 4,800,000 |
| New customers | 120,000 |
| Expansion | 60,000 |
| Contraction | (20,000) |
| Churn | (40,000) |
| Closing ARR, 31 October | 4,920,000 |
| Cash | £ |
|---|---|
| Cash at 30 September | 3,200,000 |
| Net burn in October | (250,000) |
| Cash at 31 October | 2,950,000 |
| Runway at October's burn (£2,950,000 ÷ £250,000) | 11.8 months |
Net burn (£250,000) is higher than the EBITDA loss (£209,520). The pack needs a line explaining the £40,480 gap, for example the timing of VAT payments and annual renewals not yet collected. Readers notice when cash and profit tell different stories and nobody says why.
Step 4: the commentary. Short and specific:
- Revenue £12,000 ahead of budget: two mid-size customers started in early October rather than November as budgeted.
- Gross margin 1.0 point below budget: mainly £6,000 of product tooling reclassified to cost of sales this month. The budget had these costs in R&D, so the R&D line is £6,000 better than it would otherwise be. Next year's budget will show them in cost of sales.
- Sales and marketing £10,000 under budget: an event moved from October to November. This is timing, not a saving.
AI shortcut: give an approved AI tool the P&L table above plus your rough notes ("two customers early", "event moved") and ask for commentary of no more than two sentences per line, saying whether each variance is timing or permanent. Add the reasons it can't know, and check every number it quotes.
Design rules that make packs readable
- Same layout every month. Readers learn where things are. Change the layout only when there's a reason, and say so.
- One message per page. Give each page a headline that says the point, such as "Revenue ahead of budget on early starts", not just "P&L".
- Numbers in thousands for most readers, with the unit stated (£k). Full pounds only in the appendix.
- Consistent signs and colours. Pick one convention for favourable and adverse. Don't rely on red and green alone; some readers can't tell them apart.
- Charts only where they help, such as ARR over 12 months or cash runway. A table is often clearer for budget vs actual.
- Version and date on the cover. So nobody quotes from a draft.
If you report under US GAAP (ASC 606)
Management accounts are internal, so there's no prescribed layout under either IFRS / FRS 102 or US GAAP. The revenue figures in the pack follow the same underlying model under IFRS 15 and ASC 606 for most standard SaaS subscriptions. Where a US parent reports under US GAAP, packs often show a short reconciliation for any items treated differently, so group and local numbers can be compared.
Common mistakes and audit watch-outs
- Pack doesn't tie to the ledger. If the pack's profit differs from the trial balance, every other number gets questioned. Run the tie-out checks every month.
- Post-close adjustments not reflected. A journal posted after the pack is built leaves the pack out of date. Lock the period first, or reissue with a clear version note.
- KPIs from a different source each month. Define each KPI once, write down where it comes from, and stick to it.
- Commentary that repeats the numbers. "Revenue was £12,000 ahead" isn't a reason. Say why, and whether it will last.
- Classification drift. Costs moving between cost of sales and operating costs without a policy makes gross margin trends meaningless.
- AI-drafted commentary sent without checking. AI can invent a plausible reason or misquote a number. Every AI draft is checked against the pack before it's issued.
- Board data in unapproved tools. Board packs often hold sensitive plans. Only use AI tools your company has approved for this data.
Tools that can help
Many small teams build packs in Excel or Google Sheets from a trial balance export from Xero, QuickBooks or Sage. Reporting tools such as Fathom or Syft connect to the ledger and produce standard management reports and charts, which can cut down the rebuild each month. Larger teams often use NetSuite reporting or a separate planning tool. A company-approved AI assistant can draft commentary and check consistency. None of these replace the tie-out checks and a second-person review.
Take it to your boss: one slide
A management pack people actually read
The problem
- The pack changes shape each month and readers skip to the end
- Questions in the meeting are about where to find numbers, not what they mean
- Commentary is written last, in a rush
Three changes
- Fixed page order with a one-page summary up front.
- Standard tie-out checks before anything is issued.
- AI-drafted commentary from the variance list, edited and signed off by a person.
| Risk | Control |
|---|---|
| Pack doesn't agree to the ledger | Tie-out checklist signed by the reviewer |
| KPIs calculated inconsistently | KPI definitions page, one source per KPI |
| AI errors in commentary | Approved tools only; every number checked by a person |
How we'll measure it: day the pack is issued, number of corrections after issue, and number of "where is..." questions in the meeting.
Key takeaways
- Lead with a one-page summary; put detail in the appendix.
- Keep the same page order every month so readers know where to look.
- Check cost classification before building the pack, because it moves gross margin.
- Tie the pack to the ledger, bank and billing system every month, and get a second-person review.
- Commentary explains why, and whether it's timing or permanent.
- Use AI for first drafts and movement lists; a person checks and signs off.
FAQs
How long should monthly management accounts be?
Many SaaS teams aim for 8 to 12 pages including the appendix. The summary page matters more than the total length.
What's the difference between management accounts and a board pack?
Management accounts are the monthly internal report for leadership. A board pack is usually quarterly, built from the same numbers, with more on forecasts, risks and decisions for the directors.
Should the pack show budget or latest forecast?
Many teams show both once a reforecast exists: budget for accountability, forecast for the latest view. Label each clearly.
Can AI write the variance commentary?
It can write a good first draft from the numbers and your notes. It doesn't know the business reasons unless you tell it, and it can get figures wrong, so a person edits, checks and signs off every line.
When should management accounts be issued?
Commonly between working day 5 and working day 10, depending on the close. A fixed, predictable day usually matters more to readers than the earliest possible day.
Related guides
- Variance Commentary People Actually Read
- How to Build an ARR Bridge (New, Expansion, Contraction, Churn)
- SaaS Gross Margin: What Belongs in Cost of Sales
- Burn, Runway and the 13-Week Cash Forecast
More in Metrics and Reporting guides.
From the Club
Page one says it all. So does the mug. The Team Mug · The Debits Credits Done Bag
Join the Club. New guides, early access and members-only batches. Join here.
This guide is general information about common practice. It isn't tailored to any business, and standards, tax rules and figures change. Check your own circumstances, the latest rules and, where needed, a qualified professional before acting.
Last reviewed: October 2026.