Municipalities diagnose revenue leakage by establishing a dated, controlled data baseline and logging unvalidated discrepancies within a structured exception register.
An exception represents a potential data or processing variance rather than a confirmed financial loss. Through systematic investigation, mapped control handovers, and rigorous verification, local authorities may isolate genuine operational errors, billing variances, or timing differences before executing authorised adjustments and tracking cash collections.
Establish a baseline you can reproduce
National Treasury’s MFMA Circular 64, November 2012, emphasises credible baseline information and source-data integrity. For a diagnostic, we recommend recording the extraction date, systems, included periods, record counts and matching rules before analysing differences.
Keep the initial extract and record authorised corrections in subsequent versions. A fixed comparison cohort can make before-and-after analysis reproducible, while a separate change log explains legitimate additions, exclusions or revised assumptions. Do not silently change the denominator.
Match relevant operational datasets to the billing records using agreed identifiers. Log unmatched records for investigation rather than assuming they represent losses. Differences may reflect timing, duplicates, valid policy treatment or errors. Test those explanations against source evidence.
Mapping Handover Controls Across the Revenue Chain
A rigorous revenue diagnostic requires mapping the complete end-to-end municipal revenue chain to identify control gaps, data drops, and processing vulnerabilities. A suggested sequence of handovers across the municipal revenue lifecycle proceeds as follows:
Source Record → Service/Meter/Property → Customer Account → Approved Tariff Application → Bill → Receipt → Debtor Allocation → Bank/Ledger Reconciliation
Every transition within this sequence must have an explicitly assigned operational owner and verifiable supporting evidence. For instance, bridging the transition from Service/Meter/Property to Customer Account could be evidenced by an engineering meter installation completion certificate or formal technical sign-off sheet. Similarly, linking a Customer Account to an Approved Tariff Application calls for evidence supporting the applicable tariff and account classification.
Software applications and automated enterprise resource planning systems alone do not guarantee robust internal control; conversely, manual administrative records or managed spreadsheets are not inherently inadequate provided version control, restricted permissions, and strict oversight governance are maintained.
Section 64(2) of the MFMA requires the accounting officer to take all reasonable steps to ensure the following:
- Section 64(2)(e): Management, accounting and information systems that recognise revenue when earned, properly account for debtors, and track receipts.
- Section 64(2)(f): An internal control system over debtors and revenue collection.
- Section 64(2)(h): Reconciliation of all revenue received—including funds collected by third-party external agents—at least on a weekly basis.
Mapping the handovers gives the team specific places to look for unlinked connections, incorrect tariff parameters or unallocated receipts. Record both the evidence and the limitations of the test rather than assuming every control break has a financial value.
Structure of a Synthetic Exception Register
An exception register functions as the central operational ledger for logging, tracking, investigating, and resolving potential revenue discrepancies. The table below illustrates the proposed structure of a municipal exception register.
Note: The data presented in the table below is purely hypothetical and illustrative for architectural demonstration purposes.
| Fictional case | Evidence and owner to confirm | Status and next decision |
|---|---|---|
| EX-101: meter record has no matched account | Installation record and account search; technical and revenue owners | Unvalidated: investigate the service and billing basis |
| EX-102: tariff code differs across records | Approved schedule and verified account classification; revenue owner | Validated error: obtain the required correction approval |
| EX-103: collecting-agent receipt is unallocated | Agent batch and bank record; receipting owner | Match and allocate the receipt, then verify the reconciliation |
Separate the diagnostic value from the cash result
The following numbers are entirely hypothetical. They demonstrate the distinctions; they are not a forecast or a Kettle client result.
| Stage | Illustrative value | What the figure means |
|---|---|---|
| Identified exceptions | R1,000,000 | Gross value flagged for investigation |
| Excluded after investigation | R400,000 | Valid treatment or timing differences in this fictional example |
| Validated adjustments | R600,000 | R1,000,000 less R400,000 |
| Authorised corrections posted | R600,000 | Ledger adjustments, not cash |
| Receipts matched to the corrected accounts | R450,000 | Cash recorded in this fictional period |
| Difference requiring follow-up | R150,000 | R600,000 less R450,000; not automatically a loss |
The arithmetic alone cannot establish why R150,000 remains unmatched. Review account movements, payment timing and any further adjustments before drawing a conclusion. Likewise, cash arriving after a correction does not by itself prove that the diagnostic caused the payment.
Record sustainable control improvement separately: the changed control, its owner and evidence of operation. Do not turn it into a recurring rand benefit without a defensible method, period and supporting observations. A corrected bill is not cash collected, and an identified exception is not a confirmed revenue loss.
Frequently Asked Questions
How does an exception register differ from a record of confirmed revenue loss?
An exception register logs unvalidated discrepancies—potential data or system variances that serve as leads for investigation. Investigation may establish an error and a valid adjustment; establishing a loss requires a separate assessment of the facts and applicable accounting treatment, ruling out valid exemptions, timing differences, or duplicate records.
What statutory requirements govern municipal revenue reconciliation and internal controls?
Under Section 64(2)(f) of the MFMA, municipalities must maintain an effective system of internal control over revenue and debtors. Furthermore, Section 64(2)(h) explicitly requires that all revenue received, including payments collected by third-party agents, be reconciled at least weekly.
Why must municipal revenue enhancement be treated differently from routine revenue management?
Revenue management covers the existing billing and collection discipline; enhancement concerns increasing revenue generated. Establish the existing baseline and distinguish corrections, additional billing and actual receipts. That distinction makes it possible to discuss growth without overstating the effect of a diagnostic.
Does fixing a billing discrepancy automatically translate into immediate cash recovery?
No. Correcting a billing discrepancy results in an authorised adjustment to a customer account ledger. Actual cash recovery depends on service user affordability, lawful municipal debt collection policies, and the customer's capacity to settle the updated account.
What safeguards must be maintained regarding data protection during a revenue diagnostic?
Use authorised extracts containing only the data needed for the agreed tests. Control access, retention and sharing within the engagement. Keep residents’ personal records out of public enquiry forms; confidential working files require an approved handling arrangement appropriate to their contents.