Management reporting for SaaS companies: ARR, churn, NRR and burn rate (2026)

Management reporting for SaaS companies: ARR, churn, NRR and burn rate

SaaS earns per subscription and invoices in advance. The reporting that fits — from MRR bridge to deferred revenue and automation.

What makes management reporting for a SaaS company different?

Management reporting for a SaaS company differs fundamentally from other business models on three points: the revenue is recurring, invoicing runs ahead of revenue, and the value of the business sits in the movement of the subscription base — not in the result of a single month.

‍

The first point changes what “revenue” means. At a services or trading company, every month starts at zero; at SaaS, every month starts with the subscription base of the previous one. The interesting question is therefore not how much was invoiced, but how the base moved: how many new customers came in, how many existing customers expanded or contracted, and how many canceled. Those four flows — new, expansion, contraction, churn — together form the MRR bridge, the heart of every SaaS report.

‍

The second point is the difference between cash and revenue. Many SaaS companies invoice annual contracts up front: the money arrives in month one, the revenue is earned over twelve months. That is good for working capital — customers co-finance the growth — but it makes the bank balance a misleading measure. The report must keep revenue, invoicing and cash strictly apart, with deferred revenue as a separate balance-sheet item.

‍

The third point is the audience. At SaaS scale-ups especially, an investor almost always reads along next to management, and judges the business on the standard metrics of the model: ARR growth, net retention, gross margin, burn. A report written in that language avoids monthly translation work towards the board — and enforces the same sharpness internally.

‍

The foundation remains the standard structure of a good management report: summary, P&L, balance sheet, cash flow, variance analysis, KPIs and commentary. The rest of this article fills in that structure for SaaS: the KPI set, the MRR bridge, deferred revenue, group reporting with multiple entities, and automation from the accounting system.

Which KPIs belong in the management report of a SaaS company?

The management report of a SaaS company runs on five to eight KPIs, with ARR and net revenue retention at the core. This is the set that makes the difference in practice:

• ARR (or MRR) with the bridge. The size of the subscription base, always presented with the movement: new, expansion, contraction and churn. A closing figure without the bridge is not steering information.
• Net revenue retention (NRR). What the customers of a year ago are worth today, including expansion and cancellations. Above 100%, the business grows even without new customers.
• Churn. In two flavours: logo churn (how many customers leave) and revenue churn (how much revenue leaves). They tell different stories — many small cancellations is something else than one large one.
• Gross margin. Revenue minus the direct delivery costs: hosting, third-party licenses and support. Determines how much every euro of growth really yields.
• CAC payback. How many months of gross margin it takes to earn back the acquisition cost of a customer. The efficiency measure of the growth engine.
• Burn rate and runway. With loss-making growth: how much cash does the company burn per month, and for how many more months? The KPI that opens every board agenda.
• ARR per FTE. The productivity measure: does the organization scale with the revenue, or is the team growing faster than the base?
• Rule of 40. Revenue growth plus profit margin, together at least 40 — the rule of thumb investors use to weigh growth and health in one number.

Present every KPI as the main article prescribes: level, a trend of at least twelve months and the comparison against budget. Operational additions — such as activation, usage per account or the sales pipeline — can complete the set, as long as the first page stays under eight steering metrics.

How do you report ARR growth: the MRR bridge

ARR growth is reported as a bridge: opening MRR, plus new business, plus expansion, minus contraction, minus churn, equals closing MRR. Those five lines turn one growth figure into a story with causes — and with owners, because new business belongs to sales while expansion and churn belong to customer success.

‍

A worked example. A company starts the month with EUR 100,000 MRR. EUR 8,000 of new customers comes in, existing customers expand by EUR 5,000, contract by EUR 2,000 and EUR 4,000 of cancellations leaves. Closing MRR: EUR 107,000 — net 7% growth. But the bridge shows more: gross revenue churn is 4%, and the net retention of the existing base is 99% (100 + 5 − 2 − 4). The same company could reach that 7% with EUR 12,000 new and EUR 8,000 churn — the same growth on paper, in reality a leaking bucket that gets ever more expensive to refill.

‍

Three setup rules keep the bridge reliable. First: measure from the subscription administration, not from invoicing — an annual invoice in January is not twelve times the MRR. Second: fix the definitions once. When does a customer count as churned (at cancellation or at contract end), how do pauses and downgrades count, and do one-off services count in MRR? Every definition change makes the trend unusable. Third: report the bridge monthly and cumulatively for the year, so both the monthly rhythm and the bigger picture stay visible.

‍

For depth per customer group, cohort overviews work: per intake month or quarter, the retention of revenue over time. That shows whether new vintages of customers stick better or worse than old ones — the question behind every NRR movement.

How do you handle deferred revenue?

Deferred revenue is the part of invoicing that is not yet revenue: a prepaid annual contract of EUR 12,000 produces EUR 1,000 of revenue in the month of invoicing — the remaining EUR 11,000 sits on the balance sheet as an obligation to deliver twelve more months of software. Without this strict separation, reported revenue swings with the invoicing rhythm instead of with real growth.

‍

The report therefore keeps three concepts apart. Billings: what went out in invoices this period — relevant for cash and working capital. Revenue: the part earned this month, spread evenly over the contract period. ARR: the normalized annual value of the running subscriptions. The three move differently: a strong sales month with annual contracts makes billings and cash jump, while revenue and ARR follow gradually.

‍

On the balance sheet and in the cash flow statement, deferred revenue is actually the good news of the model. Customers pay in advance, so working capital works with you instead of against you: growth brings in cash before the costs arrive. Show deferred revenue as a separate balance-sheet item with a monthly trend — a falling balance at stable revenue is an early signal that less is being sold up front, for example because customers are shifting to monthly payment.

