Bank Statement to Tally: Import in Minutes, Not Hours

Why bank imports go wrong

Most failed imports come from three things: dates in mixed formats, narration text the accountant has to decode, and the same statement imported twice. Fix these before generating XML and the rest is smooth.

Step 1 — Prepare the statement

• Export CSV from net-banking (Excel works too).
• Keep four columns: date, narration, debit, credit.
• Delete total rows, headers repeated mid-file, and blank lines.

Step 2 — Map once, reuse forever

In TallyImport open Bank Statement import and map your bank's columns. Narration rules auto-tag common entries (UPI, NEFT, charges) to ledgers — review the preview, correct the unknowns, and the mapping is remembered for the next statement from the same bank.

Step 3 — Generate and import to Tally

Confirm the preview (created/updated/skipped counts), generate the XML, then import it in TallyPrime via Gateway → Import → Vouchers. Large files run in the background under XML Exports.

Duplicate protection

Re-importing the same file flags already-seen rows instead of doubling them. When in doubt, import the statement for a fresh date range.

Limits to know

Trial accounts process 25 vouchers a day. A month of statements usually needs the Basic plan (99/month) — Professional (199/month) covers roughly 25,000 vouchers a month for busy practices.