Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Axis Bank's CIB platform exports the same transactions across CSV, PDF, and MT940 with different narration shapes — and the CSV truncates NEFT/RTGS UTRs at the 120-character column boundary. Without channel-aware parsing, '/RFB/' prefix stripping, and holiday-aware date bucketing, weekend and holiday postings collapse into wrong value dates and auto-match falls below 60 percent.
Channel-aware ingestion routes Axis CSV, MT940, and MT942 to separate parser profiles. NEFT and RTGS narrations are tokenised on hyphen delimiters with '/RFB/' prefix stripping in :86:. Holiday calendar logic maps RBI-notified non-banking days to the next available statement date. Intra-day MT942 postings are tracked for cash visibility but reconciliation closes only against the MT940 :62F: end-of-day balance. Service-charge debits route to the bank charges GL with GST split for ITC.
Axis CIB '/RFB/' parser profile, MT940 end-of-day SFTP ingestion, MT942 intra-day visibility stream, NEFT/RTGS hyphen tokeniser, RBI holiday calendar, Section 194A TDS auto-recon for interest credits above ₹40,000.
Clean Axis transaction ledger reconciled against MT940 :62F:, intra-day cash position from MT942, NACH batch credits exploded against sponsor-bank settlement files, GST-eligible bank charges in the input tax credit register, and Section 194A TDS aligned with Form 26AS.
Axis Bank is one of the three most widely used corporate banking partners in India, alongside HDFC and ICICI. Treasury and finance teams that run reconciliation on Axis current accounts deal with the bank’s Corporate Internet Banking (CIB) platform — and within that, three distinct statement channels, each with its own narration shape and parse behavior. CSV exports lose UTRs to column truncation, MT940 files carry an Axis-specific /RFB/ prefix that breaks naive parsers, and holiday cut-off windows roll postings into the next working day in ways that the date column does not make obvious. This guide walks through Axis CIB statement formats, NEFT and RTGS narration patterns, MT940 structure, holiday-aware date handling, and the intra-day versus end-of-day distinction that often goes wrong during the first month of an Axis reconciliation rollout.
Axis Bank CIB Statement Channels
Axis Bank Corporate Internet Banking provides three statement channels for current account holders. Each channel exposes the same underlying transactions but with different field shapes, delivery cadence, and data fidelity.
CIB CSV export is the default for most corporate users. It is downloaded from the CIB web portal on demand, with fields for value date, posting date, narration, debit amount, credit amount, and running balance. The narration column is free text and is truncated at approximately 120 characters. For NEFT and RTGS credits with long remitter names, the truncation often eats the trailing invoice reference — sometimes the UTR itself when the remitter bank prepends its own routing code.
CIB MT940 is the SWIFT-format end-of-day statement. It is available to corporate clients enrolled in the CIB Premium tier or the Liquidity Management Services pack. MT940 is delivered via SFTP at a scheduled time after the daily 23:30 IST cut-off. It contains the standard :60F: opening balance, :61: transaction lines, :86: narration extension, and :62F: closing balance. Because every field is structured, MT940 is the preferred ingestion path for high-volume reconciliation.
CIB MT942 is the intra-day statement. It is delivered every 30 to 60 minutes during banking hours and reflects provisional postings — credits that have hit the account but may not have cleared inter-bank settlement. Treasury dashboards consume MT942 for live cash position; reconciliation does not close against MT942.
CIB PDF download also exists but is rarely used for reconciliation. It is a signed PDF of the on-screen statement and requires an OCR engine to extract transactions. Axis’s PDF retains the full narration without the CSV’s column truncation, so it is sometimes used as a fallback when CSV imports lose data.
Axis Bank Narration Patterns by Transaction Type
NEFT Inward Credits
Axis Bank NEFT credits follow the pattern: NEFT-[UTR]-[remitter name]-[remitter bank]-[reference]
Example: NEFT-AXIS2606012345678-ABC TRADING PVT LTD-HDFC0000123-INV-2026-0451
The UTR is always 22 characters and appears between the first and second hyphen. In MT940, the same content appears inside :86: prefixed by Axis’s structured-information marker:
:86:/RFB/NEFT-AXIS2606012345678-ABC TRADING PVT LTD-HDFC0000123-INV-2026-0451The /RFB/ prefix is Axis-specific and marks the beginning of the structured narration. Parsers configured for HDFC’s /INF/ prefix will silently skip Axis files unless the profile is explicitly extended.
RTGS Inward Credits
RTGS narrations mirror NEFT: RTGS-[UTR]-[remitter name]-[remitter IFSC]-[reference]
RTGS settlement applies only to transactions above ₹2 lakh, so RTGS credits in an Axis statement are typically B2B inflows from large customers or settlements from payment aggregators. The remitter IFSC is useful for fuzzy entity matching when the legal name in the narration differs from the trade name on the invoice — reconciliation systems can fall back to IFSC-based bank-of-record matching when the name string does not exact-match a master.
UPI Credits
UPI credits to Axis current accounts appear as: UPI/CR/[UPI ref]/[VPA]/[remitter name]/[description]
Aggregator credits from Razorpay, PayU, Cashfree, and similar gateways arrive as single bulk lines covering thousands of underlying customer transactions. These lines must be matched against the aggregator’s daily settlement file, not the customer ledger. The Reserve Bank of India framework for Payment and Settlement Systems governs how aggregators report this settlement detail.
NACH Batch Credits and Debits
NACH inflows appear as a single line: NACH-CR-[batch reference]-[sponsor bank code]-[amount]
NACH outflows for collections (mandate debits originated by your company) appear under: NACH-DR-[batch reference]-[sponsor bank code]
The Axis statement does not explode the batch into individual mandates. To match each mandate to the underlying customer or vendor, the NPCI NACH settlement report — downloaded separately from the sponsor bank’s portal — is required.
IMPS Credits
IMPS credits use: IMPS-[reference]-[remitter name]-[remitter mobile last 4]-[description]
The IMPS reference is shorter than a UTR (12 characters) and does not embed the bank code. IMPS credits are common for low-value retail collections and should be routed to the same matcher profile as UPI for narration purposes.
Axis Bank Statement Format Reference
| Channel | Format | UTR Location | NACH Handling | Delivery |
|---|---|---|---|---|
| CIB CSV | Unstructured CSV | Inside narration, truncated at 120 chars | Single batch line, no mandate detail | Manual download, on demand |
| CIB MT940 | SWIFT structured tags | Inside :86: after /RFB/ prefix | Single :61: line per batch | SFTP, end-of-day after 23:30 IST |
| CIB MT942 | SWIFT intra-day | Same as MT940 | Provisional, may not include settled batches | SFTP, every 30 to 60 minutes |
| CIB PDF | Unstructured (OCR required) | Full narration, no truncation | Single batch line | Manual download |
| CMS Collection Report | Structured CSV | N/A (collection reference) | Mandate-level detail with status | SFTP, post-NACH settlement |
Amounts below ₹2 lakh route through NEFT; amounts above ₹2 lakh route through RTGS. Below ₹2 lakh IMPS is also available 24x7 for instant settlement, while above ₹2 lakh RTGS remains the standard for high-value inter-bank settlement.
Holiday Cut-off and Date Bucket Logic
Axis Bank runs daily end-of-day statement generation at 23:30 IST. On RBI-notified bank holidays — second and fourth Saturdays, Sundays, and gazetted holidays — no end-of-day MT940 is generated. The next banking day’s statement covers all postings from the intervening calendar days under a single value date.
This creates two reconciliation traps. First, NEFT and RTGS credits that settle on a Saturday or Sunday (both run 24x7 under RBI’s current framework) appear on Monday’s MT940 with Friday’s or Saturday’s actual settlement date in the :61: value-date field, but with Monday’s posting date in the :60F: statement-date header. Systems that group transactions by posting date will misalign weekend credits.
Second, NACH settlement happens only on banking days. NACH batches presented on a Friday for next-day settlement may settle on Monday if Saturday is a non-banking day. Reconciliation systems should configure an RBI holiday calendar that maps each calendar date to the relevant banking date for posting and value-date alignment.
Intra-day MT942 vs End-of-day MT940
Treasury teams often consume Axis’s MT942 intra-day statement for live cash position. MT942 is provisional — it includes credits that have hit the account during the banking day but may not have cleared inter-bank settlement. A credit that appears in MT942 at 14:00 IST may be reversed by 18:00 IST if the originating bank’s NEFT batch fails.
For audit-grade reconciliation, only the end-of-day MT940 closing balance in the :62F: tag is the book-of-record. Reconciliation should close against MT940 :62F:, and any cash-position dashboards driven from MT942 should be flagged as provisional in the operating-day reporting.
Worked Rupee Example
A manufacturing company maintains its primary current account with Axis Bank in Mumbai. On a Tuesday in June 2026, the Axis MT940 statement shows the following:
- Opening balance (:60F:): ₹4,12,55,300
- NEFT credit ₹18,40,000 —
NEFT-AXIS2606010987654-DEALER MOTORS-HDFC0000234-PO-2026-1102 - RTGS credit ₹65,00,000 —
RTGS-AXIS2606011223344-OEM BUYER LTD-ICIC0000891-CONTRACT-AXIS-2026-005 - NACH-CR batch ₹2,87,40,000 —
NACH-CR-NACH2606010001-AXIS-2870000000 - Service charge ₹1,500 —
AXIS CHG CMS JUN2026 - IGST 18% ₹270 —
IGST 18% ON CMS CHG - Closing balance (:62F:): ₹7,32,33,530
The NEFT and RTGS credits are matched directly to open invoices using the UTR-to-AR-document map. The NACH batch credit is exploded using the sponsor-bank NACH settlement file to reveal 412 individual mandate collections, each matched to the corresponding customer’s open invoice. The service charge plus GST line is routed to the bank charges GL with the ₹270 GST component flagged for ITC against Axis’s monthly tax invoice. To size the cost of leaving these exceptions to manual research, treasury teams can run the three-way match exception cost calculator on their own daily volume.
Closing
Axis Bank corporate reconciliation works cleanly once three things are configured correctly — channel-aware parsing across CSV, MT940, and MT942; /RFB/ prefix stripping inside :86: for NEFT and RTGS narrations; and an RBI holiday calendar that aligns weekend and holiday postings to the right value date. Treasury teams running multi-bank operations should add Axis alongside HDFC, ICICI, and SBI in a unified reconciliation setup, and finance controllers should verify that GST on Axis service charges is captured in the input tax credit register every month.
For wider context, see bank reconciliation software India and reconciliation software India for product-level coverage, the HDFC Bank reconciliation guide for the equivalent walkthrough on HDFC, the MT940 bank statement reconciliation India deep-dive on SWIFT tag structure, and the multi-bank reconciliation India playbook for running Axis, HDFC, ICICI, and SBI together in one workflow.