‍

Do watch the mirror side: whoever runs on annual invoices also has a real DSO. A customer who leaves a EUR 24,000 renewal invoice sitting for sixty days hits the cash position hard — precisely because the model leans on prepayment. The receivables ageing analysis therefore belongs in the SaaS report too, with renewal invoices as the point of attention.

How do you structure the management report for SaaS?

The management report for SaaS follows the seven fixed sections from the main article on the good management report — each filled in for SaaS:

1. Summary. One page with the ARR bridge as a chart, NRR, runway and the three messages of the month.
2. Profit and loss statement. In SaaS layout: revenue, direct delivery costs (hosting, licenses, support) and gross margin, then costs per function — product and development, sales and marketing, general and administrative. Show month and year-to-date next to budget and last year; one-offs separately.
3. Balance sheet. Deferred revenue as a separate item with its trend, receivables with an ageing analysis of the (renewal) invoices, and the cash position.
4. Cash flow. Operating cash flow with the billings effect visible, and with loss-making growth the burn and runway as fixed lines.
5. Variance analysis. On the ARR bridge instead of revenue alone: did the deviation come from new business, expansion or churn — and against which budget per flow? That points straight at the responsible engine.
6. KPIs. The set from this article as trends: ARR, NRR, churn, gross margin, CAC payback, burn and runway, ARR per FTE.
7. Commentary. The story: why the base moved, which churn was avoidable, how the pipeline and the runway are developing.

The functional layout also means personnel costs are not one separate P&L line but are split across the functions where people work. Because payroll is usually one collective item in the books, that split runs through cost centers; Finstack supports a dedicated mapping per cost center to divide it across the functional lines automatically.

‍

Two habits fit the scale-up character. First: do not build a separate board report — the board is the audience of the management report. One document, written in the metrics language investors use, prevents double truths and double work. Second: report the rolling twelve months next to the month, because SaaS metrics are nervous on a monthly basis — one large customer distorts a month, rarely a year.

‍

For delivery, the norm from the main article applies: within 5-10 working days after month-end, with a month-end close so figures stop shifting — and with the reconciliation between subscription administration and accounting as a fixed part of that close.

Multiple entities or international: how do you report at group level?

International growth quickly means multiple entities in SaaS: a Dutch BV holding the product and the team, and sales entities in, say, the US or the UK — often with a holding on top. For reporting, that means two levels at once: the consolidated group picture for management and investors, and the figures per entity for local steering.

‍

The internal flows make that harder than it looks. The product entity recharges development costs or license fees to the sales entities, the holding charges management fees, and the sales entities invoice the local customers. All those intercompany flows are revenue in one entity and costs in another — at group level they must cancel out, otherwise group revenue double-counts and no SaaS metric is right anymore. Currency comes on top: a base in dollars and pounds must convert to one group currency, consistently for both revenue and the ARR measurement. How elimination and consolidation work structurally is covered in consolidation for SME CFOs and the deep-dive on multi-entity consolidation.

‍

Finstack automates this for groups of 1 to 50 entities: every entity connects through its own accounting package, charts of accounts are mapped to one group chart, multicurrency administrations convert automatically to the group currency, and the engine recognizes the intercompany flows automatically — without setting up separate IC accounts. The result: a consolidated P&L and balance sheet next to the figures per entity, with every line clickable through to the source booking.

‍

For the management report this means the SaaS layout and the KPI set from this article run on both levels: per entity and for the group as a whole, without double counting — and without the month-end close having to wait for the merging.

How do you automate reporting from your accounting system?

The figures for the SaaS report come from two layers: the accounting system (revenue, costs, deferred revenue, cash) and the subscription or billing administration (MRR movements, churn, cohorts). The automation gain sits mainly on the financial side, and it can be made directly; the reconciliation between the two layers — does the MRR base match the booked revenue? — belongs to the month-end close.

‍

Dutch SaaS companies typically run on Exact Online, and internationally on Xero or QuickBooks — with a US or UK entity often side by side. Finstack connects all these packages directly via API, read-only and at transaction level: the actuals refresh automatically every day, with a manual refresh at any moment. With multiple entities, the consolidation from the previous section runs along automatically, including currency conversion.

‍

Reporting then happens wherever the team wants to work. The Finstack dashboards show revenue, costs, cash and the consolidated figures in real time, clickable through to the source transaction. The subscription metrics from the billing administration sit next to them in your own Excel or Google Sheets model: through the 2-way integration, the financial actuals refresh in that same model in one click, so the MRR bridge and the P&L come from one workbook. You can also share dashboards and reports with stakeholders such as management, investors and the accountant, by giving them access to Finstack, with access rights set per user.

‍

The effect on the rhythm: the financial side of the management report is ready on day one instead of after days of collecting, and the time shifts to the analysis of retention, growth efficiency and runway. Finstack starts from EUR 39 per month for the first entity: live in 5 minutes, set up within a day.

The 3 most common mistakes in SaaS reports

Three patterns we see again and again at SaaS companies. Each distorts the picture for management and investors; each is preventable with the right setup.

Sources and provenance

• Finstack — Reporting & insights (dashboards, Excel/Sheets sync): finstack.io/solutions/reporting-insights
• Finstack — Integrations with Exact, Xero, QuickBooks and other packages: finstack.io/solutions/integrations
• Finstack Help Center — Sources & connections (sync frequency, security): help.finstack.io
• Finstack — Pricing (from EUR 39/month): finstack.io/pricing

Last reviewed: 25 July 2026 · Next review: October 2026