# How to Manage a Queue of Transactions That Need More Information

Manage transactions needing more information in a visible queue that records the known facts, precise uncertainty, responsible person and next action. Reconcile the queue to the relevant bank, cash or ledger records. It should be a controlled route to resolution, not a permanent place where unknown amounts accumulate.

A queue and a suspense account are different things. The queue tracks work and evidence. Any temporary accounting treatment requires an approved basis and later review. Do not assume that putting an amount into a generic ledger account resolves its classification or reporting effect.

## Capture enough to identify the transaction

Record the bank or cash reference, date, amount, direction, counterparty information, source account and any related document. Include the original narration rather than replacing it with a guess.

Separate what is known from what is suspected. “₹18,000 bank debit to ABC Services” is a fact supported by the statement; “probably repairs” is a hypothesis requiring confirmation. Preserve both clearly if the hypothesis helps direct the query.

An illustrative Bengaluru distributor has a ₹25,000 UPI receipt with an unfamiliar payer name. It may be a customer payment made by another person, a deposit or another transaction. Matching only the amount to a convenient invoice could create a wrong customer allocation.

## Use one queue with meaningful statuses

Choose statuses such as new, assigned, awaiting response, evidence received, ready for review and resolved. Record the date of each change. Avoid a single “pending” label that gives no clue whether anyone has acted.

Group related entries under one case when they share a genuine underlying issue, while preserving individual transaction references. A batch of gateway settlements may need one provider reconciliation; unrelated customer receipts should remain distinguishable.

| Queue field | Purpose |
|---|---|
| Unique case reference | Tracks the issue across messages |
| Known transaction facts | Prevents repeated reconstruction |
| Information needed | Makes the request answerable |
| Named owner | Identifies who can provide the fact |
| Next action and date | Supports follow-through |
| Ledger treatment and effect | Connects work status with the books |

The queue should not expose sensitive details to people who do not need them. Provide appropriate views or limited summaries where necessary.

## Assign the question to the right person

Sales may identify a payer, purchasing may explain a supplier advance, operations may confirm a service and the owner may explain a personal transfer. A tax or accounting-policy question belongs with a suitable reviewer rather than the employee who merely submitted the bill.

Ask one precise question. For the ₹25,000 receipt, provide its date and reference and ask which customer or obligation it relates to, with supporting communication. “Please clear all unknown receipts” invites incomplete answers.

Keep accounts responsible for tracking the case, while the named respondent supplies the business fact. Escalate repeated non-response through an agreed route rather than repeatedly broadcasting the same list.

## Prioritise by impact and age

Review value, uncertainty, payment consequences, reporting dates and age. A small unknown receipt may be routine, while a large unexplained debit near month-end can affect cash interpretation or a supplier decision.

An illustrative queue contains a ₹25,000 unidentified receipt, ₹18,000 unclear payment and ₹2,000 bank charge query. Gross unresolved movements total ₹45,000. Netting inflows and outflows gives ₹5,000, which would conceal the scale and different risks of the three cases.

Show gross amounts by direction and category. Net balances can be useful for reconciliation, but they should not replace case-level review. A near-zero suspense total can still contain many significant offsetting items.

## Keep reporting consequences visible

Record whether an item is unposted, provisionally posted under an approved process or awaiting allocation. Explain which customer, supplier or expense balances may be affected. An unresolved classification can matter even when bank cash is recorded correctly.

Do not treat every unknown receipt as revenue or every payment as expense. Loans, owner funding, deposits, transfers and settlements of old balances have different effects. ICAI’s journal principles require considering both aspects and the nature of the transaction.

At closing, the reviewer should assess material unresolved items and report status. A complete-looking profit statement should not hide a significant queue whose eventual resolution could change the result.

## Resolve with evidence and a linked entry

When an answer arrives, attach it to the case and verify that it addresses the uncertainty. Update the accounting record or allocation through the approved process, then recheck the affected balance.

For the ₹25,000 receipt, confirmation from sales and the customer may establish that a director paid an outstanding invoice on the customer’s behalf. Link the receipt to the correct customer and retain that explanation. Do not rely solely on someone’s memory of a similar amount.

Record the final entry reference, reviewer and resolution date. Closing the message thread is not enough if the books remain unchanged.

## Review the queue as a process measure

Track new cases, resolved cases, oldest age and recurring causes. If 20 new queries arrive and 15 close in a week, the queue grows by five even when the team appears busy. Investigate capacity and source-data quality.

Repeated unidentified receipts may call for clearer customer payment references. Repeated unclear expenses may require better purpose fields at intake. Fixing those causes reduces work more effectively than repeatedly accelerating the same queries.

A well-run queue preserves uncertainty honestly and directs it toward a supported decision. Its success is measured by correct resolution and fewer recurring gaps, not by moving unexplained amounts into an account where they are harder to see.

## Sources and references

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