Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
SBI handles PSU, government, and PFMS-heavy current account flows — with longer 50-character narrations, PFMS credits tagged as PFMS/[scheme]/[FY]/[ref], and GSTN refund credits formatted as GSTN REFUND [GSTIN]/ARN-[ref]/[period]. Standard private-bank parsers mis-handle these formats and CSV-only YONO Business accounts lose structured data.
SBI-specific parser separates YONO Business CSV from CMP or CMS MT940 routes. PFMS credits are classified by scheme code and routed to the matching receivable (MNREGS, GST refund, subsidy). GSTN refund credits are matched to the corresponding RFD-01 ARN plus tax period. Normalisation flattens SBI's longer narrations before UTR extraction.
YONO Business CSV ingestion with DD/MM/YYYY date format, MT940 for CMP or CMS accounts, PFMS-scheme routing table, and ARN-to-tax-period mapping for GSTN refunds.
Reconciled SBI current account ledger with PFMS credits posted to correct scheme receivables, GSTN refund credits matched to RFD-01 claims, and multi-bank normalisation enabling side-by-side HDFC-ICICI-SBI reporting.
SBI bank reconciliation India presents a distinct set of parsing and matching challenges that private bank accounts do not. SBI is the primary settlement bank for public sector undertakings, government-grant recipients, and companies with significant PFMS credit flows — and its statement narration formats reflect that government-banking heritage. Finance teams configured for HDFC or ICICI account structures will encounter consistent exceptions when they apply the same reconciliation rules to SBI statements.
What SBI Bank Reconciliation Involves
SBI bank reconciliation is the process of matching the balance and individual transactions in an SBI current account statement against the corresponding entries in the company’s books of accounts. The process applies the same principles as standard bank reconciliation — match debits and credits, identify timing differences, flag unmatched items — but requires account-type-specific configuration because SBI runs multiple current account product lines with materially different statement structures.
The primary distinction is between standard SBI current accounts accessed via YONO Business, and accounts enrolled in CMP or CMS arrangements. Government-linked companies often hold both: a CMP account for high-volume PFMS inflows and a standard current account for vendor payments and salary disbursements.
SBI Account Types and Statement Sources
YONO Business (Standard Current Accounts)
YONO Business is SBI’s enterprise internet banking platform. It provides CSV statement downloads for all current account types. The CSV format includes date, description (narration), debit amount, credit amount, and balance. Date format is DD/MM/YYYY. Narration length extends up to 50 characters, which is longer than the standard formats on HDFC NetBanking or ICICI CIB.
For automated reconciliation, the narration must be parsed field-by-field. NEFT and RTGS credits embed the UTR number starting at character position 1 (format: SBIN followed by year, day-of-year, and 7-digit sequence — for example, SBIN26080123456). IMPS credits embed the UTR differently: it appears after the sender’s bank code and reference.
CMP and CMS Accounts
SBI’s CMP accounts support MT940 statement export — a structured SWIFT format used by SAP and Oracle treasury modules. MT940 field 61 carries the transaction reference and amount; field 86 carries the narrative detail including the UTR. Companies running SAP ERP can configure SAP’s Bank Statement Import (transaction FF.5) to consume SBI MT940 directly, eliminating manual CSV parsing.
Government Accounts
Government-linked entities — ministries, PSUs, grant recipients — hold SBI accounts that receive PFMS (Public Financial Management System) disbursements. These accounts may be classified as Single Nodal Accounts (SNAs) or sub-accounts under the state treasury. Their statement narrations follow PFMS’s own reference structure, which differs from standard NEFT narrations.
SBI Statement Format Reference
| Statement Source | Export Format | UTR Location in Narration | Account Type | Notable Narration Pattern |
|---|---|---|---|---|
| YONO Business (standard) | CSV | Characters 1–22, NEFT/RTGS credits | Standard current account | ”NEFT CR-SBIN26080123456-VENDOR NAME-REF” |
| CMP portal | MT940 | Field 86, after bank code | CMP-enrolled account | ”/REF/SBIN26080123456/TRF/VENDOR NAME” |
| CMS (Cash Management) | MT940 or CSV | Field 86 or characters 5–27 | High-volume corporate | ”RTGS CR SBIN260801234 CORPORATE NAME” |
| Government / SNA account | CSV | After scheme code prefix | PSU / nodal account | ”PFMS/MNREGS/2024-25/SBIN26080123456” |
| SBI YONO (IMPS) | CSV | Characters 9–30, after bank code | Standard current | ”IMPS CR 926080123456789 HDFC SENDER” |
India-Specific Reconciliation Considerations for SBI Accounts
SBI accounts used by government-linked companies carry three credit types that require separate matching rules.
PFMS disbursements arrive with a scheme code in the narration. The finance team must maintain a scheme-code-to-GL mapping — MNREGS credits go to a different GL than PM-KISAN credits, even though both arrive via PFMS. Without this mapping, all PFMS credits land in an unclassified suspense account and require manual reclassification.
GST refund credits from GSTN are routed through SBI’s government payments gateway. The ARN (Application Reference Number) in the narration is the match key against the GST portal refund ledger under GSTR-1 and the refund application filed in the GST portal. The ARN format is alphanumeric with a 15-character structure.
TDS challan auto-debits for Section 192 (salary TDS) appear as debits with the narration “OLTAS TDS CHALLAN” followed by the CIN (Challan Identification Number). The CIN — BSR code (7 digits) + date of deposit + serial number (5 digits) — is the match key against TRACES records. Reconciling TDS challan debits in SBI requires pulling the corresponding TRACES challan report and matching on CIN.
For enterprises running SBI accounts alongside HDFC or ICICI accounts, multi-bank reconciliation India requires bank-specific parser configurations that normalise UTR extraction and narration parsing before the matching engine runs.
The bank reconciliation statement India format for SBI accounts follows the same BRS structure as other banks — but the outstanding item descriptions must reference SBI-specific narration codes to be auditor-readable.
Enterprises managing SBI reconciliation at scale benefit from reconciliation software India that maintains bank-specific parser profiles, handles PFMS scheme-code mapping, and extracts UTRs from both CMP MT940 and YONO Business CSV formats without manual field configuration.
For companies using SBI as the primary settlement bank for TDS challan deposits, TDS reconciliation software that cross-references OLTAS debit narrations with TRACES challan data reduces the manual effort of CIN-based matching by automating the TRACES report import.
Enterprise banking standards and SBI’s regulatory payment infrastructure framework are published by the Reserve Bank of India, where guidelines covering NEFT, RTGS, and government payment routing for Indian commercial banks are maintained.