How to Remove an Imported Bank Statement in Tally

Work on a backup first. Gateway of Tally → Alt+Y → Backup, before you delete anything. This takes under a minute and is the difference between a mistake and a disaster.

Find what the import created

The reliable handle is the date range plus the bank ledger.

1. Gateway of Tally → Display More Reports → Account Books → Ledger
2. Select the bank ledger you imported against
3. Set the period to the statement's date range — Alt+F2 changes the period

You are now looking at every voucher touching that ledger in that window. If you had existing entries in the same period, they are mixed in with the imported ones, which is the case that needs care.

Telling imported vouchers apart from your own: the narration. Every voucher our converter produces carries the original statement description as its narration, and the counter ledger defaults to Suspense. So imported-but-unallocated vouchers are the ones still sitting against Suspense — filter or sort on that and you have your list, cleanly separated from anything you entered by hand.

Delete them

One at a time: open the voucher and press Alt+D.

In bulk, work from the Day Book, which lists every voucher for a period in one place: Gateway of Tally → Display More Reports → Day Book, then Alt+F2 to set the statement's date range. Delete from there, checking each one belongs to the import before you do.

Some Tally releases offer a multi-voucher deletion option from this report and some do not — if yours does, it will be on the button bar. Either way the deletion is not reversible, which is why the backup comes first.

If the import went to the wrong ledger

You may not need to delete at all. If the transactions are right and only the bank ledger is wrong, altering the voucher is less destructive than deleting and re-importing. For a handful of vouchers that is quicker; for hundreds, delete and re-import with the correct ledger selected.

Avoiding the problem next time

Set Show Preview to Yes. On the bank statement import screen this shows you what Tally parsed before a single voucher is written. It is the cheapest safeguard available and it costs one keystroke.

Choose Add, never Overwrite, on voucher imports — unless you know exactly what Overwrite will match. Add leaves existing vouchers alone.

Import a short period first. A one-week statement tells you whether the ledger mapping and voucher types are right, and if it is wrong you are deleting ten vouchers rather than four hundred.

Reconcile before importing, not after. If the conversion itself dropped or duplicated a row, you want to know while it is still a file. Our converter checks that opening balance plus credits minus debits equals the closing balance the bank printed, and flags the statement before you download it — a mismatch caught there is a five-second fix, and the same mismatch caught after import is this page.

Re-importing after a delete

Once the old vouchers are gone, re-import normally. If you are re-importing the same XML, Add will not duplicate vouchers whose voucher numbers match ones already present — but after a full delete there is nothing to match, so everything comes in fresh.

The walkthrough is in how to import a bank statement in Tally Prime.