# How to Keep a Bookkeeping Query Log That Gets Questions Answered

Keep a bookkeeping query log with one clear question per issue, the transaction evidence, a named respondent, a response date and the accounting action required after an answer. The log should make it easy to respond correctly. A long list of vague descriptions usually produces partial answers and repeated follow-up.

Distinguish missing facts from judgement questions. An employee can confirm what was bought or which project used it. The appropriate accounting reviewer decides classification or recognition under the applicable framework. Asking the wrong person to make that decision creates confident but unreliable answers.

## Write the question around a specific gap

Include date, amount, counterparty, bank or document reference and the evidence already available. State exactly what remains unknown. Avoid asking the respondent to reconstruct the entire transaction from a screenshot without context.

An illustrative Jaipur interior contractor has a ₹12,500 payment to a transport operator. A useful question is: “Was payment TX-448 on 8 October for the hotel project delivery or for moving office furniture? Please confirm the purpose and attach the trip note.”

The answer affects project allocation and possibly classification. “What is this?” with no reference may produce a supplier name that accounts already knows, leaving the real question unresolved.

## Use fields that support the full lifecycle

Give each query a stable identifier and connect it to the underlying document or transaction. Record the issue type, question, respondent, raised date, target response, status, answer evidence, reviewer and resulting entry reference.

| Field | Example |
|---|---|
| Query ID | Q-2026-0148 |
| Transaction | ₹12,500 payment, TX-448 |
| Question | Confirm delivery purpose and trip note |
| Respondent | Project supervisor |
| Target | Next scheduled close-preparation date |
| Outcome | Answer verified and project allocation updated |

Use actual dates in the live register. The example illustrates structure rather than prescribing a response period for every business.

## Separate facts, decisions and actions

Record the respondent’s factual answer, the reviewer’s accounting decision and the action taken as distinct fields. A supervisor confirming “hotel project delivery” does not necessarily determine every tax or ledger treatment.

ICAI’s journal material links entries with transaction facts, while its error material shows that wrong classification can remain inside balanced books. A query log helps preserve how the facts and judgement led to the eventual entry.

If the answer is incomplete, state what remains missing. Do not close a query merely because a reply arrived. “Please use transport expense” may leave the project, period and supporting record unresolved.

## Prioritise and route the work

Assign queries by the person who can provide the fact, not by who is easiest to message. Purchasing handles supplier terms, operations handles receipt and use, sales handles customer allocation and the owner handles relevant owner transactions.

Rank issues by materiality, age, dependency and upcoming decisions. An unclear ₹1 lakh supplier advance may block payment review, while an old low-value coding question may still need resolution but not immediate owner interruption.

Use a visible escalation route for unanswered items. Escalation should identify the consequence, such as a draft margin remaining provisional, rather than simply repeating an overdue label.

## Keep the log separate from the ledger

The query log manages work; it does not itself record the transaction in the books. Show whether the item is unposted, entered with an approved provisional treatment or awaiting allocation. Reconcile query status with the relevant ledger or source register.

For the contractor, an answered project query requires an actual allocation update and a reference to that action. If the ledger remains unchanged, the issue is not fully resolved even if the response is clear.

Avoid treating spreadsheet comments or personal messages as the only decision record. Link relevant correspondence to the query so another reviewer can understand the conclusion without access to a former employee’s private device.

## Measure resolution quality, not only speed

Suppose a weekly log begins with 30 queries, adds 12 and closes 18. It ends with 24, assuming no other changes. That is progress in quantity, but review which issues remain and whether closures produced correct entries.

Track reopened queries, incomplete replies and recurring causes. A rapid answer that later proves unsupported creates more work. An older complex issue may require careful review rather than a superficial deadline response.

Show age bands and value exposure without netting unrelated receipts and payments. A small net amount can conceal several material unresolved transactions.

## Preserve a useful history

Keep the original question and record later clarifications instead of rewriting the issue until it appears always to have been clear. Note changes in facts or assumptions and identify the reviewer approving the final treatment.

If a closed query leads to a correction later, link the new case to the earlier one. This helps distinguish new evidence from an avoidable earlier mistake and supports process improvement.

Access should match sensitivity. A project supervisor may need one payment question, not the whole payroll or customer-credit log. Share enough evidence to answer while protecting unrelated information.

## Review the causes with the team

Repeated questions often reveal a weak intake field or unclear procedure. If project codes are missing on 15 of 50 expense submissions, improve the source handoff. If a supplier’s statements repeatedly disagree, fix the reconciliation process.

Use a short regular review to close completed items, confirm blockers and assign precise next actions. Keep owner decisions for questions that need their knowledge or authority.

A good query log makes uncertainty actionable. It connects a clear question to evidence, an authorised judgement and a verified entry outcome, reducing both repeated follow-ups and unexplained balances in the books.

## Sources and references

- [ICAI Foundation Accounting: Basic Accounting Procedures — Journal Entries](https://resource.cdn.icai.org/74606bos60479-fnd-cp2-u1.pdf)
- [ICAI Foundation Accounting: Rectification of Errors](https://resource.cdn.icai.org/74611bos60479-fnd-cp2-u6.pdf)
- [ICAI Foundation Accounting: Bank Reconciliation Statement](https://resource.cdn.icai.org/74612bos60479-fnd-cp3.pdf)