Bank Statement to Tally XML
Find every bank transaction missing from Tally and download a ready-to-import XML — free, and it never leaves your browser.
How it works
1. Upload your bank statement (CSV, XLSX, or PDF) and your Tally Day Book export (CSV or XLSX). 2. It matches transactions by amount and date — exact matches, probable matches within a short date window, and anything genuinely ambiguous goes to you to decide, never guessed silently. 3. Review what's missing from Tally, confirm or correct the suggested ledger for each, and download a Tally-ready XML to import.
Does this replace TallyPrime's own bank reconciliation?
No — it's a step before it. Tally's built-in reconciliation works on clean CSV/XLS exports from netbanking; this tool's job is turning a messy, inconsistent bank statement (especially a PDF one) into clean, matched data first. Think of it as the step that gets your data ready for Tally's own recon, not a replacement for it.
Which file formats work best?
CSV or XLSX exported directly from your bank's netbanking portal gives the most reliable results, since the data is already structured into columns. PDF statements are supported too, but PDF text layout varies a lot between banks, so it's the more fragile path — if a PDF doesn't parse cleanly, exporting CSV instead will almost always work better.
Will it ever guess wrong and silently create a bad match?
It's built specifically to avoid that. When a bank transaction could match more than one Tally entry with the same amount, it's never auto-matched — it goes to a "needs your input" list for you to pick manually. Ledger suggestions for missing transactions are just suggestions too; nothing gets written until you download the file.
Does it fix or apply anything inside Tally directly?
No. It only generates a Tally-format XML file for you to import yourself via Tally's own Gateway of Tally → Import Data → Vouchers. Nothing is pushed into Tally automatically, and your files never leave your browser to do any of this.
What if a suggested ledger doesn't exist in Tally yet — will the import fail or create a duplicate?
By default, the exported XML only contains vouchers — it assumes every ledger it references already exists, and Tally will skip (not corrupt) any voucher whose ledger it can't find. To do better than that safely, upload an export of your Tally ledger list (List of Accounts, as CSV or XLSX) on the client-profile card: the tool then checks every suggested ledger against your real chart of accounts and only offers to create a ledger for names it can verify aren't already there — never a guess, and never touching a ledger that already exists.
Does the ledger-suggestion feature get smarter over time?
For a client you name, yes — every ledger you assign or correct is remembered (stored locally in your browser) and reused automatically the next time a similar transaction shows up, even though banks embed a different reference number on every single transaction. You can back up that learned mapping to a file and restore it later or on another device.
I don't use Tally — does this work with QuickBooks, Xero, or Zoho Books?
Yes. Alongside the Tally XML, the results screen offers a CSV in the Date/Description/Amount shape QuickBooks Online, Xero, and Zoho Books each document as their own bank-statement import format, and an OFX file — an open standard those three, Quicken, and most banks accept natively. Both carry just the transactions missing from your books, ready to import as a bank feed and categorize in that software's own reconciliation screen. There's also a full Excel report of every tab for review or sharing with anyone, on any software. QuickBooks Desktop's older IIF format and the ISO 20022 CAMT.053 bank-statement standard aren't supported yet — IIF is proprietary and Desktop-specific, and CAMT.053 is a much larger banking standard than this tool currently covers.
Is this free?
Yes, with no transaction limits, no sign-up, and no account linking required.