B2B · B2BA · CDNR · CDNRA
Invoice and note records used by the current reconciliation engine.
Match the purchase register, isolate the exceptions, preserve the evidence and let the reviewer own the final position—across every client and period.
The operating idea
GSTRecon360 keeps the source document, machine suggestion, human decision and final working as separate layers. That makes a result reviewable today and reproducible later.
The control room
One period view keeps Books and GSTR-2B fields together, makes differences legible, and leaves the reviewer’s trail intact.
Machine outcome stays visible. A confirmation changes the reviewed result, not the original suggestion.
Money is stored in paise. Tolerance is explicit, so totals do not drift through floating-point maths.
Missing is not automatically claimable. Eligibility and statutory adjustments remain separate review steps.
The review chain
The workflow is deliberately opinionated about who prepares, who decides and when a period becomes final.
Start with sample dataUpload the GST portal export and the purchase register for the selected client and return period.
GSTIN, period, file structure, supported sections and source counts are checked before a result is accepted.
Review probable pairs, missing documents, tax deltas and source evidence without overwriting the machine suggestion.
Confirm, reject or reopen with a reason. Final reports come from a versioned snapshot, not a moving screen.
What the beta covers
Invoice and note records used by the current reconciliation engine.
Recognised sections are labelled so totals are not silently discarded.
The beta surfaces evidence; it does not make opaque tax decisions.
Direct GSTN/IMS pull and push, automated filing, and opaque AI tax decisions are not part of this public beta.
Read the readiness notes ↗Practice-sized pricing
Straight answers
The product is intentionally clear about the line between matching software and professional tax judgment.
It is tax on potentially claimable purchase-register documents that are missing from GSTR-2B. Blocked or ineligible credit, RCM, reversals, POS restrictions and deferred items should be reviewed separately; the number is not a filing instruction.
No. It organises matching evidence, differences and review decisions. The preparer and reviewer remain responsible for eligibility, adjustments and the final GSTR-3B working.
No. The current workflow uses portal-downloaded GSTR-2B Excel or supported JSON files. It does not ask for GST portal passwords or OTPs.
Yes. The workspace is organised by client GSTIN, return period and reconciliation run. Re-uploads create history rather than replacing an earlier working.
Not in the public beta. IMS actions are organised for review, but portal pull/push will be introduced only through an authorised GSP and explicit client consent.
Your next client period
Start free with one client. No card and no GST portal credentials.