Conflicts of Interest
Declaration Late Submissions
An interest declaration filed after the deadline is a window during which conflicts went undisclosed and decisions may have been compromised.
Why Declaration Timeliness Matters
Annual financial interest declarations are a statutory integrity control under the Public Service Regulations and supporting MFMA and PFMA frameworks, designed to surface conflicts before they distort official decisions. Late submissions are not a clerical nuisance — each one represents a period in which an official acted without their interests on record, which AGSA and the Public Service Commission treat as a control failure. AuditPro Core measures submission timeliness against the statutory deadline so accounting officers can act on non-compliance rather than discover it after the fact.
The Numbers
AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.
On-time submissions
84%
▼ 3%
Days past deadline (avg)
12
for late filers
Non-submitters
47
escalated
SMS members compliant
96%
▲ 2%
Cumulative submissions to deadline
Late submissions by department
| Department | Late | Outstanding |
|---|---|---|
| Health | 18 | 9 |
| Education | 22 | 14 |
| Public Works | 11 | 7 |
| Treasury | 6 | 2 |
Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.
The Statutory Deadline
Designated officials must lodge their financial interest declarations by a fixed annual date set in regulation. The deadline is the line that separates compliance from a reportable breach.
The Risk in the Gap
While a declaration is outstanding, the official's conflicts are invisible to those approving their decisions. The longer the delay, the larger the window of unmanaged conflict risk.
Completeness Versus Timeliness
A declaration can be on time yet incomplete, or complete yet late — both undermine the control. Timeliness measures only one dimension and must be read alongside content accuracy.
Consequence Management
Persistent late filing should trigger consequence management, not repeated reminders. Without follow-through, the deadline loses its force and the control degrades.
How AuditPro Core Bridges the Gap
- Deadline reconciliation: AuditPro Core matches every required declarant against actual submission dates and computes lateness automatically.
- Exception workflow: overdue declarants route to consequence management with a documented escalation trail.
- Continuous monitoring: outstanding declarations are visible in real time rather than at a year-end sweep.
- Audit-ready register: the compliance status exports as evidence for the accounting officer, AGSA and the Public Service Commission.
Key Takeaways
- Each late declaration is a measurable window of undisclosed conflict, not a minor admin slip.
- Timeliness and completeness are separate tests; passing one does not satisfy the other.
- Real-time tracking lets accounting officers intervene before the statutory deadline is breached.
- Repeat lateness warrants consequence management to keep the deadline meaningful.
See This on Your Own Data
AuditPro Core renders this dashboard from your tenant's live, tamper-evident records — every figure traceable to source.