Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
GST e-invoicing is a reporting and authentication step for specified GST documents—not a government website that creates your invoice. To set it up, first check whether your business is legally covered using aggregate turnover under its PAN and any applicable exemption; then prepare invoices in your existing system, report covered documents to an authorized Invoice Registration Portal (IRP), and issue the returned invoice with its Invoice Reference Number (IRN) and QR code.
The threshold was reduced to ₹5 crore effective August 1, 2023. A separate deadline applies from April 1, 2025: businesses with annual aggregate turnover (AATO) of ₹10 crore or more must report invoices, credit notes, and debit notes within 30 days of the document date. Use this checklist as a setup guide, not an individualized legal determination; confirm current notifications, exemptions, and portal rules before acting.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →What should a small business check before setting up e-invoicing?
Start with legal applicability, not the portal. GSTN says portal enablement is not itself a determination that e-invoicing is mandatory: an enabled taxpayer may still fall outside the obligation because of an exemption or another applicable condition.
- Calculate aggregate turnover by PAN. Consider the business’s aggregate turnover across all GST registrations under the same PAN, rather than looking only at one GSTIN. GSTN’s guidance frames the test by reference to preceding financial years beginning with FY 2017–18.
- Compare it with the notified threshold. The threshold was reduced to ₹5 crore effective August 1, 2023, under CBIC Notification No. 10/2023 – Central Tax. Apply the relevant rule to the business’s turnover history; do not assume that current-year sales alone answer the question.
- Check whether the business is in the notified class and whether an exemption applies. The turnover figure is not the whole test. Confirm the current rules for the entity and transactions in question rather than assuming that every business above the threshold, or every business below it, has the same status.
- Check portal status separately. GSTN provides a portal-status check and says eligible taxpayers can self-enable if they are not enabled. Treat the status as an operational signal, not as a substitute for the legal applicability check.
For a borderline case, preserve the turnover calculation and the basis for any exemption decision, and have the business’s tax professional confirm the current notification and its application. The official guidance does not determine an individual business’s turnover, transaction mix, or exemption status.
Popular on Amazon
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Build a written applicability file
A short internal memo can prevent repeated uncertainty. Record the PAN, each GSTIN, the turnover figure for every relevant preceding financial year, the date used for the calculation, the notified threshold applied, and the rule or notification relied on for any exemption. Keep a copy of the portal-status result, but label it clearly as an enablement result rather than proof of legal liability. Revisit the memo when a new financial year closes, a registration is added or cancelled, the business changes its transaction mix, or the government changes the threshold or exemption list.
What does e-invoicing change—and what stays the same?
Your business still creates the invoice in its own accounting, billing, or ERP system. E-invoicing means reporting specified GST document details to an IRP, which validates them and returns an IRN and QR code; it does not mean entering an invoice into a government website that prepares the original document.
Recommended Free Tools
GSTN defines e-invoicing as “reporting details of specified GST documents” to an IRP to obtain an IRN. The practical sequence is:
- Create the invoice in the business’s existing system.
- Submit the required invoice data to an authorized IRP.
- After successful validation, receive the IRP’s signed response, unique IRN, and QR code.
- Issue the invoice carrying those details to the buyer and retain the response for reconciliation.
GSTN says a B2B GST invoice is valid only with a valid IRN. That makes the report-and-return step part of the invoice workflow, not an optional afterthought. Keep the existing invoice number and accounting process aligned with the IRP response so staff can identify which document was successfully reported.
What the IRP does not replace
The IRP does not replace your quotation, purchase-order check, inventory posting, customer credit approval, payment collection, bookkeeping, or GST-return process. It authenticates the specified data submitted to it. Your source system remains responsible for calculations, numbering, tax coding, customer master data, and the final printable or electronic invoice. A successful IRN therefore does not mean every commercial or accounting control has passed; it means the reported document completed the IRP validation cycle.
Also popular on Amazon
Which documents and transactions should the workflow cover?
GSTN’s overview identifies GST invoices, credit notes, and debit notes for B2B supplies, supplies to SEZs, exports, and deemed exports. The precise scope depends on current rules and the applicable schema, so map the business’s transaction types before enabling automated reporting.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesDo not assume that every ordinary B2C sale follows the same IRP process. Ask the person responsible for GST compliance to classify the documents the business issues, including credit and debit notes, and confirm the required treatment against current guidance. Build the system configuration around that confirmed scope, rather than sending every document indiscriminately or relying on a broad assumption that only invoices matter.
Prepare a transaction map
List each sales channel and customer category separately: domestic registered customers, SEZ customers, export customers, deemed-export transactions, and ordinary unregistered retail sales. For each category, note the document type, place-of-supply logic already used by the business, tax treatment, and whether a credit or debit note may later be issued. This map gives the software administrator a practical set of test cases and helps prevent a credit note or export document from being overlooked simply because the original invoice was created by a different team.
How do you set up the reporting workflow?
Once applicability and transaction scope are confirmed, use this sequence to prepare the business and its staff.
- Choose the source system. Continue creating invoices in the accounting, billing, or ERP system that holds the business’s sales and tax data. Confirm it can produce the required GST invoice information in the applicable standard schema; the IRP applies schema requirements and validations to submitted data.
- Inventory the required master data. Clean GSTINs, legal names, addresses, state and place-of-supply fields, document types, invoice series, item descriptions, units, quantities, taxable values, tax rates, and tax amounts. Decide who may amend each master field and how changes are approved. Errors in customer or item data can cause validation failures or create mismatches between the source invoice and the reported document.
- Confirm IRP connectivity and document coverage. Ask the system provider or internal administrator how the system reports to an authorized IRP, and whether the workflow covers the applicable invoices, credit notes, and debit notes. Confirm how the system displays successful responses and validation failures. This is a configuration check, not a legal determination.
- Select an authorized IRP. Register with one of the currently authorized portals. GSTN’s setup guide describes one-time mobile and email OTP verification and lists six portals, but portal authorization and onboarding details can change. Check the current authorized list and registration instructions before choosing or configuring a destination.
- Complete portal onboarding. Follow the selected portal’s current registration steps and verify that the right business users can access the reporting workflow. GSTN’s guide describes OTP verification of mobile and email as part of registration. Keep recovery contacts current so a departing employee’s phone number or email does not block reporting.
- Configure numbering and duplicate controls. Preserve a consistent invoice series in the source system and prevent staff from accidentally submitting the same invoice twice. A simple status field—draft, submitted, IRN received, rejected, cancelled or corrected—makes the handoff visible. Do not overwrite the original source record when correcting an error; retain the audit trail and link the corrected document to the relevant response.
- Test with representative documents. Before going live, test at least one document for every covered transaction category and document type, including an invoice, credit note, debit note, SEZ or export case where applicable, and a deliberately invalid record to confirm that the error message reaches the right person. Check that the returned IRN and QR code print or render clearly on the customer copy.
- Run the report-and-issue process for each covered document. Submit the required data, wait for successful validation, and capture the signed response, IRN, and QR code. Issue the invoice with those returned details; do not treat a draft or an unsuccessful submission as a completed e-invoice.
- Define how staff handle exceptions. Make sure the person preparing invoices can distinguish a successful IRP response from a validation error and knows who resolves errors before the document is issued. Check that the business can retrieve the response associated with each reported document. Establish an escalation contact for a portal outage, rejected document, or suspected duplicate.
- Reconcile records. Retain the signed IRP response and ensure the accounting system can reconcile reported documents with the business’s GST returns. Reconciliation helps surface missing or mismatched records; the IRP report should not be confused with the business’s wider accounting and return workflow.
Use a simple daily control
At the end of each working day, compare the source system’s list of covered documents with the list that has an IRN. Investigate every document still marked pending or rejected. For businesses subject to the 30-day restriction, add the document date and days remaining to the exception report. A small business does not need a complex dashboard: a controlled spreadsheet or report from the accounting system is useful if it is reviewed, assigned, and retained.
PC 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 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchAlso popular on Amazon
Reporting invoices and generating IRNs on authorized IRPs is free of charge, according to GSTN’s setup guide. The business may separately have costs for its own accounting or ERP system, implementation, integration, training, or support; no official price list for those services is established here. Ask providers to state whether a quoted amount covers software licensing, API or integration work, user support, data migration, and ongoing maintenance. Do not pay a third party merely for access to the IRP unless its separate service provides value the business actually needs.
How should a small business compare billing or ERP options?
The official workflow does not require a particular commercial product. If you are choosing or upgrading software, compare tools against the workflow rather than against brand names. A suitable system should be able to:
- prepare all required GST invoice data in the applicable standard schema;
- connect to an authorized IRP or provide a clear, controlled export and submission process;
- handle the covered invoices, credit notes, and debit notes used by the business;
- show validation errors in language staff can act on and prevent issuance before a successful response where required;
- store the signed response, IRN, and QR code with the source invoice;
- support reconciliation with accounting records and GST returns; and
- provide current support and documented pricing for implementation and ongoing service.
Ask for a demonstration using the business’s own transaction scenarios, not only a standard sales invoice. Confirm who owns the IRP credentials, how access is removed when staff leave, how a failed submission is retried, and how data is exported if the business changes providers. A low-cost tool that cannot preserve responses or reconcile documents may create more manual work than it saves.
What is the 30-day reporting rule for businesses with ₹10 crore AATO?
From April 1, 2025, taxpayers with AATO of ₹10 crore or more must report invoices, credit notes, and debit notes within 30 days from the document date. The cited IRP notice says the portal restricts IRN generation beyond that window.
This particular restriction is not a general 30-day rule for every taxpayer: it applies to the stated AATO category. If the business is in that category, configure the workflow to send covered documents promptly, track the document date, and assign responsibility for monitoring unreported items. Do not wait until month-end to discover that a document has passed the reporting window.
Also popular on Amazon
The restriction and its implementation are described in the IRP notice on the revised reporting time limit. Check the current GST system advisory and portal rules for implementation details, especially if a document is approaching or has passed the deadline.
Operational controls for the deadline
- Capture the document date automatically when the invoice, credit note, or debit note is finalized.
- Set an internal target earlier than day 30 to allow for rejected submissions, corrections, weekends, or staff absence.
- Review a weekly ageing report showing all covered documents without an IRN.
- Escalate any item with a failed submission immediately to the person responsible for GST compliance.
- Keep evidence of the submission result and the correction history for documents that required resubmission.
If an item is already outside the window, do not assume that a late IRN can be generated or that another route automatically cures the issue. Check the current GST system advisory and obtain tax advice on the specific document.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How can a business verify an e-invoice and keep useful records?
GSTN identifies two ways to check an e-invoice: the e-Invoice QR Code Verifier app and the portal’s Search IRN functionality. Use the available verification route to check the invoice or its IRN when the business needs to confirm a returned document.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For routine operations, keep the signed IRP response with the business’s own invoice record and make the response retrievable by the invoice identifier. Reconcile the set of reported documents against the accounting records and GST returns, paying particular attention to documents that received validation errors or were not successfully reported. The official guidance does not prescribe a particular internal filing system, so the business should choose a process that reliably preserves and links the response to the correct document.
Minimum record set
For each reported document, retain the source invoice or note, the IRN, the QR code as displayed on the issued document, the signed IRP response, submission date and time, user or system that submitted it, and any rejection or correction history. Link related credit or debit notes to the underlying transaction in the accounting system. Restrict editing rights after issuance and retain a readable copy that can be retrieved during a customer query, reconciliation exercise, or tax review.
Also popular on Amazon
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Common setup mistakes to avoid
- Using one GSTIN’s turnover. The threshold test is framed on aggregate turnover under the PAN, including the relevant registrations and preceding financial years.
- Treating enablement as the legal test. An enabled portal status does not itself establish that the mandate applies, and a missing enablement status does not replace the business’s duty to assess the rules.
- Waiting for the portal to create the invoice. The source system creates the invoice; the IRP reports, validates, and returns the IRN and QR code.
- Issuing before a successful response. A draft, timeout, or rejected submission is not the same as a valid IRN.
- Ignoring notes and exports. Credit notes, debit notes, SEZ supplies, exports, and deemed exports may be within the mapped scope; do not configure only ordinary domestic invoices without checking the transaction list.
- Assuming every B2C sale follows the same route. Confirm the applicable treatment instead of sending every retail document indiscriminately.
- Leaving corrections undocumented. Preserve the original source record, the failed response, the corrected data, and the successful response.
- Confusing free IRP reporting with free software. IRN generation on authorized IRPs is free, but accounting software, integration, implementation, and support may carry separate charges.
- Failing to plan for staff changes or outages. Maintain more than one trained user, current recovery contacts, and a documented escalation path.
What should be on the business’s final setup checklist?
- Aggregate turnover has been assessed on a PAN basis across GST registrations, using the relevant preceding financial years from FY 2017–18 onward.
- The ₹5 crore threshold effective August 1, 2023, the notified class, and any relevant exemption have been checked against current rules.
- Portal enablement has been checked separately from the legal applicability decision.
- The business has mapped which invoices, credit notes, debit notes, and transaction types require reporting.
- Customer, item, tax, place-of-supply, and document-series data have been reviewed for schema readiness.
- The existing accounting, billing, or ERP system can prepare the required data and submit it through an authorized IRP.
- At least one test has covered each important document and transaction category.
- Users know how to identify a successful IRP response, capture the IRN and QR code, and resolve validation failures.
- A daily or weekly exception report identifies pending, rejected, duplicate, and corrected documents.
- If AATO is ₹10 crore or more, the process tracks the 30-day reporting window from each document date.
- The signed IRP response can be retained, retrieved, and reconciled with accounting records and GST returns.
- Access, backup, support, and escalation arrangements remain workable if the primary user is unavailable.
GSTN’s e-invoicing setup guide covers enablement, registration, reporting, document scope, and the distinction between portal enablement and legal obligation. For the definition and process distinction, see the GSTN E-Invoicing FAQs.
Frequently Asked Questions
Does an IRP submission file my GST return too?
No. The IRP step reports specified document details and returns an IRN and QR code; it is distinct from reconciling those documents with the business’s GST returns. Keep the invoice record and IRP response available to support the separate return and accounting workflow.
Is portal enablement proof that my business must use e-invoicing?
No. GSTN treats enablement as an operational status, not a legal determination. Assess PAN-level aggregate turnover, the applicable notified class, and exemptions separately, and confirm the current rules for the business’s facts.
Can I create the invoice directly on the government portal?
The business creates the original invoice in its accounting, billing, or ERP system. It then reports specified data to an authorized IRP, which validates the submission and returns the IRN and QR code.
Which documents should I send to the IRP?
The official overview identifies GST invoices, credit notes, and debit notes for B2B supplies, supplies to SEZs, exports, and deemed exports. Confirm the current rules and schema for the business’s exact transaction mix, and do not assume every ordinary B2C sale follows the same process.
What should I do if an invoice is rejected by the IRP?
A rejected submission has not completed the successful validation-and-response cycle, so do not treat it as an issued e-invoice carrying a valid IRN. Have the responsible staff member review the validation issue, correct the source data as appropriate, and resubmit within any applicable reporting deadline; consult current portal guidance or a tax professional if the error affects compliance.
The Bottom Line
Bottom line: Assess the ₹5 crore threshold and exemptions on a PAN basis, separate legal applicability from portal enablement, and map the covered documents before configuring software. Create each invoice in your own system, report it to an authorized IRP, issue it only after receiving the IRN and QR code, and reconcile the signed response with your accounts. If AATO is ₹10 crore or more, build a control that reports invoices, credit notes, and debit notes within 30 days of the document date.
