Most CFOs in mid-market companies still spend five to ten hours per month consolidating Excel exports to produce financial reporting that their ERP could generate in real time. This is not a budget or competence problem — it is a configuration and monitoring discipline problem. A properly configured ERP instantly surfaces the indicators needed to manage liquidity, profitability, and compliance for a company with 100 to 1,000 employees. This guide defines the 15 essential financial KPIs, their formulas, alert thresholds, and which modules to activate in the leading ERP platforms.
Why the 2026 CFO Monitors from Their ERP, Not from Excel
The CFO Role Transformation: From Retrospective Reporting to Predictive Steering
The CFO role has undergone a profound shift since 2020. Successive crises — Covid, inflation, high interest rates — demonstrated that monthly reporting in D+10 or D+15 is structurally ill-suited to the decision speed now required. A CFO who discovers mid-month that DSO is drifting cannot correct course before quarter-end.
The interest-rate environment of 2025–2026 has made Working Capital management critical for every mid-market company with variable-rate debt. One poorly managed point of NWC translates directly into additional finance charges. This reality has pushed finance teams toward continuous monitoring, made possible by modern ERPs that calculate KPIs in memory (SAP S/4HANA, Oracle Fusion) without waiting for an overnight batch.
Native ERP Reporting vs. Excel Exports and Standalone BI
Two models coexist in mid-market companies. The first relies on daily or weekly data exports from the ERP to Excel or a standalone BI tool (Power BI, Tableau, Qlik). The second uses the ERP’s embedded BI to calculate and display KPIs directly from the transactional data source.
The export model introduces data latency, a risk of desynchronisation between modules (accounts receivable in the finance module does not always match uninvoiced deliveries in the sales module), and permanent report-maintenance overhead. The embedded model eliminates this friction but requires the ERP to be correctly configured and for the finance team to have adopted native visualisation tools.
The practical truth: few mid-market companies operate in fully embedded mode. The realistic goal is to use the ERP for the 15 critical operational KPIs — those that drive daily decisions — and to reserve the BI layer (Power BI, Qlik Sense) for ad hoc analyses and executive dashboards.
The 15 Essential Financial KPIs by Category
Category 1 — Liquidity and Cash
KPI 1 — DSO (Days Sales Outstanding)
Formula: DSO = (Accounts receivable / Revenue incl. VAT) × Number of days in the period
Frequency: Daily or weekly during active monitoring; monthly at minimum.
Alert threshold: Beyond 45 days for an industrial or distribution mid-market company with B2B customers on 30-day payment terms. Each additional 10-day increment typically represents between 8% and 12% of monthly revenue tied up in receivables.
ERP source module: Accounts Receivable (AR). In SAP S/4HANA, the Fiori app “Customer Payment Behavior” calculates DSO dynamically. In Oracle Fusion, the AR Receivables module includes a native DSO dashboard.
Market context: According to the Atradius B2B Payment Practices Trends — Western Europe 2026 report, payment delays continue to worsen, with nearly four in five European companies reporting late customer payments. The average DSO in Western Europe sits at around one month, but companies that monitor it in real time respond to drift before it compromises their cash position.
Practical example: A 300-employee industrial company that reduces its DSO from 52 to 38 days over six months via an automated dunning module in its ERP releases the equivalent of two weeks of revenue in liquidity — without opening an additional credit facility.
KPI 2 — DPO (Days Payable Outstanding)
Formula: DPO = (Accounts payable / Purchases incl. VAT) × Number of days
Frequency: Weekly, with a monthly review ahead of the cash forecast.
Alert threshold: A DPO below 30 days indicates the company is paying faster than its contractual terms (effectively granting free cash sorting to suppliers). A DPO above 90 days may signal cash pressure or non-compliance with applicable payment regulations — the EU Late Payment Directive (Directive 2011/7/EU) caps commercial payment terms at 60 days by default.
ERP source module: Accounts Payable (AP). The ERP must distinguish current liabilities from disputed invoices to avoid ratio distortion.
KPI 3 — CCC (Cash Conversion Cycle)
Formula: CCC = DSO + DIO − DPO (where DIO = Days Inventory Outstanding = (Inventory / Cost of goods sold) × Number of days)
Frequency: Monthly, as part of the Working Capital review.
Alert threshold: A high positive CCC means the company is financing its operating cycle with its own capital. The goal is to minimise it — ideally under 30 days for a distribution company, under 60 days for an industrial company with production stock.
ERP source module: Cross-module between AR, AP, and Inventory/Supply Chain. The advantage of an integrated ERP: CCC is calculated without manual consolidation.
Category 2 — Operational Profitability
KPI 4 — Gross Margin by Product Line
Formula: Gross margin = (Revenue − Cost of goods sold) / Revenue × 100
Frequency: Monthly by product line, quarterly by distribution channel.
Alert threshold: A gross margin below 30% on a product line that accounts for more than 20% of revenue warrants a pricing or sourcing review. The ERP must support analytical drill-down by product family, customer, and sales representative.
ERP source module: Management accounting (CO) or analytical module. Gross margin requires properly configured cost accounting, with direct costs allocated to profit centres.
KPI 5 — Normalised EBITDA
Formula: EBITDA = Operating profit + Depreciation and amortisation + Provisions
The normalised version excludes non-recurring items: restructurings, asset disposals, exceptional disputes.
Frequency: Monthly, with quarterly reporting to shareholders or lenders.
Alert threshold: EBITDA is rarely managed with an absolute threshold; it is the variance versus budget or month-on-month movement that triggers analysis. An EBITDA that falls more than 15% below budget requires an immediate analytical explanation.
ERP source module: Consolidation or financial reporting module. In SAP S/4HANA, the Fiori “Financial Statement app” provides EBITDA with drill-down. The ERP must have a consistent chart of accounts for the calculation to be automatic.
KPI 6 — ROI by Profit Centre or Business Unit
Formula: ROI = (Net profit of the profit centre / Allocated assets) × 100
Frequency: Quarterly for stable profit centres; monthly for ongoing projects.
Alert threshold: An ROI below the cost of capital (WACC) over two consecutive quarters justifies a strategic review of the activity in question.
ERP source module: Analytical management accounting module. Requires assets to be correctly allocated to profit centres within the ERP master data.
KPI 7 — Cost per Customer Order Processed
Formula: Cost per order = Total order-to-cash process costs / Number of orders processed in the period
Frequency: Monthly, with a comparison by channel (EDI, e-commerce, manual).
Alert threshold: Above £/€25 per order for fully manual processing, ERP automation (EDI, customer portal, automatic entry) becomes cost-effective in under 18 months for most mid-market industrial companies.
ERP source module: Sales module (SD/Order Management) coupled with management accounting. This KPI is one of the most revealing ERP maturity indicators.
Category 3 — Balance Sheet Performance
KPI 8 — NWC and Monthly Variation
Formula: NWC (Net Working Capital) = Inventory + Accounts receivable − Accounts payable
Frequency: Monthly mandatory; weekly during cash pressure periods.
Alert threshold: A positive NWC variation exceeding 5% of monthly revenue outside normal seasonal cycles must immediately trigger analysis of the three components (inventory rising? receivables extending? suppliers paid too quickly?).
ERP source module: Cross-module between AR, AP, and Inventory. This is the KPI for which an integrated ERP delivers the most value compared with a collection of separate systems.
KPI 9 — Net Debt / EBITDA Ratio
Formula: Net debt / EBITDA (Net debt = Financial liabilities − Available cash)
Frequency: Quarterly, with monthly reporting if the company is approaching a banking covenant.
Alert threshold: Most banking covenants for mid-market companies set the limit between 3× and 4×. Exceeding 3.5× in a high-rate environment exposes the company to covenant renegotiation. The ERP must be able to simulate the impact of an acquisition or investment on this ratio before a decision is made.
ERP source module: Treasury and financial consolidation module.
KPI 10 — Gearing Ratio
Formula: Gearing = Net debt / Equity
Frequency: Quarterly.
Alert threshold: A gearing ratio above 100% means the company is financed more by debt than by equity. In a high-rate environment, this level significantly increases sensitivity to interest-rate movements.
IFRS 16 note: Since IFRS 16 came into effect, operating leases are recognised on the balance sheet as right-of-use assets with a corresponding lease liability. This mechanically inflates net debt and therefore gearing. A CFO with a vehicle fleet or leased premises must distinguish between classical financial debt and IFRS 16 lease debt in their analysis.
ERP source module: Consolidation or IFRS regulatory reporting module.
Category 4 — Finance Process Efficiency
KPI 11 — Days to Close (Month-End Close Duration)
Formula: Number of business days between the last day of the period and the sign-off date for management accounts.
Frequency: At each monthly close.
Alert threshold: Beyond 7 business days, the informational value of monthly reporting is significantly reduced — corrective decisions arrive too late in the following month. Companies that have deployed continuous close on their ERP reach 3 to 5 business days.
ERP source module: Financial closing module. SAP S/4HANA includes a Financial Closing Cockpit that automates and monitors closing steps. Oracle Fusion offers an equivalent Close Manager.
KPI 12 — On-Time Invoice Payment Rate
Formula: Invoices paid on or before due date / Total invoices issued × 100
Frequency: Weekly on the active AR portfolio.
Alert threshold: A rate below 80% indicates either a data quality problem (incorrect customer addresses, invalid VAT numbers blocking dispatch) or a dunning failure. In either case, the ERP must provide a list of at-risk invoices with their due dates.
ERP source module: AR module with automated dunning workflows.
KPI 13 — Manual vs Automated Entry Rate
Formula: Manually entered accounting entries / Total entries × 100
Frequency: Monthly.
Alert threshold: A manual entry rate above 30% is a sign of an under-exploited ERP or poor integration with peripheral systems (bank, payroll, expense reports). It is also an indicator of entry-error risk and fraud exposure.
ERP source module: Accounting journals with automatic/manual distinction. This indicator is particularly revealing during a post-ERP-deployment audit.
Category 5 — Compliance and Risk
KPI 14 — Tax Compliance Rate
Formula: Tax returns filed correctly and on time / Total expected returns × 100
Frequency: Monthly (VAT), quarterly (corporation tax instalments), annually (corporation tax final balance).
Alert threshold: Any deviation from 100% must be documented with the cause and remediation date. VAT late-filing penalties under EU directives typically range from 10% to 40% of tax due depending on jurisdiction and whether the failure was deliberate. The ERP must flag upcoming declaration deadlines proactively.
ERP source module: Tax Management module with an integrated declarative calendar. ERPs certified for the 2026 e-invoicing mandates (active in multiple EU member states) now integrate real-time VAT calculation.
KPI 15 — Provisions Coverage Rate
Formula: Total provisions constituted / Total identified and quantified risks × 100
Frequency: Quarterly, before each period-end.
Alert threshold: A rate below 80% exposes the company to significant provision adjustments at year-end close. This KPI requires a rigorous risk mapping (customer disputes, product warranties, environmental liabilities) maintained in the ERP.
ERP source module: Provisions Management module or, as a fallback, a risk-tracking table maintained manually and reconciled with management accounting.
How to Configure These 15 KPIs in the Leading ERPs
SAP S/4HANA: Fiori Analytical Apps and SAP Analytics Cloud
SAP S/4HANA calculates financial KPIs directly in memory (in-memory computing), without an overnight batch. This means DSO, NWC, or EBITDA are available in real time as soon as a posting is validated.
The configuration tools are: Fiori Analytical Apps for daily operational monitoring (apps “Cash Flow Analyzer”, “Customer Payment Behavior”, “Overdue Receivables”), and SAP Analytics Cloud for executive dashboards and predictive simulation (SAP Help Portal — KPI Monitoring and Analysis). The CFO configures their dashboards directly in the Fiori interface, with configurable KPI tiles and visual alert thresholds.
The main advantage of S/4HANA: source data (sales lines, settlements, inventory) and the calculated KPIs live in the same database. There is no ETL layer between the transaction and the reporting.
Microsoft Dynamics 365 Finance: Power BI Embedded and Financial Insights
Dynamics 365 Finance relies on Power BI Embedded for analytical dashboards and Financial Insights (formerly CFO Workspace), built on Microsoft Fabric, for predictive reporting. Standard KPIs (DSO, aged payables, cash forecast) are available without custom development (Microsoft Learn — Financial Insights).
The advantage of the Microsoft suite: continuity between Dynamics 365 Finance, Teams, and Excel. Alerts on a KPI can be pushed directly into Teams, and exports to Excel remain possible without workflow disruption. The CFO already using Power BI on other perimeters finds a familiar tool.
Oracle Fusion Cloud: OTBI and Financial Reporting Studio
Oracle Fusion Cloud Finance integrates OTBI (Oracle Transactional Business Intelligence) for real-time reports based on live transactions, and Financial Reporting Studio (FRS) for regulatory financial statements (P&L, balance sheet, cash flow statement). Both tools are accessible directly from the Oracle interface without local installation.
OTBI allows the CFO to build ad hoc analyses on any dimension of the chart of accounts without involving IT. FRS handles multi-currency and multi-entity outputs, essential for mid-market companies with foreign subsidiaries.
Sage X3 and Sage Intacct: Native Dashboards and Power BI Connector
Sage X3 and Sage Intacct provide native dashboards for common KPIs (DSO, customer outstanding, supplier payment schedule). For advanced analytics, both platforms offer a certified Power BI connector that links a Power BI workspace directly to Sage data without manual export.
The advantage for internationally operating mid-market companies: Sage products are available across multiple countries, with localised compliance packages for VAT, payroll, and statutory reporting. The tax compliance KPI (KPI 14) is calculated directly from the declarative module, with country-specific rule sets updated by Sage on a rolling basis.
The 4 Classic Mistakes in a CFO Dashboard
1 — Too Many KPIs: Analytical Paralysis
A dashboard showing more than 25 indicators is no longer a management tool — it is a reporting interface that buries the essential in the accessory. The practical rule: 5 liquidity KPIs, 3 profitability KPIs, 3 operational-efficiency KPIs for daily monitoring. The remaining 4 KPIs (balance sheet and compliance) belong in a monthly or quarterly review cadence.
2 — Unreconciled Data Across ERP Modules
A DSO calculated from accounts receivable does not always match the DSO calculated from the sales module if uninvoiced deliveries are not correctly integrated. This module desynchronisation is the primary cause of teams losing confidence in ERP KPIs. Verifying reconciliation points across modules (purchasing, sales, inventory, accounting) must be part of the dashboard implementation project.
3 — Wrong Refresh Frequency
Displaying a DSO calculated from the previous night’s batch in an ERP that can calculate it in real time wastes most of the tool’s added value. Conversely, refreshing a net debt/EBITDA ratio hourly serves no operational purpose. Defining the update frequency per KPI (real-time, daily, weekly, monthly) is a configuration step that is frequently overlooked.
4 — No Leading Indicators
A dashboard composed exclusively of retrospective indicators (what happened) does not enable anticipation. Companies that have activated forecasting features in their ERP (cash flow forecast in D365 Finance, NWC simulation in SAP S/4HANA) gain a concrete decision advantage: they identify cash pressure 4 to 6 weeks before it materialises — not on the day the bank account runs dry.
90-Day Roadmap for the CFO Dashboard
D0–D30 — Audit and Selection
Map the data available in the ERP: which modules are active? Which master data (profit centres, product families, analytical codes) are consistent and reliable? Identify the 5 priority KPIs using an impact/implementation-ease matrix. For a company under cash pressure, KPIs 1 (DSO), 2 (DPO), 3 (CCC), and 8 (NWC) form the first priority tier. For a company in a growth phase, KPIs 4 (Gross margin) and 6 (ROI by BU) drive the selection.
D30–D60 — Configuration and Data Validation
Configure dashboards in the ERP or connected BI tool. Have the controller validate the first results: do the displayed figures match manual reference calculations? A divergence greater than 2% on DSO or NWC indicates a source data issue to correct before the dashboard is circulated.
D60–D90 — Live Monitoring and Adoption
Integrate KPIs into the management routine: weekly DSO/DPO review with the credit manager, monthly NWC review with the CFO and supply chain director, quarterly profitability review with the executive committee. Train end users on alerts and the corrective actions associated with each threshold.
To deepen your approach to ERP financial monitoring, see our guide on continuous close accounting, our comparison of embedded BI and ERP reporting and our CapEx/OpEx guide for ERP project financing.
