Reconciliation Process Design
A rigorous failure-anchored framework for designing reconciliation processes that catch failures systematically — anchored to Indian reconciliation consequences (Section 16(4), Section 200A, DRC-01B, CARO 2020) — for finance controllers, ICFR consultants, and CA firms.
Most reconciliation controls at Indian enterprises are procedural checklists — "run the report, tick the box, sign off." A checklist confirms that a task was performed. It does not confirm that the task caught the failure it was designed to catch. The distinction is what separates a reconciliation process that a statutory auditor signs off from one that carries a material weakness finding under Section 143(3)(i) of the Companies Act 2013. Reconciliation process design is the discipline of writing down every way each function can silently produce a wrong result, ranking failures by their true impact on the customer, and confirming that a specific control catches each one.
This cluster sits above the substantive TDS, GST, NACH, Banking and Platform Settlements clusters as a meta-layer. Where those clusters teach what to reconcile against which statute, this cluster teaches how to design the process so that Section 16(4) permanent losses do not accumulate silently, Section 200A notices do not surprise the finance function, and DRC-01B auto-notices are caught in the sequence rather than in a firefight. Every High-Priority failure mode surfaced by the framework maps to a specific existing article on the site for the substantive mechanic, a specific manual detection technique the finance team can run, and a natural upgrade path to TransactIG for the failure modes where manual detection has topped out.
Articles in this cluster present Terra Insight's own reconciliation process design framework — the 6P cause taxonomy (People / Policy / Process / Portal / Period / Partner), the 12-class failure mode taxonomy, the Action Priority table with Severity-first prioritisation, and the anchored Severity-Occurrence-Detection scale anchored to Indian reconciliation consequences. The pillar walks a worked example (TDS receivable against Form 26AS / Form 168) through all seven steps of the framework end-to-end.
GSTR-2B ITC Reconciliation Failure Modes: How to Prevent Section 16(4) Permanent Losses
Section 16(4) of the CGST Act permanently forfeits any Input Tax Credit not claimed by November 30 of the following financial year, with no rectification, no condonation, and no recovery mechanism in Indian tax law. This is the only Severity-10 anchor in the reconciliation process design framework — and it makes GSTR-2B ITC reconciliation the single highest-severity function on the Indian finance calendar. Fourteen failure modes, twelve failure classes, and the point at which the at-risk ITC queue outgrows a manual detection layer.
The Reconciliation Control Plan: A One-Page Template for Every Stream
The reconciliation control plan is the output document of the reconciliation process design method. This is the one-page template — function, failure mode, cause, Severity, Occurrence, Detection, Action Priority, prevention control, detection control, owner, cadence, evidence — with a worked example for each of the four core Indian reconciliation streams.
Reconciliation Failure Analysis: A Process Design Method for Indian Finance Teams
Most reconciliation controls at Indian enterprises are checklists that confirm a task was done — not analyses that confirm the task caught the failure it was designed to catch. This pillar sets out Terra Insight's reconciliation process design method — a seven-step discipline that installs failure analysis on top of the four reconciliation streams every Indian finance team runs, with a severity, occurrence, and detection scale anchored to Indian statutory consequences from Section 16(4) permanent ITC loss to CARO 2020 material weakness.
TDS Reconciliation Failure Modes Against Form 26AS and Form 168: Every Failure Mode That Turns Into a Section 200A Notice
A quarterly TDS receivable reconciliation against Form 26AS and the Form 168 annual statement can fail fourteen different ways under the Income-tax Act 2025 cross-era regime. Each failure mode maps to a class in the 12-class taxonomy, a cause in the 6P framework, and an Action Priority anchored to the Section 200A demand-notice consequence.
See how TransactIG installs the detection layer manual processes cannot
The framework identifies High-Priority failure modes where manual detection is not economically viable — typically the at-risk ITC queue across 200+ vendors under the Section 16(4) November 30 clock, cross-era TDS matching under the Income Tax Act 2025, and NACH batch disaggregation with return code classification. TransactIG installs the continuous detection layer these High-AP failure modes demand — the at-risk queue that manual controls cannot economically maintain.