IDFC FIRST Bank Corporate Reconciliation: Statement Formats and Narration Conventions

IDFC FIRST Bank has scaled quickly as a corporate banking partner for mid-market enterprises, NBFCs, and digital-first businesses. For reconciliation teams onboarding the bank for the first time, the practical issue is rarely the bank — it is that statement parsers built for HDFC or ICICI use forward-slash delimiters, while IDFC FIRST narrations use hyphens. UTR positions move, NACH batches hide individual mandates, and connected banking files arrive in formats that the ERP statement importer was never configured for. This guide is for treasury managers, finance controllers, and reconciliation engineers configuring IDFC FIRST corporate reconciliation for the first time or auditing an existing setup that is producing too many unmatched lines.

IDFC FIRST Corporate Statement Formats

IDFC FIRST Bank delivers corporate account statements through three main channels, each with different downstream implications.

Corporate portal CSV and Excel exports are the default for all current account holders. The export contains transaction date, value date, narration, debit, credit, and running balance columns. Narration is a single hyphen-delimited string and may be padded to a fixed column width in Excel exports — parsers should trim whitespace before splitting. Portal-exported CSVs are unsigned files; teams running internal audits should reconcile the portal CSV total to the IDFC FIRST end-of-day balance shown in the portal header before treating the file as authoritative.

IDFC FIRST MT940 over SFTP is available to corporate clients enrolled in the connected banking or cash management programme. MT940 carries the standard SWIFT tags — :60F: opening balance, :61: per-transaction line, :86: narration, :62F: closing balance — and is consumed natively by SAP and Oracle. The narration inside :86: follows the same hyphen-delimited structure as the portal CSV, which simplifies parser reuse across channels. Intraday statements via MT942 are available on request where customers need mid-day positions for treasury operations.

Connected banking files are structured CSV or XML exports that IDFC FIRST delivers as part of host-to-host integrations. These files break out payment type, UTR, counterparty, amount, and value date as discrete columns rather than embedding them inside a single narration string. Where available, connected banking is the preferred ingestion path because no narration parsing is required and downstream match keys are already structured.

PDF statements remain available from the corporate portal but should not be the primary reconciliation input. PDF parsing accuracy varies with template versions, and ERP systems that fall back to PDF for IDFC FIRST consistently show higher exception rates than those using CSV or MT940 inputs.

IDFC FIRST Narration Patterns by Transaction Type

NEFT Inward Credits

IDFC FIRST NEFT inward narrations follow: NEFT-[UTR]-[remitter name]-[remitter bank]-[reference]

Example: NEFT-IDFB2616401234567-ACME EXPORTS PVT LTD-HDFC0000123-INV-2026-0412

The UTR is always the second hyphen-delimited segment and is 22 characters in length following the standard NEFT format (4-character IFSC prefix + 2-digit year + 3-digit day of year + 7-digit sequence + padding). In MT940, the same narration appears inside the :86: tag without any additional prefix — parsers do not need to strip a vendor prefix the way they do for HDFC /INF/.

RTGS Inward Credits

RTGS narrations follow: RTGS-[UTR]-[remitter name]-[remitter bank]-[reference]

RTGS transactions are above ₹2 lakh by regulation. The remitter name carried in RTGS narrations is the legal entity name as registered with the originating bank — this may differ from the trade name on the invoice. Reconciliation engines should apply fuzzy entity matching against the AR master before declaring a counterparty mismatch. Same-day RTGS credits typically arrive between the bank’s published RTGS windows; settlement timing is governed by the Reserve Bank of India Payment and Settlement Systems framework.

UPI Credits

UPI credits to IDFC FIRST current accounts appear as: UPI-[UPI reference]-[VPA or remitter name]-[description]

The UPI reference is a 12-digit numeric. High-value aggregator credits from Razorpay, PayU, Cashfree, or PhonePe appear as consolidated single lines that net multiple underlying customer transactions for the settlement window. These single lines must be matched against the aggregator’s settlement file rather than against individual customer invoices.

NACH Credits and Debits

NACH credits appear as: NACH-[sponsor bank code]-[batch reference]-[settlement date]

NACH debits to corporate accounts (where the company is the debtor — for example, vendor payments via NACH) appear as: NACH-DR-[mandate ID]-[creditor]-[purpose code]

The credit single line aggregates the entire batch and does not enumerate individual mandates. Reconciliation systems must pull the NPCI NACH settlement report or the IDFC FIRST NACH MIS file and join on the batch reference to explode the credit into mandate-level rows. The debit form does carry the mandate ID, so corporate debit-side reconciliation is straightforward.

IMPS Credits

IMPS credits follow: IMPS-[transaction reference]-[remitter name]-[remitter mobile or account]

IMPS is used by individual customers and small remitters where amounts are below the RTGS threshold and immediate settlement is required. For corporates collecting on-demand customer payments, IMPS credits often carry the customer’s mobile number as the remitter identifier — useful for matching to a CRM record but not to a finance invoice number.

