Planning an mSCOA improvement programme across systems and reporting

Planning an mSCOA improvement programme is an advisory workflow aligning municipal systems, processes, and reporting with national chart standards.

Promulgated under Section 168 of the Local Government: Municipal Finance Management Act 56 of 2003 (MFMA), the Municipal Regulations on Standard Chart of Accounts (2014) establish a mandatory classification framework for South African municipalities. Operating within municipal scope rather than Public Finance Management Act (PFMA) structures, mSCOA regulates transaction-level recording across core financial applications.

National Treasury MFMA Circular No. 134 (issued 20 March 2026 for the 2026/27 MTREF) and Project Detail Documents for chart version 7.1 provide operational guidance for system alignment and roadmap governance. The proposed workstream matrix and acceptance process below are advisory recommendations, not additional statutory requirements.

may not contain data which is mapped or extrapolated

— mSCOA Regulations (2014), regulation 5(1)(c)

While external technical specialists assist in structuring improvement workflows, Regulation 13 requires the accounting officer to take necessary implementation steps, including delegating appropriate powers and duties. External assistance does not replace those responsibilities.

Establishing a comprehensive baseline and system landscape assessment

An mSCOA improvement programme begins with an empirical baseline review across the municipality's ICT system landscape and sub-system integrations. Under MFMA Circular No. 134, municipalities must evaluate whether core financial software and third-party sub-systems comply with minimum business process specifications.

The baseline assessment examines whether sub-systems—such as billing, payroll, asset management, and supply chain—integrate seamlessly with the general ledger without relying on manual data extrapolation. Evaluating data provenance requires reviewing historical transaction files.

Regulation 5(1)(c) mandates that the chart may not contain mapped or extrapolated data (mSCOA Regulations 2014, page 9). A documented baseline helps the municipality identify and prioritise underlying defects before technical modifications commence.

Mapping multi-dimensional chart dependencies and change controls

mSCOA requires multi-dimensional transaction recording across the seven segments in the Regulations, while Municipal Standard Classification reflects each municipality’s own structure: Funding, Function, Municipal Standard Classification, Project, Regional Indicator, Item, and Costing. Technical planning must map inter-segment dependencies to prevent posting errors.

Project Detail Documents for version 7.1 of the Regional segment specify RX account structures across 13 breakdown levels, requiring every transaction to be assigned to the lowest relevant geographical region or head office without utilising retired default accounts.

MFMA Circular No. 134 states that budget virements resulting in segment changes—such as introducing a new project or changing a region—are prohibited as virements and must be processed through a formal council-approved adjustments budget. Change control protocols ensure adjustments comply with virement rules.

Structuring practical test routines and data string validations

Testing system reconfigurations involves validation routines prior to uploading data strings to National Treasury's GoMuni portal. MFMA Circular No. 134 highlights that Stage 3 validation had not been concluded and was planned for the 2027/28 MTREF. Its preparation guidance identifies opening balance, function and regional balancing checks, including rules planned for chart version 7.2.

Municipalities must incorporate validation rules into system testing to detect transactional errors internally. Crucially, municipal finance leaders must recognise that a successful portal data upload does not automatically prove data accuracy or financial credibility.

An uploaded data string may pass technical formatting checks while containing underlying sub-ledger misclassifications. Practical testing must verify sub-ledger posting accuracy, salary clearing account unbundling, and cash flow table linkages.

Municipal finance teams should execute key technical steps across five core workstreams:

• Executing an annual mSCOA roadmap self-assessment using the Financial Management Capability Maturity Model (FMCMM) system.
• Tabling the comprehensive mSCOA roadmap and annexed e-roadmap in municipal council alongside annual budget documentation.
• Reconciling third-party sub-system transaction feeds to ensure seamless integration with the core general ledger.
• Enforcing validation rules to unbundle salary clearing accounts and eliminate opening balance rollover discrepancies.
• Conducting structured capacity building for finance officials across all system modules.

Defining acceptance evidence, handover and institutional ownership

A successful mSCOA improvement programme depends on establishing clear acceptance criteria for technical deliverables and executing a structured handover to permanent municipal staff. MFMA Circular No. 134 emphasises that the municipal mSCOA roadmap must be broader than vendor software upgrades and must be fully owned and driven by the municipality rather than external consultants or system vendors.

For this proposed workflow, technical acceptance should require verified evidence of system functionality, operational proficiency, and governance oversight. A practical handover should enable line managers to assume full operational ownership of routine mSCOA processing, monthly reporting, and roadmap maintenance.

Under Regulation 13, the accounting officer delegates operational responsibilities to appropriate officials while ensuring personnel receive continuous capacity building. Documented standard operating procedures ensure internal teams maintain chart integrity independently after advisory support concludes.

Workstream and dependency matrix for mSCOA improvement

The table below presents an advisory design matrix illustrating how an mSCOA improvement programme can align technical workstreams, key dependencies, accountable municipal owners, and primary acceptance evidence artefacts.

What good looks like

A well-designed mSCOA improvement programme makes gaps between systems, business processes and reporting visible and assigns an internal route to resolve them. By establishing an empirical system baseline, enforcing change controls, executing validation testing, and embedding internal control ownership under municipal accounting officer oversight, local government institutions can improve the evidence supporting their financial reporting.

For the wider context, read mSCOA as a municipal finance and data governance challenge.