Bank reconciliation

What is a Suspense ledger in Tally, and how do you clear it?

If a bulk import — a bank statement conversion, an Excel upload, anything with dozens of lines — lands some vouchers in a ledger called Suspense, that's not a bug. It's what's supposed to happen when a transaction's narration doesn't clearly match a real ledger.

Why it exists

A visible unknown beats an invisible guess

When software imports many transactions at once, some narrations won't map cleanly to an existing ledger — a one-off vendor, an unfamiliar UPI handle, a bank charge with a code you haven't seen before. There are two ways to handle that: guess a plausible-looking ledger, or post it to Suspense and make you look at it. Guessing is worse — a wrong guess sits quietly in your books looking correct until it distorts a report. A Suspense entry is a flag: "review this one," not "trust this one." The voucher still balances (debit still equals credit); only the classification is left open.

How bank2tally uses it

First matching rule wins — everything else goes to Suspense

Each transaction narration is checked against your ledger mapping rules in order; the first match decides the ledger. A narration that matches nothing is still converted — as a balanced voucher — but posted against Suspense, instead of being dropped or assigned to a ledger that merely looks close.

Clearing it

Folio 1 In Tally Prime, open the Suspense ledger (Gateway of Tally → Display More Reports → Account Books → Ledger) and review each voucher's narration.
Folio 2 Alter the voucher and change its ledger to the correct one — Tally lets you edit the ledger on an already-imported voucher directly.
Folio 3 If the same narration pattern will recur (a regular vendor, a recurring charge), add it to your ledger mapping rules so the next statement import maps it automatically instead of going to Suspense again.

At year end

Don't let Suspense entries sit until the audit

A Suspense ledger is meant to be temporary — a working space for the handful of lines that need a human decision, not a permanent parking lot. Left uncleared across a full year, it turns into a pile an auditor has to review line by line at the worst possible time. Clearing it in the same sitting you do the import, or at worst monthly, keeps the balance sheet's Suspense figure at zero (or close to it) and means each transaction gets classified while the context — who the vendor was, what the charge was for — is still fresh.

Not just an import artifact

Suspense exists outside bulk imports too

Tally's own manual entry can post to Suspense as well — it's a standard ledger concept, not something specific to bank2tally or to imports generally. Any time a bookkeeper enters a transaction without being sure which ledger it belongs to, Suspense is the correct place for it, for exactly the same reason: an honest "unknown" is safer than a confident-looking guess. Bulk imports just surface far more of them at once than manual entry typically does.

Questions

Is it normal to see a Suspense ledger after importing a bank statement?

Yes. Any bulk import tool that doesn't want to guess wrong will route unmatched narrations to Suspense rather than a plausible-looking but incorrect ledger.

Does a Suspense ledger entry affect my books?

The voucher is fully balanced (debit equals credit); only its ledger classification is left open. Clear it before you finalize accounts, but it doesn't unbalance anything meanwhile.

How do I stop the same transaction going to Suspense every month?

Add that narration pattern to your ledger mapping rules once. The next statement with a matching line will map straight to the right ledger instead of Suspense.

Try it on your own statement

One free conversion, no signup needed.

Convert a statement free