What Is mSCOA? A Plain-Language Guide for Municipal Officials

Incorrect or inconsistent classification of municipal transactions remains one of the recurring causes of audit findings in South Africa. The Auditor-General’s reports regularly cite poor application of the Municipal Standard Chart of Accounts (mSCOA) as a factor in qualified or adverse opinions. When finance and administration staff do not have a clear grasp of what is mSCOA and how it applies to daily transactions, the risk of misclassification rises and so does the risk of missing a clean audit. This guide explains mSCOA in plain language: what the acronym means, why National Treasury introduced it, who it applies to, what happens when a municipality is not compliant, and where to go for deeper guidance.

What does mSCOA stand for?

mSCOA stands for Municipal Standard Chart of Accounts. In simple terms, it is a standardised list of codes that every municipality in South Africa must use when recording and reporting money in and money out.

Instead of each municipality using its own labels and categories, mSCOA gives everyone the same “dictionary.” When your municipality records revenue, expenditure, assets, or liabilities, it must classify each transaction using these standard codes. That way, National Treasury, the Auditor-General, and the public can understand and compare municipal finances across the country.

mSCOA is not optional. It is required by the Municipal Finance Management Act (MFMA) and the Municipal Standard Chart of Accounts Regulations issued by National Treasury. When someone says “we need to be mSCOA compliant,” they mean your municipality must use this standard chart of accounts correctly when preparing its books and reports.

Why did National Treasury introduce mSCOA?

Before mSCOA, municipalities used different charts of accounts and different ways of classifying the same types of transactions. That made it difficult to:

Compare one municipality’s spending or revenue with another’s.
Aggregate data at provincial or national level for policy and planning.
Audit financial statements in a consistent way.
Hold municipalities to a single, transparent standard.

National Treasury introduced mSCOA to fix this. The goals are standardisation (everyone uses the same codes), transparency (it is clear what each code means), and comparability (you can compare municipalities fairly). When every municipality classifies “water revenue” or “employee costs” the same way, the system works: Treasury can see where money is going, the Auditor-General can verify that figures are correct, and councils and residents can make better decisions. The same codes also support in-year reporting under the MFMA, so Section 71 and Section 72 submissions tie directly to the annual financial statements without reclassification.

How mSCOA fits into the wider framework of municipal finance law is set out in the MFMA compliance requirements for 2026, which covers reporting deadlines, in-year submissions, and what auditors look for.

The regulatory framework behind mSCOA

mSCOA is grounded in law and regulation, not policy preference. The Municipal Finance Management Act (Act 56 of 2003) provides the statutory basis for municipal financial management and reporting. National Treasury then issued the Municipal Standard Chart of Accounts Regulations to prescribe the standard chart of accounts that all municipalities must use.

The Auditor-General audits municipal financial statements against the MFMA and the prescribed frameworks, including correct application of mSCOA. When the chart of accounts is applied incorrectly or inconsistently, the Auditor-General can report it as a finding and, where material, it can affect the audit outcome. GRAP (Generally Recognised Accounting Practice) standards also apply to municipal financial reporting; mSCOA is designed to work within a GRAP-compliant accounting framework. Understanding this regulatory chain helps officials see why “getting the codes right” is a compliance obligation, not an administrative nicety.

A brief overview of the mSCOA segments

mSCOA is built around a set of segments — think of them as questions every transaction must answer. Each segment is a different dimension of classification. National Treasury defines seven segments. You do not need to memorise them here; the idea is to get a sense of what they do.

Segment	Purpose
Fund	Which “pot” of money does this relate to? (e.g. general fund, water fund, electricity fund.)
Function	Which service or area? (e.g. administration, water, roads, community services.)
Item	What type of revenue or expense? (e.g. employee costs, rates, grants received, bulk purchases.)
Project	Is this linked to a specific project or grant? If yes, which one?
Region	Which geographic area, if your municipality reports by ward or district?
Costing	Which activity or cost centre, for internal cost analysis?
MSC (Municipal Standard Classification)	Other standard categories required by Treasury for reporting.

Not every transaction needs every segment; it depends on the type of transaction and your municipality’s reporting needs. Section 71 monthly reports and Section 72 mid-year reports submitted to National Treasury must align with the same classification used in your annual financial statements, so getting segment coding right at the point of capture reduces rework and audit risk later. When a segment is required, the correct code must be used. For step-by-step detail on the seven segments and how to apply them, see the mSCOA chart of accounts guide and mSCOA segment classification explained. To avoid the errors auditors often flag, read common mSCOA classification errors.

Who does mSCOA apply to?

mSCOA applies to all South African municipalities. There are 257 municipalities in total (metropolitan, district, and local). Every one of them must use the Municipal Standard Chart of Accounts when preparing their annual financial statements and when submitting in-year reports to National Treasury.

Whether you are in a large metro or a small local municipality, the same rules apply. The aim is a level playing field: one standard, one set of codes, one way to report. CFOs, finance managers, revenue officials, and anyone capturing or approving transactions that feed into financial reports need to understand how mSCOA applies to their work.

What happens if we are not mSCOA compliant?

Non-compliance with mSCOA has real consequences for audit outcomes. The Auditor-General checks whether financial statements are prepared in line with the prescribed framework, including correct use of the chart of accounts. When classification is wrong, missing, or inconsistent, the Auditor-General can issue audit findings. In serious cases, that can lead to a qualified or adverse audit opinion instead of a clean audit.

Only a small fraction of South African municipalities achieve clean audits each year. Incorrect or incomplete mSCOA application is often cited as one of the reasons. Typical findings include misclassification of revenue or expenditure across segments, use of invalid or obsolete codes, and incomplete segment data where Treasury reporting requires it. These findings erode confidence in the financial statements and can trigger follow-up questions from oversight bodies.

Persistent non-compliance with the MFMA and related requirements, including proper financial reporting, can also contribute to Section 139 interventions. Under the Constitution, provincial government can step in when a municipality fails to fulfil its obligations. Section 139 is not triggered by mSCOA alone, but poor financial reporting and repeated Auditor-General findings form part of the picture that can lead to intervention. Getting mSCOA right is therefore not only about avoiding audit findings; it is about demonstrating that your municipality manages its finances in line with the law.

Compliance is achievable with the right processes, training, and systems. Clear delegation of classification responsibilities, regular reconciliation to the chart of accounts, and systems that enforce valid codes at capture reduce the risk of errors before they reach the Auditor-General. Training staff who capture transactions on which segment applies to which type of transaction, and reviewing sample transactions before year-end, are practical steps that many municipalities use to improve mSCOA compliance and move toward a cleaner audit outcome.