E invoice applicability

Separate applicability from reporting limits

Notification 10/2023-Central Tax lowered the e-invoice turnover threshold to aggregate turnover exceeding ₹5 crore from 1 August 2023. Review the underlying notification as amended, relevant preceding-year turnover and excluded categories before applying that threshold to the business.

The reporting restriction is a separate test: the official IRP advisory states that taxpayers with annual aggregate turnover of ₹10 crore or more must report covered e-invoices within 30 days from the invoice date from 1 April 2025. This is not a replacement of the ₹5 crore applicability threshold.

Assess the taxpayer and document population

Prepare PAN-level turnover history across GSTINs for the relevant years and retain the calculation. Do not rely solely on one branch’s current-year sales or portal enablement status as the legal assessment. Check the specific exclusion where one is claimed.

Map B2B supplies, exports and relevant debit or credit notes against the operative rules. Distinguish e-invoice requirements from B2C QR-code requirements and e-way bills. These processes can interact, but satisfying one does not automatically satisfy the others.

Validate data before requesting an IRN

• Supplier and recipient GSTINs and the correct supply category.
• Document type, number and date, with duplicate controls.
• Item description, HSN or SAC, quantity where relevant and taxable value.
• Place of supply, tax rate, tax heads and totals.
• Export, dispatch and delivery details where required.
• The invoice version approved for reporting and the authorised system or operator.

Retain the successful registration response

Generate the invoice in the business system, report the required data through an authorised Invoice Registration Portal and retain the successful response. Check the IRN, acknowledgement and signed QR information against the invoice before distributing the final document.

A pending request, timeout or validation error is not successful registration. Reconcile the response before retrying so a network problem does not create duplicate or inconsistent local records. Keep failed items in an exception queue with an owner.

Handle errors within the permitted process

If the wrong value or customer is reported, assess the current cancellation and correction options and their time limits. Do not assume that editing the PDF changes the registered data. Preserve the original response and the record of the corrective action.

For example, an invoice is generated locally but reporting repeatedly fails because the recipient identifier is wrong. Resolve the master-data issue and confirm the actual reporting result; marking the invoice “sent” in the accounting system does not resolve the IRN exception.

Reconcile downstream records

Compare successful IRNs with the sales register, credit notes and outward-supply return data. Investigate missing, cancelled or duplicated entries and differences in tax heads. Auto-population should be reviewed before filing rather than accepted without a close process.

The GST portal’s GSTR-1 manual separates imported e-invoice data from generating the return summary and filing the statement. An IRN therefore does not complete that filing. The manual also notes that editing an imported entry clears its displayed source, IRN and IRN-date fields. Retain the registration response separately and document the reason for any return adjustment.

Monitor invoices approaching any applicable reporting limit. An internal month-end timetable should not cause documents to miss the portal restriction or other invoicing obligations. Keep a contingency procedure for system failures and retain evidence of the issue.

Prepare for implementation

Bring turnover history, GSTIN and business-category details, invoice samples, document volumes, accounting-system exports and existing IRP arrangements. Identify who owns master data, reporting failures and return reconciliation.

Kosha.Services can help document applicability and establish the operating checklist. Current notification amendments, excluded categories and reporting advisories must be checked for the actual taxpayer and period before changing the-invoicing process.