Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Yes Bank corporate statements arrive across YES Online portal exports, YES Connect host-to-host files, and MT940 — each carrying forward-slash-delimited narrations that look similar to HDFC and ICICI but with no /INF/ prefix in MT940, leading parsers misconfigured for vendor prefixes to either strip valid characters or miss UTRs entirely. NACH batch credits collapse mandate-level detail, and the post-2020 reconstruction adds a legacy account-number remap consideration for historical reconciliation.
Channel-aware parsing routes YES Online portal CSV, YES Connect SFTP files, and MT940 to dedicated configurations. Narrations are split on forward slashes and the second segment validated as a 22-character UTR for NEFT and RTGS, a 12-digit reference for UPI, and a batch reference for NACH. NACH single-line batch credits are exploded against the NPCI settlement report or the YES Connect NACH MIS file. Legacy account-number remap is applied only for pre-2020 historical reconciliation when flagged by the relationship manager.
Yes Bank forward-slash parser profile with no vendor prefix strip, YES Connect SFTP ingestion for host-to-host files and MT940, YES Online CSV fallback with completeness alert, legacy account remap toggle for historical pre-2020 reconciliation, Section 194A TDS auto-reconciliation for interest credits above ₹40,000.
Clean transaction ledger from Yes Bank statements regardless of channel, mandate-level NACH explosion via the NPCI or YES Connect MIS join, bank-charges GL line with ITC-eligible GST schedule, and Section 194A TDS credit aligned to Form 26AS.
Yes Bank holds a substantial book of mid-market and SME corporate current accounts in India. For reconciliation engineers configuring the bank for the first time, the operational pattern is closer to ICICI than to HDFC — forward-slash delimited narrations, a host-to-host channel for higher-volume customers, and MT940 available on request through corporate banking. The wrinkle that catches finance teams is the post-2020 reconstruction: most operational concerns are settled, but historical reconciliation back to that period occasionally needs a remap. This guide is for treasury managers, finance controllers, and ERP integration teams setting up or auditing Yes Bank corporate reconciliation.
Yes Bank Corporate Statement Formats
Yes Bank delivers corporate statements through two principal channels with overlapping but distinct capabilities.
YES Online is the corporate portal where authorised users log in, view balances, download statements in CSV, Excel, and PDF, initiate single and bulk payments, and pull reports. Statement exports are unsigned files; the reconciliation system should match the export total against the YES Online displayed end-of-day balance before treating the file as authoritative for the day. Excel exports may include header metadata rows above the transaction table — parsers should detect and skip these rather than treating them as transaction rows. PDF statements are available for audit purposes but should not be the primary input where CSV or MT940 are available.
YES Connect is the host-to-host integration where Yes Bank pushes statement files, payment acknowledgements, and balance reports to the corporate’s SFTP endpoint on agreed schedules. YES Connect supports CSV, structured XML, and MT940 outputs depending on customer setup. For high-volume customers — typically those processing hundreds to thousands of inward credits per day — YES Connect is the preferred channel because it removes manual portal downloads, locks in delivery times, and provides cryptographic signatures over the file. The integration specification is agreed during onboarding and depends on customer tier; treasury teams should obtain the live specification from the Yes Bank relationship manager rather than relying on third-party documentation.
MT940 over SFTP is available to YES Connect customers and carries the standard SWIFT tag set — :60F: opening balance, :61: per-transaction line, :86: narration, :62F: closing balance. The narration inside :86: follows the same forward-slash structure as the YES Online CSV, which simplifies parser reuse across channels. Unlike HDFC, Yes Bank’s MT940 :86: tag does not carry a vendor prefix such as /INF/ — parsers should not attempt to strip a prefix that does not exist. Intraday MT942 statements are available where customers require mid-day positions for treasury operations.
Yes Bank Narration Patterns by Transaction Type
NEFT Inward Credits
Yes Bank NEFT inward narrations follow: NEFT/[UTR]/[remitter name]/[remitter bank]/[reference]
Example: NEFT/YESB2616312345678/SUMMIT TRADING CO/HDFC0000123/INV-2026-0712
The 22-character UTR appears as the second segment after splitting on the forward slash. In MT940 the narration appears verbatim inside the :86: tag. Reconciliation parsers should split on forward slash, validate the second segment as a 22-character alphanumeric UTR, capture the third segment as the remitter name for fuzzy AR matching, and use the trailing segment as the customer reference candidate against the open-invoice file.
RTGS Inward Credits
RTGS narrations follow the same structure: RTGS/[UTR]/[remitter name]/[remitter bank]/[reference]
RTGS transactions are above ₹2 lakh. The remitter name carried in RTGS narrations is the legal entity name from the originating bank’s records, which may differ from the trade name on the invoice. Reconciliation engines should apply fuzzy entity matching against the AR master and avoid declaring a counterparty mismatch on a literal string comparison alone. RTGS settlement timing follows the Reserve Bank of India Payment and Settlement Systems framework.
UPI Credits
UPI credits to Yes Bank corporate accounts appear as: UPI/[UPI reference]/[VPA or remitter name]/[description]
The UPI reference is a 12-digit numeric. Aggregator credits from Razorpay, PayU, Cashfree, and PhonePe arrive as consolidated lines that net multiple underlying customer transactions for the settlement window and must be matched against the aggregator settlement file rather than individual customer invoices. For corporates collecting through their own UPI handle, individual UPI credits carry the customer’s VPA, which is useful for CRM matching but rarely sufficient for invoice-level reconciliation.
NACH Credits
NACH credits appear as a single consolidated entry: NACH/[sponsor bank code]/[batch reference]/[settlement date]
The single credit line aggregates all successful mandates in the batch. The bank statement alone does not enumerate individual debtors, mandate IDs, or amounts. Reconciliation systems must pull the NPCI NACH settlement report or the YES Connect NACH MIS file and join on the batch reference to explode the batch into mandate-level rows. NACH debit instructions on the corporate’s own account (where the company is the debtor) appear with the mandate ID in the narration and reconcile straightforwardly.
IMPS Credits
IMPS credits follow: IMPS/[transaction reference]/[remitter name]/[remitter mobile or account]
IMPS handles on-demand smaller-ticket credits below the RTGS threshold with immediate settlement. The remitter mobile number in IMPS narrations is the most reliable identifier when matching against a CRM record, but is not typically tied to a finance invoice number.
Yes Bank Statement Type Reference Table
| Statement Type | Format | UTR Location in Narration | NACH Handling | Delivery Frequency |
|---|---|---|---|---|
| YES Online CSV | Forward-slash delimited narration | Second slash segment | Single batch line, no mandate detail | Manual download, daily |
| YES Online Excel | Forward-slash delimited narration, with header rows | Second slash segment | Single batch line | Manual download, daily |
| YES Connect CSV/XML | Field-delimited structured columns | Discrete UTR field | Batch + NACH MIS link | SFTP push, end-of-day |
| MT940 over YES Connect | SWIFT :60F:/:61:/:86:/:62F: | Inside :86:, second slash segment, no vendor prefix | Single :61: line per batch | SFTP, end-of-day |
| MT942 intraday | SWIFT intraday variant | Same as MT940 | Same as MT940 | SFTP, configurable windows |
Worked Example: An SME Manufacturer’s Yes Bank Day
A mid-size SME manufacturer that uses Yes Bank as a primary collections account for domestic B2B sales processes the following on a typical day in the YES Online CSV export:
- 142 NEFT inward credits totalling ₹2,18,40,000 — distributor and wholesale customer invoice receipts
- 19 RTGS inward credits totalling ₹4,12,00,000 — institutional buyer credit-period closeouts
- 56 UPI credits totalling ₹3,80,000 — small-ticket retail customer settlements
- 1 NACH credit batch totalling ₹68,40,000 — covering 312 distributor recurring collection mandates
- 8 outward NEFT debits totalling ₹62,50,000 — supplier payments
- 3 service-charge auto-debits totalling ₹18,400 (GST inclusive)
- 1 outward NACH debit batch of ₹4,20,000 — payroll for non-payroll-bank employees
The reconciliation system splits the day’s file by transaction type and routes each block to the relevant matcher. NEFT and RTGS inward narrations are split on forward slash, the second segment validated as a 22-character UTR, and the third segment captured as the remitter name for fuzzy matching against the AR master. The single NACH credit line is exploded by joining the batch reference to the NACH MIS file pulled separately from YES Connect — without that join, the day’s reconciliation shows one matched line and 311 missing mandate-level receipts, generating false “missed collection” alerts to distributor account management. Service-charge debits route to the bank-charges GL and the 18% GST component is reserved for input credit. The outward NACH payroll batch reconciles against the salary register total.
For SME finance teams quantifying the cost of poorly configured reconciliation before approving a tooling investment, the TDS mismatch estimator translates a sample of mismatched TDS lines into an annual rupee impact.
Yes Bank-Specific Reconciliation Considerations
GST on service charges. Yes Bank debits service fees with GST at 18% included. Narrations follow YESB-CHRG-[service type]-[period] and the bank issues a monthly GST tax invoice that supports input tax credit claims. Reconciliation systems must map these debits to a bank-charges GL and separate the GST component for ITC; the common audit finding is finance teams treating the gross debit as a single charge and losing the recoverable input credit.
TDS on interest income. Section 194A applies at 10% on interest credited where annual interest exceeds ₹40,000 (₹50,000 for senior citizens). Yes Bank debits TDS as a separate line — TDS-194A-[deposit reference] — and the same amount appears in Form 26AS at quarter-end. The reconciliation system should auto-match the debit to the 26AS credit and post a TDS receivable until income tax filing settles the balance.
Post-2020 reconstruction and account numbers. In March 2020 the Reserve Bank of India led a reconstruction of Yes Bank that brought a consortium of investors into the bank. Operationally, account numbers and IFSC codes remained unchanged for the vast majority of corporate customers. Reconciliation against current statements from 2021 onwards needs no special handling. A small number of legacy customers received account-number changes during subsequent branch consolidation; where pre-2020 historical statements are being reconciled against current balances — for example, in an audit reconstruction or a long-tail customer dispute — the corporate relationship manager can confirm whether a legacy remap file is needed. Current operations from FY 2021-22 onwards do not require this overhead.
Bulk NEFT outward payments. Corporates running vendor payouts via YES Connect or YES Online upload a single payment file; the bank-side debit is a single consolidated entry covering all individual transfers. Each receiving bank shows separate inward NEFT lines with their own UTRs. Outward reconciliation at the corporate side must match the bulk debit to the payment file total rather than to individual beneficiary lines — a common parser misconfiguration is to attempt line-level matching and generate hundreds of unmatched debits.
Branch and IFSC structure. All Yes Bank IFSC codes begin with YESB0 followed by a six-digit branch code. Counterparty validation should treat YESB-prefixed remitter banks as Yes Bank and route same-bank intra-account transfers through intercompany reconciliation rather than the AR matcher.
Closing Notes
Yes Bank corporate reconciliation is operationally familiar to anyone who has configured HDFC or ICICI, with the small but important difference that MT940 :86: carries no vendor prefix — parser profiles built for HDFC’s /INF/ should not be applied here. The post-2020 reconstruction adds a one-time consideration for historical pre-2020 reconciliation but is otherwise invisible in current operations. Enterprise finance teams evaluating tooling should look for bank reconciliation software India implementations that support per-bank parser profiles and NACH MIS file joins, and reconciliation software India that holds Yes Bank alongside other corporate banks in a unified multi-bank workflow. See the HDFC Bank reconciliation guide and SBI Bank reconciliation guide for parallel configurations on two other major enterprise banks, and multi-bank reconciliation India for how Yes Bank fits into a consolidated cross-bank reconciliation setup.