MFMA Section 71 Reporting Reliability — Audit & Governance Dashboard

Why Section 71 reports are only useful if they are reliable

MFMA Section 71 requires monthly in-year budget statements so councils and treasury can steer spending before year-end, but these reports only support decisions if they reconcile to the eventual audited figures. Where monthly reporting diverges materially from the audited year-end position, in-year governance has been operating on unreliable information. AuditPro Core tests Section 71 reliability by reconciling monthly statements against audited outcomes so oversight bodies know whether the dashboards they rely on can be trusted.

The Numbers

AuditPro Core renders this view from your tenant's live, tamper-evident records. The figures below are illustrative sample data.

Munis assessed

257

Reliable reporting

61%

▲ 4%

Material variance to AFS

entities

Non-submission months

412

Section 71 reliability rate over time

Variance between in-year and audited figures

Reported item	Avg variance %	Munis affected
Revenue collected	14	71
Operating expenditure	11	58
Capital spending	22	84
Cash position	9	44

Figures shown are illustrative sample data for demonstration. AuditPro Core renders these views from your own tenant's live, tamper-evident records.

The purpose of in-year reporting

Section 71 reports give early sight of revenue, spending and cash so corrective action can be taken during the year. Their value depends entirely on their accuracy.

Reconciliation to audited figures

Comparing the sum of in-year reporting to the audited year-end position reveals systematic over- or under-statement. Large gaps mean monthly figures were misleading decision-makers.

Why divergence happens

Unprocessed accruals, premature revenue recognition and weak month-end discipline cause in-year figures to drift from reality. The drift only becomes visible at audit unless tested.

How AuditPro Core Bridges the Gap

In-year reconciliation: Section 71 monthly statements are reconciled against the audited year-end figures.
Exception workflow: material divergences raise a flag pointing to the affected reporting lines.
Traceability to source: each variance links to the in-year report and the audited balance.
Continuous monitoring: reliability is tracked monthly rather than discovered only at year-end.

Key Takeaways

Section 71 reports steer in-year spending only if they reconcile to audited results.
Material monthly-to-audited gaps mean decisions ran on unreliable information.
Accrual and revenue-recognition weaknesses are common causes of divergence.
Testing reliability monthly catches drift before year-end exposes it.