A GSTR-1 versus e-invoice reconciliation audit compares the invoice-level data auto-populated into GSTR-1 from the Invoice Registration Portal against the entity's own IRN log and sales register, identifies invoices that appear in the e-invoice system but were edited before GSTR-1 filing, invoices that appear in the sales register but have no corresponding IRN, and invoices present in GSTR-1 that cannot be traced to either the IRN log or the sales register, treating each category as a distinct exception requiring its own explanation rather than netting them against each other.
The three exception categories
| Exception | Likely cause | What to check |
|---|---|---|
| IRN generated, but GSTR-1 figure edited before filing | Manual override of auto-populated data, sometimes for a legitimate correction, sometimes to mask an error | Obtain the reason for every edit and trace the corrected figure back to the sales register and the actual invoice |
| Sales register entry with no corresponding IRN | Invoice issued outside the e-invoicing process, or booked without issuing an invoice at all | Confirms whether e-invoicing applicability was missed for this transaction, a compliance gap distinct from a GSTR-1 reporting gap |
| GSTR-1 entry with no IRN and no sales register trace | Debit/credit note adjustments, or a data entry directly into the return outside the normal invoicing flow | Trace to supporting documentation; an unsupported entry in the return with no underlying transaction is a serious finding |
Why this reconciliation is worth running separately
A GSTR-1 to GSTR-3B reconciliation and a GSTR-1 to books reconciliation are both standard procedures, but neither one specifically tests whether the GSTR-1 figures actually originated from the IRN system where e-invoicing applies. An entity can have a GSTR-1 that agrees to the books in total while containing individual invoices that were never run through the IRN process, or that were edited after IRN generation in a way that no longer matches either the invoice or the books. This reconciliation is the one procedure that surfaces that specific gap.
Common practice, not a requirement
Running this reconciliation at the invoice level for the full year, rather than on a sample, is increasingly practical because both the IRN log and the GSTR-1 filing data are available in structured, exportable form. Treating it as a full-population check rather than a sample-based one is a reasonable choice once the data is in hand, though it is not a requirement.
Regulatory requirement
The auto-population mechanism linking e-invoice data to GSTR-1, and the categories of taxpayer to whom it applies, are governed by the current GST e-invoicing notifications and the GSTN's own filing mechanics, which have changed as the applicability threshold has been lowered over time. Confirm the current mechanism before relying on a prior year's reconciliation approach.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- GST & GSTR-2BGSTR-3B vs GSTR-1 reconciliation for auditorsWhy GSTR-1 and GSTR-3B outward-supply figures disagree, the usual causes, and what to do with a difference still unreconciled at the year end.
- Revenue, receivables & cut-offMatching dispatch, invoice and ledger for revenue testingThe sales-side mirror of the purchase three-way match: what breaks it in practice, and why the unmatched population should be sized by value, not count.
- Revenue, receivables & cut-offSales cut-off testing: dispatch, invoice and ledger datesWhy dispatch, invoice and ledger dates disagree at year end, how to sample either side of the cut-off, and the evidence that settles which date governs.
- Purchase & AP auditDuplicate invoice detection during auditWhy exact matching finds almost nothing, the six match rules that do work, and how to tell a duplicate booking from a duplicate payment.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.