E-Invoicing Rules for Indian E-commerce Sellers in 2026

E-Invoicing Rules for Ecommerce Sellers in India in 2026

The e-invoicing rules for ecommerce sellers in India in 2026 mainly depend on the seller’s aggregate annual turnover, the type of customer, and whether the transaction is taxable, an export, or a supply through an electronic commerce operator. Selling on Amazon, Flipkart, Meesho, Shopify, your own website or another marketplace does not automatically make every seller liable to generate e-invoices.

For most businesses, e-invoicing applies when the aggregate turnover has exceeded the notified threshold in any preceding financial year, subject to GST exemptions and transaction-specific rules. Sellers should also distinguish between an e-invoice for B2B or export transactions and the invoice issued to an ordinary retail customer.

What E-Invoicing Means for an Ecommerce Seller

An e-invoice is not simply a PDF invoice emailed to a customer. It is a GST invoice whose key details are reported to an authorised Invoice Registration Portal, or IRP.

The IRP validates the invoice data and generates:

• An Invoice Reference Number, commonly called an IRN
• A digitally signed invoice payload
• A QR code containing invoice details
• A digitally signed QR code for verification

The seller can then share the invoice in a readable format, such as PDF, XML or a marketplace-generated document. The document may look similar to an ordinary invoice, but it must contain the IRN and the QR code when e-invoicing applies.

The invoice is not considered a valid GST tax invoice if a registered person required to issue an e-invoice issues it without reporting the invoice to the IRP. This can create problems for the seller and the buyer. The buyer may face difficulty claiming input tax credit, while the seller may face tax, penalty, reconciliation and audit issues.

E-invoicing is separate from filing a GST return. Reporting an invoice to the IRP does not replace:

• GSTR-1 filing
• GSTR-3B filing
• E-commerce operator reconciliation
• GST payment
• TCS reconciliation, where applicable
• Income-tax and accounting records

The IRP data generally helps populate GST return-related information, but the seller remains responsible for checking and filing correct returns.

Who Must Generate E-Invoices in 2026?

The general threshold for mandatory e-invoicing is an aggregate turnover of more than ₹5 crore in any preceding financial year, based on the applicable GST rules and notifications.

The important word is aggregate. A seller should not look only at turnover from one marketplace or one GST registration. The assessment generally considers the person’s aggregate turnover on an all-India PAN basis under GST, subject to the legal definition and applicable exclusions.

For example, a business may sell through:

• Its own website
• Amazon or Flipkart
• A D2C store
• Wholesale distributors
• Social commerce channels
• Offline retail outlets

If the business crosses the applicable threshold based on its aggregate turnover in a preceding year, e-invoicing may apply to its covered transactions even if the turnover of each individual channel is lower.

Turnover does not mean only marketplace sales

A common mistake is to compare only the value settled by the ecommerce platform. GST turnover can include taxable supplies, exempt supplies, exports and other components covered by the definition of aggregate turnover. It may also include supplies made by different GST registrations under the same PAN.

The business should review its GST records, financial statements and registration data rather than relying only on marketplace reports.

Existing businesses and new sellers

A business that crossed the threshold in an earlier financial year can remain covered even if its turnover falls later, unless the applicable law or a specific exemption changes its position.

A newly established seller should monitor turnover from the beginning. Waiting until the marketplace labels the seller as an e-invoice taxpayer can result in missed invoices, cancelled documents and reconciliation problems.

Exceptions and exempt categories

Some entities and types of services are exempt from e-invoicing under GST notifications. The exempt categories have included, subject to the exact conditions:

• Insurers
• Banking companies and financial institutions
• Non-banking financial companies
• Goods Transport Agencies
• Suppliers of passenger transportation services
• Suppliers of services involving admission to exhibition of cinematograph films
• Special Economic Zone units, subject to the relevant notification
• Government departments
• Local authorities

The exemption is not a general exemption for every business that sells through an ecommerce platform. It must apply to the taxpayer or transaction in the manner specified by the law.

A business should also avoid confusing a SEZ unit with an SEZ developer. Their GST treatment can differ. A composition taxpayer generally cannot issue a regular taxable tax invoice and therefore normally does not generate e-invoices in the same way as a regular taxpayer.

Which Ecommerce Transactions Need E-Invoicing?

