05/05/2026
Philip de Bruin opens with a genuine acknowledgement of what National Treasury has achieved - describing the shift to mSCOA as a landmark transformation that forced the entire local government technology ecosystem to reinvent itself.
His core argument is simple: you cannot participate meaningfully in the mSCOA environment without proper systems. The reform ended the era of disconnected billing systems, standalone asset registers, and payroll running outside the ERP. It mandates a single data model with one classification structure - and that integration is now the baseline, not an aspiration.
On system compliance, he is direct: virtually all financial ERP systems in local government are mSCOA-compliant. The challenge is not non-compliance - it is familiarity. Switching from one compliant system to another feels disruptive, like moving from Word to WordPerfect, but the underlying logic is the same. The green strings either confirm the system is computing correctly across all segments, or they don't - and there is nowhere left to hide.
He flags two practical realities for municipalities. First, loose-standing systems for asset management and payroll are no longer viable. The integration demands of mSCOA make spreadsheet-based workarounds unsustainable - structured systems are now a hard requirement. Second, APIs and web services are a stopgap, not a long-term solution for managing integrated data.
On the governance upside, he points to full audit trails, automated workflow approvals, role-based access controls and validation at source - meaning a wrong transaction simply cannot be entered without being flagged across all segments. The contrast with the manual era is stark: where Treasury once had to send a fax and wait two weeks for information that might never arrive, properly submitted mSCOA strings make municipal data available nationally in near real time.
His closing point is that the real prize - project-based budgeting, multi-year planning, aligned funding - cannot be achieved outside a structured system. The A schedules alone make manual reporting virtually impossible. The technology infrastructure is ready; what remains is consistent use.
