Indian bank statement narration codes, decoded

Instant transfer addressed to a VPA (a Virtual Payment Address such as name@oksbi) rather than an account number. Now the highest-volume rail by a wide margin, and the reason modern statements run to hundreds of lines.

In your books: Counterparty is in the VPA — the text before the @ is usually the best clue to the ledger.

Batch-settled interbank transfer operated by the RBI, with no minimum amount. Narrations usually carry a 22-character UTR followed by the counterparty name, and often an invoice or reference string.

In your books: Typically supplier payments and customer receipts — the counterparty name is usually spelled out.

Real-time settlement for high-value transfers, with a ₹2 lakh minimum. Structure resembles NEFT, though some banks omit the CR:/DR: prefix.

In your books: High-value by definition — usually a significant supplier, asset purchase, or inter-company movement.

Instant interbank transfer available around the clock, run by NPCI, with a ₹5 lakh ceiling. Narration commonly carries a 12-digit RRN and a mobile number or name.

In your books: Often staff reimbursements and urgent supplier payments made outside banking hours.

Mandate-based recurring collection or payment — loan EMIs, SIPs, insurance premiums, utility bills. Narrations reference a batch, so one line may represent a scheduled mandate rather than an ad-hoc payment.

In your books: Recurring by nature — map the mandate once and the same ledger applies every month.

The older bulk payment and collection system, largely superseded by NACH but still appearing in narrations, particularly on legacy mandates and older statements.

In your books: Treat like NACH — almost always a recurring, mappable item.

A 22-character identifier attached to NEFT and RTGS transfers. This is the one part of Indian narration that genuinely is standardised, which is why it's the most reliable field to match on.

In your books: The number to quote when asking a bank or a customer to trace a payment.

A 12-digit reference used for IMPS transactions, traceable through your bank's IMPS enquiry.

The UPI address a payment was sent to or received from, shaped like name@bankhandle (for example john@oksbi). Frequently the only human-readable clue on a UPI line.

In your books: Recurring VPAs are worth mapping to a fixed ledger — the same payee appears every month.

An 11-character code identifying the counterparty's bank branch, often embedded in cheque and NACH narrations.

Money into the account. In Tally this becomes a Receipt voucher.

Money out of the account. In Tally this becomes a Payment voucher.

A UPI payment to a registered merchant — a shop, a platform, a service provider.

In your books: Usually a business expense; the merchant name often follows the reference.

A UPI transfer between individuals rather than to a merchant account.

In your books: Worth scrutiny in a business account — often a reimbursement, an advance, or a drawing.

A transfer addressed to an account number rather than a VPA, seen most often on IMPS.

A cheque transaction. The cheque number normally appears alongside, which is what you reconcile against your cheque register.

A cheque that has passed through clearing. Commonly shown as 'TO CLG' with the instrument number for an issued cheque.

The image-based cheque clearing standard in use since 2010, sometimes named explicitly in the narration.

A bank-issued draft, purchased or credited.

A cash withdrawal or deposit at a machine.

A card payment at a terminal. The merchant name usually follows and is your best categorisation clue.

In your books: Direct business expense in most cases — fuel, supplies, travel.

The channel the instruction came through, rather than a payment type.

A fixed loan repayment. The line is a single amount, but it usually contains both principal and interest.

In your books: Split between the loan ledger and interest expense — the bank line alone won't tell you the split, so take it from the loan schedule.

A recurring payment the account holder set up with the bank directly, rather than through a NACH mandate.

Interest credited on a balance, or charged on an overdraft or loan.

In your books: Interest income or interest expense — never a supplier or customer ledger.

A bank fee — account maintenance, transaction charges, cheque book issue, SMS alerts.

In your books: Bank charges expense. Small and frequent, so worth a dedicated ledger.

An entry reversing an earlier one — a failed transfer returned, or a charge refunded. It should pair with the original line.

In your books: Match to the original entry and post to the same ledger so the two net out.

Tax the bank deducted, typically against interest credited on deposits.

In your books: TDS receivable, not an expense — it's creditable against your tax liability.

A returned or dishonoured instrument, usually followed by a separate charge line for the return fee.

NEFT credit

Rail, then a 22-character UTR, then the counterparty, then their own invoice reference — the most informative shape you'll see.

RTGS credit

Same structure as NEFT. Some banks drop the CR: prefix entirely and rely on the column position instead.

UPI merchant payment

Rail, transaction type, reference number, VPA, then an order reference. The VPA is the categorisation clue.

IMPS transfer

Often a mobile number and a name. Some banks prefix it IMPS CR instead.

Cheque clearing

Cheque number, the drawee bank's IFSC, and the instrument date — reconcile against your cheque register.

NACH mandate

A batch reference rather than a counterparty. You'll usually need the mandate itself to know what it was for.