Why do my imported Tally vouchers post to Suspense A/c, and how do I fix them?
Every imported voucher balances against Suspense A/c because only you know which expense, income, or party ledger each transaction belongs to. Reclassify them in TallyPrime by opening the Suspense A/c ledger, drilling into each voucher, and changing the Suspense line to the correct ledger.
When a Tally XML file is imported, each statement line posts as a Receipt or Payment against your bank ledger. Double entry needs a second side, and the statement itself doesn't say what that side is — "UPI/DR/4471/PAYTM" tells you money left the account, not whether it was stationery, freight, or a supplier payment. Guessing would silently mis-state your books, so the balancing entry parks in Suspense A/c, a ledger TallyPrime ships with by default.
That's deliberate, not a defect: the import never fails for want of a ledger you haven't created, and every unclassified item stays visibly parked in one place instead of being scattered into a wrong account.
To clear it in TallyPrime: open Gateway of Tally → Display More Reports → Account Books → Ledger, choose Suspense A/c, and you'll see every imported voucher. Drill into one, change the Suspense line to the correct ledger, and accept. Work down the list — transactions from the same payee usually repeat, so a statement's worth of entries collapses into far fewer decisions than it first looks.
Two things make this faster. Convert a full period at once so repeating payees group together, and review the extracted table before exporting — descriptions are preserved in full as the voucher narration, so the narration you see in Tally is the narration you approved. Amounts are reconciled against the running balance before export, so what you're reclassifying is the category, never the figure.
Try it now — free, no signup
Upload your statement
Drag & drop a PDF, scan, or photo — any bank. Our AI extracts every transaction and exports to Excel, CSV, QBO, or OFX.
Drag & drop your statement here
or browse files
Encrypted in transit · Processed in memory · Deleted immediately
Related questions
See all bank statement guides.
Last reviewed 2026-08-12.