Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Kotak Mahindra exposes the same transactions across Kotak FYN CSV, MT940, and a separate collections report — with bank-specific narration prefixes ('/PRI/' in :86:) and Kotak-internal Batch Payment IDs ('KOTBP' references) that hide individual beneficiary credits behind consolidated debit lines. Without batch-ID joins to the FYN batch-status file, payroll and NACH collection lines remain unmatched and exception queues balloon.
Channel-aware ingestion routes Kotak CSV, MT940, MT942, and the collections report to separate parser profiles. NEFT and RTGS narrations are tokenised on single-space delimiters with '/PRI/' prefix stripping in :86:. Batch Payment IDs of the form 'KOTBP[YY][NNNNNN]' on consolidated debit lines join to the Kotak FYN batch-status file to explode beneficiary-level detail. Service-charge debits route to the bank charges GL with the GST component split for input tax credit.
Kotak FYN '/PRI/' parser profile, MT940 end-of-day SFTP ingestion, MT942 intra-day visibility stream, Batch Payment ID join to FYN batch-status file, NACH collections report linkage, Section 194A TDS auto-recon for interest credits above ₹40,000.
Clean Kotak transaction ledger reconciled against MT940 :62F:, payroll and vendor payment batches exploded to beneficiary level via Batch Payment ID, NACH collections matched at mandate level, GST-eligible fee debits in the ITC register, and Section 194A TDS aligned with Form 26AS.
Kotak Mahindra Bank has become a default banking partner for many mid-market corporates, NBFCs, and fintech operating companies in India. Finance teams that move their current accounts to Kotak quickly run into a set of bank-specific behaviors in the statement — different narration markers from HDFC or Axis, a Batch Payment ID concept that drives bulk-payment matching, and a separate collections report that carries NACH mandate-level detail. Get those three things wrong during the first month of a Kotak rollout and the bank reconciliation exception queue grows faster than the team can close it. This guide walks through Kotak FYN statement channels, MT940 structure, narration patterns by transaction type, Batch Payment ID handling, fee debit and GST treatment, and the audit-grade rules that hold the daily close together.
Kotak FYN Statement Channels
Kotak FYN is the bank’s corporate banking portal, which has replaced Kotak Net for most enterprise customers. From FYN, corporate users access account statements through three primary channels.
FYN CSV export is the on-demand download. It includes value date, posting date, narration, debit, credit, and running balance columns. The narration column is free text and retains the full Kotak narration string without aggressive truncation, although very long remitter names can still spill in narrations that include reference fields beyond 140 characters.
FYN MT940 is the SWIFT-format end-of-day statement. It is delivered via SFTP after the daily cut-off to corporate clients enrolled in Kotak’s cash management services. MT940 is the preferred ingestion channel for high-volume reconciliation because every field is structured — :60F: opening balance, :61: transaction line, :86: narration extension with the /PRI/ Kotak prefix, and :62F: closing balance.
FYN MT942 intra-day is available to clients on the Liquidity Management module. It is delivered every 30 to 60 minutes during banking hours and is provisional — it should not be used as a book-of-record for reconciliation closure.
FYN Collections Report is a separate structured file that contains NACH mandate-level detail. It is downloaded after each NACH settlement cycle and is the only Kotak-native source that explodes batch credits into individual mandates with status — paid, returned, or pending.
Kotak Mahindra Narration Patterns by Transaction Type
NEFT Inward Credits
Kotak NEFT credits follow: NEFT IN [UTR] [remitter name] [remitter IFSC] [reference]
Example: NEFT IN KOTK2606012345678 ABC TRADING PVT LTD HDFC0000123 INV-2026-0891
The 22-character UTR appears between the first and second space tokens. In MT940 format, this content sits inside :86: with the /PRI/ prefix:
:86:/PRI/NEFT IN KOTK2606012345678 ABC TRADING PVT LTD HDFC0000123 INV-2026-0891The /PRI/ prefix is Kotak-specific. Reconciliation parsers built for HDFC’s /INF/ or Axis’s /RFB/ prefix will not extract any match key from Kotak MT940 files unless the profile is extended explicitly.
RTGS Inward Credits
RTGS narrations mirror NEFT: RTGS IN [UTR] [remitter name] [remitter IFSC] [reference]
RTGS settlement applies only to amounts above ₹2 lakh. Kotak RTGS inflows are common for B2B trade settlements, NBFC disbursements, and large vendor payments. The remitter IFSC token is useful for fuzzy entity resolution when the narration name does not exact-match the customer master.
UPI Credits
UPI credits to Kotak current accounts appear as: UPI CR [UPI ref] [VPA] [remitter name] [description]
Aggregator credits from payment gateways (Razorpay, PayU, Cashfree, Easebuzz) arrive as bulk credit lines covering thousands of underlying customer transactions. These are matched against the aggregator’s daily settlement file, not the customer ledger directly. The Reserve Bank of India framework for Payment and Settlement Systems sets the reporting cadence that aggregators follow.
NACH Batch Credits, Batch Debits, and Mandate Returns
NACH inflows (collections by your company from your customers) appear as a consolidated single line: NACH CR [batch reference] [sponsor bank code] [total amount]
NACH outflows (debit instructions originated by your company) appear as: NACH DR [batch reference] [sponsor bank code] [total amount]
Mandate returns from failed collections appear individually as: NACH RETURN [original batch ref] [mandate UMRN] [return reason code] [amount]
The main statement does not explode the batch credit or batch debit into individual mandates. The FYN Collections Report file is required to expand each batch into mandate-level detail with status — and the standard NACH return reason codes are documented by NPCI.
Bulk NEFT and RTGS Batch Payments
For payroll, vendor payments, and statutory disbursements, corporates upload a bulk payment file to Kotak FYN. The single consolidated debit line uses the format: NEFT BULK DR KOTBP[YY][NNNNNN] [BATCH PURPOSE]
For RTGS bulk batches: RTGS BULK DR KOTBP[YY][NNNNNN] [BATCH PURPOSE]
The KOTBP prefix marks a Kotak Batch Payment ID — for example, KOTBP26012345. Individual beneficiary credits are not in the corporate’s own Kotak statement; they sit in a beneficiary-level batch-status file downloaded from FYN after settlement. Reconciliation uses the Batch Payment ID to join the consolidated debit to the beneficiary-level credits.
Kotak FYN Statement Format Reference
| Channel | Format | UTR Location | NACH Handling | Batch Payment Detail | Delivery |
|---|---|---|---|---|---|
| FYN CSV | Unstructured CSV | Inside narration text | Single batch line | Single consolidated debit only | Manual download, on demand |
| FYN MT940 | SWIFT structured tags | Inside :86: after /PRI/ prefix | Single :61: line per batch | Single :61: line with KOTBP reference | SFTP, end-of-day |
| FYN MT942 | SWIFT intra-day | Same as MT940 | Provisional, may exclude settled batches | Same | SFTP, every 30 to 60 minutes |
| FYN Collections Report | Structured CSV | N/A (collection reference) | Mandate-level detail with paid/return/pending status | N/A | SFTP, post-NACH settlement |
| FYN Batch-Status File | Structured CSV | Per beneficiary UTR | N/A | Beneficiary-level credits with KOTBP join key | FYN portal, post-bulk-settlement |
Amounts below ₹2 lakh route through NEFT or IMPS; above ₹2 lakh route through RTGS. Below ₹2 lakh, IMPS provides 24x7 instant settlement; above ₹2 lakh, RTGS remains the standard for high-value transfers.
Fee Debit Patterns and GST Handling
Kotak Mahindra auto-debits service fees on a near-monthly cycle with narrations that follow consistent patterns:
KOTAK CHG NEFT [MONTH]— NEFT origination chargesKOTAK CHG RTGS [MONTH]— RTGS origination chargesKOTAK CHG CASH MGMT [MONTH]— Cash management services feeKOTAK CHG CMS UPLOAD [BATCH]— Per-batch upload fee for bulk paymentsKOTAK CHG NACH PRESENT [BATCH]— NACH mandate presentation feeKOTAK CHG NACH RETURN [MANDATE]— Per-return fee on bounced NACH mandates
GST at 18% is added in the same debit line — either as a single IGST 18% line item or a split CGST 9% + SGST 9% depending on whether the supplier and the registered company are in the same state. The Kotak monthly tax invoice is the GST-compliant document for input tax credit, and reconciliation systems should map fee debits to the bank charges GL with the GST component flagged for ITC.
TDS Section 194A on Interest Credits
Under Section 194A of the Income Tax Act, Kotak Mahindra deducts TDS at 10% on interest credited if total interest exceeds ₹40,000 per financial year (₹50,000 for senior citizens). The TDS debit appears as a separate line: TDS U/S 194A [reference]. Finance teams should match this debit against Form 26AS to confirm credit deposit, and to flag any mismatch as a recovery exception. Reconciliation systems that connect Kotak statements to a TDS reconciliation workflow can carry this Section 194A line straight into the TDS register for monthly closure.
Worked Rupee Example
An NBFC maintains its operating current account with Kotak Mahindra Bank in Bangalore. On a Thursday in June 2026, the FYN MT940 statement shows the following:
- Opening balance (:60F:): ₹12,84,15,400
- Bulk NEFT debit ₹4,18,75,000 —
NEFT BULK DR KOTBP26012398 PAYROLL JUN2026 - RTGS inward credit ₹85,00,000 —
RTGS IN KOTK2606010001234 PRINCIPAL BORROWER LTD ICIC0000567 LOAN-REPAY-Q1 - NACH-CR batch ₹1,42,30,500 —
NACH CR NACH26060100022 KOTAK 14230500 - NACH-RETURN line ₹15,000 —
NACH RETURN NACH26060100022 UMRN-KOTK1234567890 RETURN-INSUFFICIENT-FUNDS 15000 - Service charge ₹1,200 —
KOTAK CHG CMS UPLOAD KOTBP26012398 - IGST 18% ₹216 —
IGST 18% ON CMS UPLOAD - Closing balance (:62F:): ₹9,93,53,484
The bulk NEFT debit is joined to the FYN beneficiary-level batch-status file using the KOTBP26012398 Batch Payment ID — 287 employee salary credits are matched to the payroll register at beneficiary level. The RTGS credit is matched to the borrower’s open loan account using the UTR. The NACH-CR batch is exploded against the FYN Collections Report to reveal 412 individual EMI collections matched to mandate-level customer records, with one return flagged for re-presentation. The service charge plus IGST debit lines route to the bank charges GL with the ₹216 GST component captured for ITC. To estimate the cost of resolving such exceptions manually across a month of similar volume, NBFC operations leads can run the three-way match exception cost calculator on their daily transaction count.
Closing
Kotak Mahindra corporate reconciliation works cleanly once the three Kotak-specific behaviors are encoded — /PRI/ prefix stripping in :86: for MT940 narrations, Batch Payment ID (KOTBP) joins from consolidated debit lines to the FYN beneficiary-level batch-status file, and Collections Report joins for NACH mandate-level explosion. Treasury and finance teams running multi-bank operations should add Kotak alongside HDFC, ICICI, Axis, and SBI in a unified reconciliation setup, and controllers should verify that GST on Kotak fee debits 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 ICICI Bank reconciliation guide for the equivalent walkthrough on ICICI, the MT940 bank statement reconciliation India deep-dive on SWIFT tag structure, and the multi-bank reconciliation India playbook for running Kotak alongside the other major Indian corporate banks.