Who this checklist is for
This checklist is for CFOs, Financial Controllers, and AP Managers at Indian mid-market companies who need a fast, honest read on whether their GST reconciliation workflow will hold up under GST 2.0 enforcement. It is not a compliance certification — it is a diagnostic. Run it against your current process before your next audit or ITC reconciliation cycle finds the gaps for you.
Why GST reconciliation is the highest-risk AP task in India
Most AP teams still treat GST reconciliation as a month-end cleanup step: match GSTR-2B, chase vendors on mismatches, write off what can't be resolved before the return deadline. That approach was survivable when enforcement was periodic. It is not survivable under GST 2.0, where GSTN's ADVAIT platform runs continuous, AI-driven supplier risk scoring and a hard 30-day IRN reporting window blocks invoice registration outright. An invoice that looks clean at receipt — valid IRN, correct GSTIN, matching PO — can still fail at reconciliation because the risk flag or the filing gap exists upstream, at the GSTN level, invisible to your ERP. The checks below cover the four places that failure actually originates.
The four-area readiness check
1. GSTR-2B matching
- Invoices are matched against GSTR-2B before payment release, not only at month-end.
- There is a defined value threshold above which GSTR-2B match confirmation is mandatory before approval.
- Mismatches are routed to a named owner with an SLA, not held in an undefined exception queue.
- Your team can see, without a manual pull, which unpaid invoices are currently blocked by a 2B mismatch.
If you scored No on any item: GSTR-2B mismatches are becoming payment blockers, not cleanup tasks, once AP is automated. An invoice can sit unpaid indefinitely if no resolution workflow exists — and for MSME vendors under the Section 43B(h) 45-day rule, a blocked invoice that crosses the deadline creates a tax disallowance risk for your company, not the vendor.
2. IRN validation
- IRN status is checked when the invoice enters the AP workflow — before PO matching, not at GSTR-2B prep.
- Validation confirms the IRN was actually issued by the IRP for that invoice (an API call), not just that an IRN field is populated.
- Vendors above the ₹5 Cr e-invoicing threshold are flagged in your vendor master so validation triggers automatically.
- A missing or unverifiable IRN blocks the invoice at intake, with a specific rejection reason, rather than routing to approval.
If you scored No on any item: A populated IRN field is not proof of validity. A fabricated or reused IRN passes a presence check and fails an IRP lookup — and the gap stays invisible until the invoice doesn't appear in GSTR-2B.
3. GSTIN drift
- Vendor GSTIN status is monitored on a defined cadence (monthly minimum for high-value vendors), not only checked at onboarding.
- Your vendor master flags vendors who operate across multiple GSTINs.
- A GSTIN status change or ADVAIT-driven risk flag feeds into payment approval, not just a vendor master update.
- AP staff have a documented process for what happens when an invoice arrives under a GSTIN the vendor doesn't normally file under.
If you scored No on any item: GSTIN drift compounds under continuous risk scoring. A vendor filing irregularly at the GSTIN level creates a supplier-level flag that follows every invoice from that vendor — not just the one that triggered it.
4. The 30-day IRN window
- Your team knows the 30-day clock runs from invoice issuance date, not the date it reaches your inbox or month-end.
- Invoices are prioritized for processing based on days remaining in the 30-day window, not received date alone.
- There is an escalation path for invoices approaching the deadline with an unresolved exception.
- Your team has confirmed whether your company exceeds the ₹10 Cr turnover threshold that this rule applies to (most ₹100–2,000 Cr companies do).
If you scored No on any item: Once an invoice passes 30 days from issuance, no IRN can be generated at all — the invoice is permanently blocked at the IRP, regardless of how the internal exception gets resolved.
What to do if you score below threshold
If you answered No to more than two items in any single area, treat that area as a live exposure, not a backlog item. Start with GSTR-2B matching and IRN validation — these two determine whether an ITC claim has any standing at all, and fixing them upstream prevents the GSTIN drift and 30-day window failures from compounding. None of the four areas requires new software to address at a basic level; each requires a deliberate decision about where in your existing AP workflow the check sits and who owns the exception when it fails.
For the regulatory detail behind these checks, see GST 2.0 Accounts Payable India: What Finance Teams Must Prepare For and Vendor Portals and E-Invoicing Compliance: The IRN Validation Gap.