What ERPGov is
ERPGov is a browser-native business process management portal developed by CCG Systems. It is not a replacement for your ERP — it is a process and control layer above it. Your finance system remains the system of record; ERPGov governs how work reaches it, exposing the full functional scope of your ERP through a responsive web interface and adding CCG-developed modules built specifically for South African public finance requirements — across the MFMA, PFMA and FMPPLA environments.
The design decision that matters most: ERPGov reads and writes directly against your existing ERP database. There is no migration project, no parallel data set, and no risk to the data investment you have already made. Your ERP licences, your transaction history, your chart of accounts — all stay exactly where they are
Three legislative frameworks, one platform
South African public finance is governed by three statutes, with two charts of accounts and three distinct reporting and oversight regimes between them. ERPGov is configured to whichever applies to your institution — the process engine is common, the classification, reporting and oversight layer is not.
| MFMA Local government | PFMA National & provincial | FMPPLA Parliament & Provincial Legislatures | |
|---|---|---|---|
| Institutions | Municipalities and municipal entities | National and provincial departments, constitutional institutions and public entities | Parliament and the provincial legislatures |
| Chart of accounts | mSCOA — the Municipal Standard Chart of Accounts | SCOA — the Standard Chart of Accounts maintained by National Treasury | SCOA, applied to the legislative sector's programme and vote structure |
| Accounting officer | Municipal Manager | Head of Department or Chief Executive Officer | Secretary to Parliament or to the Legislature |
| Oversight | Council; National and Provincial Treasury | Executive Authority; National and Provincial Treasury | Executive Authority (Speaker / Chairperson) and the Act's oversight mechanism, rather than Treasury directly |
| Budget & in-year reporting | MBRR schedules; s71 monthly budget statements; s72 mid-year budget and performance assessment; adjustments budget | ENE / EPRE documentation; in-year monitoring returns; quarterly performance reporting | Annual budget approved by the Executive Authority; monthly and quarterly reporting; strategic and annual performance plans |
| Accounting framework | GRAP, in full | Modified Cash Standard for departments; GRAP or IFRS for public entities, by classification | GRAP |
| Procurement | MFMA SCM Regulations | Treasury Regulation 16A and National Treasury SCM instruction notes | An institution-specific SCM framework adopted under the Act, consistent with s217 of the Constitution and the PPPFA |
| Common to all three | Central Supplier Database; audit by the Auditor-General; delegated authority frameworks; irregular and unauthorised or fruitless and wasteful expenditure regimes; POPIA | ||
The FMPPLA column is the one most often mishandled. Legislatures are frequently treated as if the PFMA applied to them directly — it does not. The accounting officer, the approval route for the budget, and the oversight mechanism are all different, and a workflow configured on PFMA assumptions will route approvals to the wrong authority.
Why a process layer rather than a new ERP
In our financial statement review and chart remediation work, the recurring findings are rarely errors in the accounting engine. They are process failures: expenditure incurred before a commitment is raised, requisitions that bypass the delegated approver, and supporting documentation that cannot be produced at audit. Replacing the accounting system does not address any of those. ERPGov leaves your proven, supported ERP exactly as it is and rebuilds the layer where the control needs to sit.
What ERPGov changes
Process governance, not just screens
A configurable workflow engine models the real approval and escalation hierarchies of the public sector — delegations of authority, monetary thresholds, acting arrangements, escalation on delay, and a complete audit trail of every decision. Approval routes are configured to the authority your legislation actually vests: Council, Executive Authority or Speaker, as the case may be.
Controls at the point of capture
Budget availability, chart segment completeness and supporting documentation are validated before a transaction is committed — the practical control against unauthorised expenditure under MFMA s15, PFMA s38 and s45, or the equivalent duties imposed on a legislature's accounting officer under the FMPPLA, and against irregular expenditure under whichever SCM framework applies. Non-compliant work does not proceed to the ledger.
No data migration
Real-time integration against your live ERP database. Migration risk is eliminated because there is no migration — the portal is a new process and interface layer, not a new system of record.
ERP functionality extended
CCG-developed business logic fills the gaps between generic ERP and South African statutory requirements — mSCOA or SCOA segment enforcement, prescribed in-year reporting formats, and asset treatment aligned to the framework your institution reports under.
Unified module access
Single sign-on across finance, procurement, assets, HCM and reporting. One login, one portal, one set of user credentials to administer — and no client software to deploy or maintain.
Anywhere access
Approvals, requisitions, leave and reporting from desktop, tablet or mobile. Managers and approvers are no longer tied to an office workstation to keep processes moving.
Core modules
ERPGov ships with ten core modules covering the domains every MFMA, PFMA and FMPPLA institution needs. The set is not fixed — because every module is built on the same workflow, identity and document foundation, further modules can be introduced without re-architecting the platform or disturbing what is already in production.
Chart of accounts enforcement and statutory reporting
In every sphere the chart of accounts is not a reporting layer — it determines whether a transaction is valid at all. ERPGov treats classification structurally rather than as a reporting-time reconciliation exercise, and is configured to whichever chart applies to your institution.
mSCOA
All seven mSCOA segments — Project, Function, Item, Fund, Costing, Regional and Municipal Standard Classification — carried as mandatory dimensions on every transaction and validated against the current released chart version. Data strings are formatted and validated for LGDRS / GoMuni submission so rejections are resolved internally rather than at the portal.
SCOA
The SCOA classification framework applied as mandatory dimensions on every transaction, aligned to the segment structure and item definitions published by National Treasury and reconcilable to the transversal systems your institution reports through. For legislatures, mapped to the programme, sub-programme and vote structure the Act's reporting is built on.
The controls applied over the chart are common to all three frameworks:
Enforcement at capture
segments are mandatory dimensions, not optional analysis fields. Incomplete or invalid classification strings do not post.
Cross-segment validation
invalid segment combinations are rejected at capture rather than flagged at year end.
Chart version currency
segment tables and validation rules are maintained as National Treasury issues new chart releases and circulars, so compliance is sustained rather than re-projected each year.
Legacy code mapping
historical coding is translated to the current chart during implementation so prior-year comparatives remain usable.
Prescribed reporting outputs
MBRR-format s71 and s72 schedules for MFMA institutions; in-year monitoring and quarterly reporting for PFMA institutions; and monthly, quarterly and annual reporting to the Executive Authority for institutions under the FMPPLA.
Continuous exception reporting
anomalous or incomplete transactions are surfaced while current, not reconstructed during audit.
Platform capabilities inherited by every module
These are properties of the platform rather than per-module features, and apply automatically to any module added after implementation. Identity, access control and audit trail are covered under Security & Governance.
Real-time integration with your existing ERP database
no staging, no overnight batch, no reconciliation between portal and ERP.
Multi-company and multi-environment access
Production, Development and UAT reachable from the same portal with clear separation.
Document linkage at every transaction
the DMS is available from within each module, so supporting evidence is attached where the work happens rather than filed separately.
Configurable workflow routing
approvals, escalations and delegations modelled on the authority your legislation vests.
How ERPGov is built
ERPGov follows a conventional three-tier architecture with a clearly separated API layer. That separation is deliberate: it lets the process layer evolve independently of the ERP beneath it, and it means ERP upgrades and ERPGov releases do not have to be coupled.
Architecture layers
Presentation tier
Browser-native responsive web portal. No client software installed on user devices. Rendered for desktop, tablet and mobile. Session and identity handled at this layer against your directory.
Application / API tier
ERPGov application services and REST API endpoints. Hosts the workflow engine, business rules, validation logic and document management services. This is where CCG-developed public sector functionality lives — separate from, and non-invasive to, your ERP application.
Data tier
Your existing ERP and payroll databases on Microsoft SQL Server. ERPGov is a consumer of this tier, not a replacement for it. Your ERP remains the single system of record and the source of every statutory report.
Deployment topology
The same application supports three deployment configurations, selected against your connectivity, data residency position and internal IT capacity.
On-premises
Presentation, application and data tiers hosted in your own environment. Full institutional control and offline resilience. Suits entities with existing server infrastructure and internal IT capability.
Cloud
Hosted delivery with managed patching, backup and disaster recovery. Lowest internal infrastructure burden and shortest time to stand up.
Hybrid
Your ERP database and financial records remain in your own environment while the portal presentation layer is cloud-delivered. The usual configuration where data residency is a stated requirement.
Architecture principles
One version of financial truth
All subsystems feed the general ledger. Nothing posts to the GL except validated, authorised transactions, and both statutory and management reporting derive from that same ledger — so the portal, the budget statements and the annual financial statements articulate to one source.
Non-invasive extension
ERPGov does not modify your ERP's application code or database schema. Your ERP installation remains vendor-supportable and upgradeable, and CCG functionality is layered cleanly above it.
Separation of environments
Production, Development and UAT are distinct environments with distinct data. Configuration and release changes are proven in UAT before touching production financial data.
Data classification and sovereignty
The architecture explicitly documents what data traverses the portal layer, what does not, and what is never stored outside your environment — so data residency questions have documented answers.
Integration architecture
ERPGov's integration design connects the finance, payroll and operational systems that MFMA, PFMA and FMPPLA institutions already run. Each interface is documented in the integration inventory with its direction, trigger, data set and control points.
Payroll to general ledger
Your payroll system posts payroll journals to the general ledger through a controlled, reconciling integration. Control totals tie to the payroll register by design, closing a reconciliation gap that recurs frequently in the financial statement reviews we perform.
HCM bridge
The ERPGov HCM module interfaces to your payroll and HR system through a dedicated API service, adding travel, onboarding, back-pay and promotion reporting functionality without altering the payroll system itself.
Procurement commitment control
Purchase orders raised in P2P commit against BUD in real time. Goods receipt matches to order, invoice matches to both. Three-way matching is enforced, not optional.
Asset and depreciation posting
Capital acquisitions and depreciation post from the asset register to the GL automatically. The register and the GL tie without manual journals or year-end reconciliation exercises.
CSD and supplier data
E-Procurement links vendor registration to Central Supplier Database records, keeping supplier master data aligned with National Treasury's authoritative source — a requirement common to all three procurement regimes.
Identity federation
Unified portal single sign-on federated to Microsoft Entra ID (formerly Azure AD), so joiners, movers and leavers are handled once in your directory and flow through to ERP access.
Infrastructure design
Every ERPGov engagement includes a documented infrastructure architecture covering sizing, storage, availability and the specific network prerequisites the portal requires.
Sizing
production workload modelled to user count and transaction volume
High availability
resilience design proportionate to institutional risk appetite
Hardened environments
supported where outbound access is restricted by policy
Storage
production workload modelled to user count and transaction volume
Connectivity
network, certificate and DNS prerequisites specified in advance
Test environment
parallel portal hierarchy for UAT and training
CCG supplies the full technical prerequisite specification to your IT function before implementation begins, including firewall, certificate and DNS requirements. Nothing is discovered on go-live weekend.
Security, control and governance alignment
Public finance systems carry public money and personal information. ERPGov's architecture is documented against recognised international frameworks so that your internal audit function, your external auditors and your accounting officer are all working from the same evidence base.
Framework alignment
COBIT 2019
Architecture and management practices mapped to COBIT governance and management objectives — including architecture management, change enablement and managed security services.
ITIL 4
Service management practices aligned to the ITIL Service Value System, covering incident, change, service request and architecture management for the operational platform.
ISO/IEC 27001:2022
Platform controls mapped to Annex A, spanning access control, cryptography, secure development, logging, and supplier and network security.
POPIA
Personal information of employees, ratepayers and suppliers is processed under the conditions of the Protection of Personal Information Act — purpose limitation, access restriction, security safeguards, and documented treatment of any cross-border processing.
Corporate governance of ICT
The architecture and control documentation is structured to support the ICT governance assessments every sphere is measured against in AGSA IT audits — change management, user access management and IT service continuity — whether assessed against municipal ICT governance requirements, the Corporate Governance of ICT Policy Framework applicable to departments, or a legislature's own adopted ICT governance framework.
A note on what alignment means.
CCG documents ERPGov's architecture and controls against these frameworks. That is a mapping exercise supported by written evidence — it is not third-party certification, and we do not represent it as such. Where your institution requires certified assurance, we will say so plainly and scope it separately.
Controls built into the platform
Identity and access
single sign-on with multi-factor authentication, federated to Microsoft Entra ID; role-based permissions administered centrally.
Segregation of duties
capture, review, approval and posting are distinct roles with system-enforced separation.
Complete audit trail
every transaction records the acting user, timestamp and change history. Nothing is silently amended.
Encryption in transit
SSL/TLS enforced across all portal and API communication.
Documented data classification
single sign-on with multi-factor authentication, federated to Microsoft Entra ID; role-based permissions administered centrally.
Environment separation
production financial data is isolated from development and UAT activity.
Change control
configuration and release changes follow a documented change process with UAT sign-off.
An architecture document you can hand to your auditor.
Every ERPGov implementation is accompanied by a full architecture and infrastructure document covering component inventory, server roles, integration inventory, data classification, network requirements and control mapping. When AGSA asks how the system works, the answer already exists in writing.
Let's discuss your ERP position
Whether you report under the MFMA, the PFMA or the FMPPLA, and whether you are assessing ERPGov for the first time or reviewing the processes running over an existing platform, we will give you a candid view of scope, sequence and effort.