Audit & assurance

Financial statement audit readiness: a management-owned plan before the request list arrives

A practical framework for management teams preparing records, responsibilities, schedules and explanations before a financial statement audit begins.

7 min read

Start with the reporting objective

Clarify why the financial statements are being prepared, who will rely on them, which entity or entities are in scope, which reporting period matters and which deadline cannot move. Those facts determine the right conversation about scope, information and timing.

The objective should also identify whether there have been changes in ownership, financing, systems, accounting policies, operations or significant contracts. A clear change log gives the engagement team a more useful starting point than a last-minute document collection exercise.

Name the owners behind the schedules

A reliable request process begins by mapping each area to an owner: cash and bank support, revenue, receivables, payables, payroll, inventory, fixed assets, debt, equity, tax balances, commitments and subsequent events. The owner does not need to know every answer; they need to coordinate the records and questions for the area.

Where preparation and review sit with different people, define both roles. That helps management see where a schedule is still being prepared, where it has been challenged and where a decision is needed.

Make reconciliations explainable

A reconciliation is most useful when it identifies the source records, period, preparer, reviewer, unresolved items and conclusion. A clean-looking balance is not enough if the explanation for a material movement, manual adjustment or ageing difference is missing.

Keep a focused exception log for unresolved differences, late information, estimates and judgements. For each item, record the owner, the next step, timing and whether the matter affects the financial statements or the planned audit work.

Use the request list as a shared plan

Turn the information request into a live coordination tool rather than an inbox of attachments. Track the item, purpose, owner, period, source, due date, status and any follow-up question. If a document cannot be provided, record why and agree the appropriate alternative with the engagement team.

Audit work is tailored to the facts and applicable requirements. This article is general information, not a substitute for an audit plan, an engagement letter or advice on the financial reporting framework that applies to a particular entity.

More practical perspectives.

Audit & assurance

SOC 2 readiness: build an evidence plan before you need it

A practical, non-technical way to organise ownership, controls and evidence before a SOC 2 examination begins.

Read article

Audit & assurance

SOC 2 Type 1 or Type 2: start with the decision your customer needs to make

A practical way to frame the report conversation around intended users, system boundaries, evidence and timing—before selecting labels or dates.

Read article

Audit & assurance

Customer due diligence: prepare the controls and evidence behind the security questionnaire

A practical operating framework for SaaS and technology teams responding to customer security, risk and assurance questions without turning every questionnaire into a one-off project.

Read article

Important note

This article is general information and may not reflect the latest standards, law or your specific circumstances. It is not audit, tax, legal, investment or other professional advice. Obtain advice before acting.