Skip to content

Recon: guide

Help release c4e6d48f22a45602 · Generated 22 November 2026. Online at docs.mycadesk.in/modules/recon/.

Help explains how the software works and is not professional advice; refer to the statute or notification.

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.

Reconciliation mappings for parties and ledger heads

Map a deductor's TAN or a vendor's other GSTIN to the party ledger in the books, and tell the app which books ledgers are TDS receivable, GST input, sales and so on, for one client or as firm defaults.

Books name parties and ledgers in their own words. Mappings tell the reconciliation how to read them. Everyone can see mappings; managers, partners and the owner change them. A saved mapping is used by the next run.

Party mappings (per client)

Choose a client, then Add a party mapping:

  • A deductor's TAN to a party ledger: for AIS, TIS and 26AS against the books (R4).
  • Another GSTIN of a vendor to its ledger: when a vendor bills from a GSTIN the books do not hold.

Give the Party ledger (as in the books), and a Payment nature when the deductor deducts under several sections (for example professional fees or rent), written in lower case with underscores, such as professional_fees.

Ledger heads

Ledger head rules say what a ledger is: TDS receivable, GST input (IGST, CGST, SGST or cess), RCM payable, interest income, rent income, professional receipts, sales, purchases, a blocked-credit review head, or other. Match on the ledger name, its group or its primary group, and give the Name in the books. Rules can be set for one client or as firm defaults for every client.

Suggestions from an R4 run

Opened from an R4 run, the page lists Ledgers with TDS whose deductor is not mapped, with the TDS in the books and the closest deductor in Form 26AS. Map it opens a party mapping filled with the ledger and the suggested TAN for you to check and save.

Example

A synthetic client's books hold a ledger "Rent received - Shop 2" with TDS. The R4 run suggests the closest deductor (TAN shown masked). You add a party mapping from that TAN to the ledger with payment nature rent.

Start a reconciliation and find runs

Choose the client, what to reconcile, the registration and the months; the app uses the latest published data and reuses an identical run if one exists.

Reconciliation (/reconciliation) lists runs, newest first, filterable by kind and status. A tag marks automatic re-runs. Filter by client from a client's page to see only their runs.

Before you start

Upload the client's data for the period under Data imports and wait until it is published: for example the GSTR-2B and the purchase register or a Tally sync for R1 (Upload a client's return, register or statement).

Start a run

Steps

  1. Choose Start a reconciliation (/reconciliation/new).
  2. Find and choose the Client.
  3. Choose What to reconcile. Only kinds switched on for your firm and included in its plan are offered.
  4. Choose the registration (GSTIN or PAN) and the From month and To month.
  5. For R1 choose the Books: Tally books if synced, else the purchase register; or one of them.
  6. Choose Start.

The latest published data of each input is used and the run records exactly which versions. If an identical run already exists (same inputs, rules and settings), it is opened instead of starting a new one.

Run statuses

StatusMeaning
Queued, RunningBeing matched
CompletedDone
Completed with warningsDone; an input was partial or some documents refer to originals that are not among the inputs
FailedThe engine stopped; re-run it
Out of dateNewer data was published, an input was withdrawn or erased, or billing changed; re-run it
InvalidatedAn input was withdrawn or erased

Bulk runs

A bulk run starts one run per client you may run, for up to 2,000 clients. Clients without the needed data are skipped and listed with the reason. Bulk runs queue behind runs people start by hand.

If the run cannot start

MessageSee
The data is not published for that period
The matching rules are not published yet
Not possible for this kind
A value is outside what the firm allows

Work reconciliation exceptions

Filter the exceptions board, assign owners, move exceptions through their statuses, and resolve, waive or reopen them with a reason; or change many at once in Excel.

Reconciliation exceptions (/reconciliation/exceptions) lists every exception your runs have raised. Filter by status, severity, kind of exception, reconciliation and owner, including "Unowned (the owner left)".

Severity

SeverityMeaning
Critical, HighBlocking: these need action before the work is done
LowWorth a look
InformationFor the record

For "Only in the books" exceptions, the firm's setting decides the tax amount at which an exception is high rather than low (Reconciliation settings and matching rules).

Change many at once

Select exceptions (or every open exception on the page), then Assign to a member or Set status.

Statuses

Open, In progress, Waiting for the vendor and Waiting for the client are open statuses. An exception closes as Resolved, Waived or Void (its input was withdrawn). A new exception gets a date it should be done by, from the firm's setting.

On an exception

The page shows the reconciliation, the Evidence (the documents on each side) and the History of every change.

  • Update the exception: status, owner, target date and a note.
  • Resolve the exception: choose how it was resolved (corrected in the books, the vendor amended their return, ITC reversed, or difference accepted). Accepting a difference needs a note of at least 20 characters.
  • Waive the exception: give the reason (at least 20 characters). Only managers and above can waive.
  • Reopen the exception after it was resolved or waived, with a reason of at least 20 characters.

