
E-invoice data can flow into GSTR-1 automatically, but auto-population is not a substitute for reconciliation. Before filing, compare the sales register, Invoice Registration Portal records and the draft GSTR-1 at invoice level. Investigate every missing document, duplicate and value difference while the return is still editable.
This GST e-invoice reconciliation checklist gives finance teams a repeatable month-end process without mixing outward-supply checks with input tax credit reconciliation.
Start with three complete data sets
Download or export the following for the same GSTIN and tax period:
- the final sales register from the accounting or billing system;
- the IRP e-invoice report, including IRN and IRN date; and
- the draft GSTR-1 data, including the e-invoice details available for download.
The GST Portal’s GSTR-1 guidance confirms that e-invoice information received from the IRP is auto-populated into specified GSTR-1 tables. The portal also provides a “Download Details from E-Invoices (Excel)” option.
Use the same cut-off time for all three files. If sales entries continue to change after the reports are downloaded, freeze the period or record those late entries separately. Otherwise, the reconciliation may show differences caused only by timing.
Build a dependable matching key
Invoice number alone is often too weak. A practical matching key combines:
- supplier GSTIN;
- financial year;
- document type;
- invoice, debit note or credit note number; and
- document date.
Normalise obvious formatting differences before matching. For example, remove accidental spaces, standardise letter case and check whether the accounting export has dropped leading zeros. Keep the original source values in separate columns so the audit trail remains intact.
Do not merge two documents simply because their taxable value and tax are the same. Each invoice series should remain traceable to the document issued.
Classify the reconciliation results
Split the output into four groups.
Complete matches
The document appears in the books, IRP report and GSTR-1 with the same recipient GSTIN, document number, date, taxable value, tax rate and tax amounts. Check place of supply and reverse-charge indicators where relevant.
Documents missing from one source
List invoices found in the books but absent from the IRP report, IRP documents that do not appear in the books, and records missing from the draft GSTR-1. Assign each item to billing, accounts or the GST return preparer for review.
A missing record may be a genuine error, a timing difference or a document outside the e-invoice population flow. Record the reason instead of forcing a match.
Value or classification differences
Compare taxable value, invoice value, rate-wise tax, place of supply, recipient GSTIN, supply type and the applicable GSTR-1 table. Review exports, SEZ supplies, credit notes and debit notes separately because their reporting fields differ from ordinary domestic B2B invoices.
Small differences should not be written off automatically. A rounding policy must be consistent and documented.
Cancelled, amended or exceptional documents
Maintain a separate list for cancelled documents, later corrections, test invoices, rejected transactions and entries posted after the period cut-off. Note the source record, the reason, the person who approved the treatment and the action taken in the return.
Check the GSTR-1 source fields
For auto-populated e-invoice records, the GST Portal can show Source, IRN and IRN Date in the processed-document view. These fields help distinguish IRP-sourced records from entries added through another route.
The portal guidance also states that if an auto-populated e-invoice record is edited in GSTR-1, the Source, IRN and IRN Date fields become blank. Treat that as a control point. Keep evidence of why the edit was necessary and who approved it.
Where the underlying billing or IRP data is wrong, identify the legally available correction route for that document and period before changing the return. Do not rely on a portal edit alone to repair inconsistent source records.
Tie the invoice detail to the return summary
After resolving invoice-level differences, regenerate the GSTR-1 summary and compare it with:
- the sales register by tax rate and supply type;
- output tax ledgers in the books;
- credit and debit note totals;
- export and SEZ classifications; and
- the final exception list.
The GST Portal’s GSTR-1 filing manual directs taxpayers to download e-invoice details, add or amend records where appropriate, generate the summary, review it and then file the statement.
A clean total is not enough if individual recipient GSTINs or invoice numbers are wrong. Complete both invoice-level and summary-level checks.
Keep an exception register
Use one line per unresolved item with columns for source, document number, mismatch type, amount, owner, proposed action, approval and closure date. Save the three source reports, the reconciliation workbook, supporting emails or notes, and the final filed return together.
This file will help when a customer reports that an invoice is missing, the return data needs explanation, or the same exception appears again next month.
Questions businesses often ask
Does auto-population mean GSTR-1 is ready to file?
No. It reduces re-entry, but businesses still need to check completeness, classification and consistency with their books.
Can auto-populated e-invoice details be edited?
The GST Portal guidance allows editing before filing. An edit clears the displayed Source, IRN and IRN Date fields, so document the reason and confirm the correct compliance treatment first.
Should purchase invoices be included in this reconciliation?
This checklist covers outward supplies and supplier-side GSTR-1 preparation. Purchase-register and GSTR-2B checks belong in a separate input tax credit reconciliation.
ProTax Consultancy’s GST Services can help businesses organise the source files, investigate exceptions and review GSTR-1 before filing. The work remains tied to the taxpayer’s actual books and portal records rather than assumptions based on summary totals.
*Photo: Pavel Danilyuk / Pexels (free Pexels licence).*
