Finance and tax heads choose GST reconciliation software from feature lists and demos on vendor data, then discover at month-end that probable matches are unexplained, IMS actions carry no user trail and amendments double-count.
Decide the kind of tool first, check it against twelve streams of work, then run twelve scenario files built from your own months and score each tool on gates and weighted streams.
A stream-by-stream must-have table, twelve masked scenario files with expected results, a data-access review covering consent and credentials, and a score sheet with gates signed off by the tax head.
A shortlist of tools that tie every bucket to the purchase register and GSTR-2B totals on your own data, with logged IMS actions and a supplier follow-up list, filed as evaluation evidence.
GST reconciliation software in India is easy to demonstrate and hard to judge. Every product looks clean on the vendor’s sample data. The differences show on your own months: when an invoice number carries a prefix, when a supplier amends a credit note two months later, when one of four GSTIN credentials expires the night before GSTR-3B.
This guide is written for the finance head or tax head running GST across several GSTINs with an ERP. It gives you a way to choose the kind of tool, a stream-by-stream checklist, twelve scenario files to build from your own data, and a worked month showing what a good tool should display on the day after GSTR-2B is generated. No product is named or ranked. Every rule cited comes from GSTN, CBIC or GST Council sources, checked on 18 November 2026.
All the tables below are also packaged as a GST reconciliation software evaluation kit (Excel score sheet, scenario templates and a vendor-response log).
What kind of GST reconciliation tool are you buying?
Decide the kind of tool before you compare products. A shortlist that mixes an ERP add-on, a filing suite and a spreadsheet will be compared on the wrong things. The five kinds below differ in where the data lives, what they are strongest at and what you should test hardest.
| Kind of tool | Typical strength | What to test hardest | Typical fit |
|---|---|---|---|
| ERP-native GST module | Same data as the books, no export step | Portal data refresh, IMS actions, multi-GSTIN consolidation, supplier follow-up | Single entity or ERP-centric teams |
| GST return-filing suite | Filing and reconciliation in one place | Depth of GSTR-2B and IMS matching compared with filing features | Teams that file in-house |
| Enterprise GST platform (often with ERP connectors and e-invoicing) | Volume, many GSTINs, integrations | Implementation effort, speed of rule changes, audit trail, supplier workflow | Groups with several GSTINs and ERPs |
| Specialist reconciliation tool (GSTR-2B, IMS, ITC at risk) | Matching depth and supplier follow-up | Connection to the books and to filing, ownership of data | Teams with ITC leakage and many suppliers |
| Spreadsheet or macro workbook | Control and transparency | IMS trail, volume, key-person risk | Low volume, few GSTINs |
Two questions settle most of the choice. How many GSTINs and purchase invoices do you process each month? And does your team file returns itself, or does a CA firm file for you? A practice running many client GSTINs has a different problem, covered in our CA firm GST reconciliation tool guide. If you are weighing GST tools against broader platforms, see GST reconciliation software for the full scope of the category.
What must GST reconciliation software do, stream by stream?
A GST reconciliation tool must cover twelve streams of work, from fetching portal data to producing an audit pack. Use this table as the spine of your evaluation: each row says what the tool must do, how to test it and what a good result looks like.
| Stream | The tool must | Test it with | Good looks like |
|---|---|---|---|
| Get portal data | Pull or accept GSTR-2B (and GSTR-2A where needed), IMS records, filed GSTR-1 and GSTR-3B for every GSTIN | Refresh two GSTINs, then stop one credential | Status per GSTIN, retry, no silent gap; credentials held as agreed in writing |
| Match purchase register to GSTR-2B | Match at invoice level on supplier GSTIN, number, date and value, with a stated tolerance | Files T1 to T6 | Exact, probable, value-mismatch, missing and unexpected buckets that add up to both totals |
| Work the IMS | Record accept, reject and pending per invoice, with bulk actions and a user trail; show the effect on the next GSTR-2B | File T7 | Every action logged by user and time; effect on ITC shown before you commit |
| Apply ITC conditions | Track section 16(2)(aa), the section 16(4) time limit, the 180-day payment rule, blocked credits, reverse charge and imports | Files T6, T8, T9 | Age and countdown per invoice; reversal proposed, not posted silently |
| Pre-filing guard | Warn before GSTR-3B if ITC claimed exceeds GSTR-2B, and before filing if liability gaps risk DRC-01B or DRC-01C | A draft GSTR-3B with ITC above GSTR-2B | A warning with the amount and the invoices responsible, before filing |
| Reconcile outward supplies | Compare sales register, e-invoices, GSTR-1 and GSTR-1A with GSTR-3B liability, including amendments and credit notes | File T11 | Ties to the GSTR-3B liability, each break with a reason |
| Annual return | Prepare the books-versus-returns comparison for GSTR-9 and GSTR-9C | One full year of one GSTIN | Table-wise differences with sources |
| Supplier follow-up | List missing invoices by supplier, send and track requests | The “not in GSTR-2B” bucket | One list per supplier with status and age |
| Many GSTINs | Consolidate by PAN and state; handle branch transfers | Two GSTINs sharing suppliers | One view with GSTIN-level drill-down |
| Notices and audit | Produce the evidence pack for a mismatch notice or audit query | One past notice | Source files, matches, user actions and dates in one export |
| Controls | Roles, maker-checker for IMS actions and rule changes, period lock | A junior user’s login | Actions blocked or routed for approval as designed |
| Operations | Run a normal month and three times that volume | Time both runs | Time stated; failures handled visibly |
The multi-GSTIN row deserves extra weight for groups. How a central team and branch teams share IMS decisions is a design choice in itself; our multi-GSTIN IMS workflow article sets out the operating models.
How do you test GST reconciliation software on your own data?
Give every shortlisted vendor the same twelve scenario files, built from your own closed months and masked where needed, with the expected result written down before the run. A tool that gets the answer right on your data is worth more than one that looks good on its own sample.
Twelve scenario files
| ID | Scenario | What to check |
|---|---|---|
| T1 | A normal month for one GSTIN | Totals tie to the purchase register and to GSTR-2B |
| T2 | Invoice numbers written differently (prefix, leading zeros, slashes, spaces) | Probable matches shown with the reason, not forced |
| T3 | Value within tolerance versus a real mismatch (₹1 rounding versus a ₹590 tax difference) | Tolerance visible and approved; the ₹590 stays a mismatch |
| T4 | Credit notes and amendments reported in a later month | The amendment replaces the original, not adds to it |
| T5 | Supplier GSTIN typed wrongly, or a second GSTIN of the same PAN | Flagged with the PAN link; not matched blindly |
| T6 | Supplier files late; invoice appears in a later GSTR-2B | Carried forward with age and a section 16(4) countdown |
| T7 | A hundred IMS records: accept, reject and pending, a credit note kept pending, one accepted with a partial ITC reduction declared, a remark on a rejection, and a Bill of Entry record | Effect on the next GSTR-2B, pending age against the limit, complete user trail |
| T8 | Reverse-charge and import entries | Not reported as “missing in GSTR-2B” |
| T9 | Invoices unpaid beyond 180 days (rule 37) and a supplier whose GSTR-3B is still unfiled at the cut-off (rule 37A) | Reversal proposed with payment evidence; re-availment tracked |
| T10 | The same supplier billing different GSTINs of yours | Shown per GSTIN and at PAN level |
| T11 | Sales register against GSTR-1 and GSTR-3B, with one amendment and one credit note | Ties to the liability with each break explained |
| T12 | A month where the vendor’s own numbers did not tie | An anonymised example and how the tool explained it |
For the monthly workflow these files are drawn from, see GSTR-2B versus purchase register reconciliation.
Tolerances and probable matches
Ask where the matching tolerance is set, who can change it and whether a change is logged. A ₹1 rounding difference is usually safe to accept; a ₹590 tax difference is not. The tool should show probable matches (T2) as a separate bucket with the reason, such as “invoice number differs only by prefix”, and leave the decision to your team. A tool that silently folds probable matches into exact matches inflates its match rate and hides the cases you most need to see.
A month that did not tie
Every reconciliation tool meets months that do not tie. Ask the vendor to show one, anonymised: what the gap was, how the tool displayed it and how the customer resolved it. A vendor that cannot show such a month either has not looked or will not say.
How should the tool get GST portal data?
There are three routes for portal data into a reconciliation tool: manual download and upload, a connection through an authorised GST Suvidha Provider (GSP) using API access, or an ERP connector. Each has a different consent model, refresh frequency and failure mode.
| Route | What it needs | Watch for |
|---|---|---|
| Download from the portal and upload | A person each month for each GSTIN | Missed months, version control, no daily IMS view |
| Tool connects through an authorised GSP using API access | Taxpayer consent and credentials, usually with an OTP step | Who holds credentials, how consent is revoked, refresh limits, error messages |
| ERP connector pulls portal data into the books | ERP configuration | Which ERP version and which GSTINs, where mapping lives, who owns the data |
Application Service Providers reach GST data through GSTN-empanelled GSPs with OTP-based taxpayer consent. A GSTN advisory of 29 September 2025 describes a “Manage API Access” screen under My Profile where a taxpayer can see which providers hold active consent, revoke it and view access logs. Ask every vendor which GSP it uses, how long consent lasts and what the tool shows when access lapses. Not every GSP is a reconciliation tool, and not every reconciliation tool is a GSP.
What should you see on the day after GSTR-2B is generated?
GSTR-2B is generated on the 14th of the following month (for quarterly QRMP filers, on the 14th after the quarter). On the 15th, a good tool should show every purchase invoice in exactly one bucket, with the buckets adding up to the register and to GSTR-2B. The worked month below is illustrative.
Illustrative month: four GSTINs, 1,500 purchase invoices, average ITC ₹7,800 per invoice, ITC in the books ₹1,17,00,000.
| Bucket (books side) | Invoices | ITC in books | Share of invoices |
|---|---|---|---|
| Exact match | 1,320 | ₹1,02,96,000 | 88.0 percent |
| Probable match (formatting differences) | 78 | ₹6,08,400 | 5.2 percent |
| Value mismatch | 24 | ₹1,87,200 (GSTR-2B shows ₹1,76,500; difference ₹10,700) | 1.6 percent |
| Not in GSTR-2B | 58 (from 41 suppliers) | ₹4,52,400 at risk | 3.9 percent |
| Not expected in GSTR-2B (reverse charge, imports, ISD) | 20 | ₹1,56,000 | 1.3 percent |
| Total | 1,500 | ₹1,17,00,000 | 100 percent |
GSTR-2B also holds 20 invoices worth ₹1,63,000 of tax that are not in the books: each must be booked or rejected. The differences between tools show at three points:
- Whether the 78 probable matches are explained with a reason, or quietly counted as exact.
- Whether the 58 missing invoices, ₹4,52,400 of ITC, become a follow-up list for 41 suppliers with age and status.
- Whether IMS decisions on the 1,442 records in GSTR-2B (1,320 + 78 + 24 matched to the books, plus the 20 not yet booked) are logged by user and time.
The ₹10,700 value gap across 24 invoices is small against ₹1.17 crore, but each one is a supplier conversation, and the tool should list them by supplier with the invoice-level difference.
How should IMS actions be recorded and controlled?
IMS lets a recipient accept, reject or keep pending each inward record that a supplier saves or files in GSTR-1, GSTR-1A or IFF. The tool you buy should record every action by user and time, allow bulk actions with review, and show the effect on the next GSTR-2B before anyone commits.
What the official rules say
Per the GSTN IMS FAQ, IMS went live on the portal from 1 October 2024. Records with no action are deemed accepted when GSTR-2B is generated; rejected records do not flow to GSTR-3B; pending records stay out of GSTR-2B until acted on. From the October 2025 tax period, GSTN added the option to keep certain credit notes pending for a limited period, to declare how much ITC is reduced when accepting a credit note, to add remarks on reject and pending, and an Import of Goods section for Bills of Entry with accept or pending only. Reverse-charge records do not go through IMS actions. For the portal steps, see accept, reject and pending in the IMS dashboard.
Bulk actions and the trail
Bulk acceptance of a thousand records is a convenience and a risk. Test that the tool shows which records a bulk action touched, who approved it and whether one record can be reversed without undoing the batch.
Maker-checker
A rejection removes ITC from GSTR-2B. Ask whether a junior user can reject without approval, whether rejection reasons are captured and whether the tool can lock a period after GSTR-3B is filed.
What is changing
The 57th GST Council, meeting on 8 October 2026, recommended a new sub-rule (6A) in rule 60 to give IMS a rule-level basis, including a limit on how long credit notes can stay pending; sub-rules (1A) and (1B) in rule 61 to align GSTR-3B liability with GSTR-1 and GSTR-3B ITC with GSTR-2B; rule 86C (an Electronic Credit Reversal and Reclaim Statement); and rule 86D (an Electronic Statement of tax paid and ITC claimed on reverse charge). The Council recommended the alternate mechanism from the return of April 2027 and a time-bound public consultation. These are recommendations, not notified rules. Ask every vendor how it will handle them once notified.
Which ITC rules should the tool track for you?
The tool should track the conditions that decide whether ITC can be claimed or must be reversed, and show each one per invoice before filing, not after. The table lists the rules, what the tool should show and the source.
| Rule | What it says (summary) | What the tool should show |
|---|---|---|
| Section 16(2)(aa), CGST Act | ITC only if the supplier has reported the invoice and it is communicated to you (in practice, shown in GSTR-2B); in force since 1 January 2022 | ”Not in GSTR-2B” bucket with age |
| Section 16(2)(ba), CGST Act | ITC only where the credit communicated to you has not been restricted; in force since 1 October 2022 | Restricted records flagged separately |
| Section 16(4), CGST Act | No ITC after 30 November following the end of the financial year, or the annual return date if earlier | Countdown per open invoice |
| Rule 37, CGST Rules | ITC reversed with interest if the supplier is not paid within 180 days of the invoice; re-availed on payment | Unpaid-age per invoice, reversal proposed, re-availment tracked |
| Rule 37A, CGST Rules | ITC reversed where the supplier’s GSTR-3B is still unfiled by 30 September after the year end; reversal by 30 November | Supplier filing status at the cut-off |
| Section 17(5), CGST Act | Blocked credits (for example, certain motor vehicles, food and beverages, club memberships) | Blocked items excluded from the claim with the reason |
| Rules 88C and 88D, CGST Rules | DRC-01B for liability gaps between GSTR-1 and GSTR-3B, DRC-01C for ITC claimed above GSTR-2B, at thresholds set on Council recommendation | Pre-filing warning with the amount |
Our Section 16 ITC under the IMS regime article covers these conditions in depth. Thresholds for DRC-01B and DRC-01C are not stated in the rules themselves, so ask the vendor how its warning threshold is set and kept current.
Twenty questions for any vendor, and the red flags
Ask every vendor the same questions in writing, record the answers in a response log, and compare them side by side. Answers given only in a demo are hard to hold anyone to.
Data. 1. Which portal data do you fetch, for which forms? 2. How often? 3. What happens when a credential or consent expires? 4. Who holds the credentials?
Matching. 5. What are the match keys? 6. What are the tolerances and where are they set? 7. Show a probable match and its reason. 8. How do you handle amendments that arrive months later?
IMS. 9. Which IMS actions can I take in bulk? 10. Where is the user trail? 11. Can I see the effect on GSTR-2B before committing?
Rules. 12. How quickly do you ship a rule change, and how do I see what changed? 13. How will you handle the 57th Council changes if notified?
Workflow. 14. Can I get a per-supplier list with status and age? 15. Can suppliers be sent requests from the tool, and are responses tracked?
Audit. 16. What is in the export for an auditor or a notice? 17. Can I see who accepted or rejected each record, and when?
Security. 18. Where is data stored, and who are the sub-processors? 19. How is access controlled and reviewed?
Operations. 20. What did you test at three times normal volume, and how long did it take?
Red flags. End the evaluation, or at least pause it, if a tool:
- matches only on totals, not invoices;
- reconciles only against GSTR-2A;
- shows no IMS actions or no user trail;
- quotes a match rate with no definition of what counts as a match;
- cannot show a month that did not tie;
- cannot export who accepted or rejected what;
- asks for portal credentials without written consent terms.
How should you score GST reconciliation software and decide?
Score in two steps. First apply gates: a tool that fails any gate is out, whatever its total. Then weight the remaining streams to match your business. The weights below are examples to adapt, not an industry standard.
Gates (pass or fail): buckets add up to both totals on T1; the ₹590 mismatch in T3 stays a mismatch; amendments in T4 replace rather than add; IMS actions in T7 are logged by user; data storage and sub-processors are disclosed in writing.
| Stream | Single GSTIN, ERP-centric | Several GSTINs, central tax team | High-volume retail, many suppliers |
|---|---|---|---|
| Purchase register to GSTR-2B matching | 25 | 20 | 20 |
| IMS actions and controls | 15 | 20 | 20 |
| ITC conditions and pre-filing guard | 20 | 15 | 15 |
| Outward reconciliation | 15 | 10 | 10 |
| Supplier follow-up | 10 | 10 | 20 |
| Many GSTINs | 0 | 15 | 5 |
| Audit export and notices | 15 | 10 | 10 |
| Total | 100 | 100 | 100 |
Score each stream 0 to 5 from the scenario runs, multiply by the weight and divide by 5. A score sheet that does this, with gates and weights you can edit, is in the evaluation kit. For a broader view across reconciliation categories, see comparing reconciliation platforms for India.
Where Terra Insight fits today
GST outward reconciliation (GSTR-1 and GSTR-3B) leads the TransactIG GST roadmap, and GST inward reconciliation (GSTR-2A, GSTR-2B, ITC and IMS) is on the roadmap. Delivered today are TDS reconciliation and bank-to-books matching, with an exception queue, exports and presets; use this guide’s method on any GST tool you evaluate.
- ▸ GSTN, FAQs on Invoice Management System (IMS)
- ▸ GSTN, FAQ on changes in IMS from the October 2025 tax period
- ▸ GSTN, FAQs on viewing Form GSTR-2B
- ▸ GST Council, recommendations of the 57th meeting (PIB, 8 October 2026)
- ▸ CBIC, Notification No. 26/2022-Central Tax (rule 37 amended, rule 37A inserted)
- ▸ CBIC, Notification No. 38/2023-Central Tax (rule 88D and FORM GST DRC-01C)
- ▸ GSTN, Taxpayer advisory on transparency of data access via GSP and ASP (29 September 2025)