Suspense account review: identify the receipt before clearing the balance
Last month a receipt of 1,200 reached the bank with a reference nobody recognised. It was recorded as debit bank 1,200, credit suspense 1,200, so the bank account stayed correct while the source was traced. This month a customer's remittance advice shows that 800 of that receipt paid an existing invoice. The other 400 is still unexplained. Clearing the whole 1,200 in one entry would be tidy. The evidence supports clearing 800. All figures are hypothetical, in generic currency units.
What a suspense balance does and does not tell you
ACCA's study article on suspense accounts, written by a member of its Financial Accounting examining team, describes suspense as a temporary home for amounts awaiting correct classification. Its example of an unidentified bank receipt uses the same debit-bank, credit-suspense treatment; the amounts in this article are our own. Each correction comes from comparing what was recorded with what should have been recorded.
The article also shows that many errors never touch suspense, such as transactions left out entirely or posted to the wrong account on the correct side. A nil suspense balance does not show the books are right, and a small net balance can hide larger debits and credits offsetting each other.
Sources and context, checked :
Clear only the evidenced 800
The bank is not posted again; the cash was recorded when it arrived. No revenue is created, because the 800 invoice was already in the ledger.
Where the software allows, make the correction through the customer allocation process rather than a journal straight to the receivables control account. That way the invoice shows as paid and the customer ledger agrees with the general ledger.
| Stage | Debit | Credit |
|---|---|---|
| Recorded on receipt | Bank 1,200 | Suspense 1,200 |
| Correction for the identified invoice | Suspense 800 | Customer receivable 800 |
| Left in suspense | Credit balance 400 (1,200 - 800) |
Trace the remaining 400
The customer whose remittance explained the 800 is the obvious first contact: ask what the rest of the payment covered. Other sources are the receivables ledger, other remittance advice, customer correspondence and the payer details the bank can provide. An amount that matches an open invoice is weak evidence on its own when several customers owe the same sum. When asking, do not reveal other customers' details.
If reliable evidence shows the 400 settles a second existing invoice, debit suspense 400 and credit that receivable 400, leaving nil. That is one possible outcome, not one to assume. An overpayment, a payment meant for another business or a receipt of uncertain ownership needs the accounting owner's assessment instead.
Keep each item on a dated list
We suggest a line-by-line list that totals to the ledger balance, with:
- Transaction date, bank reference and amount
- Debit or credit direction
- The original entry and the evidence held now
- Owner, next action and review date
Review the list, not just its total
Show each proposed correction as the recorded entry against the required entry, with its approval and reference. Reconcile the residual after every correction. At each close, review items individually, especially large or old ones and any debits and credits that net each other down.
Age is not evidence
An item does not become income or an expense because nobody has explained it. Do not clear it to sales or sundry expenses for that reason, and do not delete or merge the suspense account to make items disappear. A review trigger such as 30 days is an internal target if a business adopts it, not a legal deadline. Refunds, unclaimed funds and errors in accounts already filed need separate assessment.
For the 400 here, the next action is a dated request to that customer asking what it covered, with escalation to the accounting owner if no answer arrives by the review date.