Warning

Accepting a difference on a high or critical exception counts as a waiver: only a manager or above can do it, you confirm it is you (Step-up), and the owner of the exception cannot approve their own (unless the firm is set up as a solo practitioner).

Work in Excel

From a run, Download for Excel, change the status, owner, resolution or note in the workbook, and upload it back. The app lists each row's result before anything changes; rows changed by someone since your download are refused. Waivers of blocking exceptions in the workbook ask you to confirm it is you before they are applied.

Read a reconciliation run

A run's summary, the return tables compared, every row with its match status and explanation, the exceptions it raised, re-running, and the vendor follow-up list.

A run page has these parts. Its title is the kind, such as "R1 · GSTR-2B and IMS against the books".

Summary

Counts of rows by status and the totals per tax head on each side. Warnings say when an input was partial or a document refers to an original that is not among the inputs.

Return tables compared

For kinds that compare returns (R2, R3), each table line of one return against the other, with "Within tolerance" where the difference is inside the firm's tolerance. Indicators point to risks to look at, such as liability in GSTR-1 exceeding GSTR-3B, or ITC claimed exceeding GSTR-2B, beyond the threshold in the rules.

Rows

Filter with Show. Each row is one of:

StatusMeaning
MatchedSame document on both sides, amounts within tolerance
Matched with differences in formatSame document; number or date written differently
Matched by handA person matched it
Suggested matchA likely match proposed for review (when suggestions are on)
Amounts differSame document, amounts beyond tolerance
Only in the returnOn the portal side only
Only in the booksIn the books only
ExcludedLeft out by a person

For R1 the ITC column shows the credit status of each GSTR-2B document (). Explain shows why the row got its result: the rule that matched, the document numbers as normalised, the differences and the source records.

Exceptions from this run

Rows that need action raise exceptions, listed here and on the exceptions board (Work reconciliation exceptions). You can also work them in Excel from here.

Re-run

Re-run starts a new run on the latest data. It is highlighted when the run is out of date or failed. If nothing changed, the same run is shown. Manual matches and exclusions are carried into the new run where the same documents are present.

Vendor follow-up list (R1)

Build the vendor follow-up list collects the open exceptions vendors must act on (only in the books, amounts differ, ITC blocked in GSTR-2B), grouped by vendor. When it is ready, Download the list (Excel) and, after sending it, Mark as sent. Earlier lists are under Follow-up lists of this run.

R4 mappings

An R4 run links to Reconciliation mappings for parties and ledger heads with suggestions for ledgers with TDS whose deductor is not mapped.

Reconciliation settings and matching rules

The firm's reconciliation settings (tolerances, document-number tokens, default period, automatic re-runs, severity, exception dates) and the list of published matching rules.

Reconciliation settings and rules (/reconciliation/settings) shows the firm's settings and the matching rules in use. Partners, the owner and firm admins change the settings; everyone can read them. Each change can carry a reason, which is kept in the audit log. New runs use the new values; each run records the values it used.

Firm settings

SettingShown asDefaultRange
recon.tolerance.head_abs_inrTolerance per tax head (₹)1.000 to 100
recon.tolerance.taxable_pctTolerance on taxable value (as a percentage of the GSTR-2B value)00 to 1
recon.doc_number.extra_tokensExtra document-number tokens to ignorenoneup to 50 words
recon.default_period_rangeDefault period for a new runfinancial year to datemonth, quarter or financial year to date
recon.auto_rerun_on_supersedeRe-run automatically when newer data is publishedonon or off
recon.severity.high_tax_inrTax at risk that makes an exception high (₹)10,000.000 to 10,00,000
recon.exception.default_due_daysDays given to a new exception (its target date)51 to 30
recon.metering.enabled(not shown)onon or off

Notes:

  • Tolerances: two amounts within the tolerance count as matched.
  • Extra tokens are prefixes or suffixes your clients add to document numbers (for example a branch code) that matching should ignore, in addition to those in the rules. Separate them with commas.
  • Automatic re-run: when a newer version of an input is published, the latest run of that scope is re-run by itself and tagged "Automatic re-run".
  • Severity: an "Only in the books" exception with tax at or above this amount is high, else low.
  • Metering records the use of each completed run for future pricing; nothing is charged.

Matching rules

Matching rules lists the rule set of each kind, with its version and whether it is published. "Not published yet (awaiting CA review and approval)" means runs of that kind cannot start yet (). Thresholds marked "Awaiting CA confirmation" are still being checked. Rules cannot be changed here.