Scoping finance close, reconciliation and preventative-control support

Scoping finance close, reconciliation and preventative-control support is the process of defining the technical scope, evidence access, and deliverables of operational support.

Defining the commissioning mandate, reporting framework, and institutional boundaries

Before commissioning external support for financial close, reconciliations, or preventative controls, an institution must establish a formal commissioning mandate that verifies its governance context, reporting period, and applicable accounting framework.

provide sufficient time for reviewing the financial statements

— Auditor-General South Africa, Preventative Control Guide5, review guidance

The mandate should record the basis for the actual reporting framework and edition. Do not allocate MCS, GRAP or IFRS solely from a generic institutional label; confirm the reporting period and applicable requirements.

Public entities cannot automatically be assumed to apply MCS or GRAP without verifying their statutory listing, reporting framework, and financial year-end rules. Period-specific guidelines must also be distinguished from permanent statutory rules and accounting standards.

National Treasury's Guideline on Financial Year-end Procedures 2024–2025 prescribes specific closure schedules and submission dates for PFMA-compliant institutions for that reporting cycle. It does not establish universal statutory deadlines across municipal entities or private corporate sectors.

Similarly, the Auditor-General South Africa (AGSA) Preventative Control Guide 05 provides internal control guidance on financial statement preparation, offering practical control benchmarks rather than serving as an accounting standard. Proposed commissioning mandates, advisory roles, and review templates serve as advisory operational tools rather than newly enacted statutory mandates. Defining these boundaries upfront ensures that external support targets documented control vulnerabilities without exceeding institutional authority.

Determining account populations, ledger modules, and evidence dependencies

Scoping close, reconciliation, and preventative-control support differs fundamentally from managing a general close implementation roadmap or completing an individual balance-sheet substantiation template. An implementation roadmap sequences an agreed improvement programme, while a substantiation pack organises evidence and exceptions across selected account classes. In contrast,, scoping support establishes the specific account populations, ledger modules, and operational boundaries for external assistance.

The commissioning scope must map target account populations across key ledger modules—such as general cash accounts, trade receivables, trade payables, property plant and equipment registers, and provisions. Identifying these specific account populations upfront prevents scope creep and focuses support on high-risk transaction streams.

Evidence access dependencies must be mapped before operational support begins. External consultants require timely access to primary transaction records, contracts, sub-ledgers, bank statements, and operational personnel. If primary documentation is missing or unaligned, the documentation gap must be logged as an operational dependency rather than filled through arbitrary assumptions.

Scope conclusions must remain strictly bounded by verified empirical evidence. The identification of a reconciliation discrepancy or missing contract file does not authorise automatic write-offs, retrospective approvals, or unverified ledger adjustments.

Distinguishing consultant preparation, management approval, and independent oversight

Establishing clear operational boundaries between consultant preparation, management approval, and independent oversight is essential for sound financial governance. External consultants provide operational capacity, technical analysis, and draft reconciliations, but they do not exercise statutory management authority or issue formal audit assurance opinions.

Under the PFMA, accounting officers and accounting authorities retain ultimate legal responsibility for financial management, internal controls, and statement accuracy. Consultant preparation of reconciliations or control schedules does not diminish executive accountability or alter statutory delegation frameworks. Management retains sole authority to approve journal entries, adjust accounting records, and accept draft financial statements.

Preventative control frameworks emphasise that internal audit units and audit committees provide independent evaluation and oversight of financial controls. Internal audit units evaluate control effectiveness and report findings to management, but they do not provide an automatic financial statement audit opinion.

while the AGSA serves as the primary external auditor for public institutions under constitutional mandate, it is not the universally exclusive auditor for every entity type across all commercial sectors unless specified by law. Management must maintain realistic expectations regarding audit independence, recognising that external auditors evaluate submitted statements independently without assuming management responsibilities.

Structuring deliverables, acceptance criteria, and operational handover

A well-scoped support assignment specifies clear deliverables, formal review mechanisms, and explicit management acceptance criteria. Rather than open-ended operational assistance, support outputs should take the form of completed reconciliation files, exception logs, draft journal proposals, and updated control procedure documentation.

Acceptance criteria must require that all consultant-prepared reconciliations align strictly with the general ledger, include verifiable supporting evidence, and detail any unresolved exceptions. Management must review draft reconciliations against primary records before approving journal entries or incorporating figures into draft financial statements.

Operational handover is a vital phase of any external support mandate. AGSA preventative control guidance highlights that where external specialists or consultants are utilised, management must ensure effective oversight and knowledge transfer to internal staff.

Building internal technical capability ensures that resolved reconciliation routines and preventative controls are permanently embedded into standard operating procedures and routine period-close disciplines. This supports internal ownership and reduces avoidable reliance on external support in subsequent financial cycles.

Operational scoping and accountability matrix

The matrix below outlines the structural scope, required outputs, retained management ownership, and formal acceptance criteria for commissioning close, reconciliation, and preventative-control support.

Sustaining governance and control over external support mandates requires embedding structured oversight mechanisms into project execution:

• Establishing a formal project charter that defines technical boundaries, account populations, data access rules, and executive review milestones before operational work begins.

• Requiring all consultant deliverables to be presented as structured reconciliation files supported by primary evidence and general ledger control account extracts.

• Maintaining strict separation between consultant preparation activities, executive management approvals, and independent internal audit or audit committee oversight functions.

• Agreeing competent management review and the applicable approval route for consultant-prepared reconciliations and proposed adjustments.

• Implementing structured staff shadowing and operational handover sessions during deliverable finalisation to ensure technical knowledge is retained within the internal finance team.

For wider context, read the close and balance-sheet substantiation overview.