The path of an audit engagement

This page describes how a typical annual financial statement audit proceeds with Enterpriseapimanager. Special purpose work and readiness assessments follow shorter versions of the same discipline.

1. Scoping call. We learn entity structure, systems, prior-year auditor status, inventory locations, and the date statements must be signed. You leave with a preliminary sense of fee drivers.
2. Engagement letter. Responsibilities, fee, materiality approach, and access expectations are written down. Work does not start until the letter is signed.
3. Information request list. Trial balances, reconciliations, related-party schedules, and access instructions arrive before fieldwork so sample selection is not improvised on day one.
4. Interim procedures. High-risk areas — revenue cut-off patterns, journal entry testing, or control walk-throughs — may be tested before year-end to shorten the final window.
5. Year-end fieldwork. Inventory counts, bank confirmation chase, substantive testing of material balances, and subsequent events review happen on an agreed calendar.
6. Draft comments and closing meeting. Statement comments and management letter points are discussed before final wording, so directors are not reading findings for the first time at sign-off.
7. Opinion and letter. The signed auditor’s opinion and management letter are delivered. Open points for next year are listed with suggested owners.

What we ask of finance teams

Complete records beat last-minute spreadsheets. Designate one contact for confirmations. Keep warehouse supervisors informed of count dates. Tell us early about related-party or foreign-currency facilities that might not appear on the main trial balance.

What slows an opinion

Late bank confirmations, incomplete inventory ownership evidence, and unsigned related-party agreements are the most common delays we see. We will say so in planning rather than discover them in the final week.

Review the flagship audit Request a proposal