Supported banks and their statement layouts
TieOut converts statements from 7 Indian banks — SBI, HDFC, ICICI, Kotak, Axis, Federal and PNB — into Excel, CSV and Tally XML, with a separate profile for HDFC ENet corporate accounts. Every one was checked against a real statement and passed running-balance validation. That is why the list is eight profiles long instead of a hundred.
Why a short list is the honest one
A PDF has no table. It stores text fragments at x/y coordinates, and the columns you see are visual alignment, nothing more. Reconstructing rows means knowing where that specific bank puts its columns, which way its narration wraps, what it prints in an empty amount cell, and which lines are summaries rather than transactions. That is per-bank work, and it is measured from real documents.
So a converter advertising "100+ banks" is either doing something generic that breaks in ways you have to catch yourself, or counting banks it has never seen a statement from. Each page below states what was verified and what the layout does that trips other tools up.
Supported banks
Convert a State Bank of India statement to Excel or Tally XML
SBI does not repeat the column header on transaction pages, so there is no header row to read the layout from after page one. TieOut assigns columns by measured x-position instead, which is why a converter that only looks for headers loses everything after the first page.
verified Verified against a real 847-transaction netbanking statement — every row passed the balance chain, and it is the largest statement tested against any profile.
Convert a HDFC Bank statement to Excel or Tally XML
HDFC repeats its header row, so the column layout is read from the header text when it is present and falls back to measured x-ranges when a page drops it. That covers both the common statement variants without you choosing anything.
verified Verified against a real 150-transaction retail netbanking statement with a 100% balance-chain pass.
Convert a ICICI Bank statement to Excel or Tally XML
ICICI prints the page marker — “Page 2 of 2” — on the same line as a transaction rather than on its own line. A converter that drops any line containing a page marker drops a real transaction with it. TieOut only skips lines that are nothing but a page marker.
verified Verified against a real-format 2019 “Statement of transactions” — 37 of 37 rows passed the balance chain.
Convert a Kotak Mahindra Bank statement to Excel or Tally XML
Kotak’s own name does not reliably appear on page one of the statement, so the bank is detected from the KKBK0 IFSC prefix instead of from the letterhead. Converters that key off the bank name alone frequently fail to recognise the file at all.
verified Verified against a real 193-transaction netbanking statement. Opening and closing balances matched the summary printed on the statement itself.
Convert a Axis Bank statement to Excel or Tally XML
Axis particulars wrap upward. The date and the amounts sit on the last line of a transaction block and the description continues on the lines above it — the opposite of every other bank here. A converter that reads wrapped text downward attaches each narration to the following transaction, so the amounts stay right, the descriptions all shift by one row, and nothing about the file looks wrong. This is the single most consequential quirk in the supported set.
verified Verified against a real 58-transaction e-statement, including its upward-wrapping particulars.
Convert a Federal Bank statement to Excel or Tally XML
Federal prints each row across two baselines about 5pt apart — the dates on one, the values on the other. Grouping text into rows by exact vertical position therefore splits every transaction in half. TieOut uses a wider line tolerance for Federal specifically, which is why the rows come out whole.
verified Verified against a real Gen-1 statement. That statement contained a single transaction, so the layout is confirmed but the volume testing other banks have had is not there yet.
Convert a Punjab National Bank statement to Excel or Tally XML
The netbanking layout uses a single amount column plus a separate DR/CR type column, rather than separate withdrawal and deposit columns. The sign of every transaction comes from that one letter, so misreading it inverts the entry.
verified Verified against a real statement with a full balance-chain pass, across both PNB layouts.
Corporate and variant layouts
HDFC ENet (corporate) — verified The wholesale/ENet statement is a separate layout and is supported as its own profile — Date | Transaction Description | Chq/Ref. No | Value Date | Debit Amount | Credit Amount | Closing Balance, dates DD-Mon-YYYY, negative balances with a leading minus. Because it shares a page-one fingerprint with the retail statement, both profiles are run against the file and whichever extraction validates is the one you get.
What is not supported
- Scanned or photographed statements, from any bank. They are images and need OCR, which is not built yet.
- Credit card statements. Different document, different layout, no running balance to validate against in the same way.
- Banks not listed above. An unrecognised statement is rejected rather than parsed badly — a refusal you can see beats a table you cannot trust.
Getting your bank added
Send a statement. That is genuinely the whole process, and it is the most useful thing anyone can contribute — a profile is built by measuring one real document. Use a personal statement or redact a client's rather than sending live client data, and see the privacy policy for what happens to a file you email in (used to fix the parser, deleted once the fix ships).
FAQ
Which Indian banks can TieOut convert?
SBI, HDFC, ICICI, Kotak, Axis, Federal and PNB, plus HDFC ENet for corporate accounts — 7 banks and 8 statement profiles in total. Each has been checked against a real statement and passed the balance-chain validation, which is why the list is short and specific rather than a claim of "100+ banks".
What does “supported” actually mean here?
That a real statement from that bank was parsed and every row passed the running-balance check — balance equals previous balance plus credit minus debit, with the final balance matching the printed closing figure. It is not a claim that the bank appears on a list somewhere. Where verification was thin, the bank’s page says so.
My bank is not listed. Will it work?
Probably not yet — TieOut recognises a statement by its layout, so an unlisted bank will usually be rejected rather than parsed badly. Send the statement in and it becomes the next profile. Adding a bank is mostly a matter of measuring one real document.
Are scanned bank statements supported?
Not yet, for any bank. A scan is an image and needs OCR, which is being built as an optional step. Native PDF e-statements downloaded from netbanking work today and are more accurate anyway, because the text is already in the file rather than being guessed from pixels.