The Year-End Audit Preparation Timeline: What to Do and When

The audit does not begin when the auditors arrive. It begins months earlier, in the quality of the close process, the completeness of the evidence trail, the resolution of accounting judgements and the conversations that either happen or do not happen between management and the audit team.

Finance teams that treat the audit as something that happens to them — a period of responding to requests and managing disruption — tend to find it the most costly and stressful part of the year. Finance teams that treat it as something they prepare for, with a defined timeline and clear ownership, tend to find it far more manageable.

The difference is rarely about the quality of the underlying finance function. It is almost entirely about planning.

This article sets out what good preparation looks like across the three months before fieldwork begins, and why the timing of each element matters.

Three months before fieldwork: the foundation work

The period three months out from fieldwork is when the decisions and conversations that will determine the shape of the audit need to start happening.

The most important conversation at this stage is with the audit partner. A pre-audit planning meeting three months before fieldwork gives both sides time to act on what they discuss. The agenda should cover the areas of audit focus for the year, any changes in the business — new systems, acquisitions, changes to revenue streams, refinancing — that will affect the risk assessment, and the anticipated timetable through to sign-off. It should also be the moment when management flags any accounting treatments they anticipate discussing, rather than presenting them to auditors as resolved matters during fieldwork.

This conversation is underused by most management teams. Auditors appreciate it. It builds the relationship. And it removes the element of surprise from the areas that are most likely to generate discussion.

Alongside this, three months out is the right time to begin the significant judgement papers. These are the documents that support the accounting treatments that involve genuine uncertainty — impairment of goodwill, provisions for uncertain outcomes, revenue recognition on complex contracts, going concern. Each one takes time to do properly: assembling the facts, identifying the relevant accounting standard, documenting the reasoning and building the sensitivities. Starting this work three months out means it can be reviewed, refined and, where appropriate, shared with auditors before fieldwork rather than handed over on day one.

This is also the moment to review the prior year management letter honestly. Every finding and observation from the prior year audit should be assessed: has it been remediated, and is there evidence of remediation? If not, what will the answer be when auditors ask about it this year? The management teams that arrive at the clearance meeting with a completed remediation log, supported by evidence, earn credibility with auditors. Those that arrive with good intentions and incomplete actions do not.

Two months before fieldwork: the evidence and documentation phase

With eight weeks to go, the focus shifts from decisions and conversations to documentation and evidence.

The PBC list should be in hand by this point, either formally issued by the auditors or assembled from the prior year list with additions for the current year's specific circumstances. Every item on the list should be assigned to a named person in the finance team, with a target completion date of at least two weeks before fieldwork begins. The items that require the most time are the ones involving reconstruction or analysis — detailed account analyses, complex reconciliations, population extracts for sampling — and these should be started now.

The financial statements should be in substantial draft form by six weeks before fieldwork. This means the trial balance is agreed to management accounts, all significant adjustments have been processed, and the notes are being drafted rather than outlined. The notes, in particular, take longer than most teams anticipate: the accounting policies need to be current, the disclosures need to reflect the actual position and the going concern note needs to be drafted in a form that management is comfortable with before it goes to auditors.

The balance sheet reconciliation suite should be complete and reviewed. Every material account should have a supporting workpaper showing the balance per the ledger, the reconciling items with explanations and the net position. Workpapers should be signed off by a reviewer, with the sign-off evidenced in a way that distinguishes it from nominal sign-off.

This is also the time to complete the access review. A formal review of who holds access to the financial system, at what level, with access removed for leavers and appropriate for current role-holders, should be completed and documented before fieldwork. Auditors will test this. Having a current, completed access review ready to produce is straightforwardly better than having to explain why it has not been done.

One month before fieldwork: finalisation and readiness review

With four weeks to go, the preparation should be moving towards completion rather than starting.

The financial statements should be complete in all material respects. If they are not, there is now limited time for revision, and any significant open item represents a risk to the fieldwork timetable. The audit partner should have sight of a substantially complete draft at this stage — this allows them to identify questions they will have early, and gives management time to prepare answers.

The PBC pack should be substantially assembled. Items that are not yet complete should be on a named individual's task list with a specific deadline, and the Finance Director should have visibility of the status. Items that cannot be produced within the required timeframe should be escalated — not left to surface as gaps on day one of fieldwork.

This is also the right moment to brief the broader finance team about the audit. Everyone who will interact with auditors during fieldwork should know the timetable, understand their responsibilities and know what to do when an auditor asks them something they are not certain about. Audits slow down when requests get lost in email threads, when documents have to be explained to auditors by people who did not prepare them, and when the finance team is simultaneously managing fieldwork and the normal close process without coordination. A brief but genuine team briefing prevents most of this.

The board or audit committee should also receive a pre-audit briefing at this stage. The board needs to know the key areas of judgement, the status of the going concern assessment and any matters that are likely to require discussion before the opinion is signed. Boards that encounter significant audit matters for the first time in the clearance meeting are less well placed to respond to them than boards that have been kept informed throughout the process.

During fieldwork: active management

The fieldwork period is not passive. The finance team's job during this phase is to respond to queries promptly, escalate uncertainties quickly and manage the auditor relationship actively rather than reactively.

A named contact for each category of request, a clear turnaround expectation for responses, and a daily check-in with the audit senior to surface any emerging issues are the three practices that most reliably keep fieldwork on track. When issues arise — and they sometimes do regardless of preparation — the quality of the management response matters as much as the issue itself.

The clearance meeting, at the end of fieldwork, is not the moment to negotiate findings. That conversation is much harder after the audit evidence has been gathered than before fieldwork began. If there are areas of genuine disagreement, raise them with the audit partner during fieldwork — or, better, in the pre-fieldwork conversations three months earlier.

The underlying principle

The single most useful reframe for finance teams approaching the annual audit is this: everything that auditors find during fieldwork already existed before they arrived. The errors, the control gaps, the judgements that need more support — none of these are created by the audit. The audit reveals them.

The implication is straightforward. The time to address them is before fieldwork begins, not after auditors have documented them in a working paper. A structured preparation timeline is not about managing the audit better. It is about using the months before it to resolve the things that would otherwise become findings, so that fieldwork is a process of verification rather than discovery.

Finance functions that operate on this basis find the annual audit straightforwardly less difficult than those that do not. And over time, the cumulative effect — fewer findings, shorter fieldwork, stronger management letters — compounds into a meaningfully better governance position.