Management dashboards can look precise while different teams calculate the same KPI differently. Sales may count booked orders, operations may count shipments, and finance may count recognized revenue. The resulting debate is not simply a data problem: it can lead executives to make decisions using incompatible definitions, and public reporting can become difficult to support.
Financial controllers can improve trust in metrics by treating key performance indicators (KPIs) as governed reporting objects—with an owner, approved definition, data lineage, calculation logic, reconciliation, review, and change history. The framework below is useful for internal dashboards and can help identify which externally communicated financial measures require additional disclosure controls.
1. Build a KPI inventory and classify each measure
Start with a central register of metrics used in board packs, operating reviews, investor presentations, lender reporting, forecasts, and recurring management dashboards. Capture the metric name, business purpose, audience, frequency, owner, and system/report source.
Classification matters. A KPI may be an operational statistic, a financial measure calculated under the accounting framework, a non-GAAP financial measure, or—when IFRS 18 applies—a management-defined performance measure (MDPM). Not every metric is subject to the same rules, and internal management use does not automatically make a measure subject to securities disclosure rules.
For example, “units shipped” is an operational metric, “revenue” is an accounting measure, “adjusted EBITDA” is typically a non-GAAP measure, and an IFRS 18 management-defined performance measure is a narrower category: a subtotal of income and expenses used in public communications outside the financial statements to communicate management’s view of entity-wide financial performance, subject to the standard’s criteria. See the IFRS 18 key terms.
2. Assign an accountable business owner and finance steward
Each KPI should have a named business owner responsible for explaining performance and a finance steward responsible for definition integrity, calculation, controls, and reporting consistency. Avoid shared ownership that leaves no one accountable.
The owner should explain what decisions the metric supports, why it is useful, and what actions follow when results miss expectations. Finance should challenge whether the metric measures the intended outcome or creates incentives to shift behavior—for example, rewarding sales bookings without considering cancellations, collections, or margin.
3. Approve a precise definition and formula
Document the definition in plain English and the calculation in a reproducible formula. Include units, period, numerator and denominator, inclusions, exclusions, treatment of one-time items, timing rules, currency, and rounding. If the measure is a ratio, define both components and how zero, negative, missing, or unusually large values are handled.
Do not allow “margin,” “customer retention,” “productivity,” or “adjusted earnings” to be interpreted differently by each business unit. A short KPI specification should be version-controlled and accessible beside the dashboard.
4. Establish source systems and data lineage
For each KPI, record the originating systems, tables or reports, extraction date, transformation steps, and responsible data owner. Finance should be able to trace a displayed number back to source transactions or approved source data—not just to a manually edited spreadsheet.
In SAP S/4HANA environments, distinguish operational sources such as sales orders, deliveries, billing, production confirmations, and workforce data from accounting sources such as Universal Journal balances. Document the logic connecting them. If a KPI uses a data warehouse, identify the query or model, filters, and refresh process.
5. Reconcile financial KPIs to an authoritative source
Where a KPI uses accounting data, reconcile it to the general ledger, subledger, or financial statement measure as appropriate. For operational metrics, reconcile counts to the source system or explain the control totals and data-quality checks.
For example, a finance-approved revenue dashboard should state whether it uses billed revenue, recognized revenue, or another defined measure. The controller should reconcile the financial amount to the appropriate ledger or reporting view and document differences caused by timing, scope, eliminations, or currency conversion. Reconciliation is not necessarily a one-to-one tie-out for every operational KPI; the expected relationship and acceptable variance should be documented.
6. Control adjustments and preserve consistency between periods
Adjusted metrics are especially sensitive. Create an adjustment policy that defines eligible items, approval requirements, evidence, and whether gains and losses are treated consistently. Keep the GAAP or IFRS measure visible in the supporting reconciliation, and preserve a history of changes in calculation or presentation.
US SEC staff guidance warns that non-GAAP measures can be misleading when labels are unclear, when adjustments change GAAP recognition or measurement, when recurring cash operating expenses are excluded, or when similar items are treated inconsistently across periods. See the SEC’s Non-GAAP Financial Measures interpretations (last updated December 13, 2022). The controller should challenge recurring “one-time” adjustments rather than simply accept them.
7. Manage KPI changes through formal version control
Definitions should not change silently. Require a change request documenting the reason, impact on comparability, effective period, approver, affected reports, and whether prior periods need to be recast or restated for management analysis. Preserve the previous definition and calculation so results can be reproduced.
When a metric is retired or replaced, document the successor metric and communicate the change to users. A dashboard that changes its denominator mid-year without explanation can create misleading trends even if the new calculation is mathematically valid.
8. Set thresholds, review evidence, and exception actions
For important KPIs, define expected ranges, warning thresholds, and escalation paths. A review should investigate unusual movements, not merely acknowledge a green or red indicator. Evidence should include the reviewer, date, analytical procedures performed, explanations challenged, supporting documents, and actions assigned.
Use a practical exception log: metric, period, threshold breached, root cause, owner, corrective action, due date, and closure evidence. Repeated exceptions should trigger a process or definition review rather than repeated manual explanations.
9. Add a disclosure-control gate for external use
Before a KPI is included in an earnings release, investor presentation, filing, lender package, or public website, require finance and appropriate legal/IR review of its classification, definition, prominence, reconciliation, consistency, and supporting evidence. Internal dashboard approval is not a substitute for external disclosure review.
For US SEC registrants, Regulation G and Item 10(e) of Regulation S-K may apply to non-GAAP measures. For Canadian issuers, National Instrument 52-112 governs non-GAAP and other financial measures. The Canadian Securities Administrators announced final amendments on October 15, 2026, intended in part to maintain NI 52-112 requirements for measures historically covered when disclosed outside the financial statements after IFRS 18 adoption. Subject to necessary approvals, the amendments are scheduled to come into force December 29, 2026. Review the CSA announcement and the NI 52-112 regulatory instrument page for current status.
IFRS 18 is effective for annual reporting periods beginning on or after January 1, 2027, and requires qualifying management-defined performance measures to be disclosed in a single note to the financial statements. It applies to entities reporting under IFRS; it is not a universal requirement for Canadian entities using ASPE. The controller should map public metrics to the applicable reporting and disclosure framework rather than assume the same rules apply in the US, Canada, IFRS, and ASPE environments.
Controller’s KPI governance checklist
| Control | Evidence to retain |
|---|---|
| Metric inventory and classification | Approved catalog with purpose, audience, and category |
| Definition and calculation | Formula, scope, inclusions/exclusions, version |
| Ownership | Named business owner and finance steward |
| Data integrity | Source lineage, refresh logs, completeness and validation checks |
| Financial reconciliation | Ledger tie-out or documented source control total and differences |
| Adjustments | Policy, approvals, evidence, and period-to-period consistency |
| Change management | Change request, impact assessment, approval, communication |
| Performance review | Analytical review, exceptions, actions and follow-up |
| External disclosure | Classification, reconciliation, legal/IR approval, final version |
Conclusion
Reliable KPIs are not created by a dashboard tool alone. They require consistent definitions, clear ownership, traceable data, reconciliations, controlled adjustments, change management, and documented review. Financial controllers who establish these controls can make management reporting more useful, reduce metric disputes, and improve readiness when a KPI moves from an internal decision tool to an external disclosure.
Informational only: This article provides general finance-control guidance, not legal, accounting, or securities-disclosure advice. Organizations should assess applicable requirements and their specific facts with qualified advisers.
Sources and further reading
- SEC — Non-GAAP Financial Measures (CFIs; last updated December 13, 2022)
- Canadian Securities Administrators — NI 52-112 amendments ahead of IFRS 18 (October 15, 2026)
- Alberta Securities Commission — NI 52-112 regulatory instrument and status
- IFRS Foundation — IFRS 18 key terms, including management-defined performance measures





