GST e-invoicing · India
GST e-invoicing and dispatch workflows for India
Under GST e-invoicing, a business uploads its B2B invoices to the Invoice Registration Portal (IRP). The IRP generates and returns a unique Invoice Reference Number (IRN), a digitally signed e-invoice and a QR code. VisionONE links these returned details to the invoice records in your ERP. Checked on einvoice1.gst.gov.in on 3 November 2026.
Connect eligible invoice documents, returned IRNs and signed QR details with the ERP records your team uses. Review e-way bill and dispatch information alongside finance, with a supported integration setup and clear exception handling.
Comparing Kenya and India requirements? Start at the e-invoicing compliance hub, or read the GST e-invoicing ERP readiness guide and the e-way bill and dispatch guide.
GST invoice registration
Connect eligible ERP invoice documents to the configured Invoice Registration Portal workflow, with the source records kept in view.
IRN & acknowledgement
Review the returned Invoice Reference Number and acknowledgement details against the original ERP document.
Signed QR output
Keep the returned signed QR information with the invoice output. Confirm the document format in a supported product demo.
E-way bill from dispatch
Review delivery or transfer records with the transporter and movement details needed for the configured e-way bill workflow.
Corrections & exceptions
Follow rejected or unconfirmed requests with their returned messages, source documents and next review action.
Finance & record review
Keep invoice registration, dispatch and ledger records connected, while reviewing each status and responsibility separately.
India invoicing workflows connected to VisionONE ERP
Discuss your GST invoice workflowOn this page
Part of VisionONE ERP
Supported GST invoice registration workflow
From the invoice
to registration and dispatch review.
Follow one fictional invoice through preparation, registration, response review and its linked delivery. Keep the source document and each returned status together.
Stage 1 of 4 · Prepare
Start with the document and its GST details.
The fictional invoice INV-DEMO-033 totals INR 59,000. Review the supplier and recipient details, document date, items and applicable transaction treatment before submission. No real GSTIN or tax-rate calculation is modelled in this example.
Illustrative record
- Invoice
- INV-DEMO-033
- Company
- COMPANY-DEMO-IN
- Document type
- Illustrative B2B invoice
- Invoice total
- INR 59,000
Stage 2 of 4 · Register
Send through the supported registration connection.
Keep the source invoice reference with its submission history. Until the returned result is confirmed, the request stays under review. Sending an invoice request does not by itself establish that registration succeeded.
Illustrative record
- Invoice
- INV-DEMO-033
- Request
- Illustrative submission
- Response
- Awaiting confirmation
- IRN received
- Not yet recorded
Stage 3 of 4 · Review
Match the response to the original invoice.
The illustration now assumes successful registration of INV-DEMO-033. In the real workflow, retain the returned IRN, acknowledgement and signed QR details with the invoice. Check the source reference and printed document output before completing the review.
Illustrative record
- Invoice
- INV-DEMO-033
- Illustrative status
- Registration successful
- Invoice total
- INR 59,000
- IRN and signed QR
- Real sample required
Stage 4 of 4 · Dispatch
Keep goods movement and invoice status distinct.
A fictional delivery DN-DEMO-033 carries the same invoice reference. Confirm e-way bill applicability, transporter details, movement information and the returned result. The example leaves the e-way bill in review; invoice registration does not prove that dispatch requirements are complete.
Illustrative record
- Delivery
- DN-DEMO-033
- Linked invoice
- INV-DEMO-033
- Movement review
- Transport details required
- E-way bill status
- Pending review
Educational records explain the workflow; they are not a product screen or government-issued document. No GSTIN, IRN, signed QR code or e-way bill number has been fabricated. Actual connection, fields and document support are confirmed during setup.
IRN responses, signed QR codes and dispatch records
Know what sits
behind each document status.
GST e-invoicing software in India should keep registration evidence close to the ERP invoice. Review the delivery and e-way bill records alongside it, with each result clearly identified.
See the invoice and its returned result together.
The illustration assumes that INV-DEMO-033 was registered successfully. The real record should retain its returned identifiers and signed QR information, so the team can compare the source invoice with the registered result.
- Illustrative invoice total
- INR 59,000One source invoice · no tax calculation
| Record | Review status |
|---|---|
| INV-DEMO-033Source invoice | Illustrative success |
| IRN and acknowledgementReturned registration details | Real sample required |
| Signed QR and invoice outputDocument verification | Real sample required |
An ERP printout alone does not establish registration. Review the actual returned result and verify the signed output using the applicable official process.
Give the movement its own review.
DN-DEMO-033 is linked to the same invoice. Its e-way bill status remains pending review in this example. Confirm the applicable movement, transport details and returned status independently of the invoice registration result.
- Linked delivery
- DN-DEMO-033E-way bill: pending review
| Record | Review status |
|---|---|
| Delivery noteDN-DEMO-033 | Linked to invoice |
| Transport and movement detailsMode, locations and responsible party | Review required |
| E-way bill resultApplicability and validity checks | Pending review |
Invoice data can feed related dispatch workflows, but transport details and the actual e-way bill result still need review. Do not treat a preliminary slip as proof that every movement requirement is met.
Keep the source, response and delivery linked.
Review the original invoice, its registration result and the linked delivery with their own identifiers. A later correction or cancellation needs a documented process and its own returned status; the original record should remain traceable.
- Invoice reference
- INV-DEMO-033Invoice, registration and delivery kept distinct
| Record | Connected source |
|---|---|
| ERP invoiceINR 59,000 | INV-DEMO-033 |
| Registration resultIllustrative successful outcome | INV-DEMO-033 |
| Delivery reviewE-way bill pending review | DN-DEMO-033 |
These records are linked references, not amounts to add. The INR 59,000 invoice total is recorded once; a submission and delivery do not create extra invoiced revenue.
These are fictional review records, not VisionONE product outputs. Ask to see a permitted, redacted invoice, actual registration response and the supported e-way bill workflow for the current product version.
IRN, QR and e-way bill scope
One invoice needs
the right connected records.
ERP integration with a GST Invoice Registration Portal connects the source document with its returned evidence. Agree the supported connection and dispatch scope around the way your business invoices and moves goods.
- Eligible invoice documents are created in the business system, then reported through the supported registration connection.
- The IRP returns registration details; the signed QR information belongs with the invoice output.
- Transport and movement details are reviewed for the related e-way bill workflow and actual dispatch.
Registration and goods movement answer different questions.
An IRN identifies a registered invoice. Review the separate e-way bill applicability, transport details and returned result for the goods movement. Confirm the supported workflow in your demonstration and proposal.
Review supplier and recipient details, document types and applicable GST treatment with the source records.
Keep the actual IRN, acknowledgement and signed QR details with the invoice and its submission history.
Confirm the applicable e-way bill flow, transport information, returned result and validity before dispatch.
These service-name labels identify workflow stages; they are not government approval badges.
Corrections and exceptions
Keep the message,
the next action and the history together.
A rejected invoice, an uncertain result and a registered document needing correction require different follow-up. Give the finance and support teams the evidence to choose the next step.
Read the returned validation message
Identify the source document, returned message and person responsible for follow-up. Check the affected master data or invoice field before retrying.
Investigate an unconfirmed request
Review the submission history and actual registration status before repeating a request. A missing response needs investigation so the same document is not reported twice.
Use the applicable correction process
After registration, review cancellation or correction options with the India team and your tax reviewer. Keep the reason, original reference and returned status with the document trail.
Official requirements and review dates
Make the requirements
worth checking.
Keep eligibility, reporting windows, corrections and dispatch requirements under a named review. Official guidance was checked on 12 October 2026; confirm it again when configuring or changing your deployment.
Applicability and exemptions
Confirm taxpayer applicability, transaction categories and exemptions using current official GST guidance before enabling production registration.
Reporting window
The official IRP guidance describes a 30-day reporting restriction for AATO of INR 10 crore and above from 1 April 2025. Recheck current applicability and changes before use.
Cancellation review
Official IRP guidance permits cancellation within 24 hours of generation, subject to the applicable conditions. Review related e-way bill status and the supported cancellation flow promptly.
Movement details and validity
Check the applicable e-way bill requirements, transport mode, movement details, status and validity. Use current official rules and the actual returned record.
Named reviewer and evidence date
Record which official guidance was reviewed, when it was checked and who approved the business setup. Keep the tax reviewer separate from the integration configuration owner.
Product version and pilot tests
Confirm the supported connection, current product version, output fields and exception behaviour. Test invoice registration and dispatch with permitted sample documents.
Connected India ERP records
Keep the invoice,
the ledger and the delivery in view.
Choose the finance and stock workflows around the registration and dispatch records your team needs to review.
Start with your India invoicing requirements. Bring your entity and branch structure, eligible document types, transaction volumes and goods-movement examples. Agree which registration, dispatch and reporting outputs belong in the implementation scope.
Implementation and scope
Connection, testing
and rollout.
Scope your GST invoice and dispatch workflow with the Hyderabad team. Review the supported integration, current version, records and responsibilities before agreeing the rollout.
Prepare the records and scope
Bring invoice, credit-note and debit-note examples, relevant GSTIN and branch details, delivery records and transporter information. Agree document support and applicable requirements.
Configure the connection and test
Confirm the current integration route, access arrangements, master mappings and output formats. Test a successful invoice response and a relevant rejection or uncertain-result case.
Reconcile the pilot and go-live
Review the IRN and signed output with the ERP invoice, then test the applicable e-way bill workflow. Confirm responsibilities, training and support before production use.
Questions, answered
Before your
GST integration demo.
Bring the documents you issue today and one exception you need to explain. Confirm the connection, returned evidence and dispatch workflow your team needs.
Which invoice documents are supported?
VisionONE’s published India scope describes eligible B2B invoices, credit notes and debit notes reported to an Invoice Registration Portal. Confirm the document categories, applicable eligibility, current connection and product version using your sample documents during the demo.
How are rejected responses reviewed?
Review the returned message against the original ERP document and the relevant master data. Preserve the submission history, assign responsibility for the correction and confirm the next response. Check actual registration status before repeating a request whose result is uncertain.
Is e-way bill generation supported?
VisionONE describes an e-way bill workflow from delivery notes and stock transfers. Confirm the supported connection, movement types, transport details, output and exceptions in the current version. Review applicability and the actual returned status rather than treating invoice registration as proof of completed movement requirements.
Where do we confirm current eligibility and deadlines?
Use current GST portal, official notifications and IRP guidance with your India tax reviewer. Check taxpayer and document applicability, exemptions, reporting windows and cancellation conditions separately. The reporting-window threshold is not a substitute for the overall e-invoicing applicability test.
What is returned after successful registration?
Official guidance describes a returned IRN and signed invoice information, including the signed QR code. Keep the actual acknowledgement and signed output with the source invoice. Ask to review a permitted redacted response and printed document in your product demo.
Can we edit a registered invoice on the IRP?
Official IRP guidance says a registered invoice cannot be amended on the portal. It describes a 24-hour cancellation window with applicable conditions. Review a required correction promptly with your tax reviewer and the implementation team, including any related e-way bill status.
What should we bring to an India integration demo?
Bring anonymised invoice documents, a delivery note or transfer, your entity and branch structure and the transporter fields you use. Include an exception and the output your team needs, so the demo can show the supported connection and its limits.
See it with your records
Bring one invoice.
Follow registration and dispatch.
Review the ERP invoice, returned IRN and signed QR details, then the linked delivery. Include one exception so the demo covers the follow-up behind each document status.
Hyderabad team · +91 81435 33535 · no obligation.