Classify before you fix
The first task is not to patch every row. It is to know whether the case is a missing invoice, a tax delta, a duplicate, or a GSTIN error.
Guide page
ITC Mismatch Guide for GST Teams
ITC mismatch is one of the highest-intent search terms in the category because the user already knows there is a filing problem. The page should therefore focus on classification, impact, and action instead of generic theory.
This page should explain ITC mismatch in practical terms: what the mismatch means, how it is categorized, what should be fixed immediately, and what can wait for vendor follow-up.
Impact-first review
High-risk mismatches should stay at the top of the queue because filing consequences matter more than spreadsheet neatness.
Resolution logic
The page should tell the user what to do next: verify, normalize, follow up, or hold the claim.
What ITC mismatch means in practice
In practical terms, ITC mismatch means that the books-side view of recoverable credit does not agree with the portal-side view in the current period. That could happen because the vendor filed late, the invoice number was entered differently, or the tax amount changed after a credit note. The page should keep the explanation tied to these operational realities.
- Late vendor filing can shift the invoice into a later period.
- Invoice format differences can hide a valid match.
- Tax deltas and credit notes can change the claim value.
How to resolve the mismatch
The answer depends on the mismatch type. A missing invoice usually needs vendor follow-up. A GSTIN issue often needs normalization or master-data correction. A tax delta can require a review of the original bill, while a duplicate claim risk should be removed before the report is signed off.
- Follow up on missing invoices.
- Normalize identity fields before the next match run.
- Separate recoverable from non-recoverable cases.
- Document the action taken in the report.
How the page should convert
Because the user is already feeling filing pressure, the page should give them a clean next step: open the sample mismatch page or run a demo reconciliation. The copy should be direct and practical, not promotional.
- Use a clear CTA to the demo run.
- Link to sample mismatches and the sample report.
- Show the resolution sequence as a short checklist.
ITC mismatch categories and action
| Category | What it means | Action | Risk |
|---|---|---|---|
| Missing invoice | Books entry absent from 2B | High | Follow up with vendor |
| Tax delta | Amount differs by a small value | Medium | Verify bill or credit note |
| GSTIN mismatch | Identity fields do not line up | High | Normalize master data |
| Duplicate claim | Same invoice appears twice | High | Remove one entry |
| Portal-only row | Invoice exists in 2B but not books | Medium | Investigate booking delay |
Frequently asked questions
What should I do first when I see an ITC mismatch?
Classify the mismatch by type, because the right action depends on whether the problem is missing data, a value delta, or a duplicate entry.
Does every mismatch mean lost credit?
No. Some cases are timing issues or formatting issues that can be resolved before filing.
Why should the page link to sample output?
Because the user is looking for practical recovery, not a definition only. The sample pages prove the workflow.
Next step
Open the app, run a sample reconciliation, and see the report structure.