Bank statement formats in India vary from bank to bank in column order, date format, and whether debit and credit amounts share one column or sit in two separate columns. There is no single standard PDF or Excel layout that every Indian bank follows, which is why a statement from HDFC Bank looks structurally different from one issued by SBI or Axis Bank even though both contain the same underlying transaction data. Understanding these structural differences helps you read statements correctly and avoid errors when moving transaction data into accounting software.
This matters more than it sounds. If you are manually re-typing entries, or if a spreadsheet formula assumes a fixed column position, a format change between banks - or even between two branches of the same bank - can silently shift your numbers. This guide walks through the structural differences you are likely to encounter and how OneBooks GST handles them.
What is a bank statement format?
A bank statement format is the specific arrangement of columns, headers, date conventions, and narration style a bank uses to present transaction data in its passbook, PDF, or Excel statement. It is not the transaction data itself - two banks can report an identical payment with the same date and amount but lay it out in completely different columns and wording.
Why do bank statement formats differ across banks?
Each bank builds its core banking and statement-generation system independently, usually with different software vendors and different release years. There is no regulatory template that dictates statement layout the way there is for a GST invoice or a GSTR-1 JSON schema. Banks are free to choose their own column order, page headers, and narration conventions, and they periodically redesign these templates, which is why even statements from the same bank can look different if you compare one from five years ago with a current one.
How does column order differ between banks?
The core columns - date, narration/description, reference or cheque number, debit, credit, and balance - appear in nearly every Indian bank statement, but the order and grouping differ. Some points of variation:
- HDFC Bank statements typically list date, narration, cheque/reference number, value date, withdrawal amount, deposit amount, and closing balance as separate columns.
- ICICI Bank statements commonly show transaction date, value date, description, cheque number, and then separate debit and credit columns followed by balance.
- SBI (State Bank of India) statements often use txn date, value date, description, reference number, debit, credit, and balance, with SBI's narration strings tending to be longer and more code-heavy than private banks.
- Axis Bank statements generally follow a similar date-narration-cheque number-debit-credit-balance pattern, though column widths and header labels differ from HDFC and ICICI.
- Kotak Mahindra Bank statements typically include date, narration, cheque/reference number, debit, credit, and balance, with a distinct summary block at the top listing account details and the statement period.
Exact column labels, widths, and ordering can change when a bank updates its statement template, so treat the list above as a general structural pattern rather than a fixed specification. Always check the actual column headers on the statement you have in hand.
| Structural element | Common pattern | What to watch for |
|---|---|---|
| Date format | DD/MM/YYYY or DD-MM-YYYY | Some statements use DD-MMM-YYYY (e.g. 05-Aug-2026); mixing formats in one sheet breaks sort order |
| Debit/credit columns | Two separate columns | A few statement exports use one signed amount column instead (negative for debit) |
| Narration style | Bank-specific transaction codes plus payee text | UPI, NEFT, and IMPS references are embedded differently by each bank |
| Page headers | Account holder name, account number, IFSC repeated on every page | These header rows can get mistaken for transaction rows during parsing |
| Opening/closing balance rows | Shown once per page or once per statement | Repeated balance rows across pages can look like duplicate transactions |
Why do some statements combine debit and credit into one column?
Most Indian bank statements use two separate columns - one for debits (withdrawals) and one for credits (deposits) - leaving the non-applicable column blank for each row. Some exports, particularly certain Excel downloads or older statement templates, instead use a single amount column with a sign or a separate indicator flag (Dr/Cr) to show direction. When you are consolidating statements from multiple banks into one sheet, this difference is one of the most common sources of an incorrectly summed total, because a formula built for a two-column layout will misread a signed single-column statement.
How does narration style differ between banks?
Narration is the free-text description attached to each transaction, and it is where banks differ the most. A UPI payment might appear as UPI/123456789012/Payment from Phone/name@upi in one bank's format and as a shorter, code-only string in another. NEFT and IMPS references, cheque numbers, and merchant names are embedded in the narration in bank-specific patterns rather than in dedicated columns in many statements. This is significant for categorization, since rule-based matching (for example, mapping every narration that contains the text AMAZON to a sales ledger) needs to account for how each bank formats that text.
What about repeating headers and page breaks in PDF statements?
PDF bank statements repeat the account holder's name, account number, IFSC code, and column headers at the top of every page, and sometimes repeat the running balance at the top or bottom of each page as a checkpoint. When extracting data from a multi-page PDF, these repeated header and balance rows need to be identified and excluded, or they can be misread as transaction rows or cause a running balance to be double-counted. This is one of the more error-prone parts of manual PDF-to-Excel conversion; see our guide on converting a bank statement PDF to Excel for a closer look at that process.
How does OneBooks GST handle different bank formats?
OneBooks GST is a GST and accounting platform for Indian businesses that includes a bank statement upload feature supporting PDF and Excel files, parsing them into dated transaction rows with ledger mapping before export to formats like Tally XML. Rather than requiring you to reformat each bank's statement into a single template yourself, the parser is built to read the transaction table regardless of which column order or narration style the source bank uses, and to separate real transaction rows from repeated page headers and balance checkpoints. Once parsed, transactions are ready for categorization and export through the bank statement parser workflow under Admin > Bank Statements.
If you work with statements from several banks - say HDFC for your current account and Kotak for a secondary account - you can upload each one separately and let the platform normalize them into a consistent internal structure before you map ledgers or export to your accounting system.
Frequently asked questions
Do all Indian banks use the same bank statement format?
No, Indian banks do not use a single standard bank statement format. Each bank designs its own statement layout, so column order, date format, and narration style differ between banks such as HDFC, ICICI, SBI, Axis, and Kotak, even though they all report the same core transaction details.
Why does my bank statement have debit and credit in one column?
Some banks and some export types use a single signed amount column instead of separate debit and credit columns, typically showing debits as negative values or with a Dr/Cr flag. This is less common than the two-column layout but appears often enough in certain Excel exports that it is worth checking before you sum a column.
Why do bank statement column headers repeat on every PDF page?
PDF statements repeat the account details and column headers on every page so that each printed or exported page is readable on its own without needing the first page for context. When extracting data programmatically, these repeated rows need to be filtered out so they are not mistaken for transaction entries.
Can I get one consistent format for statements from different banks?
You can normalize statements from different banks into one consistent internal structure using a parsing tool built to read varying bank layouts, such as the bank statement upload feature in OneBooks GST, rather than manually reformatting each bank's export into a common template by hand.
Does the bank statement format affect GST reconciliation?
The statement format itself does not change your GST liability, but an inconsistent format across banks increases the chance of manual transcription errors that can affect the accuracy of your books and downstream reconciliation. Verifying totals after any format conversion is good practice before those figures feed into your accounting records.