IDFC FIRST Statement Type Reference Table

Worked Example: A Mid-Size NBFC Reconciling a Day’s IDFC FIRST Activity

Consider a mid-size NBFC that uses IDFC FIRST as its primary collections account. A single day produces the following on the corporate portal CSV:

• 247 NEFT inward credits totalling ₹4,82,30,000 — borrower EMI receipts and lump-sum prepayments
• 38 RTGS inward credits totalling ₹7,65,00,000 — institutional disbursement returns
• 1,124 UPI credits totalling ₹62,40,000 — small-ticket borrower repayments via the NBFC’s UPI handle
• 1 NACH credit batch totalling ₹3,15,80,000 — covering 2,847 mandate-level EMI collections
• 12 outward IMPS debits totalling ₹4,80,000 — refund disbursements
• 4 service-charge auto-debits totalling ₹38,200 (GST inclusive)
• 1 Section 194A TDS debit of ₹14,200

The reconciliation system splits the day’s file by transaction type. NEFT and RTGS inward narrations are split on hyphens and the second segment validated as a 22-character UTR; matches run against the NBFC’s expected receivables file. UPI credits aggregate into a single block and reconcile against the aggregator settlement file rather than individual loan accounts. The single NACH batch line is exploded by joining on the batch reference to the NACH MIS file pulled separately — without that join, the bank statement alone shows one matched line and 2,846 missing receipts at the borrower level. Service-charge debits route to the bank charges GL with the 18% GST component reserved for input credit. The Section 194A TDS debit posts to the TDS-receivable GL and is matched against Form 26AS at quarter-end.

Without channel-aware parsing and the NACH MIS join, the same day’s file produces hundreds of false exceptions at the EMI level — visible to credit operations as “missed payment” alerts that are in fact reconciliation gaps, not customer delinquency. For teams sizing the operational cost of these exceptions before approving a tooling investment, the three-way match exception cost calculator translates an exception rate into rupee cost per month.

IDFC FIRST-Specific Reconciliation Considerations

GST on service charges. IDFC FIRST debits service fees with GST at 18% included. Narrations follow IDFC-CHRG-[service type]-[period] and the bank issues a consolidated monthly GST tax invoice. Reconciliation systems must map these debits to a bank charges GL and separate the GST component for input credit claims; mishandling here is a common audit finding because finance teams treat the gross debit as a single charge and lose the recoverable ITC.

TDS on interest income. Section 194A applies at 10% on interest credited where annual interest exceeds ₹40,000 (₹50,000 for senior citizens). IDFC FIRST debits TDS as a separate line — TDS-194A-[deposit reference] — and the same amount appears in Form 26AS. The reconciliation system should auto-match the debit to the 26AS credit and post a TDS receivable until the income tax filing settles the balance.

Bulk NEFT outward payments. Corporates running vendor payouts or salary disbursements via IDFC FIRST NetBanking or connected banking upload a single payment file; the resulting bank-side debit is a single consolidated entry covering all individual transfers. The receiving banks each show separate inward NEFT lines with their own UTRs. Outward reconciliation at the corporate side must match the bulk debit to the payment file total, not to individual beneficiary lines — a common parser misconfiguration is to attempt line-level matching and generate hundreds of unmatched debits.

Pre-merger account numbers. A subset of legacy Capital First customer accounts were migrated into IDFC FIRST account number ranges at the time of the merger. Historical reconciliation against pre-2018 statements may need a remap file that translates legacy account numbers to current IDFC FIRST account numbers; relationship managers can provide this mapping where needed.

Branch and IFSC structure. All IDFC FIRST IFSC codes begin with IDFB0 followed by a six-digit branch code. Counterparty validation in the reconciliation engine should treat IDFB-prefixed remitter banks as IDFC FIRST and route any same-bank intra-account transfers through the appropriate intercompany reconciliation rather than the AR matcher.

Closing Notes

IDFC FIRST corporate reconciliation is operationally straightforward once the parser is configured for hyphen-delimited narrations and the NACH batch join is wired up. The most common failure modes are reuse of HDFC or ICICI parser profiles (forward-slash delimited), reliance on PDF inputs where CSV or MT940 are available, and treating the NACH credit line as a single matched transaction rather than exploding it to mandate level. Enterprise finance teams evaluating tooling should look for bank reconciliation software India implementations that support per-bank parser profiles and external settlement file joins as first-class configurations, and reconciliation software India that can hold IDFC FIRST alongside other corporate banks in a single multi-bank workflow. See the HDFC Bank reconciliation guide and ICICI Bank reconciliation guide for parallel configurations on the two largest enterprise banks, and MT940 bank statement reconciliation India for the SWIFT format details that apply across all corporate banks delivering MT940.