Skip to main content
Resources

Reconciliation and bank-statement-intelligence resources

Everything Terra Insight publishes in one place — long-form research on Indian reconciliation, free interactive calculators, ERP and payment-gateway integration notes, and head-to-head comparisons with adjacent products.

Recent additions

Latest from the insights library

How-To
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.

How-To
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.

How-To
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.

How-To
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.

How-To
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.

How-To
The 6P Cause Taxonomy for Manual Reconciliation: People, Policy, Process, Portal, Period, Partner

Manufacturing's Ishikawa 4M and 6M cause categories were built for a physical production line and collapse six or seven distinct Indian reconciliation causes into a single 'Method' bucket. This method article publishes Terra Insight's 6P replacement — People, Policy, Process, Portal, Period, Partner — each anchored to specific Indian statutory and portal-specific failure surfaces from Section 16(4) November 30 permanent ITC loss and Rule 37A cascading reversal to the IMS 15-day action window and the Form 168 quarterly cadence, with a worked walkthrough showing how the 6P surfaces failure modes a Method-only taxonomy would hide.

How-To
Action Priority for Reconciliation: Why Severity-First Prioritisation Beats "Materiality"

A materiality-first reconciliation register systematically hides Section 16(4) permanent-loss exposures because materiality is a transaction-level concept and reconciliation failure modes are cumulative concepts. The Action Priority table replaces the materiality-cutoff filter and the multiplicative Risk Priority Number with a Severity-first lookup where any Severity 9 or 10 row is High Action Priority regardless of the current-period rupee value. This method article publishes the AP table, contrasts it against the RPN arithmetic that dilutes Severity into a middle-of-the-pack score, and walks through three worked case studies where sub-materiality current periods hid High AP exposures that a materiality filter would have cleared.

How-To
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.

How-To
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.

Talk to the team

If you are evaluating TransactIG for reconciliation or TransactIQ for bank-statement intelligence, we will configure a working demo against your real patterns.