Skip to content

Reconciliation

Reconciliation compares two published sources for a client and period (for example GSTR-2B against the books), explains every row, and raises exceptions for the team to resolve.

A reconciliation run compares two published datasets of a client for a period: a return or statement on one side, the books or another return on the other. Each row is matched, marked as a difference or found on one side only, with an explanation of why. Differences that need action become exceptions with an owner and a status.

Runs read only published data from Data imports and record exactly which versions they used. When newer data is published, the run is marked out of date and can be re-run.

Kinds

KindComparesScopeSwitch
R1GSTR-2B and IMS against the books (Tally or the purchase register)GSTINff.recon.r1
R2GSTR-1 against GSTR-3BGSTINff.recon.r2
R3ITC: GSTR-2B against GSTR-3BGSTINff.recon.r3
R4AIS, TIS and Form 26AS against the booksPANff.recon.r4
R5The firm's own TDS receivable against Form 26ASthe firmff.recon.r5
R6GSTR-1 against the e-invoice registerGSTINff.recon.r6
R7GSTR-1 against the e-way bill registerGSTINff.recon.r7
R8The books against the TDS statementTANff.recon.r8

Each kind is switched on per firm and also needs the plan feature. R5 has its own partners-only page (); R8 is started from a frozen TDS statement in the TDS workspace.

ff.recon.suggestions turns on suggested matches: for documents that do not match exactly, the run proposes a likely partner ("Suggested match"). A suggestion is never applied by itself.

Where to go

Matching rules

The rules and thresholds each kind uses are platform content. A chartered accountant reviews each version, it passes the platform's tests and the platform owner approves it before it is used. They cannot be changed by a firm; the firm can only set its tolerances and a few options.

Last reviewed 27 October 2026