E-Invoice Audit Trail and Record-Keeping Checklist

What Is an E-Invoice Audit Trail?

The expression “e-invoice audit trail” is not defined separately in the CGST Act or the Rules. In practice, it means a connected set of records showing:

• What document was created
• When it was reported to the IRP
• What data the IRP accepted
• Which final invoice was sent to the recipient
• Whether the IRN was cancelled or replaced
• How the transaction was reported in the GST returns
• Whether the accounting entry was edited later

These records should allow the finance team to move from an invoice number to its accounting voucher, IRP evidence, GST-return disclosure, and any subsequent correction without depending on disconnected spreadsheets.

Legal Requirement and Internal Control

GST law requires businesses to maintain invoices, credit notes , debit notes , accounts, and related records. Electronic records must also have proper backups and edit or deletion logs.

The law does not prescribe a separate IRN register, IMS action register, or folder of QR-code screenshots. Businesses may maintain them as internal controls where they make reconciliation and exception tracking easier.

E-Invoice Applicability at a Glance

Notification No. 10/2023-Central Tax reduced the e-invoice turnover threshold to ₹5 crore with effect from 1 August 2023.

Check Entity-Level Exemptions

Crossing the turnover threshold does not make every registered person liable. Notification No. 13/2020-Central Tax , as amended, excludes specified classes of registered persons.

These include government departments, local authorities, SEZ units, insurers, banks, financial institutions, including NBFCs, specified Goods Transport Agencies, passenger-transport service suppliers, and multiplex admission service suppliers.

The exemption applies to the specified class of registered person. For example, it applies to an SEZ unit but not automatically to an SEZ developer.

Do Not Rely Only on IRP Enablement

The “e-invoice status of taxpayer” facility can be used as an initial indicator, but portal enablement is not conclusive proof that the legal obligation applies. An enabled GSTIN may belong to an exempt entity or another taxpayer outside the notified requirement. Before treating a supplier as liable, confirm: 

• PAN-based aggregate turnover
• The financial year in which the threshold was crossed
• Entity-level exemptions
• Document type
• Nature of the supply

Monthly E-Invoice Status Check

Use a monthly e-invoice status check to identify covered documents that were created in the accounting system but were not successfully registered on the IRP . Complete this review before filing GSTR-1 rather than waiting for a mismatch, recipient complaint, or departmental notice.

30-Day Reporting Control

From 1 April 2025, taxpayers with AATO of ₹10 crore or more cannot report covered invoices , credit notes, or debit notes after 30 days from the document date. The GSTN advisory on the 30-day reporting limit gives the example that an invoice dated 1 April cannot be reported after 30 April. 

• Generate IRNs as close to the invoice date as possible.
• Run a daily ageing report for covered documents without an IRN.
• Escalate unresolved documents before they reach 21 days.
• Complete final corrective action before the end of the 30-day period.
• Record the reason and obtain professional advice where the reporting period has already expired.

This timetable is an internal control and not a statutory schedule. Document the result of the monthly review as part of the GST close.

Records to Keep for Each Covered Document

Rule 56 requires registered persons to maintain relevant invoices, credit notes, debit notes, delivery challans, and tax records. Electronic records must be backed up, and businesses must maintain a log of edited or deleted entries . A practical document set should contain:

Keeping the signed JSON is a strong internal control, although GST law does not specifically designate it as a compulsory record.

Records should be stored GSTIN-wise and financial-year-wise. The final invoice, IRP response, and related exception evidence should remain connected through the same document number or system reference.

IRN Cancellation and Corrections

An IRN may generally be cancelled through the IRP within 24 hours from the time the document was reported. Cancellation is not permitted where the linked e-way bill remains active or has been verified by an officer during transit. Partial cancellation is also not allowed. When an IRN is cancelled:

• Retain the original invoice, IRN, and cancellation acknowledgement.
• Record the cancellation time, reason, and internal approval.
• Do not delete the original accounting entry without preserving its history.
• Do not reuse the same document number to generate another IRN.
• Link any replacement invoice with the cancelled document.
• Confirm how the cancellation or replacement is reflected in GSTR-1 or GSTR-1A.
• Review the linked e-way bill separately where applicable.

The same supplier GSTIN, document type, document number, and financial-year combination cannot be reused to generate another IRN after cancellation.

Where the 24-hour IRP cancellation window has expired, follow the legally available GST-return amendment or credit-note process. Do not record the IRN as cancelled when it remains active on the portal.

QR Code Records and Verification

