Audit questions are not the problem.
A statutory audit should involve challenge. Auditors need to understand the business, test evidence, question management judgement and obtain sufficient appropriate audit evidence before signing an audit report.
The frustration for many finance teams is different.
It is the same schedule being requested twice. A document being uploaded and then chased again. A junior team member asking a question without understanding the business. A late request arriving when the audit timetable is already under pressure.
That is not a necessary feature of a rigorous audit. It is usually a process problem.
Why repeated audit questions damage confidence
When audit questions are poorly coordinated, the finance team starts to lose confidence in the process.
The concern is not only the time spent answering. It is what the experience suggests.
If the audit team does not appear to know what has already been provided, management may reasonably wonder whether the audit is being properly managed. If the same point keeps coming back through different people, the client may struggle to understand whether the issue is still open or simply not updated on the file.
For finance directors and controllers, this matters because audit work sits alongside payroll, tax, management reporting, board packs and operational demands. Audit requests consume real management time.
What good audit request management looks like
A better process normally starts before fieldwork.
The audit team and client should agree one controlled request list. That list should show what is required, who owns it, when it is due, whether it has been received, and whether it has been reviewed and cleared.
Those last two stages are different.
Received means the client has provided something. Reviewed and cleared means the audit team has checked whether it answers the audit requirement.
Where those statuses are not separated, confusion follows. The client thinks the item is complete. The auditor may later come back because the evidence was incomplete or not sufficiently clear.
The role of senior involvement
Senior involvement does not mean the partner answers every question.
It means the audit is planned and supervised so the team understands the business, the significant risk areas and the matters likely to require judgement.
Before questions reach the client, the audit team should ask internally:
- Have we already received this evidence?
- Is this question necessary for the audit objective?
- Does the person asking understand the business context?
- Can several related questions be combined?
- Does this point require manager or partner input before going back to management?
That internal discipline protects both audit quality and client time.
What finance teams can do before the audit starts
Clients also have a role in making the process work.
A finance team can help by preparing reconciliations, supporting schedules, board minutes, agreements, key accounting papers and explanations of significant movements before audit fieldwork. For areas involving management judgement, such as provisions, going concern, impairment, revenue recognition or related-party matters, it is usually better to prepare the position early rather than wait for the audit team to ask.
The aim is not to remove challenge. It is to make the challenge more focused.
A practical audit-readiness test
Before the audit begins, ask:
- Is there one request list or several competing versions?
- Does every major area have an owner?
- Are the most judgemental areas identified early?
- Does the audit team understand the business before issuing detailed requests?
- Are senior review points expected during the process, not only at the end?
- Are meetings being used to resolve issues, not simply update status?
If the answer to these questions is unclear, the audit may still get completed, but it is more likely to feel difficult than necessary.
The main point
A well-run audit should feel rigorous, but it should not feel repetitive.
Questions are part of audit quality. Poorly coordinated questions are not.
For finance teams, trustees and boards, the goal should be a process where the audit team understands the business, controls the information flow and raises issues early enough for management to respond properly.
That is how audit protects quality without wasting management’s time.
FAQs
Should an auditor ask detailed questions?
Yes. An audit requires evidence, challenge and professional scepticism. The issue is not the existence of questions, but whether they are relevant, coordinated and raised at the right time.
How can a finance team reduce repeated audit requests?
Use one request list, keep evidence in a structured folder, agree ownership and ask the audit team to distinguish between received, reviewed and cleared items.
What is audit readiness?
Audit readiness means the records, reconciliations, supporting evidence and management explanations are prepared before fieldwork starts, especially in areas likely to involve judgement.