Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
ICICI CIB statements use hyphen-delimited NEFT narrations and a /TXT/ prefix in MT940 :86: (not HDFC's /INF/), so running the wrong parser produces null match keys. iCollect virtual account numbers are the correct primary key for collection accounts, not the UTR — a common misconfiguration that routes payments to the wrong invoice.
ICICI parser profile strips /TXT/ prefix and splits narration by hyphens to extract UTR, counterparty, and reference. iCollect credits are keyed on virtual account number as the primary identifier, with UTR as a secondary key. Service-charge auto-debits are routed to the bank charges GL with 18% GST linked to the monthly ICICI tax invoice for ITC.
ICICI /TXT/ parser profile with hyphen delimiters, iCollect virtual-account-first routing, CIB CSV and MT940 dual ingestion, and Section 194A TDS check on interest credits above ₹40,000.
Correctly extracted UTR and counterparty for every ICICI credit, invoice-accurate iCollect attribution via virtual account number, bank charges ITC schedule, and reconciled ledger ready for BRS reporting.
ICICI Bank is the second-largest private sector bank in India by assets and a primary banking partner for a large share of mid-market and enterprise companies. Its Corporate Internet Banking (CIB) platform, iCollect service, and MT940 statement export are widely used — but each has specific configuration requirements that differ from HDFC and Axis. Teams migrating from one bank’s reconciliation setup to another, or adding ICICI to a multi-bank configuration, encounter these differences consistently. This guide is for finance controllers, treasury teams, and ERP integration leads configuring ICICI bank reconciliation.
ICICI Bank Statement Formats for Enterprise Accounts
ICICI offers multiple statement delivery options depending on account tier and banking relationship.
CIB CSV Export is available to all Corporate Internet Banking users. The CSV contains date, transaction description, debit, credit, and balance columns. Like most bank CSVs, the description field combines payment type, UTR, counterparty name, and reference in a single free-text string. Field length is constrained — narrations over approximately 100 characters may be truncated.
ICICI MT940 via CIB is available to corporate accounts with CIB access and a formal SFTP arrangement. MT940 delivers structured statement data with :61: for transaction detail and :86: for narration — using /TXT/ as the prefix. This is the preferred input for automated reconciliation engines.
iCollect Statement is a separate report for accounts using ICICI’s virtual account collection service. It lists individual payer credits with virtual account number, payer name, UTR, amount, and timestamp — in a separate structured report not visible in the main account statement.
ICICI Narration Patterns by Transaction Type
NEFT Inward Credits
ICICI NEFT inward credits use hyphens as delimiters — different from HDFC’s forward slashes. Format: NEFT-[UTR]-[counterparty name]-[reference]
Example: NEFT-ICIC2268012345678-RELIANCE INDUSTRIES LTD-PO-2026-0091
In MT940, this becomes: :86:/TXT/NEFT-ICIC2268012345678-RELIANCE INDUSTRIES LTD-PO-2026-0091
RTGS Inward Credits
ICICI RTGS narrations follow: RTGS CR:[UTR] [counterparty] [reference]
The format is closer to HDFC’s RTGS narration than the NEFT narration — using space-separation rather than hyphens. RTGS credits above ₹2 lakh carry the full 22-character UTR.
UPI Credits
UPI inward credits follow the NPCI standard format: UPI/P2M/[UPI ref]/[remitter VPA]/[description]
The Reserve Bank of India mandates the UPI payment system operating parameters including transaction reference standards. For iCollect-enabled accounts, UPI credits to virtual account numbers appear with the virtual account reference as the primary identifier.
iCollect Virtual Account Credits
ICICI iCollect credits appear in the main account statement as: NEFT-[UTR]-ICICI iCollect-[VA number]-[payer name]
The virtual account number is the match key — not the UTR — because all iCollect credits route through the same physical ICICI account. Reconciliation must extract the VA number and attribute the credit to the corresponding invoice or mandate.
ICICI Statement Type Reference Table
| Statement Type | Export Format | UTR Field Location | Account Type | Notable Quirk |
|---|---|---|---|---|
| CIB Portal CSV | Unstructured CSV | Within narration text (hyphen-delimited) | All CIB accounts | Truncation at ~100 chars; hyphen delimiter may conflict with entity names containing hyphens |
| MT940 (CIB) | SWIFT :61:/:86: | Inside :86: after /TXT/ prefix | CIB accounts with SFTP | /TXT/ prefix differs from HDFC /INF/ — requires separate parser config |
| iCollect Report | Structured CSV | Discrete field | Accounts with iCollect | Virtual account number is primary key, not UTR |
| CIB PDF | Unstructured (OCR required) | Embedded in narration | All CIB accounts | Not suitable for automated reconciliation |
| InstaAlert CSV | Minimal structured | Short narration with UTR | Current accounts | Real-time alerts, limited narration length |
ICICI vs HDFC: Key Narration Differences
The most common multi-bank reconciliation misconfiguration is applying HDFC narration parser rules to ICICI statements. Three differences cause systematic matching failures:
First, the MT940 :86: prefix: ICICI uses /TXT/, HDFC uses /INF/. A parser configured for /INF/ on ICICI MT940 files extracts nothing.
Second, the NEFT narration delimiter: ICICI uses hyphens, HDFC uses forward slashes. A regex pattern written for HDFC’s NEFT CR:[UTR]/[name]/[ref] format will not extract UTR from ICICI’s NEFT-[UTR]-[name]-[ref] format.
Third, iCollect vs. standard credit attribution: HDFC does not have an equivalent to ICICI iCollect’s virtual account narration pattern. Finance teams running TDS reconciliation software for customers who remit via iCollect must configure the virtual account number as the match key for those credit entries.
ICICI-Specific Reconciliation Considerations
Service charges and GST. ICICI service charge debits carry narrations in the format ICICI BANK CHARGES [service type] [period]. GST at 18% on service fees is either bundled in the same debit or posted separately. ICICI provides a GST-compliant monthly invoice for input tax credit claims. The charge GL mapping and GST component separation should be automated in the reconciliation rule set to avoid manual adjustments at month-end.
TDS on fixed deposit interest. Under Section 194A, ICICI deducts TDS at 10% on FD interest exceeding ₹40,000 per year per account holder. This debit appears as TDS ON INTEREST [FD reference] [quarter] in the statement. The amount must reconcile against Form 26AS. Finance teams running TDS reconciliation software should map ICICI 194A debits to the TDS receivable account and confirm credit in Form 26AS before each advance tax payment.
For enterprise teams building a multi-bank reconciliation setup, reconciliation software India implementations for ICICI must include a /TXT/ MT940 parser, a hyphen-delimited NEFT narration extractor, and a separate iCollect virtual account attribution rule. See the bank reconciliation process guide for the matching methodology, bank reconciliation statement India for the BRS output requirements, and multi-bank reconciliation India for configuring ICICI alongside HDFC and Axis in a unified workflow.