Choose for review quality, not just matching speed
The right GST reconciliation software should help your practice explain differences, document decisions and prepare defensible client deliverables. A dashboard showing a high match rate is not enough if reviewers cannot trace the underlying data or understand why an invoice was classified as eligible.
For CA firms, tax consultants and accounts heads, the buying decision should cover four essentials: data sources, legal logic, multi-GSTIN operations and client reporting. Use the checklist below during demonstrations and pilot testing.
*Law context: statutory content reviewed as of 21 September 2026. Confirm the applicable position against the notification in force before acting, including relevant effective dates and extensions.*
1. Establish where every number comes from
Check source coverage and traceability
Ask the vendor to reconcile your actual accounting exports, not only a prepared demonstration file. The software should identify the source, GSTIN, return period and import timestamp for each dataset.
Depending on your assignment, useful inputs include:
- Purchase registers and GSTR-2B data for ITC review.
- Sales registers, GSTR-1 and GSTR-3B for outward-supply and liability checks.
- Debit notes, credit notes and amendment records.
- Relevant Invoice Management System records or statuses, where applicable.
- Prior-period exceptions and documented adjustments.
Portal-derived data, accounting records and manually uploaded files should remain distinguishable. Ask whether repeat imports replace earlier versions, create duplicates or preserve a comparison history.
Test messy records
Use invoices with different date formats, leading zeros, punctuation, duplicate references and credit notes. Check whether matching tolerances are configurable and whether each proposed match has an understandable reason.
A useful system separates exact matches, suggested matches, value differences, missing records and duplicates. It should not silently merge uncertain matches or treat a manually accepted match as proof of ITC eligibility.
2. Examine the legal logic behind classifications
Separate reconciliation from entitlement
An invoice appearing in GSTR-2B is an important reconciliation input, but it does not, by itself, establish that ITC can be claimed. Receipt of supplies, documentary support, restrictions, payment-related conditions and applicable time limits also need review.
Section 16 of the CGST Act addresses conditions for taking ITC; section 17 includes restrictions and blocked-credit provisions. Ask how the software supports these checks without presenting every matched invoice as automatically claimable.
Evaluate whether it can record:
- Business-use and blocked-credit assessments.
- Required reversals and subsequent reclaims, where applicable.
- Missing documents and supplier follow-up status.
- Reviewer decisions, supporting evidence and approval dates.
Some checks require information outside GST portal data. The vendor should clearly identify those dependencies.
Ask for dated, explainable references
A legal label should lead to an explanation, not just a coloured warning. Ask whether rule descriptions show their statutory basis, effective date and update history.
Where a treatment depends on a notification, circular or period-specific relaxation, the reference should be identifiable. Confirm who maintains the legal logic and how changes are communicated. Avoid treating software alerts as substitutes for professional judgment.
3. Use a worked example to test the workflow
Assume a client’s purchase register shows ₹1,00,000 of GST recorded as potential ITC for a month. GSTR-2B contains matching entries totalling ₹80,000; entries corresponding to the remaining ₹20,000 are absent.
During review, the team identifies ₹10,000 within the matched ₹80,000 as blocked credit. Assume the remaining ₹70,000 satisfies all applicable eligibility conditions, with no other reversals or adjustments.
The software should help present this clearly:
- Potential ITC recorded in books: ₹1,00,000.
- Matched with GSTR-2B: ₹80,000.
- Blocked credit within matched entries: ₹10,000.
- ITC supported for claim under the stated assumptions: ₹70,000.
- Unmatched amount requiring investigation: ₹20,000.
The unmatched ₹20,000 should not be labelled permanently lost merely because it is absent in this month’s statement. Its treatment requires investigation, applicable legal checks and monitoring of time limits. Ask the vendor to demonstrate supplier follow-up, reviewer notes and carry-forward tracking for that amount.
4. Test multi-GSTIN controls under real workloads
Keep registration-level work separate
A consolidated view is useful, but each GSTIN’s source data, exceptions and approvals must remain separately identifiable. Test clients with several registrations, different accounting formats and different team owners.
Your demonstration should cover:
- GSTIN-wise access permissions and assignment of reviewers.
- Bulk imports with clear success and failure logs.
- Registration-wise reconciliation and completion status.
- Client-level summaries with drill-down to each GSTIN.
- Safeguards against importing one registration’s data into another.
Also check how the system handles amendments and cross-period differences. A carried-forward exception should retain its history rather than reappear as an unexplained new mismatch every month.
Check approval and filing boundaries
If return preparation or filing is included, distinguish importing, editing, approving and filing permissions. Ask who can change reviewed figures, whether changes reopen approval, and how final submission authorisation is recorded.
For any portal connection, clarify the authorisation method, credential handling and data-access boundaries.
5. Inspect what the client actually receives
Client deliverables should explain the issue, its value and the next action. A large spreadsheet of unexplained exceptions simply transfers the review burden to the client.
Request sample outputs showing:
- An executive summary by GSTIN and period.
- Invoice-level exceptions with reasons and action owners.
- Supplier-wise follow-up lists.
- A bridge from book figures to reviewed return figures.
- Open items, decisions and approval evidence.
Check exports for readability and portability. Your practice should be able to retain working papers and retrieve client records if it later changes software.
6. Make the purchase decision through a controlled pilot
Run a pilot using one straightforward client and one complex multi-GSTIN client. Include unresolved prior-period items, amendments and a repeat import. Compare the outputs with your team’s independently reviewed working papers.
Record what worked, what required manual intervention and which explanations were missing. Also review commercial scope, user limits, implementation support, data retention, backup arrangements and exit assistance before committing.
As a practical next step, try the free pre-filing simulator to explore a pre-filing review workflow, then apply the same checklist to shortlisted vendors. Choose GST reconciliation software that makes your team’s decisions traceable—not merely its dashboard look complete.