Absolute Match
184.20 Cr · 2,10,412 lines
GSTIN, invoice number, date and tax agree. Credit that can be claimed.
Identify. Classify. Reach the vendor. Reduce the gap.
GSTITC matches the Purchase Register to GST ITC (GSTR-2A) across 100+ combinations, classifies every line, then works with vendors until Mismatch and No Match come down.
100+ matching combinations4 outcomes, every line placedMillions of lines already run
Data intake
How the books get in.
Today, intake is a structured file handoff with your GST cell, Purchase Register and GSTR-2A / ITC extracts as Excel, CSV, or an equivalent flat file. There is no self-serve public upload and no live SAP or Oracle connector yet. ERP connectors are on the roadmap; we will say so when they exist rather than imply they do now.
We map GSTIN, vendor GSTIN, invoice number, date, invoice type, taxable value, tax rate and tax. You do not need a GSTITC-branded template if those columns can be identified. Cleanup of obvious field variants is part of ingest; we do not ask you to pre-match the register to 2A.
How that data is hosted after ingest, on our India tenancy or in a database you bring, is on the Security page.
Why 100+ combinations
GSTIN, PAN, invoice number, date, invoice type, taxable value, tax rate and total tax can fail to agree in many different ways. The engine runs those combinations so a near-match is not treated as a mismatch, and a true No Match is not mixed in with either.
Running fewer combinations means more lines fall into Mismatch or No Match than they should, and that credit sits at risk longer than necessary.
Match dimensions
GSTINPANInvoice numberInvoice dateInvoice typeTaxable valueTax rateTotal tax
Illustrative sample pack
2,41,806 purchase lines · 2,28,441 GSTR-2A lines · 22 GSTINs
Four outcomes
Every line is placed. Sample period Jul 2026: ₹ 211.43 Cr classified across 2,41,806 purchase lines.
Potential Match
12.64 Cr · 8,904 lines
A near-match on GSTIN, invoice number, date or tax. Review before you treat it as safe.
Operationally: your GST cell reviews it before it is treated as claimable. It is not mailed to vendors. If review shows a true disagreement, it moves to Mismatch and into the queue. If the fields agree, it can be treated as Absolute Match.
Mismatch
8.41 Cr · 12,318 lines
A pair exists on both sides, but GSTIN, invoice number, date or tax still disagrees. The vendor needs to correct it.
No Match
6.18 Cr · 10,172 lines
In books, not in 2A, the vendor has not filed. Or in 2A, not in books, review and book if eligible.
What the operating layer does
Mismatch and No Match (in books, not in 2A) need the vendor. No Match that is in 2A, not in books, needs finance. Potential Match stays with your GST cell until someone decides it is safe or it belongs on the queue. Software tells you which is which. The operating layer reaches vendors by email under your name, tracks rectification, and writes the result back into the next cycle.
- 1
Identify exceptions
After classification, every Mismatch and No Match line is surfaced as an exception. The engine tells you exactly which field disagrees, or that the invoice has no counterpart at all.
- 2
Reach vendors
Email from your domain, Microsoft 365, Google Workspace, or your SMTP, not from a GSTITC address. Messages are tracked per vendor and per invoice. Replies land in your inbox and are tied back to the exception.
- 3
Write back to the next cycle
Rectified invoices enter the following period's match run. The exception count comes down period after period, not just in a one-time clean-up.
Action queue · Jul 2026
₹ 14.59 Cr
in Mismatch and No Match
Vendors in queue312
Exception lines22,490
Mismatch12,318 lines
No Match10,172 lines
Illustrative sample period, not a named client result.
The objective is explicit.
Reduce Mismatch. Reduce No Match. Claim the ITC that belongs to the enterprise, period after period, not just once.
How we work with you
After you say yes.
Kickoff
A named GST-cell contact, your GSTIN list, and structured Purchase Register plus GSTR-2A / ITC extracts for the first period. IT and InfoSec join when there is a security review, a bring-your-own database, or outreach from your mailbox.
First cycle
We map fields, run the engine, classify every line, and stand up the exception queue. Duration is scoped at kickoff, and it depends on GSTIN count, extract quality, and whether InfoSec review is in the path. We will not publish a fake week-count.
Who is in the room
Your GST cell owns the operating rhythm. AP / shared services when the register has to be extracted. IT / InfoSec for review and optional connectors. On our side: a dedicated engagement contact, the matching run, and the people who work the vendor queue.
Every period after
The same ingest → match → classify → close loop, on the GST filing calendar. Rectified invoices enter the next run. Success is Mismatch and No Match coming down, not a one-time clean-up.
Ready to discuss your books?
We work with large-enterprise finance departments. Gurugram-based, Niviverse Technologies Private Limited.