Ecommerce businesses usually have two broad transaction categories:

1. Supplies to registered businesses, including B2B sales
2. Supplies to final consumers, including B2C sales

The e-invoice treatment is different for each.

B2B sales

If an ecommerce seller is registered under GST, crosses the applicable threshold and is not exempt, B2B taxable invoices generally need to be reported to the IRP.

This includes sales where the customer provides a valid GSTIN and asks for a business invoice. It can include:

• Orders placed through a marketplace
• Orders on the seller’s own website
• Bulk orders received through email or a sales team
• Sales to retailers and distributors
• Supplies to offices, schools, clinics or companies
• Drop-shipped orders where the seller remains the supplier

The buyer’s GSTIN must be checked carefully. A wrong GSTIN can affect the buyer’s input tax credit and create a mismatch between the invoice, e-way bill and GST return.

Export invoices

Export invoices are covered by e-invoicing requirements where the seller is otherwise liable and the transaction falls within the notified categories.

The invoice must generally carry the correct export information, including details such as:

• Whether the export is under payment of IGST or under a Letter of Undertaking
• Port code, where required
• Shipping bill-related information when available
• Recipient and delivery details appropriate to the export
• Currency and taxable value
• Relevant place-of-supply details

An ecommerce seller exporting goods through a courier, logistics company or cross-border marketplace should coordinate invoice data with the shipping and customs process. The marketplace’s international settlement statement is not a substitute for a correctly issued GST export invoice.

B2C retail sales

A normal B2C invoice to an individual consumer is generally not reported as an e-invoice through the IRP in the same manner as a B2B invoice. The seller must still issue a proper GST invoice where required and account for the sale in its GST records.

This distinction is important. “No IRN for a normal retail invoice” does not mean “no invoice” and does not mean “no GST compliance”.

Certain large registered taxpayers may have separate requirements relating to dynamic QR codes for B2C invoices. This is a different requirement from B2B e-invoicing. Whether it applies depends on the taxpayer’s turnover, the applicable notification and the nature of the sale.

A seller should not place an IRN on every retail invoice simply because the order was received through an ecommerce website. It should configure the system based on the transaction type and the current GST rules.

Supplies through an ecommerce operator

A seller may sell goods through an ecommerce operator without the operator becoming the supplier for GST purposes. In that situation, the seller usually remains responsible for issuing the invoice for the goods.

There are separate rules where an ecommerce operator is liable to pay GST under section 9(5) of the CGST Act for specified services. In such cases, the operator’s invoicing responsibility may differ from an ordinary sale of goods through a marketplace.

The contract, business model and nature of supply matter. A seller should not assume that the marketplace will issue every invoice or that the marketplace’s settlement report is sufficient for GST purposes.

Seller, Marketplace and Customer Responsibilities

An ecommerce transaction can involve the seller, the marketplace, the logistics provider and the customer. Each party may have different responsibilities.

The seller’s responsibility

The seller should generally ensure that:

• The GST registration details are correct
• The invoice is issued in the legal name of the supplier
• The customer’s GSTIN is captured correctly for B2B orders
• The place of supply is determined correctly
• The tax rate and HSN or SAC are correct
• The invoice is reported to the IRP when required
• The IRN is linked to the final invoice
• Credit notes and debit notes are handled correctly
• GST returns reconcile with books and marketplace reports
• The invoice and related records are retained for the prescribed period

The marketplace’s responsibility

The ecommerce operator may collect information, facilitate payment, generate a document, collect GST TCS where applicable, and send order data to the seller. These functions do not always make it responsible for the seller’s tax invoice.

The platform may have its own invoice template, but the seller should check whether it supports:

• Seller GSTIN
• Buyer GSTIN
• IRN
• QR code
• HSN or SAC
• Place of supply
• Shipping and billing addresses
• Tax breakup
• Credit note references
• Returns and cancellation status

Where the seller uses marketplace fulfilment, the shipping address and billing address should not be assumed to determine the place of supply without checking GST rules.

The customer’s responsibility

A business customer wanting input tax credit should provide its correct GSTIN before the order is invoiced. If the order is billed as B2C and the customer later asks for a B2B invoice, the seller may need to cancel and reissue the document subject to the applicable GST process.

The customer should preserve the e-invoice received from the seller and check the invoice details before claiming credit.