QR code records should remain linked to the final invoice, IRN evidence, and any supplier communication used to resolve a mismatch. The QR code returned in the signed JSON must appear on the invoice and should not be provided only on a separate sheet. It contains the following key details:

• Supplier and recipient GSTINs
• Supplier invoice number and date
• Invoice value
• Number of line items
• HSN code of the main item
• IRN
• IRN generation date

When Verification Is Useful

GST law does not require every recipient to scan and preserve the result for every inward invoice. Verification is particularly useful where:

• The supplier is new
• The invoice value is material
• The QR code appears altered or incomplete
• The invoice does not appear in expected GST records
• The GSTIN or invoice details do not match the transaction
• The recipient suspects that the invoice PDF was prepared before IRN generation

A failed scan does not automatically invalidate the invoice. Printing quality, PDF compression, or image damage may affect readability.

In such cases, obtain a clean copy, verify the signed JSON or QR data through an authorised facility, match the GSTINs and document details, and ask the supplier to confirm the IRN status. Record the outcome before claiming or retaining ITC.

IMS and GST Return Reconciliation

The Invoice Management System has been available on the GST portal since the October 2024 tax period. It allows recipients to review specified documents that suppliers have saved or filed through GSTR-1, GSTR-1A, or IFF. In April 2026, GSTN also released an Excel-based IMS Offline Tool for individual and bulk actions.

A recipient is not required to actively accept or reject every document. However, material, unknown, or inconsistent records should be reviewed rather than allowed to move through deemed acceptance without examination.

For monthly reconciliation , preserve the IMS download used for review, the final GSTR-2B, the purchase-register reconciliation, and evidence supporting material rejections or pending decisions.

IMS acceptance does not independently establish ITC eligibility . The recipient must still apply the relevant conditions, restrictions, and reversals under GST law.

How Long Must E-Invoice Records Be Retained?

Section 36 of the CGST Act requires relevant books and records to be retained for 72 months from the due date for furnishing the annual return for the financial year to which the records relate.

Retention deadline = Applicable annual-return due date + 72 months

Example: If the applicable annual return due date for FY 2025-26 is 31 December 2026 and is not extended, the related e-invoice records must generally be retained until 31 December 2032.

Do not calculate the period from the invoice date or financial-year end alone. If records relate to an appeal, revision, proceeding, or investigation, they must be retained until the later of:

• The normal 72-month period, or
• One year after the final disposal of the matter

A fixed table based on 31 December may become inaccurate if the annual-return due date is extended. Maintain a financial-year-wise retention schedule based on the actual applicable due date. Electronic records should also be:

• Backed up outside the primary accounting system
• Tested periodically to confirm that archived files can still be opened
• Protected from automatic deletion before the retention period ends
• Included in any ERP migration or software-discontinuation plan

What to Prepare for an Audit or Notice

GST law does not prescribe one standard e-invoice audit file. For an audit or notice , prepare a period-wise index that links each covered document to its final invoice, IRP acknowledgement, cancellation or correction history, and GST-return treatment. 

Include the sales-register reconciliation with IRP data and GSTR-1, the purchase-register reconciliation with IMS and GSTR-2B, and the instructions required to access electronic records and backups. Rule 57 requires electronic records to be backed up and produced on demand in a readable format.

Penalties and Demand Exposure

Penalty Note

There is no single fixed penalty called an “e-invoice audit-trail penalty”. Moreover, Section 122 covers failures relating to the maintenance of records, furnishing of documents, and issuance or accounting of invoices.

Section 125 is a general penalty provision and should not be treated as the automatic penalty for every e-invoice record failure.

The applicable tax, interest, and penalty depend on the relevant financial year, type of default, and legal provision invoked.

Keep Invoice, IRN, and GST Records Connected with BUSY

BUSY helps finance teams generate e-invoices through an IRP-integrated workflow, obtain IRNs and QR codes, print them on invoices, and connect billing data with GSTR-1 preparation.

This reduces dependence on disconnected spreadsheets when reviewing missing IRNs, cancelled documents, and GST-return differences.

Trusted by more than 6 lakh businesses, BUSY accounting software can help make invoice generation and monthly compliance checks part of the same accounting workflow.

Conclusion

A reliable e-invoice record system should link each invoice to its IRN, QR code, correction history, and GST return treatment. This makes it easier to trace documents and explain how each transaction was reported.

Reviewing these records during the monthly close helps finance teams identify errors early and produce clear evidence during scrutiny or audit.