Your ERP go-live is behind you. User acceptance tests are complete, training is done, and the cutover went smoothly. Now what?
For many CFOs and Finance Directors at SMEs and mid-market companies, the post-go-live period feels like a vacuum: the project is officially closed, the implementation team is stepping back, and dashboards are not yet in place. This window — roughly between day 30 and day 365 after go-live — is precisely when bad habits take root, processes drift, and the value the ERP was meant to deliver quietly evaporates.
The answer is not to launch another project. It fits in a dashboard of 12 indicators, readable directly from your ERP, organised around four cycles: Order-to-Cash, Purchase-to-Pay, financial close, and treasury. Each indicator has a formula, an alert threshold, and a monitoring frequency. No theory — just practical governance.
Why CFOs Need Dedicated ERP KPIs
After go-live, two types of problems coexist and look almost identical on the surface. The first is a data quality problem: customers without analytical codes, purchase order lines poorly filled in, receipt statuses blocked. The second is an operational performance problem: payment terms lengthening, reminders missed, invoice approval workflows backed up.
A CFO without an ERP dashboard cannot tell the difference. They receive a degraded figure, they ask the team, the team explains it is “the new system,” and the issue gets kicked to the IT department. A CFO with the right KPIs sees immediately whether the problem is technical (data) or operational (process), and directs action accordingly.
These 12 indicators are also distinct from those tracked by the CIO or IT Director, which focus on system stability, adoption rates, and infrastructure performance. For the technology and operations-side dashboard, see our companion article: 15 ERP KPIs Every CIO Must Track After Go-Live.
KPIs 1 to 3: The Order-to-Cash Cycle (O2C)
The O2C cycle covers everything that happens between a customer placing an order and the company collecting payment. It is the central mechanism of working capital on the receivables side.
KPI 1: DSO (Days Sales Outstanding)
Definition: the average number of days of revenue still awaiting collection at a given date.
Formula: (Accounts receivable / Revenue for the period) × number of days in the period.
How to read it in your ERP: every mid-market ERP — Sage X3, Sage Intacct, SAP Business One, Dynamics 365 Business Central, Odoo, Unit4 — includes an aged debtor report or a native DSO indicator in the Accounts Receivable module. If your ERP does not calculate it directly, export the aged receivables report and compute it in Excel as a temporary measure while you set up proper BI.
Frequency: weekly. A variation of more than three days in a single week warrants an explanation.
Alert threshold: a DSO that exceeds your contractual payment terms by more than 15 days is a red flag. APQC’s Open Standards benchmarking data provides DSO medians by industry sector and company size — use these to calibrate your sectoral reference rather than comparing against a generic target.
Pitfall: DSO calculation methods vary between ERP systems. SAP and Odoo do not necessarily use the same convention (rolling period vs accounting period, gross vs net revenue). Before benchmarking your DSO externally, document the exact formula your system uses.
KPI 2: Receivables Matching Rate
Definition: the percentage of customer invoices that have been fully matched (cleared) against incoming payments, at 30 days after issue.
Formula: (Number of invoices matched at day 30 / Total invoices issued) × 100.
How to read it in your ERP: unmatched entries create an “open item” visible in the aged receivables report. A well-configured accounts receivable dashboard displays the matching rate directly.
Frequency: weekly.
Alert threshold: below 85% at day 30 is a problem. Typical causes: partial payments not correctly allocated, cheques processed without proper application, unresolved credit notes waiting to be applied.
ERP value-add: a low matching rate often signals that teams are collecting payments but not entering them correctly in the ERP. This is a data quality indicator, not just a collections performance metric.
KPI 3: Overdue Reminders Not Triggered
Definition: the number of customer invoices past their due date by more than X days (X being your dunning trigger threshold) that have not yet generated a reminder in the ERP.
How to read it in your ERP: the “Dunning” or “Credit Management” module should display invoices that qualify for a reminder but have not received one. If this module has not been configured, that is the first task in your post-go-live stabilisation plan.
Frequency: weekly.
Alert threshold: any number above zero deserves attention. More than ten overdue invoices without a reminder in a single week indicates that the automated dunning workflow is not active or is being bypassed.
KPIs 4 to 6: The Purchase-to-Pay Cycle (P2P)
The P2P cycle covers procurement from purchase order to supplier payment. It is the mirror of the O2C cycle and drives working capital on the payables side.
KPI 4: DPO (Days Payable Outstanding)
Definition: the average number of days a company takes to pay its suppliers.
Formula: (Accounts payable / Purchases for the period) × number of days.
How to read it in your ERP: the symmetric counterpart of DSO, available in the Accounts Payable module of any mid-market ERP.
Frequency: monthly (less volatile than DSO).
Alert threshold: across most European jurisdictions, standard payment terms are capped at 60 days from invoice date or 45 days end of month under national implementations of the EU Late Payment Directive. Exceeding these limits exposes the company to statutory penalties and interest. Conversely, a DPO that is too short may indicate you are paying before you need to, unnecessarily depleting available cash.
Calibration: a DPO between 30 and 45 days is optimal for most mid-market service or distribution businesses. Manufacturers and capital-intensive industries tend to operate between 45 and 60 days depending on sector norms.
KPI 5: Three-Way Match Rate
Definition: the percentage of supplier invoices automatically matched against a corresponding purchase order (PO) and goods receipt (GR) without manual intervention.
Formula: (Number of invoices auto-matched / Total invoices received) × 100.
How to read it in your ERP: in the Purchasing/Payables modules, this KPI is often labelled “automatic approval rate” or “first-time match rate.” Well-configured ERPs calculate it in real time.
Frequency: weekly.
Alert threshold: according to AP Automation 2026 benchmarks published by Cadel.ai, top-performing AP teams maintain an automatic match rate above 90%. Below 70%, the supplier validation process is predominantly manual, generating delays and error risk.
Impact: a low rate typically reveals three distinct problems — POs not raised before ordering, receipt entries posted with a delay, or supplier prices not updated in the master data. The ERP tells you exactly where to act.
KPI 6: Invoices Pending Approval for More Than 5 Days
Definition: the number of supplier invoices whose status is “awaiting approval” in the approval workflow, for more than five business days.
How to read it in your ERP: in the approval queue of the Payables module. Every mid-market ERP allows filtering by document age.
Frequency: daily during close periods, weekly otherwise.
Alert threshold: more than ten invoices pending for five days indicates the approval circuit is backed up. Common causes: approvers absent without a configured delegation, workflows not aligned with actual organisational structure, approval thresholds set too low.
KPIs 7 to 9: Financial Close and Reporting
These three KPIs measure the health of your close process and the quality of accounting data.
KPI 7: Monthly Close Cycle Time
Definition: the number of calendar days between the end of the accounting period (last day of the month) and the date when consolidated financial statements become available.
How to read it in your ERP: note the date of the last validated entry for period N and the date you produced your first balance sheet/P&L. The difference is your close cycle time.
Frequency: monthly.
Alert threshold: according to APQC’s General Accounting Open Standards benchmark (panel of more than 2,300 organisations), the median is 6.4 calendar days. The top 25% close in 4.8 days or fewer. Beyond 10 days, you are in the bottom quartile. A reasonable target for an SME at six months post-go-live is to come in below six days.
Note: close cycle time is not just a speed indicator. It is also a proxy for data quality and process maturity. A 12-day close typically means six days of actual close work plus six days of corrections.
KPI 8: Manual Journal Entry Rate
Definition: the percentage of accounting entries posted manually, as opposed to those generated automatically by the Purchasing, Sales, Banking, Payroll, and Fixed Asset modules.
Formula: (Number of manual entries / Total entries for the period) × 100.
How to read it in your ERP: in the general ledger, filter by creation mode “manual” vs “automatic” or “interface.”
Frequency: monthly.
Alert threshold: more than 20% manual entries at six months post-go-live indicates that automations are not in place or are being bypassed. This rate should normally fall below 10% by twelve months. A manual entry is not inherently bad — what is problematic is a persistently high proportion, which signals processes that the ERP has not yet captured.
Value-add: this is one of the most powerful indicators for identifying grey areas where the ERP has not replaced legacy workflows. Every frequently recurring manual entry is a candidate for automation.
KPI 9: Bank Reconciliation Anomalies
Definition: the number of line items in discrepancy during reconciliation between the bank statement and the treasury ledger in the ERP.
How to read it in your ERP: in the Treasury or Banking module, the bank reconciliation report lists unmatched transactions. Count lines more than three days old.
Frequency: weekly.
Alert threshold: more than 15 unmatched lines older than seven days outside close periods is a warning sign. At monthly close, this figure should trend to zero.
What it reveals: persistent reconciliation anomalies can signal duplicate payments, uncorded receipts, or off-system transactions (manual transfers, direct debits not entered).
KPIs 10 to 12: Treasury and Working Capital
These three indicators give a view of treasury health and the efficiency with which the business converts accounting profit into cash.
KPI 10: Cash Conversion Cycle (CCC)
Definition: the cash conversion cycle measures the number of days between the moment the company pays for its purchases and the moment it collects payment for its sales.
Formula: CCC = DSO + DIO (Days Inventory Outstanding) − DPO.
How to read it in your ERP: if your ERP includes inventory management, all three components can be calculated natively. For service businesses without inventory, the CCC reduces to DSO − DPO.
Frequency: monthly.
Alert threshold: a positive and growing CCC means your working capital requirement is increasing — the business needs to finance more and more days of its operating cycle. A CCC that grows by more than five days over three months without a clear explanation (seasonality, rapid growth) warrants root-cause analysis.
KPI 11: 30-Day Cash Flow Forecast Accuracy
Definition: the variance between the projected cash balance at day +30 (forecast produced at the start of the month) and the actual balance recorded.
Formula: |Forecast D+30 − Actual D+30| / Actual D+30 × 100.
How to read it in your ERP: in the Treasury or Cash Management module. If your ERP does not include native forecasting, export projected outflows (supplier invoices due, payroll, fixed charges) and expected inflows (customer invoices due for payment) to Excel.
Frequency: monthly (comparison of start-of-month forecast vs end-of-month actual).
Alert threshold: a variance above 15% indicates that ERP data is not reliable enough to serve as a forecasting base. The most common causes: supplier due dates not entered, customer payments not anticipated in the system, or off-system transactions not captured.
The objective: get below 10% variance at six months post-go-live. A forecast accurate to 90% is a signal that your ERP is well fed and your processes are being consistently followed.
KPI 12: Commitment Coverage Ratio at 30/60/90 Days
Definition: the ratio of available cash plus expected inflows to committed outflows over the next 30, 60, and 90 days.
Formula: (Available cash + Receivables due within X days) / Payables due within X days.
How to read it in your ERP: in the Treasury module, configure forecast horizons at 30, 60, and 90 days. Every mid-market ERP supports this type of report. More recent cloud ERPs — Sage Intacct, SAP Business One Cloud, Business Central, Unit4 Financials — provide native cash flow forecast dashboards.
Frequency: weekly.
Alert threshold: a ratio below 1.0 on the 30-day horizon means expected inflows do not cover certain commitments — this is an immediate cash pressure alert. Between 1.0 and 1.2: tight, monitor closely. Above 1.5: comfortable safety margin.
Building Your CFO Dashboard in the ERP
Native dashboards, Excel exports, or dedicated BI?
After go-live, the temptation is to export everything to Excel to maintain control. This is a trajectory error: you recreate exactly the shadow IT the ERP was supposed to eliminate.
Priority 1: activate your ERP’s native dashboards, even if imperfect. They have the advantage of being fed in real time. Priority 2: if your ERP does not natively calculate certain KPIs (matching rate, forecast accuracy), build parameterisable reports within the ERP. Priority 3: if your ERP has limited reporting capabilities, connect a lightweight BI tool — Power BI, Tableau, or embedded tools like Sage Analytics — pulling directly from ERP tables, not from manual exports.
The trap of KPIs calculated differently across ERPs
Be cautious about cross-system comparisons without first verifying the underlying formulas. Two concrete examples. For DSO: SAP calculates on net revenue by default; Odoo may use gross revenue depending on configuration. For close cycle time: some ERPs count calendar days, others business days. Before benchmarking your performance externally, document the exact formula your system uses.
For more on structuring the monthly close in your ERP, see our operational checklist: ERP Year-End Close: The CFO Checklist J-90/J-30/J-7.
Recommended review cadence
A post-go-live CFO dashboard works best on two rhythms. The weekly rhythm covers fast-moving operational indicators: DSO, dunning, invoices pending, 30-day coverage. A 20-minute review with the Finance key user is sufficient. The monthly rhythm covers structural indicators: DPO, close cycle time, CCC, forecast accuracy, manual entry rate. This naturally maps to your close review agenda.
For KPIs to escalate to the executive committee, limit yourself to three: DSO vs target, close cycle time (in days), and CCC. These three figures provide a complete picture of operational financial health without overwhelming the committee with technical detail.
Summary: the 12 KPI Dashboard
| # | KPI | Simplified formula | Frequency | Alert threshold |
|---|---|---|---|---|
| 1 | DSO | Receivables / Revenue × days | Weekly | > contractual terms + 15 days |
| 2 | Matching rate | Invoices cleared at D+30 / Total | Weekly | < 85% |
| 3 | Overdue reminders | Overdue invoices without reminder | Weekly | > 0 (target: zero) |
| 4 | DPO | Payables / Purchases × days | Monthly | > 60 days (EU directive) or < 30 days |
| 5 | Three-way match rate | Auto-matched invoices / Total | Weekly | < 70% |
| 6 | Invoices pending > 5 days | Invoices blocked in workflow | Daily | > 10 |
| 7 | Close cycle time | Days from month-end to statements | Monthly | > 6.4 days (APQC median) |
| 8 | Manual entry rate | Manual entries / Total | Monthly | > 20% (at 6 months) |
| 9 | Reconciliation anomalies | Unmatched lines > 7 days | Weekly | > 15 lines |
| 10 | CCC | DSO + DIO − DPO | Monthly | Growth > 5 days over 3 months |
| 11 | Forecast accuracy D+30 | |Forecast − Actual| / Actual | Monthly | > 15% variance |
| 12 | Commitment coverage D+30 | (Cash + Receivables D+30) / Payables D+30 | Weekly | < 1.0 |
The 3 KPIs to Implement First
For finance teams starting from scratch on ERP-driven governance, prioritisation matters. If you have only two weeks to get started, focus on these three.
DSO (KPI 1): this is the cash thermometer. A rapid DSO deterioration reveals problems in the customer cycle before they become a treasury problem.
Invoices pending approval (KPI 6): this is the most direct adoption indicator. If the approval circuit is backed up, it means ERP processes have not yet become team habits.
Close cycle time (KPI 7): this is the barometer of data quality and system maturity. It falls naturally at the end of each month and provides an objective measure of the progress you are making.
Conclusion
A well-governed ERP delivers measurable value to the CFO. These 12 KPIs are not an exhaustive list of everything that can be measured — they are the minimum sufficient set to quickly detect whether your ERP is delivering on its promises or whether silent problems are accumulating.
Setting up this dashboard takes between two and four weeks for an SME with a mid-market ERP. The return on investment is immediate: every additional automated reminder, every supplier invoice validated on time, every day saved on the close, is time recovered for analysis and decision-making.
To go further on measuring your ERP’s value, see our complete guide: ERP ROI: A Complete Guide to Measuring Your Return on Investment.
For the complete year-end close checklist in a cloud ERP: ERP Year-End Close: The CFO Checklist J-90/J-30/J-7.
Download our ERP evaluation framework to benchmark your maturity level across 30 criteria and identify the priority workstreams in your post-go-live stabilisation plan.
