How to Prepare for Your First Institutional Audit: A 90-Day Plan

The first institutional audit after a PE investment or a significant growth milestone is a different experience from the audits that came before it.

Scope is broader. Scrutiny is higher. The audit team is typically more senior and more thorough. The board — now including investor representatives — expects a clean, timely opinion with no surprises. And the finance team, often leaner than the business would ideally have it, is expected to deliver this while continuing to run the day-to-day close process.

The businesses that navigate this well do not do it through heroic effort in the final weeks. They do it through structured preparation that starts months before fieldwork.

This is a 90-day plan for finance teams approaching their first institutional audit.

The Starting Point: An Honest Gap Assessment

Before anything else, you need to understand where you actually are.

Set aside one to two days to work through the following with your finance team:

Evidence: For the key areas auditors will test — revenue, payroll, fixed assets, controls — can you produce evidence of each transaction and control operation within 24 hours of a request? Or would producing it require reconstruction and research?

Documentation: Are your accounting policies written down? Are control processes documented, or do they exist only as unwritten practice? Are templates and workpapers consistent across the team?

Ownership: Does each control area have a named owner — someone who understands the process, performs it and can answer questions about it?

Prior year findings: If you have been audited before, what did the management letter say? Have the agreed actions been implemented? Can you evidence that implementation?

The output of this assessment is a gap list. The 90-day plan is the process of closing it.

Days 1–30: Foundations

Week 1–2: Engage the auditors early

Your audit engagement partner is a resource, not an adversary. Arrange a pre-audit planning meeting within the first two weeks. The agenda should cover:

• Their overall audit approach and areas of focus for the year
• Key dates: fieldwork, clearance meetings, board presentation
• The PBC list — request a draft as early as possible
• Any areas where they will want pre-agreed accounting treatments
• Changes to the business in the year that will affect their risk assessment

This conversation does two things. It tells you exactly what they are going to ask for. And it allows you to raise anything unusual early — before it becomes a mid-audit problem.

Week 1–4: Draft the financial statements

The financial statements should be substantially complete before fieldwork begins. This is counterintuitive to teams that have historically produced the draft as a product of the audit rather than an input to it. But auditors cannot test the financial statements until they exist in a reviewable form, and every day of delay in the draft is a day of delay in the opinion.

Identify the accounting judgements that will require the most work — revenue recognition, goodwill, provisions — and start building the supporting papers now.

Week 1–4: Map your controls

Create or update a simple controls matrix covering the key financial reporting processes. For each control, document: what the control is, how often it operates, who performs it, what evidence is produced and who reviews it.

This is not a complex exercise. A one-page spreadsheet covering 20 to 30 key controls is sufficient. Its value is in making the control environment visible and in identifying gaps before auditors do.

Days 31–60: Evidence and Workpapers

Week 5–6: Build the PBC pack

The PBC (Prepared by Client) pack is the collection of documents, schedules and workpapers that you will provide to auditors at the start of fieldwork. A well-organised, complete PBC pack is one of the highest-value readiness investments you can make.

Do not wait until two days before fieldwork to start this. The items that take longest to produce are inevitably the ones that reveal a gap.

Week 5–8: Close the significant judgement papers

For each area of significant accounting judgement, prepare a standalone paper that documents: the relevant accounting standard, the facts of the situation, the accounting treatment selected, the rationale for that treatment, the range of outcomes considered, and the sign-off from the relevant authority.

Where you are uncertain about the treatment, this is the time to raise it with the auditors — not during fieldwork.

Week 6–8: Run the access review

Complete a formal review of access rights to the financial system, payroll system and banking platforms. Document who has access, at what level, whether it is appropriate for their current role, and what action has been taken where access is no longer appropriate.

Remove leavers who still have active access. Resolve any segregation of duty conflicts, or document the compensating controls where resolution is not possible.

Days 61–90: Finalisation and Readiness

Week 9–10: Complete the financial statements

By the end of week 10, the financial statements should be complete in all material respects. This means: the trial balance is agreed, all significant adjustments have been processed, the notes are drafted, and the judgement papers are finalised.

Anything left open at this point is a risk of fieldwork delay.

Week 9–11: Run a pre-audit internal review

With the PBC pack substantially complete, run a review of your own. Ask a member of the team — or an external adviser — to work through the pack as an auditor would: check that documents are present, that reconciliations agree, that workpapers are signed off and that the logic is clear.

Identify the three to five items most likely to generate auditor queries. Prepare a clear narrative for each.

Week 10–12: Brief the team

Every member of the finance team who will interact with auditors during fieldwork should be briefed before fieldwork begins. The briefing should cover:

• The audit timetable and key dates
• Their individual responsibilities during the fieldwork period
• How to handle auditor requests — who fields them, what the turnaround expectation is
• What to do if they receive a question they cannot answer
• Any areas of sensitivity that should be escalated to the FD before being addressed

Fieldwork breakdowns often happen not because evidence does not exist but because the person who holds it does not know what to do with an auditor in front of them.

Week 11–12: Board briefing

Before fieldwork begins, brief the board or relevant investor representatives. Cover the audit timetable, the key areas of judgement, the going concern position and any matters that are likely to require board discussion before the opinion is signed.

Investors and board members who are informed in advance are partners in the process. Those who hear about issues for the first time during the audit are a risk to the timetable.

What Success Looks Like

A successful first institutional audit does not mean no findings. It means that the audit proceeds to timetable, that fieldwork queries are answered promptly, that the financial statements required no material revision and that the management letter — if there is one — contains observations the finance team already knew about and is already working on.

That outcome is achievable for most businesses with structured preparation. The constraint is usually time — which is why the 90-day runway exists.

If you are approaching your first institutional audit with less than 90 days to go, the plan is the same. The pace is different.