Is my organisation financially healthy — this month, not last audit?

Financial viability indicators are a legal requirement, yet most organisations still calculate them once a year, by hand, from a completed set of financial statements. A liquidity problem or a collapsing collection rate can therefore run for eleven months before anyone in the executive sees it, by which point the corrective options are narrow and expensive. The performance dashboard replaces that annual exercise with a standing summary of seventeen (17) financial performance indicators, calculated directly from the financial management system rather than re-keyed from extracts. Each indicator appears as a tile carrying its most recently reported value, a time-series trend so direction is visible before you click, and a red, amber or green status set against National Treasury norms or your own approved policy targets. The result is a single view that the finance team, the executive and the oversight structure are all reading from — refreshed daily, and consistent because it is generated once from source rather than assembled separately by each department.

Can I answer my ward councillors when they ask what this number means?

The harder problem in most reporting packs is not a missing number — it is a number nobody can explain. A current ratio, a gearing figure or a collection rate lands in front of a council committee, and the discussion stalls because no one present can say which norm it breaches, why it moved, or what the realistic remedies are. An indicator you cannot explain is an indicator you cannot defend. Every indicator we publish therefore carries written interpretation alongside it: what the indicator is, how it is calculated, and what a high or low reading is telling you about the organisation. Interpretation is surfaced where the user is looking, through an information pane attached to that area of the dashboard, and comprehensively through maintained help documentation. That content is written by municipal finance practitioners rather than report builders — people who have carried a deputy CFO's responsibilities, run budget reform and Municipal Standard Chart of Accounts (mSCOA) implementation, and restructured ledgers for audit. It is the difference between showing a ratio and telling a CFO what that ratio means for the next cash-flow cycle.

Why did this number move — and can I prove it?

An official sees a figure they do not like. To find out why, they request an extract from finance, wait, reconcile it by hand against a report built on a different basis, and by the time the cause is understood the reporting period has closed. Static spreadsheets cannot be interrogated; they can only be rebuilt. Drill-through collapses that into one click. Selecting any indicator opens a dedicated analysis page showing the calculation method, the last reported value, the year-on-year change, the indicator's own history and — the part that matters most — the time series of every input variable in the formula. If the collection rate has fallen, you can see on the same axis whether billing rose or receipts dropped. Filters are global and persist as you move between views, so an analyst can set a period, a service or a ward once and carry it through the whole investigation. Every finding exports to Excel, Word, PowerPoint, PDF or CSV, because the answer usually has to end up in a report to council.

Where does this trend take us if nothing changes?

Financial failure is almost never sudden. It is a ratio drifting the wrong way for eight quarters while nobody is watching the slope. Expenditure grows faster than revenue, a capital programme outruns its funding capacity, a debt threshold is approached — and the first formal signal arrives in an audited statement, long after the cheap corrections were available. Forecasting extends every indicator beyond what has already happened. Each indicator's own validated history is projected forward and presented as a range with an upper and a lower bound rather than as a single number, which is an honest way to show a projection and a more useful basis for a decision. The forecast sits on the same page as the calculation and the input-variable history, so it can be interrogated in context. Because each indicator is already scored against a National Treasury norm or your own policy target, a projection that crosses a threshold can be flagged before it happens rather than diagnosed after the audit. Where the question is larger than a single indicator, the same team builds Long-Term Financial Plans, budget scenario models and affordability envelopes.

A provincial treasury is legally accountable for spotting municipal financial distress early, and is usually doing it by hand. Ten separate reports are pulled from the National Treasury Local Government Database each month, transposed into spreadsheets, reformatted into presentations and memoranda for the MEC for Finance and National Treasury, and filed. There is no consistent history, no comparison across municipalities on the same basis, and a real risk of transcription error in numbers that trigger intervention decisions. The Municipal Finance Management Act (MFMA) monitoring dashboard replaces that monthly scramble. Data is drawn from the National Treasury Local Government Database — the same submitted, processed figures National Treasury itself works from — transformed through purpose-built scripting into a relational repository, and published as an interactive web-based dashboard covering every municipality in the province on a common basis, with history retained. Its purpose is oversight rather than compliance reporting. Sections 5 and 6 of the MFMA delegate the duty to monitor implementation of the Act, and the dashboard is built as an early-warning instrument for exactly that duty: identifying where support or intervention is required, and evidencing it when the province reports upward.