Planning a financial reporting and accounting improvement programme

A financial reporting and accounting improvement programme is a structured operational framework to resolve technical accounting issues and elevate statement quality.

Establishing the governance, reporting framework, and baseline audit scope

Executing a technical accounting improvement initiative requires establishing a firm governance structure and verifying reporting parameters. Public sector entities operating under the Public Finance Management Act (PFMA) must align financial statement preparation with National Treasury's prescribed framework. Identify the framework actually applicable to the institution and reporting period. Do not assume that GRAP, the Modified Cash Standard or IFRS applies solely because an organisation is publicly owned.

provide sufficient time for reviewing the financial statements

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

It is essential to distinguish between statutory accounting standards and guidance documents issued by oversight bodies. The Auditor-General South Africa (AGSA) Preventative Control Guide 05 provides internal control guidance on financial statement preparation, offering practical control benchmarks rather than constituting an accounting standard itself.

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

Before launching technical remediation, the accounting officer, chief financial officer (CFO), and finance leadership must confirm applicable standard editions and verify prior-period audit findings. Proposed project structures, specialist review committees, and technical documentation templates serve as advisory operational mechanisms to drive quality, rather than newly created statutory mandates. Defining these parameters upfront prevents misdirected effort and ensures that technical accounting workstreams directly address documented audit deficiencies.

Building the technical accounting issue inventory and evidence gap analysis

A disciplined improvement programme relies on a comprehensive inventory of technical accounting issues rather than generic public finance control objectives. Finance functions frequently encounter complex accounting challenges involving asset valuation, lease commitments, financial instrument credit losses, revenue recognition, and unaligned sub-ledgers. The issue inventory categorises every known accounting anomaly, prior-year audit finding, and emerging standard amendment into distinct, manageable technical files.

Each identified issue must undergo a rigorous fact-finding process and evidence gap analysis to establish whether supporting records are valid, accurate, and complete. Under AGSA guidance, reliable financial reporting requires proper record-keeping and orderly document management to substantiate ledger balances. When primary documentation—such as underlying contracts, physical asset logs, or third-party confirmations—is missing, the finance team must document the specific evidence gap before attempting accounting adjustments.

Scope conclusions must remain strictly bounded by available evidence. Identifying a documentation gap or accounting uncertainty does not authorise automatic write-offs, retrospective approvals, or arbitrary ledger adjustments. Instead, the gap analysis establishes the empirical foundation required to determine whether sufficient evidence can be retrieved or whether formal accounting judgements must be formulated.

Formulating technical judgement papers and securing specialist review

When complex accounting transactions cannot be resolved through routine transactional processing, the finance function can use a structured technical judgement paper. Technical judgement papers articulate the factual background of a transaction, analyse the relevant accounting principles, evaluate alternative accounting treatments, and recommend a defensible position. The proposed paper records facts, assumptions and technical reasoning for review; it does not itself establish that an estimate or treatment is correct.

Drafting technical judgement papers requires appropriate technical capacity and specialised expertise within the finance unit. Where internal capacity gaps exist, institutions may engage external technical accounting specialists to assist with technical evaluations. AGSA guidance highlights that when external consultants or specialists are utilised, management must enforce strict deliverable monitoring and ensure knowledge transfer to internal staff so that technical capabilities are permanently retained within the organisation.

Agree a competent technical review route appropriate to the issue and institution. Management should identify who can assess assumptions, applicable requirements and evidence. Internal audit and the audit committee retain their assurance and oversight roles; they are not automatically the preparers or approvers of every technical accounting judgement. A specialist review should record its scope, evidence, conclusions and limitations. It is not automatically a formal assurance opinion or compliance certification.

Authorising accounting adjustments and embedding operational handover

Once a technical judgement paper receives specialist and executive clearance, any resulting accounting adjustments or note disclosures must follow formal authorisation workflows. Journal entries modifying general ledger balances, asset registers, or liability provisions must be supported by approved adjustment schedules and backed by complete audit trails. Under National Treasury guidelines, institutions must ensure that all identified material misstatements are corrected prior to finalising financial statements for submission.

Authorised adjustments must be seamlessly reflected in the primary financial statements and accompanying disclosure notes. Test adjusted figures across the primary statements and supporting schedules, with review by the competent owners through the applicable approval route. Record and resolve any secondary classification errors or discrepancies detected during final statement compilation.

To prevent recurring accounting deficiencies in subsequent reporting periods, the improvement programme must conclude with a formal operational handover. The finance function should update standard operating procedures, standardise monthly reconciliation templates, and deliver targeted training to accounting personnel. Embedding resolved accounting treatments into day-to-day accounting disciplines transforms project-based improvements into sustainable institutional practices.

Structural execution matrix for accounting improvement

The following matrix outlines the core operational workstreams, dependencies, primary owners, and acceptance criteria for executing a technical accounting improvement programme.

Sustaining financial statement quality beyond an improvement programme requires embedding preventative controls directly into routine finance operations. Key operational mechanisms include:

• Maintaining standard operating procedures for all transaction types to ensure consistent accounting classification and processing across all operational units.
• Executing disciplined daily and monthly reconciliations between general ledger control accounts, sub-ledgers, asset registers, and bank statements.
• Performing independent supervisor reviews of monthly reconciliations and spot-checking supporting documentation to detect errors proactively.
• Compiling quarterly and half-yearly interim financial statements to test accounting controls and resolve complex reporting issues well before year-end.
• Establishing formal review layers with defined management review, internal audit and oversight responsibilities prior to statutory submission.

For wider context, read the financial accounting advisory overview.