GST E-Invoicing Explained for Small Businesses

What an e-invoice is: IRN, QR code and IRP

Your software prepares the invoice data in the notified e-invoice schema, a JSON structure covering seller and buyer GSTINs, document number and date, item details with HSN codes, taxable values and tax amounts. This file is sent to an IRP. The IRP checks it, for example that the GSTINs are valid and active and that the same document number has not already been registered by you in that financial year.

If the data passes validation, the IRP generates the IRN, a unique hash derived from your GSTIN, document type, document number and financial year. It signs the invoice data and returns it with a signed QR code containing the key details. You print or embed the QR code on the invoice you send to the buyer, who or whose auditors can verify it later. The IRP then passes the data to the GST system, which uses it to auto-populate the relevant parts of your GSTR-1 and, where applicable, the e-way bill system.

Who must generate e-invoices: the turnover limit

E-invoicing applies to registered businesses whose aggregate turnover, calculated on PAN across all GSTINs, exceeded the notified threshold in any financial year from 2017-18 onwards. It began in October 2020 for the largest taxpayers and the threshold has been lowered in stages since then, bringing many small and mid-sized manufacturers, traders and service providers into scope. The e-invoice applicability turnover limit has been ₹5 crore since August 2023, but check the current threshold on the e-invoice portal; once you cross it in any year, you generally remain covered even if turnover later falls.

Certain categories are exempt regardless of turnover, including SEZ units, insurers, banking and financial institutions including NBFCs, goods transport agencies, passenger transport services and multiplex cinema admissions. Exemptions are listed in notifications and can be modified, so confirm whether your category is covered. Note that the obligation is on the supplier: if you are a small buyer purchasing from a large supplier, you will receive e-invoices but do not need to generate them yourself.

Which documents are covered, and which are not

E-invoicing covers B2B supplies to registered buyers, supplies to SEZs, exports and deemed exports, and the related credit notes and debit notes. B2C invoices to unregistered customers are not reported to the IRP, although very large taxpayers have a separate requirement to print a dynamic QR code on B2C invoices. Documents such as delivery challans, bills of supply for exempt goods and internal transfers within the same GSTIN are generally outside e-invoicing.

B2B supplies that attract reverse charge are generally covered too, even though the buyer pays the tax, while exempt supplies billed on a bill of supply are not. Treat "B2B and export documents" as the starting assumption and check edge cases with your adviser. Getting the document type right in your software matters, because a credit note must reference the original invoice and carry its own IRN.

• Covered: tax invoices to registered buyers, credit notes, debit notes, exports, SEZ supplies
• Not reported to IRP: B2C invoices (large taxpayers have separate dynamic QR rules)
• Generally outside scope: delivery challans, internal stock transfers within the same GSTIN
• Check with your adviser: nil-rated B2B supplies, reverse charge cases, unusual document types

Time limits for reporting and cancelling

For most businesses, the practical rule is simple: generate the IRN before you issue the invoice to the buyer or dispatch the goods. For larger taxpayers above a notified turnover level, there is also a hard reporting window: invoices must be reported to the IRP within a fixed number of days of the invoice date, and the IRP rejects older documents. This window was introduced for the largest taxpayers first and has since been extended to a wider group, so check whether it applies to you and plan your backdating and approval workflows around it.

Cancellation is tightly limited. An IRN can be cancelled on the IRP only within a short window after generation, measured in hours rather than days, and only in full; you cannot partially cancel or edit a registered e-invoice. You also generally cannot cancel an IRN while an active e-way bill is linked to it. After the window closes, the correct fix is a credit note or debit note, which itself needs an IRN, or an amendment through your GST return where permitted.

How e-invoicing connects to e-way bills and returns

If goods movement needs an e-way bill, you can generate it along with or immediately after the IRN, using the invoice data already sent to the IRP plus transport details such as vehicle number or transporter ID and distance. This removes the duplicate entry that used to happen on the e-way bill portal, and many billing systems do both in a single step when the user saves the invoice.

E-invoice data also flows into your GSTR-1, so the B2B and export tables are auto-populated. You still need to review and file the return, and anything not reported through the IRP must be added manually. Because the data comes from the IRP, differences between your books and the return usually point to invoices that were created in software but never registered, or cancelled on one side only. A monthly check that matches your sales register to the IRN list catches these before filing.

How billing software integrates: direct API, GSP or ASP

There are three broad ways to generate e-invoices. Very small volumes can be handled on the IRP's own web portal or free offline tools, by entering or uploading invoice data and downloading the result. This works for a handful of invoices a day, but manual re-entry creates errors and does not scale.

Most businesses use billing or accounting software that connects to the IRP through a GST Suvidha Provider (GSP), an authorised intermediary that provides API access, often packaged by an Application Service Provider (ASP), the software vendor. Many popular accounting packages include this. Direct API access to the IRP is available to taxpayers meeting eligibility conditions, typically larger ones, and requires registering API credentials and managing security yourself.

For custom billing systems, the integration pattern is the same whichever route you pick: build the schema JSON from your invoice, authenticate, submit, store the IRN, acknowledgement and signed QR against the invoice, and handle errors clearly so users can fix data and resubmit. Keep API credentials on the server, and log every request and response for audit.

Common mistakes and how to avoid them

Most rejections from the IRP are data problems that should have been caught in your own software before submission. Validating master data once, at the point where customers and items are created, is far cheaper than fixing invoices one by one at month end. The other common category is process: invoices printed and sent before the IRN exists, or cancellations done in the software but not on the IRP.

• Invalid or cancelled buyer GSTIN; verify GSTINs when creating customer records
• Wrong or incomplete HSN codes, or wrong state codes affecting IGST vs CGST and SGST
• Reusing a document number already registered in the same financial year
• Rounding differences between line totals and invoice totals
• Issuing the invoice to the customer before the IRN and QR code are generated
• Cancelling in the billing software but not on the IRP, or vice versa
• Missing the reporting window where it applies, often because of slow internal approvals

E-invoicing readiness checklist

Before your first e-invoice, or when reviewing an existing setup, work through the list below with your accountant and software provider. It is also worth doing a few test invoices on the sandbox or with a low-value real transaction before switching the whole team over. Keep a short written procedure for cancellations and credit notes, since those are the steps staff get wrong most often.

• Confirm applicability against the current threshold, based on aggregate turnover across all GSTINs
• Register on the e-invoice portal and decide which IRP and integration route to use
• Clean up customer GSTINs, addresses, state codes and item HSN codes
• Configure document series so numbers are unique per financial year
• Ensure invoice print formats show the IRN and signed QR code
• Set up e-way bill generation with IRN where goods move
• Train staff on the cancellation window and on using credit and debit notes after it
• Reconcile your sales register with IRNs and GSTR-1 every month

Need e-invoicing in your own software?

If your business already uses a packaged accounting product with e-invoicing built in, the checklist above is mostly about clean data and process. When comparing accounting software for small business in India, or POS software for small business counters, ask whether e-invoicing works directly from the invoice screen or needs a separate upload. If you run custom billing, POS or ERP software, the IRP integration has to be built into it. RED SAG builds billing and accounting software with GST e-invoicing and e-way bill integration from Tiruppur, and works with your tax adviser on the compliance side.