Municipal finance services
mSCOA and MFMA compliance
mSCOA is not a software problem. It is a data discipline problem that shows up in software. We help municipalities get the segments right at the point of transaction, so that section 71 reports, the budget and the annual financial statements all tell the same story.
Where mSCOA usually goes wrong
Municipalities went live on the Municipal Standard Chart of Accounts in July 2017. Almost a decade on, the systems are in place nearly everywhere. What is often still missing is the discipline behind them.
The common problems are consistent from one municipality to the next. Transactions get posted to a default or suspense item because the correct segment string is not obvious at capture. The project segment is used loosely, so capital spend cannot be traced to a project or an asset. Budget and actual are captured on different segment logic, which makes variance reporting meaningless. Journals are passed at year end to force a trial balance to behave, and those journals do not carry proper segmentation.
By the time this reaches the AFS, the damage is already done. The chart cannot be corrected retrospectively without a lot of work, which is why we prefer to fix the capture rather than clean up afterwards.
What we help with
mSCOA implementation and support
Chart configuration, segment mapping, opening balance migration and the practical rules your staff need in order to capture correctly the first time.
Section 71 reporting
Monthly budget statements prepared and reconciled to the ledger, submitted within the required timeframe, with variances explained rather than just reported.
Budget alignment
The approved and adjusted budget captured on the same segment basis as actuals, so the GRAP 24 comparison in the AFS reconciles without a manual bridge.
Data quality reviews
Interrogation of posted transactions to find default postings, unsegmented journals, project segment misuse and mapping that has drifted.
Financial management support
Hands on support to the CFO and finance staff through the budget and reporting cycle, including temporary staff during peak periods.
System alignment
Working in Munsoft and other municipal financial systems so recommendations are practical for the system you actually run.
The MFMA calendar we work to
| Requirement | Section | Timing |
|---|---|---|
| Monthly budget statement to the mayor and treasuries | s71 | Within 10 working days after month end |
| Mid-year budget and performance assessment | s72 | By 25 January |
| Adjustments budget | s28 | Usually by end February |
| Annual financial statements to the Auditor-General | s126 | Within 2 months of year end, so 31 August for a 30 June year end |
| Consolidated annual financial statements | s126 | Within 3 months, so 30 September |
| Annual report tabled in council | s127 | Within 7 months of year end |
Swipe sideways to see the rest of the table.
Most municipalities meet these dates. The 2024-25 audit outcomes put on time AFS submission at 98 percent. Meeting the date and having the underlying data hold up are two different things, and the second is where we spend our time.
Why this matters for the audit
mSCOA data quality is not a reporting inconvenience. It drives findings directly. Capital expenditure that cannot be traced to a project cannot be traced to an asset, which becomes a property, plant and equipment finding. Budget comparisons that do not reconcile become a GRAP 24 finding. Expenditure classified to the wrong item becomes a misstatement in the statement of financial performance. Unsegmented journals become an internal control finding.
Fixing the chart usually improves several audit areas at once, which is why we treat it alongside asset registers and statement preparation rather than as a standalone exercise.
Frequently asked questions
What is mSCOA?
The Municipal Standard Chart of Accounts, introduced by the Municipal Regulations on a Standard Chart of Accounts and effective for all municipalities from 1 July 2017. It prescribes a multi segment classification for every transaction, covering project, function, item, funding, region and costing, so that municipal financial information is comparable across the country.
We are already on an mSCOA compliant system. Why would we need help?
Being on a compliant system means the software can produce a valid segment string. It does not mean the strings being captured are correct. Most of the work we do is on capture discipline, mapping that has drifted over time, project segment usage and journals that were passed without proper segmentation.
Can you prepare our section 71 reports?
Yes, either preparing them or reviewing what your team produces before submission. Either way the report gets reconciled to the ledger first, because a section 71 report that does not agree to the general ledger creates a problem later in the year rather than solving one now.
Do you work with Munsoft?
Yes. Munsoft is one of our primary systems, along with CaseWare for statements and working papers. We also work with other municipal financial systems, since the underlying mSCOA logic is the same regardless of which vendor the municipality uses.
Can mSCOA problems from prior years be corrected?
Partly. Current year capture can be corrected as you go, and mapping can be fixed going forward. Prior year data can sometimes be reclassified where the underlying transaction detail still exists, but where it does not, the practical answer is to document the limitation and prevent it recurring rather than to reconstruct history that cannot be supported.
Discuss your municipality’s requirements
Ambition Partners Advisory is a Chartered Accountant (SA) led practice working with municipalities, municipal entities, government departments and public entities across South Africa. Tell us where you are in the reporting cycle and we will send you a scope, timeline and fee.