Matched
Present in both your books and the 2B, with the tax agreeing. This credit is safe to claim, and it is reported as a separate figure so you know exactly how much is.
Upload the GSTR-2B you downloaded from the portal and it is matched against your purchase register invoice by invoice — not total against total. Every invoice is flagged, so an unfiled supplier stops being a surprise you discover in a notice.
कौन-सा credit सुरक्षित है — पहले जानिए।
Your entitlement to input tax credit does not depend on you. It depends on whether your supplier actually filed. A bill can be perfectly genuine, correctly booked and fully paid, and the credit still be unavailable because the other side never uploaded it — and you find out when the department asks, not when you claim.
The usual defence is a spreadsheet: export the 2B, export the purchase register, sort both by invoice number and stare. It falls apart on formatting. One side writes the GSTIN with spaces, the other without. One writes INV/2026/0042 and the other INV-2026-42. The supplier reported a single invoice as three rate lines while you booked it as one. Every one of those becomes a false mismatch you spend an evening chasing.
Finkitaabh matches invoice by invoice and normalises all of that first: GSTIN and invoice-number formatting is standardised, and a single invoice reported across several rate lines is folded back into one before comparison. A configurable rounding tolerance absorbs paise-level differences. What is left on the exception list is a real exception.
Four states, and a number you can actually act on.
Present in both your books and the 2B, with the tax agreeing. This credit is safe to claim, and it is reported as a separate figure so you know exactly how much is.
In both, but the tax differs. Flagged for investigation before you claim, rather than quietly averaging out inside a total.
Booked by you, absent from the portal file — your supplier hasn't filed. This is the credit at risk, and knowing early is what gives you time to chase them.
In the 2B but nowhere in your ledger — a purchase bill you never recorded. Found credit, and a gap in your books closed.
ITC as per books, ITC as per 2B and ITC safely matched, so the difference between what you could claim and what you should claim is a number, not a feeling.
Your books-side ITC in the same shape as the portal file, so your CA can work a genuine side-by-side in Excel.
Same data. Very different night.
| The job | The usual wayHow it tends to go | On FinkitaabhCloud + AI |
|---|---|---|
| Comparing the two files | Two exports, sorted by hand in a spreadsheet | Uploaded and matched invoice by invoice, automatically |
| GSTIN written differently on each side | A mismatch you investigate and then discard | Normalised before comparison — never surfaces |
| One invoice, three rate lines in 2B | Reads as three unmatched entries | Folded back into a single invoice, then matched |
| A two-rupee rounding difference | An exception on the list either way | Absorbed by a tolerance you configure |
| A supplier who hasn't filed | Discovered at a notice, months later | Flagged as "missing in 2B" this month, while you can still chase |
| Knowing what is safe to claim | A judgement call on a total | A reported figure: ITC safely matched |
“The usual way” describes common manual and desktop-era workflows we see in Indian businesses — not any particular product. Every Finkitaabh claim is a capability shipped today.
You download it from the GST portal for the period, the same way you do today, and upload it here. Nothing needs to be re-keyed and nothing has to be requested from us.
Invoice by invoice. A total-versus-total check tells you that something is wrong; it does not tell you which supplier, which bill or how much is at risk. Every invoice gets one of four verdicts, and the exception list is what you work through.
No — that is specifically designed out. GSTIN and invoice-number formatting is normalised, and a single invoice the supplier reported as several rate lines is folded back into one before matching. The rounding tolerance is configurable so paise-level differences are absorbed rather than escalated.
That is a commercial conversation with your supplier, and the value of the report is that you can have it in time. The invoice, the party and the amount at risk are all named, so the follow-up is specific rather than a general request to please file.
The same ITC discipline runs through both. Eligible credit is claimed in 4(A) of the 3B and ineligible credit is disclosed in 4(D) without being set off, and blocked credits under section 17(5) never reach the ITC figure because they are charged to cost when the purchase is booked.
A 30-minute personalised walkthrough with our product specialist — in Hindi or English, whatever you're comfortable with. We'll set up a sample company that looks like your business.