Compliance Monitoring
Compliance Breaches by Act
Sorting contraventions by the legislation breached turns a list of incidents into a map of where statutory control is weakest.
Why Grouping Breaches by Act Matters
Not all compliance failures carry the same legal consequence: a breach of the MFMA's supply chain provisions triggers irregular expenditure, while a PRECCA contravention can become a criminal matter. Grouping breaches by the Act or regulation contravened lets the accounting officer and audit committee see concentration, prioritise remediation and meet the AGSA's expectation that material non-compliance is identified and addressed. AuditPro Core classifies each finding against the specific statutory provision so accountability and reporting follow the law, not a generic category.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
Total breaches
184
▼ 12 vs prior year
Material breaches
29
Repeat breaches
47
26% of total
Acts contravened
11
Breaches by legislation
Top contravened sections
| Section | Act | Count | Material |
|---|---|---|---|
| Procurement thresholds | SCM Regs | 22 | 7 |
| Expenditure controls | MFMA | 19 | 5 |
| Reporting deadlines | PFMA | 16 | 4 |
| Data processing | POPIA | 11 | 6 |
| Appointment process | Labour Relations | 9 | 2 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
Provision-level classification
A breach is most useful when tagged to the exact section or regulation it offends, not just the Act in general. That precision is what lets management cite the correct remedy and lets the auditor confirm whether the matter is material non-compliance.
Concentration analysis
When breaches cluster under one statute, the root cause is usually systemic rather than isolated. A spike under the SCM Regulations, for example, points to a procurement process flaw rather than a series of unrelated errors.
Consequence differentiation
Different Acts carry different downstream effects: MFMA SCM breaches feed the irregular expenditure register, while POPIA or PRECCA breaches may invite regulatory or criminal exposure. Classifying correctly routes each breach to the right response.
How AuditPro Core Bridges the Gap
- Statutory taxonomy: findings are tagged to the specific section or regulation, so reporting matches the legal framework rather than a loose label.
- Exception workflow: each breach routes to an owner with a remediation due date and consequence-management flag.
- Continuous monitoring: recurring breaches under the same provision are surfaced as systemic, not incidental.
- Audit-ready export: the breach register exports grouped by Act for the management report and AGSA compliance schedule.
Key Takeaways
- Tag breaches to the precise provision, not just the Act, to drive the correct remedy.
- Clustering under one statute signals a systemic control weakness worth root-causing.
- Differentiate consequences — irregular expenditure, regulatory penalty and criminal exposure are not the same.
- A grouped register is the backbone of the compliance section of the audit report.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.