How to Convert ICICI Bank Statements to CSV or Excel

Prepare the ICICI statement before upload

Use the original PDF

Use the original statement PDF downloaded from ICICI Bank whenever possible. Avoid screenshots because they often reduce OCR quality and remove table structure. If the PDF is encrypted, provide the document open password only. Do not provide internet banking passwords, OTPs, card PINs, or any login credential.

Validate account and period

Confirm that the statement period, account suffix, and page count are correct. ICICI statements may include account summaries, transaction tables, customer information, branch details, and notices. Your final CSV should normally contain only transaction rows. Use summary values to validate the file, but keep them out of the import dataset unless a reviewer explicitly wants them in a separate section.

Step-by-step ICICI PDF conversion workflow

1. Upload the ICICI PDF. Add the PDF open password if the statement is protected.
2. Review extracted pages. Confirm that transaction pages produced rows and that non-transaction pages were not mixed into the table.
3. Check withdrawals and deposits. ICICI statements may use separate amount columns. Decide whether to keep two columns or create a single signed amount column.
4. Export Excel for cleanup. Use Excel when you need formulas, notes, filters, or a reviewer status column.
5. Create a final CSV. Save a clean CSV after removing summary rows, repeated headers, and any rows that do not belong in the import.

Fields to preserve from ICICI statements

A good ICICI export usually includes transaction date, value date, particulars or narration, withdrawals, deposits, and balance. Value date can matter when the posting date differs from the effective date. Particulars can include UPI IDs, NEFT or IMPS references, cheque numbers, ATM activity, card payments, and transfer notes.

Do not shorten particulars too early. The long text may be exactly what an accountant needs to identify the transaction. Keep the raw particulars in the master workbook, then create a simplified description only if the accounting import requires it.

Common ICICI conversion cleanup

Remove repeated headers

Repeated headers are common in long statements. Remove any rows that repeat the table header between transaction rows. Also remove rows that contain account information, statement period text, branch information, or summary totals. These lines are useful for context but should not be imported as transactions.

Merge wrapped particulars

Wrapped particulars are another common issue. Long payment references can span multiple visual lines in the PDF. If a converted row has no transaction date but contains text, it may belong to the row above. Review these lines before export so the description remains complete and the row count is accurate.

Review numeric formatting

Numeric formatting also needs attention. Indian number formatting, commas, and OCR quality can affect values. Sort by withdrawal and deposit amounts to detect unusual numbers. Compare at least one high-value withdrawal, one high-value deposit, the first transaction, the last transaction, and the closing balance against the PDF.

Using ICICI CSV or Excel in real workflows

For tax preparation, Excel is usually the better first export because it allows notes, categories, reviewer initials, and client questions. For import into accounting software, CSV is usually the final format after review. Keep both files when possible: a review workbook for audit trail and a clean CSV for upload.

If you process several ICICI accounts or months, convert each statement separately first. This keeps account-level balances and date ranges clear. After review, you can combine clean files into a consolidated workbook if the project requires it. Combining before validation makes duplicate detection and balance checks harder.

Bank Statement Converter helps by turning the PDF table into rows, but it does not replace review. The safest workflow is automated extraction, targeted validation, then final export.

How to format ICICI rows for import

Most accounting systems do not need every column from the original statement. They usually need date, description, and amount. However, deleting useful ICICI fields too early can make later review harder. Keep transaction date, value date, particulars, withdrawals, deposits, and balance in the master workbook. Then create a separate import sheet with only the fields required by the destination system.

If you combine withdrawal and deposit columns into a single amount column, withdrawals should normally be negative and deposits positive. Use a formula in Excel so the calculation is visible. Once the formula result is reviewed, copy values into the final CSV if the import system cannot handle formulas.

For client work, add review columns instead of editing the bank text directly. Useful columns include category, reviewer note, client question, and source page. This keeps the ICICI particulars intact while giving the accountant room to classify transactions.

Batch processing ICICI statements

When converting several ICICI statements, use consistent file names. Include client name, bank name, account suffix, and statement month. A file name such as client-icici-4321-2026-03.pdf is easier to trace than statement-final-v2.pdf. Use the same name pattern for the exported Excel and CSV files.

Batch workflows should still stop when the input is questionable. If a PDF is missing pages, has a cropped amount column, or appears to cover the wrong date range, flag it before conversion. It is faster to request a correct source file than to repair a spreadsheet built from incomplete information.

Teams that process ICICI statements repeatedly can use API conversion for intake systems or internal portals. The API workflow is useful for submitting PDFs programmatically, but final review should still happen before tax, audit, or accounting use.