KPIs in management reporting: choosing, presenting and maintaining the right set (2026)

KPIs in management reporting: choosing, presenting and maintaining the right set

From the classic financial core to business-model-specific steering numbers — and the choice between dashboard and report.

What are KPIs in management reporting?

KPIs (key performance indicators) in management reporting are the steering numbers that summarize how the business is performing: a compact set that tells management and investors at a glance whether things are on course — and where correction is needed.

‍

The difference with the P&L and the balance sheet is compression. The financial statements show all figures in their context; the KPI section distills the handful of numbers that are actually steered on. A good KPI is therefore not an arbitrary metric, but a number with three properties: it is influenceable (someone can do something about it), it has an owner (someone is responsible for it) and it is tied to the earnings model (when this number moves, the result moves with it).

‍

In the structure of a good management report, the KPI section is the sixth of the seven fixed sections, between the variance analysis and the commentary. That place is logical: the KPIs summarize what the preceding sections showed in detail, and the most striking movements get their story in the commentary right after.

‍

The section’s pitfall is inflation. KPI lists grow by themselves — every meeting adds one, none ever removes one — until the section has become a second book of tables. This article therefore covers not just which KPIs belong in it, but above all how to keep the set small, consistent and meaningful: first the financial core and the business-model choice, then the presentation, the choice between dashboard and report, the maintenance of the set and the automation.

Which KPIs belong in every management report?

Every management report — regardless of business model — runs on a financial core of six to eight numbers. This is the set that carries the first page in practice:

• Revenue growth. Against budget and the same period last year — the first question of every reader.
• Gross margin. The percentage that tells whether the earnings model is intact; the first place where price pressure and mix shifts become visible.
• EBITDA or operating result. The profitability of the operation, as an amount and as a percentage of revenue.
• Working capital. How much capital the business holds in receivables, inventory and payables — and whether it grows with revenue or beyond it.
• DSO and DPO. How fast customers pay and how fast the business itself pays: the two dials that directly influence working capital.
• Cash position and credit headroom. Today’s balance plus the room that is left — the KPI that determines how much time the business has to adjust course.
• Personnel costs as a percentage of revenue. For most SMEs the largest cost item — and the first to fall out of step in growth or contraction.

The guideline from the main article applies in full: at most eight numbers on the first page. Whoever wants to show more moves the rest to an appendix — the core must be readable at a glance. And every KPI deserves a definition fixed once: what counts in the DSO, which costs fall under EBITDA — so the discussion about the measurement method does not return every month, and trend lines stay comparable across the years.

How do you choose the right KPIs for your business model?

On top of the financial core, every business deserves two to four KPIs that capture its own earnings model — the numbers that tell how revenue and margin come about. Those differ fundamentally per model.

‍

A staffing firm steers on utilization and margin per professional; a wholesaler on inventory turnover and the cash conversion cycle; an agency on billable ratio and the effective hourly rate; a restaurant on prime cost and revenue per seat; a manufacturer on added value and cost per unit. And a SaaS company steers on its own subsection of metrics — ARR, churn, net revenue retention, CAC payback — that lives next to the classic financial core, because billing and revenue diverge there. For each of these models, the full KPI set with its pitfalls is covered in the dedicated deep-dive article within this cluster.

‍

The selection logic is the same every time. Question one: which two or three numbers predict the result three months from now? Question two: who can influence each number, and does that person know it? Question three: is the number already indirectly in the financial core — and if so, does the separate KPI add anything? What passes those three questions belongs in the set; the rest does not. In practice, rarely more than four survive — and that is exactly the point: the business-model KPIs are the sharpest numbers of the section, not the most numerous.

‍

In a group with multiple entities, the KPI section works on two levels: a compact group set next to the business-model KPIs per operating company — how that fits together is covered in management reporting for a holding company with multiple entities.

‍

Next to entities, cost centers are the second dimension to slice the numbers on: a P&L per team, location or project next to the total. Whoever assigns cost centers consistently in the bookkeeping can track KPIs per unit and even group cost centers across entities — all locations of one region, for example. Finstack supports filtering and grouping on cost centers, up to a dedicated mapping per cost center in the reporting structure.

How do you present KPIs: level, trend and comparison

For every KPI the same presentation rule applies: show the level, the trend over at least twelve months and the comparison against budget and last year. A number on its own says nothing — a DSO of 45 days is fine coming from 55 and worrying coming from 35.

‍

The trend matters more than the level. Monthly figures move on timing and chance; the twelve-month line shows whether something is really changing. Choose per KPI the form that reads fastest: a small trend chart (sparkline) next to the number does more than a table with twelve columns, and a color signal — on track, attention, action — only works when the thresholds are agreed in advance and do not move monthly with the outcome.