Key E-Invoice Details Ecommerce Sellers Must Get Right

Ecommerce invoices contain more than the product name and selling price. The following fields commonly cause errors.

GSTIN and legal names

The supplier’s GSTIN and legal name should match the registration. The buyer’s GSTIN should be validated against the GST portal or a reliable accounting integration.

A marketplace profile name, brand name or trade name may not be the legal name required on the tax invoice.

HSN and product mapping

The HSN code should match the product being sold. Businesses should maintain a product master with:

• SKU
• Product description
• HSN code
• GST rate
• Unit of measurement
• Applicable cess
• Whether the item is taxable, exempt or nil-rated

The level of HSN detail required can depend on the taxpayer’s turnover and the applicable GST rules. Incorrect HSN mapping can affect tax rate, e-invoice validation and return reporting.

Place of supply

The place of supply determines whether the transaction is interstate or intrastate and which tax components appear on the invoice.

For goods, the delivery location is often relevant. For services, different place-of-supply rules can apply. An online order routed through a marketplace is not automatically an interstate supply merely because the platform has offices in another state.

Discounts and marketplace deductions

Seller-funded discounts, platform-funded discounts, coupons, shipping charges, cashbacks and commissions should be mapped correctly.

A marketplace commission deducted from the seller’s settlement is not necessarily a reduction in the seller’s taxable value. The seller may need to account for the marketplace’s service invoice separately.

The invoice should show the actual taxable value and tax treatment according to the contractual arrangement and GST rules. It should not simply copy the net payout shown in the marketplace settlement report.

Returns, cancellations and credit notes

Returns are frequent in ecommerce. The seller should create a process for connecting:

• Original order number
• Original invoice number
• IRN
• Return or cancellation reason
• Delivery status
• Refund date
• Credit note, where required
• GST return treatment

An order cancellation before invoice generation may be handled differently from a return after delivery and invoicing. The software should not automatically issue a credit note for every cancelled order without checking whether a supply and tax invoice were actually created.

The 30-Day Reporting Rule for Larger Taxpayers

From 1 April 2025, taxpayers with aggregate annual turnover of ₹10 crore or more are subject to a time limit for reporting certain invoices, credit notes and debit notes to the IRP. Such documents generally need to be reported within 30 days from the document date.

This rule is particularly relevant to ecommerce sellers because orders can be created in one system, fulfilled through another and invoiced in batches. A delayed integration or month-end upload can create a compliance failure even where the invoice itself is otherwise correct.

Sellers in this category should avoid treating the IRP as a monthly upload utility. Their systems should generate and report the document soon after the invoice is issued.

The rule should be reviewed against the current advisory and notification for the relevant document types and turnover calculation. Businesses close to the ₹10 crore level should implement the process before crossing it rather than waiting for an ERP warning.

E-Invoicing, E-Way Bills and GST Returns

These systems are connected but not interchangeable.

An e-invoice may provide information used for e-way bill generation, but an IRN does not automatically satisfy every e-way bill requirement. Product movement, vehicle details, transporter information and other fields may still be needed.

Similarly, the marketplace’s TCS statement does not replace the seller’s responsibility to report outward supplies and reconcile tax liability.

Penalties and Business Risks

Issuing an invoice without a required IRN can create several risks. Depending on the facts, the department may question whether a valid invoice was issued, whether input tax credit is available to the recipient and whether penalties apply.

Other practical risks include:

• Buyer complaints about blocked or disputed input tax credit
• E-way bill generation failures
• Rejection of invoice data by the IRP
• GST return mismatches
• Incorrect tax collected from customers
• Delays in marketplace settlement reconciliation
• Repeated invoice cancellation and reissue
• Difficulty explaining records during a GST audit

A failed IRP request is not automatically a tax violation if the business corrects the data and reports the invoice through the proper process. However, a seller should not silently continue with manually numbered invoices where e-invoicing is mandatory.

The correction process should be documented. Keep the original payload, error message, corrected payload, IRN, invoice PDF and relevant communication with the marketplace or software provider.

Choosing Software for Ecommerce E-Invoicing

A small seller may manage invoices through GST-compatible software. A growing D2C brand or marketplace seller may need an integration between its ecommerce platform, accounting system, inventory software, shipping application and IRP provider.

Before selecting a tool, check whether it supports:

• Multiple GST registrations
• Multiple sales channels
• B2B, B2C and export logic
• Marketplace order imports
• Real-time or prompt IRP reporting
• IRN and QR code storage
• GSTIN validation
• HSN and tax-rate controls
• Credit notes and returns
• Failed-request retry handling
• Duplicate invoice prevention
• E-way bill integration
• GSTR-1 reconciliation
• TCS reconciliation
• Audit logs and user permissions
• GST-compliant data export

A PDF generator alone is not enough. The system must prevent the business from issuing one invoice in the marketplace and a second invoice in the accounting software for the same supply.

API integration or manual upload?

Manual upload may work for a lower order volume if the business has strong checking procedures. It becomes risky when orders arrive from several channels or when return volumes are high.

API-based integration can reduce repetitive work, but it does not eliminate the need for tax configuration. Incorrect product masters, wrong GSTINs or bad place-of-supply rules will be transmitted faster through an integration.

The right design depends on order volume, number of GST registrations, sales channels, product categories and whether the business exports.

Practical Compliance Checklist for Sellers in 2026

Use the following checklist before the next filing cycle:

1. Calculate aggregate turnover on the relevant PAN basis, not only by marketplace.
2. Check whether the business crossed the ₹5 crore e-invoice threshold in any preceding financial year.
3. Check whether the business is subject to the 30-day reporting rule applicable to taxpayers at or above ₹10 crore.
4. Identify exempt categories and confirm that the exemption actually applies.
5. Separate B2B, B2C, export and SEZ transactions in the order system.
6. Validate customer GSTINs before generating B2B invoices.
7. Map every SKU to the correct HSN and GST rate.
8. Configure interstate and intrastate place-of-supply rules.
9. Generate the IRN before sending a covered invoice to the customer.
10. Store the IRN, QR code and signed invoice data with the order record.
11. Connect returns and cancellations to the original invoice.
12. Reconcile marketplace settlements, GST TCS, books and GST returns.
13. Test e-way bill data for products that require movement documentation.
14. Give authorised staff a process for IRP errors and duplicate invoices.
15. Review the setup whenever the business adds a marketplace, state registration, product category or export channel.

GST notifications and portal requirements can change. The seller should verify the current position with a GST professional or refer to official CBIC, GSTN and IRP communications before relying on an old software setting.

Frequently Asked Questions

Does selling on Amazon or Flipkart automatically require e-invoicing?

No. Marketplace participation alone does not decide e-invoice applicability. The seller’s aggregate turnover, transaction type, GST registration status and any applicable exemption are the key factors.

Do ecommerce sellers need an IRN for every customer invoice?

No. Normal B2C retail invoices are not treated the same as covered B2B and export invoices under the e-invoice system. A seller may have to issue proper GST invoices to all relevant customers, but the IRN requirement depends on the transaction and the seller’s liability.

Is an ecommerce marketplace responsible for issuing the seller’s invoice?

Not always. In a normal sale of goods, the seller may remain the supplier and invoice issuer even when the marketplace processes the order and payment. The responsibility can differ for specified services where the ecommerce operator is liable to pay GST under section 9(5).

Can a seller generate one e-invoice at the end of the month for all orders?

This can create risk and may not be permitted for the relevant taxpayer or document. Sellers subject to the reporting time limit, including those covered by the 30-day rule, need a process that reports documents within the prescribed period.

What happens if the seller’s e-invoice contains a wrong GSTIN?

The seller should follow the applicable cancellation and reissue process rather than editing an IRN silently. The buyer should be informed, and the corrected invoice, credit note or cancellation should be reconciled with GST returns and marketplace records.

Does an e-invoice replace the GST return?

No. E-invoicing registers specified invoice data with the IRP. The seller must still file GST returns, pay tax, reconcile TCS and maintain accounting records.

Where to Start

First, calculate aggregate turnover across all GST registrations and sales channels. Then classify your orders into B2B, B2C, export and other categories, and check whether your accounting or ecommerce software can generate, report and store IRNs without duplicate invoices.

Document the product master, GSTIN validation, return process and marketplace reconciliation before order volume increases. If you need help reviewing an ecommerce billing workflow or planning a GST-compatible integration, talk to the Govindani Infotech team on WhatsApp; pricing is confirmed by the team there.