Preparing for your first external audit

First audits feel existential because every request seems urgent. Most are not. The teams that survive fieldwork with their calendars intact treat preparation as a project with a freeze date, an owner matrix, and a single binder index.

Eight weeks out

Confirm the reporting framework, entity list, and comparative periods. Inventory systems that touch cash, revenue, or lending balances. Identify who can export what without opening a ticket that takes five days.

Six weeks out · freeze discipline

Agree when the trial balance freezes for audit purposes and how late adjustments will be logged. Late journals without a log destroy trust faster than an honest error.

Four weeks out · PBC rehearsal

Draft your own provided-by-client list using last year’s peer examples or a training checklist. Fill it once for practice. Gaps that appear now are cheaper than gaps that appear after auditors arrive on site or on the video link.

Two weeks out · walkthrough readiness

Pick process owners for revenue, payroll, and treasury. Give them a one-page script: systems, approvals, exception handling. They should not memorize accounting theory; they should narrate what actually happens on Tuesday afternoons.

Fieldwork week

Centralize requests in one tracker. Answer with references to binder sections, not new ad-hoc spreadsheets. When you do not know, say so and commit to a time—silence reads as avoidance.

Representation letters

Read them before signing day. If a clause describes controls you do not operate, escalate early. Management representations are not ceremonial; they are part of the evidence file.

Softwareinfrastructure cohorts run a mock PBC against anonymized trial balances so the first real list is not your first list. See courses or ask about fit.