About
bank2tally is built and run by Shuraim Abdul Aziz, as an independent tool. It is not a product of Tally Solutions or of any bank, and isn't affiliated with either.
Why this exists
TallyPrime can't open a bank statement PDF directly — it only imports XML, or Excel via a separate process. Its own Connected Banking feature helps, but it only covers four partner banks (Axis, SBI, ICICI and Kotak Mahindra), needs TallyPrime Release 6.0+, an active TSS subscription, and bank enrollment with Tally.NET credentials — and it doesn't cover HDFC at all. Most accountants just have the PDF their bank emailed them. bank2tally reads that PDF and hands back Tally-ready XML, without any of that setup.
What it does today
HDFC Bank, State Bank of India, ICICI Bank, Axis Bank, Kotak Mahindra Bank, Bank of Baroda, Union Bank of India and Canara Bank — each parser is built against that bank's actual column layout, not a generic PDF-table guess. It only handles text-based PDFs (the kind net banking downloads); scanned or photographed statements aren't supported yet. Every unmatched transaction line is posted to a Suspense ledger instead of being guessed at, and every unsupported upload is logged so new banks get added by real demand, not assumptions.
Your data
Statement files are converted in memory and discarded the moment your download starts — no copies, no backups. Payments are handled entirely by Paddle.com Market Limited as merchant of record; bank2tally never sees or stores card details. Full detail is in the Privacy Policy.
How it's built
Every parser is built against either a real statement PDF or a precisely-sourced open-source parser's column definitions — not a guess at what a bank's layout "probably" looks like. Where that verification isn't available yet, bank2tally doesn't ship a parser for that bank at all; a wrong guess at column order risks a silently wrong ledger entry, which is worse than simply not supporting the bank yet. Unsupported uploads and bank requests are logged specifically so the next parser gets built from real demand and, ideally, a real sample.
Honestly, it's small
There's no support team, no sales call, and no claim of a large user base here — bank2tally is built and operated by one person. What that means in practice: bug reports go straight to the person who can fix them, feature requests aren't filtered through layers of product process, and the roadmap is driven by what people actually ask for rather than a quarterly plan. It also means being upfront about limits — scanned PDFs aren't supported yet, and neither are banks without a verified parser — rather than overselling what the tool can do today.
Get in touch
Email shuraimabdulaziz.2022@gmail.com — including for a statement format bank2tally didn't handle correctly; that's exactly the feedback that decides what gets built next.
Questions
No. bank2tally is an independent, third-party tool. It produces a standard Tally XML import file but has no affiliation with Tally Solutions or with any bank.
It's built and operated by Shuraim Abdul Aziz. Contact shuraimabdulaziz.2022@gmail.com with questions, bugs, or a statement format that didn't convert correctly.
Because a parser is only added once its column layout is verified against a real statement or a precisely-sourced open source parser — a wrong guess risks a silently wrong ledger entry. Unsupported banks are tracked by real demand so the next one gets built deliberately, not guessed at.
One free conversion, no signup needed.