ICICI Bank statements look simple at first glance — a tidy seven-column tabular layout — but the format hides two annoyances. The cheque/reference number column is empty for most rows, which trips up naive parsers into shifting columns. And the narration for UPI, NEFT and IMPS transactions wraps across two or three lines in the PDF, which gets split into separate rows in tools that do not stitch the wrap lines back together. This guide walks through how to get a clean Excel file from any ICICI statement format, including the iMobile-generated PDFs that have a slightly different layout from the NetBanking ones.
What ICICI statement layouts are supported
The converter auto-detects all of these:
- ICICI NetBanking e-statement — the standard PDF generated from Bank Accounts → Statement of Account on the website. Columns:
Sr No | Value Date | Transaction Date | Cheque Number | Transaction Remarks | Withdrawal Amount (INR) | Deposit Amount (INR) | Balance (INR). - ICICI iMobile-generated statement — the PDF you get from the iMobile Pay app under Services → Account Statement. The column order matches NetBanking but the page header and footer differ.
- ICICI Current Account — same underlying layout as savings, with longer narration on vendor payments.
- ICICI Salary Account — same layout as savings (the difference is which side of the bank it is registered against, not the statement format).
- ICICI NRE/NRO Account — same column structure with the IBAN block added to the header. The parser ignores the IBAN block.
Step 1: Download your statement from ICICI
From iMobile Pay, open the app, go to Services → Account Statement, pick the date range, choose PDF as the format, and email it to yourself. From NetBanking, sign in, go to Bank Accounts → Statement of Account, pick the period and the PDF format, and download.
ICICI PDFs are typically password-protected. The password is usually your registered date of birth in DDMMYYYY format, or it is documented in the email body if the statement was emailed. To remove the password, open the PDF in your viewer, enter the password, then use File → Print → Save as PDF to produce an unprotected copy. The converter does not accept password-protected uploads (this is a deliberate security choice — we never see your password).
Step 2: Upload to the converter
Drop the unprotected PDF onto the upload zone on the home page. Auto-detection routes it to the ICICI parser whether it came from NetBanking or iMobile.
If you want CSV output (for QuickBooks, Xero, Wave or any cloud accounting tool), tick the Download as CSV instead of Excel checkbox before uploading. If you want a Tally Prime voucher workbook, tick Also include Tally template — the workflow is documented in our Tally import guide.
Step 3: Verify the conversion
Open the Excel file and do these three checks:
- Row count against a rough scroll-through of the PDF.
- Sum of the Withdrawal Amount and Deposit Amount columns using
=SUM(), compared against the printed totals in the statement summary block. - Last row’s balance against the printed closing balance.
The converter does not currently run automatic reconciliation for ICICI (unlike Scotia, BMO, RBC or Axis) because the printed summary on ICICI statements is sometimes rendered with different rounding than the per-line totals, which would produce false-positive warnings. The manual three-step check above takes about 30 seconds and is reliable.
How UPI, NEFT and IMPS narration wrap is handled
An ICICI UPI line in the PDF wraps across two or three rows: the first row has the date, amount and partial narration; the next row has the VPA (e.g. shopkeeper@oksbi); the third row often has the UPI reference number. The parser stitches these continuation lines back onto the originating transaction row, so the Excel file shows one row per transaction with the full narration in the Transaction Remarks column.
Same logic applies to NEFT and IMPS lines: the originating-bank reference, the counterparty name, the IFSC code and the remark all get joined into a single Remarks cell. If you would rather see the raw wrapped lines as separate rows (rare, but useful for some forensic accounting workflows), save the PDF as a .txt file from your viewer first and upload that instead.
The empty-cheque-number column quirk
The Cheque Number column is empty for the majority of rows on an ICICI statement (everything except actual physical cheque transactions, which are now rare). A common failure mode in naive parsers is that they treat the empty column as missing and shift every subsequent column left by one, mangling all the amounts. The ICICI parser handles this by tracking column geometry by pixel position rather than by white-space splitting, so empty cells stay empty and column alignment stays correct.
What the Excel output looks like
The Excel file has one sheet called Transactions with columns Date, Value Date, Cheque Number, Transaction Remarks, Withdrawal Amount, Deposit Amount, Balance. Amounts are stored as numbers (not text), so sums, sorts and pivots work immediately. Indian comma-format amounts like 1,23,456.78 are preserved as numeric values (the lakh-comma display is purely a formatting choice, not part of the underlying number).
If you merged multiple ICICI statements together, you get an additional All Transactions sheet at the front of the workbook with all rows combined and sorted by date.
What if auto-detection fails?
If the converter does not recognise your PDF as ICICI (this is uncommon but happens with very old layouts or with re-saved PDFs), expand the Wrong format detected? Pick your bank manually disclosure under the upload zone and select ICICI Bank from the dropdown.
If that still produces zero rows, the most likely cause is that the PDF is a scanned image of a printed statement rather than a digital download. Image-only PDFs need OCR, which the converter does not run. The fix is to download a fresh e-statement from NetBanking or iMobile (always digital).
Privacy
The PDF is processed in memory during the conversion. A usage log row is written with the bank format, page count, transaction count and file size for analytics and rate-limiting — not the transaction data itself. Full details are on the privacy page.