Three weeks over schedule. PBC documents that arrived in the final days of fieldwork. Evidence sitting in inboxes while the team reconciled transactions in Excel the night before the exit meeting. That is not a rare failure story. For audit teams running field audits on manual processes, it is the default outcome.
A field audit demands more coordination, more documentation, and more real-time decision-making than any other audit type. When the execution infrastructure is built on spreadsheets and shared folders, every stage carries delay risk. Late PBC submissions stall fieldwork. Incomplete workpapers hold up sign-off. Manual evidence matching misses exceptions that surface only after the partner review.
This article walks through the field audit process step by step, gives you a stage-gated checklist you can use immediately, and names the five pitfalls that predictably blow up timelines — with concrete prevention steps for each.
Answers
A field audit is conducted on-site at the auditee's location, giving auditors direct access to records, systems, and personnel. A desk audit is performed remotely, with the auditee submitting selected documents for review. Field audits cover broader scope and require more preparation from both sides.
The six stages are: audit planning and risk assessment, building the audit plan and scoping controls, pre-fieldwork communication and PBC requests, fieldwork including control testing and substantive testing, analytical review and evidence reconciliation, and finally reporting, opinion, and sign-off.
The PBC list drives pre-fieldwork preparation. It typically includes trial balances, general ledger detail, prior-period financial statements, board minutes, material contracts, control documentation, and system-generated reports. All items should be confirmed received and validated before the first day of fieldwork.
Ask about materiality thresholds and how they were set, which controls will be tested and to what standard, the PBC list and submission deadlines, how scope changes will be communicated, and what the expected timeline is from fieldwork completion to report issuance.
Duration depends on entity size, complexity, and the breadth of scope. A straightforward engagement can complete fieldwork in one to two weeks. Complex, multi-entity engagements can run six weeks or longer. The most reliable predictor of timeline is how quickly the PBC list is fulfilled at the start.
More Blogs
