To generate an e-invoice in India, prepare the invoice in your billing or accounting system, submit its data to an Invoice Registration Portal (IRP), and use the returned Invoice Reference Number (IRN), digitally signed invoice data and QR code on the final document. Validation then means checking that the IRN exists, the signed data matches the invoice and the QR code resolves through an IRP verification service. A PDF created without IRP registration is not an e-invoice under the GST system.
The workflow below applies the operational guidance published by the IRIS IRP operator for GSTN. Thresholds, exemptions, schemas and portal controls can change, so confirm the live GST notifications and your GSTIN’s status before relying on a particular rule.
As an Amazon Associate I earn from qualifying purchases.
What an Indian e-invoice is—and what it is not
An e-invoice is a standard tax invoice, debit note or credit note whose prescribed data has been reported to an Invoice Registration Portal (IRP) and accepted for registration. The IRP checks the submission, assigns a unique IRN, digitally signs the invoice JSON and produces a QR code. The registered information is passed to GST systems and the e-way bill system, and invoice information can be used for return population. See the IRIS IRP overview of e-invoicing.
Creating a PDF, printing an invoice, or emailing a document does not by itself complete e-invoicing. The invoice must carry the registration details returned by the IRP, and your records should preserve the response used to create it. Registration also does not replace your responsibility for the underlying sale, place-of-supply analysis, rate selection, customer details or other accounting and tax judgments.
#1 Best Overall
Who must check applicability
Start with the GSTIN that will issue the document. The IRIS IRP mandate page records an aggregate annual turnover (AATO) threshold of ₹5 crore, effective 1 August 2023. AATO in any preceding financial year from FY 2017–18 onward is considered, and the page describes AATO as being based on GST returns. Therefore, a business should not look only at its current-year turnover.
The same material says regular taxpayers and SEZ developers can generate e-invoices, and that an e-commerce operator may generate them on a seller’s behalf. Only the supplier generates the e-invoice; the recipient and transporter do not generate one for the supplier’s transaction. Confirm the latest position for your entity and transaction type on the IRP e-invoicing mandate page and through the GST system.
Applicability checklist
- Review AATO for every preceding financial year from FY 2017–18, using the turnover reflected in GST returns.
- Check whether the specific GSTIN is enabled for e-invoicing. Eligibility can be GSTIN-specific rather than a conclusion you make from a company-wide turnover figure.
- Check whether an exemption or exclusion applies to your entity or document. Do not assume that crossing or falling below a current-year figure changes the rule immediately.
- Confirm the document type is one the current e-invoice system accepts, such as a tax invoice, debit note or credit note.
- Recheck the live GST notification and IRP status before changing your process, because the ₹5 crore figure is the published mandate threshold from 2023, not a guarantee that every future rule will be identical.
Prerequisites before you submit an invoice
The IRP’s prerequisites guidance describes portal access and setup requirements. In particular, multi-factor authentication (MFA) is required for portal access; follow the current sign-in instructions rather than relying on an old saved login procedure.
Have the commercial and tax data ready before opening the submission screen. At minimum, you will need the supplier GSTIN, the recipient GSTIN, document number and date, document type, item descriptions, HSN or SAC, quantities and values where applicable, and the applicable IGST, CGST or SGST treatment. The recipient GSTIN is required in the web-form workflow. Keep your source invoice and supporting order or delivery records available so that a typographical correction is not mistaken for a tax adjustment.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Data-quality checks that prevent avoidable rejections
- Use a document number and series that your accounting system has not already used for a registered document.
- Match the legal name and GSTIN of the supplier and recipient. A correct-looking name with a wrong GSTIN can still make the registered invoice unusable.
- Use the correct HSN for goods or SAC for services, with the level of detail required by the current schema.
- Reconcile taxable value, tax rate and tax amounts before submission. Check whether the transaction is intra-state (CGST and SGST) or inter-state (IGST) according to the applicable place-of-supply treatment.
- Ensure dates, decimal precision, unit codes and address fields follow the current e-invoice schema used by your upload method.
Choose a generation method
IRP material describes three practical routes. Select one based on invoice volume, whether your billing data is already structured, and whether you need the IRN returned automatically to your accounting system.
| Method | Best fit | How it works | Main control to add |
|---|---|---|---|
| IRP web form | One invoice at a time, low volume or occasional issuance | Enter the document, supplier, recipient and item data in the portal and submit it for registration. | Review every field before submission and download the response immediately. |
| Bulk spreadsheet or Excel utility | Multiple invoices whose data is already tabulated | Populate the prescribed template or utility, validate the file and upload it for bulk generation. | Use a controlled template, test a small batch and reconcile each returned IRN to the source invoice. |
| ERP or API integration | Regular volume and an existing accounting, billing or ERP system | Your system sends the required payload to the IRP and writes the returned IRN, signed data and QR information back to the invoice workflow. | Build duplicate prevention, response logging, retry handling and an exception queue before going live. |
The IRP describes these routes and the Excel utility in its e-invoicing guidance. No dedicated printer or special physical device is identified as a prerequisite; the process is based on the portal, a structured file or software integration.
How to generate an e-invoice through the web form
The web-form route is appropriate when you have a small number of documents and can enter the data carefully. The portal guide describes a seven-step form. Labels can change as the portal is updated, so use the current screen and schema if a field name differs.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Sign in and select the generation function. Complete the required MFA setup and sign in to the IRP. Choose the option to generate an e-invoice through the web form.
- Enter document details. Select the document type (for example, tax invoice, debit note or credit note), document number, document date and any other header fields shown as mandatory. Keep the number and date identical to the accounting record that will be delivered to the customer.
- Enter supplier details. Select or enter the supplier GSTIN and review the legal name and address that the portal displays. Some information is auto-populated from the selected GSTIN and remains editable where the form permits; compare it with your authorized invoice master data.
- Enter recipient details. Provide the recipient GSTIN and the requested billing and shipping information. The recipient GSTIN is required for this workflow. Check that the recipient state and place-of-supply information support the IGST or CGST/SGST treatment you intend to report.
- Add item lines. Enter each product or service, HSN or SAC, quantity, unit, price, taxable value and any discount or other field required by the form. Item data is not a free-text summary: it must be sufficiently specific for the applicable schema and tax calculation.
- Review tax and totals. The form computes tax values and displays IGST, CGST and SGST applicability from the entered details. Compare the calculated totals with your source invoice, correct any mismatch and review the preview before sending.
- Submit and save the response. Submit the document to the IRP. If it passes the portal’s checks and is not a duplicate, save the returned IRN, digitally signed invoice JSON and QR information, then update the invoice delivered to the customer with the returned details.
The detailed field flow is documented in Generate Through Web Form. The form’s acceptance is not a substitute for reviewing the commercial transaction; it means the submitted payload was registered under the IRP’s checks.
Bulk upload and ERP/API generation
Bulk spreadsheet or Excel utility
Use the bulk route when invoices are already maintained in a structured spreadsheet or can be exported from your billing system. Download the current template or utility from the portal, map every source column to the current schema, and preserve the exact document number and date used in your ledger. Before sending a large batch:
- Test the template with a small set containing both IGST and CGST/SGST examples, a service line and any unusual customer or address case you routinely handle.
- Run the utility’s validation and correct errors in the source data rather than manually altering a generated response.
- Upload the batch and record the IRP response for each row, including failures and duplicate messages.
- Reconcile every successful IRN to the originating invoice number, then release only the completed documents to customers or downstream systems.
A spreadsheet upload is not a license to reuse yesterday’s template indefinitely. Schema fields, validation messages and portal limits can change; obtain the current utility and release notes before a new filing cycle.
ERP or API integration
An integration sends invoice data from your ERP or billing application to the IRP and receives the registration response. It is usually the most efficient route for recurring volume, but it requires stronger controls than a manual form:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →- Payload mapping: map GSTINs, document types, HSN/SAC, units, tax rates, addresses and totals to the current API schema.
- Idempotency and duplicate prevention: stop a retry from creating confusion when the first request succeeded but the response was delayed. Store the request identifier and reconcile by document number and returned IRN.
- Response handling: persist the IRN, signed JSON, QR data, timestamp and the original payload or a retrievable link to it.
- Exception routing: send rejected, duplicate and timed-out documents to a human queue; do not silently mark them as registered.
- Access security: protect credentials, rotate them under your internal policy and restrict who can resend or cancel a document.
- Release monitoring: review the current schema and IRP release notes whenever the portal changes validation behavior.
The IRP describes API integration as a way to return registration data into an existing ERP workflow. An implementation partner or software provider may help with mapping, but responsibility for the submitted invoice remains with the supplier.
Rank #4
What the IRP returns and how to complete the invoice
For a valid, non-duplicate submission, the IRP generates a unique IRN, digitally signs the invoice JSON and produces a QR code. IRIS IRP explains that the unique invoice number is generated using a hash algorithm when a valid tax invoice, debit note or credit note is sent for e-invoice production. The returned values are registration evidence, not optional decoration.
After a successful response:
- Store the IRN against the exact document number and GSTIN that were submitted.
- Retain the digitally signed JSON in a retrievable, access-controlled location. Do not keep only a screenshot of the portal page.
- Render or print the QR code and returned details on the customer-facing invoice in the format supported by your billing system.
- Ensure the PDF, printed copy and any electronic invoice sent to the recipient all correspond to the registered data. If a value changes, follow the applicable correction or cancellation process rather than editing the visible copy alone.
- Pass the response to your accounting, dispatch and e-way bill processes so that each downstream record references the same invoice and IRN.
How to validate an e-invoice
Validation has two layers. First, verify that the IRP registered the document and that the returned artifacts belong to it. Second, review the tax and commercial data independently. A QR code that opens successfully does not prove that the sale was classified correctly, that the tax rate was appropriate or that every underlying field was accurate.
Portal verification procedure
- Locate the invoice artifacts. Obtain the invoice, its IRN and, where available, the signed invoice JSON from the supplier or your own accounting system.
- Check the IRN. Confirm that an IRN is present and that it is associated with the supplier GSTIN, document number, document type and date shown on the invoice.
- Verify the QR code. Use the IRP’s Verify QR Code facility to scan or submit the QR information. Compare the returned supplier, recipient, document and value fields with the invoice you received.
- Verify the signature. Use the IRP’s Verify Signed E-Invoice facility against the signed JSON. Confirm that the signature validates and that the decoded content matches the invoice, not merely a similar document number.
- Perform accounting review. Check the purchase order or sales order, delivery evidence, place of supply, HSN/SAC, taxable value and tax amounts. Resolve a discrepancy with the issuer before posting or claiming credit.
- Retain evidence. Store the verification result or audit trail with the invoice record, subject to your retention and access policies.
The IRP portal exposes both verification services through its navigation; see the prerequisites and portal guidance for current access instructions. The portal’s registration check is not an independent audit of the transaction’s legal tax treatment.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Time-sensitive controls you must build into the process
30-day reporting limit for ₹10 crore AATO taxpayers
An IRIS IRP release note says that, from 1 April 2025, taxpayers with AATO of ₹10 crore or more must report invoices, credit notes and debit notes within 30 days from the invoice date. After that period, IRN generation is restricted. This is a separate operational control from the general ₹5 crore applicability threshold: a business can be covered by e-invoicing and also face the tighter 30-day reporting rule once it reaches the stated AATO level.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Configure your billing system to warn well before day 30, account for weekends or internal approval delays, and escalate documents that have not received an IRN. Read the applicable advisory and current release note at Notified E-invoice Schema and dated release notes before treating the timing as universal for every taxpayer.
Cancellation within 24 hours
IRIS IRP states that its basic access allows cancellation of an IRN within 24 hours of generation. Treat this as a portal cancellation window, not as proof that all accounting, supply, return or tax consequences have automatically disappeared. Coordinate any cancellation with your ledger, customer communication, inventory and applicable GST reporting process, and issue a fresh document only through the permitted procedure.
RSP-based validation change from 1 February 2026
A 1 February 2026 release note says Total Item Value validation was relaxed for retail selling price (RSP)-based tax calculations when at least one line item has an HSN notified for RSP-based calculation and the document date is on or after 1 February 2026. It lists suppression of validation errors 2194, 2234 and 2235 on the API, web form, Excel utility and JSON upload platforms. This narrow exception should not be generalized to ordinary invoices; use the current schema and error documentation to decide whether it applies to a particular line.
Troubleshooting common failures
| Symptom | Likely control to check | Action |
|---|---|---|
| Portal says the GSTIN is not enabled or the user cannot generate | GSTIN eligibility, enablement or exemption status | Check the GST system and IRP applicability information for that GSTIN. Do not infer status from another GSTIN owned by the same company. |
| Duplicate or already-registered document | Document number, supplier GSTIN and document type/date already used | Search your IRN register and accounting system. Do not change a document number merely to bypass a duplicate; investigate which submission is authoritative. |
| Tax totals do not match | Place of supply, tax type, rate, taxable value, discount or rounding | Reconcile the source invoice and correct the payload before resubmitting. Obtain tax advice for a classification dispute. |
| HSN/SAC or item validation error | Code, description, unit, quantity or schema version | Use the current notified schema and the exact error description. Check whether a documented RSP exception applies; do not suppress an error without evidence. |
| API call times out after submission | Unknown outcome rather than automatic failure | Query your integration logs and IRP status before retrying. A blind retry can create duplicate handling problems. |
| QR scans but displayed data is wrong | Invoice rendering or mapping, not necessarily IRP registration | Compare the QR result and signed JSON with the PDF. Stop distribution and correct the document through the permitted process. |
| Invoice is older than the applicable reporting window | 30-day control for taxpayers at or above ₹10 crore AATO | Escalate immediately, check the current advisory and document the resolution; do not assume the portal will accept a late request. |
Recordkeeping and internal controls
A defensible process connects four records: the source transaction, the submitted payload, the IRP response and the customer-facing invoice. Assign one internal reference to all four. Limit editing rights after IRN issuance, log who cancels or resubmits a document, and reconcile the IRN register to the sales or purchase ledger at least as often as your close process requires.
For incoming invoices, ask suppliers for the IRN and a readable QR code, then verify samples or all documents according to your risk policy. For outgoing invoices, make the verification step part of release approval rather than an afterthought. Preserve failed submissions and correction notes so an auditor can see why the final document differs from an earlier attempt.
Practical decision guide
- Occasional invoices: use the web form, with a second-person review of GSTINs, item codes and tax totals before submission.
- Several invoices from a prepared data file: use the current bulk utility, test the mapping and reconcile every returned IRN.
- Daily or high-volume billing: integrate your ERP or billing application, but require duplicate prevention, response logging, alerting and a manual exception queue.
- Receiving invoices: verify the IRN, signed data and QR result before posting material transactions, while separately reviewing the tax treatment and commercial evidence.
The essential outcome is not a PDF that looks complete. It is a traceable chain from an accurate source transaction to an IRP-registered document whose IRN, signed JSON and QR code agree with the invoice delivered or received.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
