A missing receipt or unclear expense can look like a small bookkeeping problem, but the real operational risk is losing track of what was asked, what the client supplied and what remains unresolved. A controlled query process helps a bookkeeping practice keep the record moving without quietly turning assumptions into accounting evidence.
Separate the transaction from the evidence gap
Start by recording what is actually known: the transaction date, amount, payee or bank description, the client file it belongs to and the source record currently available. Then describe the evidence gap separately. The missing item might be a receipt, invoice, business-purpose explanation or confirmation of who incurred the cost. Keeping those two parts apart prevents the query itself from changing the underlying record.
Give every query a clear reference
A useful query register should let a bookkeeper return to the same issue without searching old email threads. A short reference can connect the transaction, accounting period, client response and supporting document. The reference does not need to be complicated; consistency matters more than an elaborate numbering system.
Ask a question the client can actually answer
Requests such as “please send missing receipts” often create another round of correspondence because the client cannot tell which item is meant. A better query identifies the relevant transaction and states precisely what is missing. Where several possibilities exist, explain what needs confirming rather than suggesting an answer. The aim is to collect evidence, not steer the client towards a convenient classification.
Track status instead of relying on the inbox
Email is useful for communication but weak as the only control record. Give each query a simple status such as raised, awaiting client, response received, evidence incomplete or resolved. The team can then review open work by status rather than repeatedly reopening messages. This becomes especially useful near a period close, when a handful of unresolved items can otherwise disappear among routine correspondence.
Preserve the response that resolves the issue
When the client replies, retain enough context to show why the query was considered resolved. If a document arrives separately from the email response, connect it to the same query reference. If the reply only answers part of the question, leave the remaining point open rather than marking the whole item complete. A later reviewer should be able to understand the decision without reconstructing the conversation from scratch.
Escalate judgement rather than guessing
Some queries stop being simple evidence collection and become accounting, tax or policy judgements. A bookkeeping workflow should make that boundary visible. Where the available information does not support the treatment, route the item to the appropriately responsible person instead of filling the gap with an assumption. Recording the escalation also shows why processing paused.
Close queries with a final reconciliation
Before closing a query, check that the response, supporting evidence and bookkeeping record agree. Confirm that any replacement document has not created a duplicate and that the final treatment corresponds with the evidence received. The close step should also remove the item from the active query list, so old questions do not continue appearing as unresolved work.
Use the register to improve client record collection
Over time, recurring query types can reveal where a client's record-supply process is weak. Repeated missing purchase evidence, unclear card transactions or incomplete explanations can inform a better monthly request checklist. The purpose is not to manufacture metrics; it is to notice repeat friction and improve the next collection cycle. A well-run query register therefore does more than tidy the current period: it helps the practice make future bookkeeping work easier to verify.