‍

The comparison against budget ties the KPI section to the agreement with management and investors; the comparison against last year shows the development independent of planning quality. With seasonal patterns, the same month last year is the relevant yardstick — you do not compare terrace revenue with December. When a KPI deviates materially, the explanation belongs not in the KPI section itself but in the variance analysis and the commentary — the section shows, the story explains.

‍

And keep the layout identical every month: the same KPIs, the same order, the same design. The reader who knows the section scans it in thirty seconds — and that is exactly the intent. Whoever shuffles the layout monthly forces every reader to search anew and undermines precisely the pattern-recognizing reading the section is built for — recognizability is a feature here.

Dashboard or report: where do the KPIs live?

In both, each with its own role: the dashboard gives the continuous picture, the report remains the monthly decision document. Whoever mixes the two gets meetings about daily swings or a report that arrives too late to steer.

‍

The dashboard is for in between: continuously current figures, the core KPIs as trends, and the ability to click through when something stands out. It answers the question “how are we doing?” at any moment of the month, without requiring a reporting round. The pitfall: a dashboard invites steering on daily movements — so agree which signals do warrant interim action (cash, order intake) and which wait for the monthly meeting.

‍

The report — per the main article a document of at most around ten pages, as Word or PowerPoint in PDF format, or a dashboard with the same fixed layout — remains the moment of judgment and decision: the figures are final after the month-end close, the variance analysis has run and the commentary is written. The KPI section in the report is therefore not a copy of the dashboard, but the validated monthly snapshot with context.

‍

The condition for both to work side by side: one source and one set of definitions. If the dashboard shows a different margin than the report, doubt wins — and both lose. Dashboard and report should share the same underlying figures and the same KPI definitions, so the difference between the two is only the moment and the depth, never the number. How to set up that single source returns in the automation section further down.

How do you keep the KPI set small and meaningful?

A KPI set only stays small with explicit maintenance — three agreements keep it healthy.

‍

One in, one out. KPI lists grow by themselves: every incident adds a metric (“we want to track this from now on”), and nobody feels called to remove one. The simplest brake is a fixed maximum — eight on the first page — with the agreement that a new KPI only enters when another leaves. That forces every addition into an explicit trade-off instead of a silent pile-up.

‍

Recalibrate yearly, not monthly. One fixed moment per year — logically during the budget process — to hold the set against the light: does every KPI still measure something being steered on this year? A business moving from hours to retainers or launching a new product line needs different steering numbers than last year. Change in between only on a fundamental shift in the business model — otherwise the trend line loses its value.

‍

Give every KPI an owner. A number without an owner is an observation; a number with an owner is a steering tool. The owner knows the definition, explains the movement in the monthly meeting and brings the actions when the number falls out of step. KPIs for which no logical owner presents itself are usually not steering numbers but statistics — and that is a cut criterion in itself.

‍

The test for the whole section is the same as for the commentary: does this number lead to different decisions or better questions? If not, it is ballast — however interesting the number looks on its own.

How do you automate the KPI reporting from your accounting system?

The financial KPIs — revenue, margin, EBITDA, working capital, DSO/DPO, cash — come straight from the accounting system, and exactly that part can be fully automated. Manually maintained KPI tabs are where definitions start to drift and monthly figures start to deviate from the source.

‍

Finstack connects accounting packages such as Exact Online, AFAS and Twinfield — plus, among others, Odoo, Xero, QuickBooks and MS Dynamics 365 BC — directly via the API, read-only and at transaction level. The actuals refresh automatically every day; the KPI definitions are fixed in the mapping, so dashboard and report are guaranteed to show the same number. In a group, the consolidation runs along, including automatic intercompany elimination — the group set and the per-entity figures come from one process, from 1 to 50 entities.

‍

Operational KPIs — hours from the time registration, orders from the ERP, covers from the POS system — live in their own systems. The practical route: put them next to the financial core in the team’s own Excel or Google Sheets model, and let the financial columns fill through the 2-way sync. That creates one KPI overview with one refresh moment, without the financial figures ever becoming manual work. In the Finstack dashboards, every financial KPI is moreover clickable through to the source booking — and sharing with stakeholders such as management, investors and the accountant works with access rights per user.

‍

The effect: the KPI section is ready on day one of the month instead of as the tail end of the collection work. 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 KPI sections

Three patterns we see again and again in KPI sections. Each makes the section weaker than the figures beneath it; each is preventable with a fixed agreement.

Sources and provenance

• Finstack — Reporting & insights (dashboards, Excel/Sheets sync): finstack.io/solutions/reporting-insights
• Finstack — Integrations with Exact, AFAS, Twinfield 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