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.
The 90-Day GSTR-2B Catch-Up Plan: How to Clear Six Months of Backlogged ITC Before the Section 16(4) Deadline
The CFO opens the September month-end review and realises the GSTR-2B reconciliation has not been run since April. Six months of unmatched input tax credit sit in the ERP against the Section 16(4) November 30 deadline — after which the credit is permanently lost with no rectification, condonation, or refund. This is the 90-day catch-up plan the tax analyst, tax manager, and controller run together — with the weekly extract, the retrospective three-way match, the at-risk queue against the deadline, and the exit back onto the monthly five-day cycle by Week 12.
The Aggregator Dispute Playbook: Letter Templates and Portal Escalation for Zomato, Swiggy, Amazon, and MakeMyTrip Settlement Errors
A Zomato settlement lands 22 per cent short of the expected commission. A Swiggy payout misapplies Section 194O TDS on the gross including customer packaging fees. An Amazon disbursement carries an FBA long-term storage fee against inventory that cleared out ninety days ago. A MakeMyTrip payment holds a hotel reservation payout across a disputed cancellation policy invocation. Each of these has a different dispute window — Amazon seven days, Zomato fifteen, Swiggy twenty-one, MakeMyTrip thirty — and each requires a differently phrased letter that names the right portal ticket path, the right statute anchor, and the right escalation ladder from portal support officer through single point of contact and operations manager to the key account director.
The Deductor Query Playbook: Letter Templates for Form 168 Mismatch and TDS Credit Recovery
The finance team pulled the quarterly Form 168 and one deductor's Rs 84,200 deduction on a Rs 8,42,000 Section 194J code 1005 professional-fee invoice is missing from the credit statement. This is the five-letter escalation ladder — Level 1 polite query through Level 5 statutory-auditor escalation — that Indian tax teams run to convert a Form 168 gap into either a corrected credit or a defensible commercial recovery, with the CGST-Act, Income-tax-Act-2025, and CARO 2020 anchor for each escalation.
The TDS Backlog Manual: The Pre-March 31 Correction Sprint for FY 2018-23 Time-Barred Returns
The 31 March 2026 correction deadline for FY 2018-19 through FY 2022-23 TDS statements is the hardest deadline in the Indian tax calendar — five financial years closing to correction simultaneously with no condonation provision. This is the seven-week sprint that an Indian finance team runs against an illustrative Rs 84 lakh backlog spread across roughly 2,600 line items when Rs 68 lakh of the exposure sits in the oldest year alone. Week 1 extracts the backlog from TRACES by financial year; Week 2 categorises every line into challan mismatch, PAN error, amount mismatch, or section drift; Weeks 3 and 4 file corrections in priority order; Weeks 5 and 6 handle TRACES turnaround and rejection resolution; Week 7 signs off the residual with an Ind AS 37 provision for the irrecoverable balance.
The Vendor GSTR-1 Follow-Up Playbook: Six Letter Templates from Nudge to Legal Notice
The Section 16(4) November 30 deadline turns a supplier's late GSTR-1 filing into a permanent input tax credit loss for the recipient. This playbook is Terra Insight's six-letter escalation ladder — from a T+30 accounts-payable nudge to a T+180 pre-legal notice — that keeps the input tax credit exposure recoverable across the calendar window before the deadline slams shut.
Bank Statement Narration Parsing in Excel: Formulas for NEFT, RTGS, UPI, and NACH Match Keys
Every Indian finance team that reconciles a bank statement in Excel spends the first working hour of the day converting narration strings into a UTR column, a VPA column, a NACH batch column, and a counterparty column that will actually match against the ERP. This is the recipe — the six narration structures, the public Excel formulas that parse each one, the column-truncation and unrecognised-pattern traps, and a downloadable workbook that takes a raw statement paste and returns a parsed match-ready table.
Bank Reconciliation Runbook: The Day-by-Day Sequence for Indian Enterprise Finance Teams
Days 1 to 5 of the monthly close are the bank window. Left to drift, they compress into a scramble that feeds broken data downstream into every other reconciliation stream. This runbook walks the five-day sequence the AR analyst owns, the AP analyst runs in parallel, the tax analyst picks up on Day 3, and the finance manager signs off on Day 5 — from MT940 auto-match through multi-invoice aggregation, TDS-net customer receipts, platform settlements, and the five-bucket exception queue that opens the TDS window.
The DRC-01B Notice: A 72-Hour Triage Playbook for Indian Finance Teams
A DRC-01B notice landed on the GSTN portal this morning. You have seven days to reply under Rule 88C of the CGST Rules. The first three days are what decides whether the case closes with a DRC-03 payment, closes with a Part B rebuttal, or escalates into a Section 73 or Section 74 assessment machinery. This is the hour-by-hour triage playbook the tax analyst, tax manager, and controller run together — with the statutes each decision anchors against, the working paper each hour produces, and the sign-off ceremony that releases the reply to the portal.
The Form 168 Shortfall: A Twelve-Step Investigation for TDS Receivable Mismatches
The TDS receivable ledger says Rs 8,42,000 was credited by a client across the quarter. Form 168 shows Rs 6,73,000. The gap is Rs 1,69,000, and a controller cannot sign off the quarterly close without either recovering it, provisioning against it, or documenting it as a rolling exception with an owner and a date. This is the twelve-check investigation an Indian tax executive runs before either happens — each check anchored to a specific statute, each closing either with a rupee-tagged recovery, a next action, or a documented dead end.
GSTR-1 vs GSTR-3B Runbook: The Final Five-Day Sequence Before Month-End Filing
Days 16 to 20 of the monthly close carry the sequence that either files GSTR-3B at 11am on the twentieth or files it at 11:47pm on the twentieth under time pressure. The four earlier windows have each produced a signed-off working paper; this final window assembles those into GSTR-3B, catches the GSTR-1 versus 3B mismatch before Rule 88C fires a DRC-01B intimation, and closes the month against a defensible audit trail. Runs the GST executive as owner, the tax manager as independent reviewer, and the controller as the final sign-off on the filing.
Platform Settlement Decomposition in Google Sheets: Zomato, Swiggy, Amazon, and Razorpay Payouts to Line-Level
A working recipe for the Google Sheets workbook that splits every platform settlement an Indian merchant receives — Zomato, Swiggy, Amazon, Razorpay — into the five-part decomposition the Day 4 bank window needs: gross order value, commission, Section 194O TDS, Section 52 TCS, platform fee, and net bank credit. Formulas explained at the level a senior AR analyst or tax executive can lift and adapt, an illustrative Rs 4,80,000 monthly Zomato payout worked end to end, and a public 'Make a Copy' Sheets template linked inline.
TDS Receivable Aging Workbook: Excel Recipe for Form 168 Reconciliation and 180-Day Escalation
TDS receivable is the largest working-capital exposure most Indian finance functions carry and the one least visible until quarter-end. This is the recipe for the Excel workbook that ages the receivable ledger against Form 168 downloads, runs the two-key match across the old Section 194 codes and the new payment codes 1001-1092, computes the 180-day escalation trigger for provisional Section 197 certificates, and generates a mail-merge-ready deductor follow-up list from the exceptions.
The Rs 47,236 Unreconciled Bank Credit: A Decision Tree for Indian Finance Teams
Every practitioner has lived it — a Rs 47,236 credit on the HDFC statement, 45 days old, no candidate invoice, no remittance advice, no counterparty name in the narration. This is the seven-branch decision tree that turns the 8pm chase into a documented sequence with a specific statute at each fork, a worked rupee example per branch, and a Section 37 or Section 41 writeoff protocol for the credit that resolves to nothing.
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.