Managing audit queries and client responses

Managing audit queries means running a single list of every outstanding request to the client, each with an owner, a due date and a stated reason it is needed, rather than scattering requests across email and WhatsApp. A query is escalated when its due date passes without the document or a credible reason, following a path the firm has agreed in advance. A query is closed only when the file shows what was received, who reviewed it, and whether it actually resolved the point raised — not merely that something came back.

Why queries need a list, not a thread

Most firms run queries as a mix of WhatsApp messages, emails to whichever client contact answered last time, and verbal asks during a site visit. This works until the file is reviewed three weeks later and nobody can say which of the twelve things asked for in September actually came back, and which were quietly dropped because the deadline arrived first. A query list exists to answer one question at any point in the engagement: what is still owed to us, by whom, and since when.

The list is separate from the working papers it feeds into. A working paper documents the procedure and the conclusion; the query list documents the logistics of getting the inputs for that procedure. Conflating the two means a paper can't be marked complete until every related email thread is manually checked, which is exactly the kind of check that gets skipped under deadline pressure.

What a query record needs

Raising a query well

A query that names exactly what is needed and why gets answered faster than one that doesn't, for the same reason a precise review point gets cleared faster than a vague one. The client-side staff answering requests are usually not the people who understand why the auditor wants a particular reconciliation; a request that explains the gap in a sentence gets routed to the right person internally instead of sitting in an inbox.

• State the document or explanation needed in terms the client's accounts team will recognise, not audit terminology.
• Give a reason in one line: "to agree the closing balance to the bank statement" is enough.
• Set a due date that reflects when the team actually needs it to stay on schedule, not an arbitrary standard period.
• Raise it in writing even if it was first asked verbally on site. A verbal request that is never written down cannot be escalated later.
• Batch related requests to the same owner rather than sending five separate emails over a week.

Escalation: what it means and when to use it

Escalation is not a tone of voice. It is a defined step that changes who is accountable for the delay — typically moving the request from the staff contact to a manager or director on the client side, and from the audit senior to the audit manager or partner on the firm's side. Doing this consistently, rather than only when someone remembers to be firm, is what makes it effective.

1. 01Set the trigger in advanceAgree, as a firm policy, how many days past the due date a query sits before it escalates automatically — commonly a short grace period rather than an indefinite one.
2. 02Escalate to a named person, not a general reminderA second email to the same contact who missed the first deadline is not escalation. Escalation means a different, more senior person becomes aware of the delay.
3. 03State the consequence plainlyIf the item affects the audit timeline or the ability to complete a specific procedure, say so. "This is needed to complete inventory verification and the fieldwork is scheduled to close Friday" is more effective than a repeated general reminder.
4. 04Record that the escalation happenedDate, who escalated, who it went to, and what was said. This record is itself relevant if the matter later affects the report — for example, a scope limitation.
5. 05Decide what happens if it still isn't answeredSome unanswered queries are a scheduling inconvenience. Others mean a procedure cannot be completed and the implication for the report has to be considered. Knowing which kind of query this is should happen when it's raised, not when the deadline has already passed.

Closing a query properly

A query log that only tracks open and closed hides the most useful information in the file: what was actually received, and whether it was enough. Closing a query should require two things recorded, not one.

• What was received — the specific document, with a reference to where it now sits in the working papers.
• A statement that it resolves the point raised, or a note that it is a partial answer and what remains open as a result.

The second point matters more than it sounds. A client sending "the bank statements" when the request was for all pages across the full year, and the team marking the query closed because something arrived, is one of the more common ways a gap survives into the signed file. Closing on receipt rather than on sufficiency is a process failure dressed up as progress.