Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian companies make 5–6 statutory payments each month (TDS by 7th, GST by 20th, PF by 15th, ESI by 15th, professional tax, advance tax quarterly) across different portals with different match keys (Challan 281 CIN, GST CPIN, PF TRRN, ESIC IP, OLTAS CIN). Missing any deadline triggers Section 201(1A) 1.5%/month TDS interest or Section 50 GST interest.
Build a single statutory payment register keyed on payment type, with each row linking the bank debit to the respective match key (CPIN, TRRN, CIN, BSR+serial) and the portal confirmation status. Reconcile bank debits to portal confirmations within 5 working days and flag any portal-pending item for inquiry.
Unified register across TDS, GST, PF, ESI, advance tax, and professional tax; deadline calendar with interest-rate library; bank narration parser for each payment type; portal-status tolerance of 5 working days.
A CFO-visible statutory payment dashboard with zero missed deadlines, zero Section 201(1A) or 50 interest charges, and an audit-ready compliance pack covering all five portals.
Statutory payment reconciliation in India is the process of confirming — with evidence from each government portal and from the bank — that every statutory obligation for the month has been paid on time, in the correct amount, and recorded correctly in the books. For a company with a workforce, GST registrations, and direct tax liability, this means reconciling 5 or more payment types against 5 or more portals every month, each with a different match key and a different deadline.
This guide is for finance controllers and compliance teams responsible for monthly statutory closure.
What Statutory Payment Reconciliation Is
Statutory payment reconciliation is distinct from general accounts payable reconciliation. It involves comparing:
- The obligation calculated from the books (TDS deducted, GST liability, PF contribution, ESI contribution, advance tax instalment) against the challan amount on the respective portal.
- The challan on the portal against the bank debit using the payment-specific match key.
- The bank debit against the expense or liability ledger in the books.
The reconciliation fails — and a compliance risk exists — when any of these three links breaks: the portal shows a different amount than the books, the bank debit does not carry the expected match key, or the ledger does not reflect the bank debit.
Statutory Payment Register Structure
The statutory payment register is the central tool. It is a monthly worksheet with one row per obligation and the following columns: obligation type, portal name, due date, challan amount (calculated), challan amount (filed), match key (TRRN / CPIN / CIN / BSR+date+serial / challan number), portal confirmation status, bank debit date, bank debit amount, and variance. Any row with a non-zero variance or an unconfirmed portal status is an open item requiring resolution.
Match Key Reference by Payment Type
| Statutory Payment | Portal | Match Key | Bank Narration Prefix | Deadline | Interest Rate if Late |
|---|---|---|---|---|---|
| TDS (Challan 281) | TRACES / Income Tax | BSR code + deposit date + challan serial | OLTAS TDS | 7th of following month (30 April for March) | 1.5% per month (18% p.a.) under Section 201(1A) |
| GST (PMT-06) | GST Portal | CPIN (14-digit) | NEFT CR GSTN CPIN | 20th of following month | 18% p.a. under Section 50 CGST Act |
| PF ECR (Challan) | EPFO Portal | TRRN | EPFO TRRN | 15th of following month | 12% p.a. under Section 7Q EPF Act |
| ESI Challan | ESIC Portal | Challan number | ESIC CHALLAN | 15th of following month | 12% p.a. under ESI Act |
| Advance Tax (Challan 280) | Income Tax / OLTAS | CIN (BSR + date + serial) | OLTAS ADVANCE TAX | Quarterly: 15 Jun / 15 Sep / 15 Dec / 15 Mar | 1% per month under Section 234C |
| Professional Tax | State portal (varies by state) | Challan number | Varies by bank | 15th–20th (state-specific) | Varies by state: typically 1%–2% per month |
Why Siloed Statutory Management Creates Risk
Most Indian companies manage statutory payments across two or three teams: the tax team handles TDS and advance tax; the HR or payroll team handles PF and ESI; the accounts team handles GST. Each team logs into its own portal and posts its own ledger entries. The consolidated bank statement sees all six payments — but no single team reconciles all six against the bank.
Double-payment risk. When two teams both initiate a GST challan for the same period — because neither checked whether the other had already done so — the GST portal credits the second CPIN to the electronic cash ledger. The excess sits in the cash ledger and does not generate a refund automatically. Identifying the double payment requires comparing the electronic cash ledger balance against the expected GST liability, which requires the accounts team to cross into the GST team’s records.
Deadline miss due to no consolidated view. The TDS deadline (7th) falls before the PF/ESI deadline (15th) and the GST deadline (20th). Without a single register showing all three deadlines for the current month, it is possible for the accounts team to close the month believing all statutory payments are complete, while the tax team has not yet filed the TDS challan.
Portal credit lag causing false open items. Each portal has a different confirmation lag: TRACES confirms within 3–5 days; the GST portal confirms CPIN within 1–2 days; EPFO confirms TRRN within 1–2 days; OLTAS (advance tax) confirms CIN within 3–7 days. A reconciliation run immediately after a payment cycle will show several open items that are timing differences, not errors. The statutory payment register must distinguish between confirmed and pending items by portal status, not only by bank debit status.
Reconciling the Register to the Bank Statement Monthly
At month end, the statutory payment register should be reconciled to the bank statement in two passes:
Pass 1 — Match by narration prefix. Filter the bank statement for all entries beginning with OLTAS, EPFO TRRN, ESIC CHALLAN, NEFT CR GSTN CPIN. Each entry should map to one row in the statutory payment register.
Pass 2 — Confirm portal status for each matched item. For every matched bank debit, verify that the match key (TRRN, CPIN, CIN, challan number) appears on the respective government portal as confirmed. Items where the bank debit is confirmed but the portal status is pending should remain tagged as open until portal confirmation arrives.
Any bank debit that cannot be matched to a row in the statutory payment register is an unidentified statutory payment — a risk that must be resolved before the month is closed.
The Institute of Chartered Accountants of India publishes internal control standards governing statutory payment compliance, reconciliation evidence requirements, and finance function accountability, which apply to the statutory payment register as a core internal control document.
For companies managing all six statutory payment types in a single system, reconciliation software India that ingests bank statements alongside portal exports automates the narration-prefix matching and portal status tracking that otherwise requires logging into 5–6 portals manually each month. Where individual statutory challans do not reconcile — particularly TDS — TDS challan mismatch resolution provides the diagnostic framework. The reconciliation audit trail India guide defines the evidence standard for each matched item in the statutory payment register. The month-end close reconciliation checklist India incorporates statutory payment register sign-off as a required step before books are closed. TDS reconciliation software that extends to statutory payment matching reduces the portal login count and consolidates the exception register for all statutory obligation types.