Scoping hands-on mSCOA support is an advisory commissioning workflow that defines technical deliverables while preserving municipal internal ownership.
In South African local government, municipal finance operates under the Municipal Regulations on Standard Chart of Accounts (mSCOA) promulgated under the Municipal Finance Management Act 56 of 2003 (MFMA). As municipalities prepare for the MTREF, technical support helps address system integration and reporting backlogs. However, municipal leaders must distinguish operational advisory assistance from statutory management accountability under mSCOA governance.
Distinguishing the municipal mSCOA roadmap from adviser task schedules
should not be prepared or driven by system vendors or external consultants
— National Treasury MFMA Circular134,20March2026,section4.3,page16
Commissioning mSCOA support requires separating the municipality's statutory mSCOA roadmap from external adviser task schedules. Under National Treasury MFMA Circular No. 134 (20 March 2026), the municipal mSCOA roadmap is an institutional document that must be owned by the municipality rather than prepared or driven by vendors or consultants.
Section 4.3 of MFMA Circular No. 134 places roadmap preparation and ownership with the municipality rather than external providers (MFMA Circular No. 134, page 16). While an adviser maintains a task schedule detailing specific deliverables, the mSCOA roadmap governs system hardware, governance, functionality, and staff proficiency across municipal units.
Circular No. 134 requires the municipal mSCOA roadmap and annexed FMCMM e-roadmap to be tabled in council alongside annual budget documentation. Conflating an adviser's task schedule with the council-approved roadmap risks eroding internal ownership and creates unmanaged reliance on third-party specialists.
Preserving statutory accounting officer delegations and ownership
Commissioning hands-on support must respect statutory responsibility allocations under local government legislation. Under Regulation 13 of the mSCOA Regulations (2014), the accounting officer must take necessary steps to implement the Regulations, including appropriate delegation, capacity building, systems changes and reporting. Advisory recommendations represent editorial methodology rather than legal obligations.
Regulation 13 explicitly directs the accounting officer to delegate necessary powers and duties to appropriate internal officials, rather than imposing a blanket ban on delegations. While external advisers assist municipal teams with diagnostic reviews and error resolution, the scope should identify authorised municipal decision-makers and the limits of support access; it should not invent a blanket prohibition on lawful delegations.
Preserving internal ownership requires ensuring municipal line managers review, verify, and approve all system configurations and ledger adjustments. External advisers provide technical expertise, but municipal officials must retain decision-making rights to safeguard records.
Managing technical validations across current and planned chart versions
Scoping advisory support requires aligning technical tasks with National Treasury's phased validation framework. As outlined in Section 4.4 of MFMA Circular No. 134, Stage 3 automated validations on the GoMuni upload portal are planned for introduction in the 2027/28 MTREF. Understanding this timeline prevents municipalities from misinterpreting portal feedback.
During the 2026/27 MTREF operating under chart version 7.1, advisers assist municipal teams in resolving data string errors, such as unbundled salary clearing accounts and cash flow table linkages. Technical support helps municipalities prepare for chart version 7.2 updates, which is described in Circular 134 as introducing further validations checking opening-balance rollovers and funding-segment cash-flow links.
advisers assist staff in testing validation rules within software solutions before submitting data strings to the LGDRS. However, technical portal acceptance does not prove substantive accounting correctness, requiring management to perform ongoing sub-ledger reconciliations.
Structuring bounded support deliverables and capability transfer
To maintain control over advisory engagements, municipal leadership must structure support around bounded deliverables and access controls. For diagnosis, the institution may choose read-only access or controlled extracts where authorised. This is a proposed access-control design, not a right of access conferred on advisers by Regulation 5(2)(c).
The following are proposed engagement controls for municipal leaders to adapt to their approved access and delegation arrangements:
- Establishing read-only data extraction access for external specialists during diagnostic review phases.
- Requiring formal written sign-offs from internal line managers before applying system mapping changes.
- Agreeing joint co-performance of sub-ledger reconciliations between external advisers and internal clerks.
- Identifying who may post and approve journals under the municipality’s actual permissions and delegated authority.
A support scope should define how internal staff will practise and demonstrate the agreed tasks before handover. Under Regulation 13(b), the accounting officer must ensure responsible officials receive necessary capacity through training. advisers should co-perform system reviews alongside municipal staff, so internal teams can apply the work and identify matters requiring further support.
Advisory four-column commissioning and acceptance matrix
To operationalise advisory scope management, municipal finance leaders can deploy a structured commissioning matrix. The table below presents an advisory design framework outlining support workstreams, deliverables, access control boundaries, and acceptance evidence requirements.
| Support workstream | Specific technical deliverable | Access & control boundary | Acceptance & skills transfer evidence |
|---|---|---|---|
| System Landscape Review | Sub-system interface diagnostic report | Read-only access to ICT system logs | Reconciled interface report signed by IT Head & CFO |
| Chart Segment Mapping | Version 7.1 posting matrix & virement check | Read-only access to general ledger setup | Verified 7-segment posting matrix signed by CFO |
| Validation & Data Testing | Pre-upload data-quality exception log | System test environment read-only access | Validated test data string log & staff coaching file |
| Capacity & Skills Transfer | Module user guide & competency assessment | Non-administrative training access | Signed staff competency log & training sign-off |
What good looks like
A well-scoped municipal mSCOA support engagement balances external technical assistance with strong internal control ownership. By distinguishing adviser task schedules from the council-approved roadmap, preserving statutory delegations under Regulation 13, aligning technical checks with National Treasury validation timelines, and enforcing skills transfer, municipal leadership can strengthen control ownership and institutional capability.
Sources
- Municipal Regulations on Standard Chart of Accounts (2014) — mSCOA regulations
- Regional Indicator Project Detail Document, version 7.1 (January 2026) — Regional Indicator
- MFMA Circular 134 (20 March 2026) — MFMA Circular No. 134
Frequently Asked Questions
How does the municipal mSCOA roadmap differ from a consultant's task schedule?
Under Section 4.3 of MFMA Circular No. 134, the municipal mSCOA roadmap is an institutional plan covering hardware, governance, system functionality, and staff proficiency across departments . A consultant's task schedule is a contract workplan detailing specific deliverables . Circular No. 134 explicitly mandates that the municipal roadmap must be owned by the municipality and not prepared or driven by consultants .
Does mSCOA Regulation 13 prohibit the delegation of mSCOA operational tasks?
No, Regulation 13 of the mSCOA Regulations (2014) explicitly requires the municipal accounting officer to delegate necessary powers and duties to appropriate internal officials . Delegating operational duties to trained staff supports administration while maintaining internal ownership over records .
When will Stage 3 automated validations be introduced by National Treasury?
Section 4.4 of MFMA Circular No. 134 states that Stage 3 automated validations were planned for the 2027/28 MTREF in the March 2026 circular . Municipalities should request system vendors to incorporate validation rules within software to resolve errors in funding, opening balances, and regional segments .
What key technical validation changes are planned for mSCOA chart version 7.2?
Under Section 4.4 of MFMA Circular No. 134, chart version 7.2 will implement automated validation rules to enforce proper funding segment usage and Cash Flow Statement population . Additionally, version 7.2 will introduce checks over year-end opening-balance rollovers. The proposed support should test reconciliation differences and supported adjustments; it should not set every ledger account balance to zero .
How can a municipality ensure that hands-on support results in genuine skills transfer?
Municipalities can specify joint performance of selected tasks and review whether staff can repeat them independently . Under Regulation 13(b), the accounting officer must provide for responsible officials’ capacity. The proposed support contract can define training evidence, handover acceptance and payment conditions without presenting those design choices as automatic statutory requirements .
Read mSCOA as a municipal finance and data governance challenge for the wider context.