The Reconciliation Playbook
A day-by-day operational discipline for running bank, TDS, GSTR-2B, and GSTR-1 vs 3B reconciliation as a synchronised 20-day monthly close cycle — with named roles, exact portal steps, and escalation triggers. Pairs with the Reconciliation Process Design cluster: design ↔ operations.
Most Indian finance teams close the month in the last seventy-two hours. A cadence that could run cleanly across a twenty-day window compresses into a scramble on the eighteenth, nineteenth, and twentieth — bank reconciliation, TDS challan deposit, GSTR-2B pull, IMS actions, ITC match, GSTR-3B filing, all colliding at once. The result is not a broken finance team. It is a broken cadence. This cluster is the day-by-day playbook for running the four reconciliation streams every Indian enterprise runs — invoice to bank, TDS against Form 26AS or Form 168, GSTR-2B input tax credit matching, and GSTR-1 versus GSTR-3B — as a synchronised sequence rather than a last-week scramble.
Each article names the role that does each step, the portal or tool the step happens in, the exception trigger that stops the sequence, and the sign-off gate that closes it. Owner discipline — AR analyst, AP analyst, tax executive, tax manager, finance manager, controller — is not decoration; it is the mechanism that makes the twenty-day cadence sustainable when the team is understaffed, when the ERP is misbehaving, or when a portal is down. Every article ties back to Terra Insight's Reconciliation Process Design cluster (the design layer above this cluster) — the runbook tells you how to run the sequence; the failure analysis tells you what the sequence is designed to catch. Together they cover both the design and the operations of reconciliation.
Downloadable working artefacts extend the playbook into the finance team's file system. Excel and Google Sheets recipes turn the cluster from reading material into working tools that get forwarded internally, saved into shared drives, and returned to month after month. The interactive workbooks under /tools/ carry the same match logic and categorisation buckets described in each runbook — the article teaches the discipline; the tool applies it to your ledger.
GSTR-2B ITC Reconciliation Runbook: The Five-Day Cycle for Indian Finance Teams
Days 11 to 15 of the monthly close carry the highest single severity of the entire reconciliation cadence — the Section 16(4) November 30 deadline turns any missed input tax credit into a permanent statutory loss. This runbook walks the five-day window the indirect tax executive runs, the tax manager reviews, and the controller signs off, from IMS actions through the three-way match with its five categorisation buckets to Rule 37 and 37A handling and the at-risk queue keyed to Section 16(4).
The Reconciliation Playbook: A Day-by-Day Monthly Close Guide for Indian Finance Teams
Most Indian finance teams close the month in the last seventy-two hours because four reconciliation streams — bank, TDS, GSTR-2B, and GSTR-1 versus GSTR-3B — collide in the same three-day window. This playbook is Terra Insight's day-by-day operational discipline for running the four streams as a synchronised twenty-day sequence, with named roles, sign-off gates between windows, an escalation protocol tied to the Section 16(4) November 30 deadline, and a weekly review that keeps the reconciliation process design register connected to the runbook exceptions.
TDS Reconciliation Runbook: Monthly Deposit and Quarterly Form 168 Match for Indian Finance Teams
TDS is the one reconciliation stream where a five-day operational slip becomes a Section 200A demand notice with 1 percent monthly interest, and where a quarterly Form 168 mismatch left unresolved for three quarters becomes a permanent write-off. This runbook sequences the TDS window across Days 6 to 10 of the monthly close for the tax executive who runs it, with a quarterly Form 168 reconciliation layered on top in June, September, December, and March.
Three-Way ITC Reconciliation in Excel: Purchase Register, GSTR-2B, and IMS Actions in One Workbook
A working recipe for the Excel workbook that runs the three-way match every Indian finance team is supposed to run before signing off on GSTR-3B Table 4 — purchase register versus GSTR-2B versus IMS action log, with a five-bucket categorisation, an at-risk queue that counts down to the Section 16(4) November 30 deadline, and a supplier follow-up sheet that generates from the exceptions. Formulas explained at practitioner level and the companion interactive tool linked.
See how TransactIG installs the continuous detection layer the manual playbook cannot
The playbook works up to specific thresholds — around 200 vendors under GSTR-2B, multi-GSTIN groups, aggregator-heavy revenue models. Above those thresholds, the twenty-day cadence cannot economically maintain the at-risk ITC queue that the November 30 Section 16(4) deadline demands. TransactIG installs the continuous automated aging queue with escalation triggers, freeing the twenty-day cadence from the failure modes it was quietly absorbing.