E-invoicing India versus the Peppol 4-corner model

Mandatory electronic invoicing has grown along two lines worldwide. E-invoicing India follows the first: clearance. Every B2B invoice must be reported in advance to an Invoice Registration Portal (IRP), which returns an Invoice Reference Number (IRN) and a signed QR code, and without that number the document is legally not an invoice. The second line is the Peppol 4-corner model, where no government body sits in the transaction flow and an invoice is valid because it meets the standard and has been delivered. Any company invoicing across borders meets both, often inside one ERP programme.

This article sets out what applies in India as at 9 September 2026, places it alongside countries that chose Peppol or another clearance system, and closes with a checklist for the business and the integrator.

Why e-invoicing India is on your agenda

With India in your supply chain you face three challenges, wherever your company is established.

You buy from an Indian supplier. The mandate covers exports, with or without payment of tax, and supplies to Special Economic Zones, not only domestic B2B. An Indian supplier above the threshold who exports to you must generate an IRN. If none exists, the invoice is not a valid invoice under Indian law. That does not decide your own VAT or GST position, but it affects your customs file, your payment certainty and your supplier’s compliance standing.

You sell into India or run an Indian entity. With a GST registration above the threshold the obligation applies to your own invoicing, and your ERP has to feed a system that makes the document valid only after the authority replies.

You build or run the integration. Supporting both worlds means combining two process models that behave differently. One delivers asynchronously without blocking. The other requires synchronous approval and halts the outbound process the moment the IRP returns an error.

How the Indian clearance model works: IRP, IRN and QR code

The legal core sits in Rule 48 of the CGST Rules. Sub-rule 48(4) requires notified classes of registered persons to prepare their invoice by uploading the particulars of FORM GST INV-01 and thereby obtaining an Invoice Reference Number. Sub-rule 48(5) states that every invoice issued by such a person in any other manner “shall not be treated as an invoice”. That is a validity rule, not a penalty clause.

The threshold

The obligation depends on Aggregate Annual Turnover (AATO). Notification No. 10/2023 – Central Tax of 10 May 2023 substituted “five crore rupees” for “ten crore rupees”, effective 1 August 2023. Five crore equals 50 million Indian rupees (INR). That threshold still stands as at 9 September 2026, and no notification has lowered it further. The test runs across every financial year since 2017-18, so a supplier who crossed the line once stays in scope.

The process steps

1. The source system assembles the invoice data in the prescribed JSON schema.
2. The data goes to an Invoice Registration Portal, through a direct API connection or a GST Suvidha Provider.
3. The IRP validates the payload, checks for duplicates on supplier GSTIN, document number, document type and financial year, and generates an IRN in the form of a 64-character hash.
4. The IRP returns the digitally signed invoice data together with a signed QR code.
5. Only then may the invoice be issued, carrying that QR code.

The QR code carries both GSTINs, the invoice number and date, the taxable value, the total tax amount, the number of line items, the HSN code of the main line item, and the IRN with its generation date. It is verifiable evidence.

Two properties are routinely missed. GSTN documentation states that the IRP will not store or archive e-invoice data, leaving archiving entirely with the taxpayer. And cancellation is possible only within 24 hours of reporting, and is blocked once an active e-way bill exists, after which a credit note is the only route.

E-way bill, reporting window and two-factor authentication

Movement of goods needs a second document. Under Rule 138 an e-way bill is required above a consignment value of 50,000 rupees, and since 1 January 2025 it may only be created against a base document dated within 180 days, with extensions capped at 360 days.

A reporting window applies as well. Taxpayers with an AATO of ten crore rupees and above must report invoices, credit notes and debit notes to the IRP within 30 days of the document date, a threshold that moved from one hundred crore to ten crore with effect from 1 April 2025. The IRP rejects documents outside the window, and without an IRN there is no valid invoice.

Two-factor authentication on the e-invoice and e-way bill systems was phased in as well: from 1 January 2025 above twenty crore AATO, from 1 February 2025 above five crore, and from 1 April 2025 for all taxpayers and transporters. The one-time password arrives by SMS, the Sandes app or the NIC-GST-Shield app.

Two families: clearance against the Peppol 4-corner model

India is not alone. The clearance idea originated in Latin America, where Brazil, Mexico and Chile were first to require technical approval of the invoice by the tax administration before the transaction. Italy made B2B invoicing through the central Sistema di Interscambio mandatory from 1 January 2019, in the FatturaPA format. Poland uses Krajowy System e-Faktur, mandatory from 1 February 2026 for the largest businesses and from 1 April 2026 more broadly. Malaysia phased in MyInvois from August 2024, with the tax authority validating the document and returning a unique identifier and a QR code. India applies the same logic: approval first, identification number as proof.

The Peppol model works the other way round. Four corners: sender, sender’s serviceprovider, receiver’s serviceprovider, receiver. Peppol Authorities supervise the Peppol Serviceproviders but stay out of the transaction flow. The Australian Taxation Office puts its position plainly: it receives no copy of the e-invoice and cannot view the contents.

The geographic spread is now wide. Peppol Authorities operate in Australia, Belgium, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Japan, Luxembourg, Malaysia, the Netherlands, New Zealand, Nigeria, Norway, Oman, Poland, Portugal, Singapore, Slovakia, Sweden, Taiwan and the United Arab Emirates, with NHS Supply Chain as the authority for England. A few examples show how differently countries build on that base.

• Japan. The Digital Agency has been the Peppol Authority since September 2021 and maintains JP PINT, aligned with Peppol PINT BIS Billing and tied to the qualified invoice system.
• Singapore. InvoiceNow runs on the Peppol network. The GST InvoiceNow Requirement started on 1 November 2025 for newly incorporated companies registering voluntarily for GST and extended on 1 April 2026 to all new voluntary registrants, with further phases towards 2031.
• Australia and New Zealand. Both use the shared A-NZ Peppol specification. Australian Commonwealth agencies have had to process e-invoices within five days since 1 July 2022, without a general B2B mandate.
• United Kingdom. The government confirmed in 2026 that Peppol will be the core interoperability network and that an e-invoicing mandate follows in 2029, as covered in our guide to the UK e-invoicing mandate starting April 2029.
• Germany. Since 1 January 2025 businesses must be able to receive e-invoices in EN 16931 format. The issuing obligation follows on 1 January 2027 above 800,000 euro turnover and on 1 January 2028 for all others.
• France. From 1 September 2026 every business in scope must be able to receive e-invoices, and large and mid-sized companies issue them through Plateformes Agréées, which also transmit transaction and payment data to the tax administration. Smaller businesses follow on 1 September 2027.
• Belgium. Since 1 January 2026 all Belgian VAT-registered businesses exchange structured electronic invoices, with Peppol as the default network and no central portal. The general tolerance period expired during the first quarter of 2026, and the e-reporting step towards a 5-corner arrangement is scheduled for 2028.
• Malaysia. Both worlds at once: MDEC acts as Peppol Authority while the legal submission runs through MyInvois.

At EU level, ViDA sets direction: adopted on 11 March 2025 and in force since 14 April 2025, it applies digital reporting requirements to cross-border B2B transactions from 1 July 2030, with national systems aligning by 1 January 2035. That is one regional track alongside the national choices above.

Where the two models collide

India has no Peppol Authority and no Peppol connection to the IRP. Supporting both brings five concrete challenges.

• Sequence. Peppol delivers and reports nothing to a tax authority afterwards. India approves first, so your outbound process gains a blocking step with no Peppol equivalent.
• Transport. Peppol uses AS4 between accesspoints, with an SMP and an SML for addressing. India uses token-based REST APIs to a single portal, so an accesspoint cannot satisfy the Indian obligation and an IRP integration produces no Peppol delivery.
• Identification. Peppol uses participant identifiers based on recognised schemes. India uses a GSTIN per state and per entity, so one group can hold dozens, each with its own credentials.
• Semantics. Peppol BIS Billing follows EN 16931. The Indian INV-01 schema carries fields with no counterpart there, such as HSN codes, place of supply by state code and the GST reverse charge flag.
• Evidence. In Peppol your serviceprovider’s delivery confirmation is your proof. In India it is the signed IRP response containing the IRN, which you retain yourself.

The split reaches beyond India. We examined the same divide in our comparison of the Greek clearance model and the Peppol approach.

Five challenges you run into in practice

The PDF without a QR code. An Indian supplier emails a tidy invoice with no QR code. If that supplier is in scope, the document is not an invoice, and booking it anyway leaves a payables position on a document that may later be withdrawn and reissued.

The invoice that arrives too late. A quantity dispute holds the invoice for five weeks. For a supplier at ten crore AATO or above the window has closed and the IRP refuses the IRN. The supplier reissues under a new number, and purchase order, goods receipt and invoice fall out of alignment.

Two versions of the truth after a correction. Corrections after 24 hours run through credit notes, which must themselves be reported within the window. If your ERP keeps only the latest version, an Indian audit cannot be reconstructed.

A shipment standing still. The e-way bill is missing or the base document is older than 180 days, so goods wait while the invoice is already approved.

An API change nobody scheduled. GSTN announced in June 2026 that from 1 August 2026 the ship-to GSTIN must be captured in the e-invoice API and the e-way bill by IRN API. Teams that do not track these advisories discover them when invoices start bouncing.

Practical checklist for the business and the integrator

Purchasing: you receive invoices from India

1. Ask each Indian supplier in writing whether they fall under the mandate and which GSTINs they use, and record it in your vendor master data.
2. Require in your purchasing terms that invoices from in-scope suppliers carry an IRN and a valid QR code, and that the supplier provides the signed IRP response on request.
3. Check on receipt that the QR code is present and readable, using the verification facility of the e-invoice system. Make this a fixed step, not a sample check.
4. Reconcile the QR code values against the invoice header in your ERP: both GSTINs, invoice number, date, taxable value and tax amount. A mismatch means a different document from the one reported to the IRP.
5. Store the QR code and, where available, the signed IRP response with the invoice. The IRP archives nothing on your behalf.
6. Define an exception route for invoices without an IRN: block and return to the supplier, never approve manually as a workaround.
7. For goods, request the e-way bill number and link it to the shipment so delays surface early.
8. Cap your own dispute turnaround. With suppliers at ten crore AATO or above, every week of discussion consumes the 30-day window.

Sales and your own Indian entity

1. Determine per GST registration whether you exceed five crore rupees AATO, tested across every financial year since 2017-18.
2. Make invoice numbering unique per GSTIN and per financial year, since the IRP rejects duplicates on that combination.
3. Release the invoice to the customer only after the IRN has been returned. Releasing earlier means sending invalid documents.
4. Assign who may cancel within 24 hours, document the credit note procedure that applies afterwards, and treat the 30-day window as a hard internal deadline.

Integration: what the serviceprovider or integrator has to build

1. Choose the access route deliberately: direct API access with IP whitelisting, or through a GST Suvidha Provider. Record who owns the tokens and how they rotate.
2. Support two-factor authentication without depending on an individual. No shared mobile numbers in production.
3. Treat the IRP call as a synchronous, blocking step with idempotency. On timeout, query whether the IRN already exists before resubmitting.
4. Build error handling per IRP error code, separating recoverable validation errors from final rejections such as breaching the 30-day window.
5. Monitor the age of documents in the queue and raise alerts well before day 30.
6. Persist the full signed IRP response, including IRN and QR payload, with a retention period that satisfies both Indian and local requirements.
7. Implement the 1 August 2026 change: mandatory ship-to GSTIN in the e-invoice API and the e-way bill by IRN API, URP for unregistered recipients, and the new state code and PIN code validations.
8. Keep the Indian flow architecturally separate from your Peppol flow. An accesspoint performs AS4 transport inside the Peppol 4-corner model and has no role in clearance, so one generic connector for both builds in wrong assumptions about delivery and validity.
9. Make your monitoring distinguish delivered, reported and cleared. In Peppol, delivered is enough. In clearance countries it is not.
10. Subscribe to GSTN and NIC advisories and schedule a fixed quarterly slot for schema and API changes. The same discipline applies to KSeF and MyInvois.

What is not yet settled

The GST Council announced an approach to B2C e-invoicing in September 2024, with a voluntary pilot in selected sectors and states and a nationwide rollout that publications place in financial year 2026-27. That remains a stated direction rather than a published obligation, so allow for the expansion but do not build irreversible decisions on a date that has not appeared in a notification. The same caution applies to any further reduction of the AATO threshold below five crore rupees.

If you want the underlying model clear before making country decisions, our guide to Peppol invoices and the 4-corner model covers the basics.

Sources

1. CBIC, Rule 48 CGST Rules, sub-rules 48(4) and 48(5)
2. Notification No. 10/2023 – Central Tax, 10 May 2023, threshold lowered to five crore rupees from 1 August 2023
3. GSTN, GST e-invoice/IRN System FAQ, version 1.4
4. GSTN, GST e-invoice/IRN System FAQ, version 1.3, on cancellation, archiving, exports and SEZ
5. GSTN advisory on the 30-day reporting window for AATO of ten crore rupees and above, effective 1 April 2025
6. e-Invoice System, Verify Signed Invoice
7. Advisory on updates to the e-way bill and e-invoice systems: phased two-factor authentication and the 180-day rule
8. GSTN advisory on mandatory ship-to GSTIN in the e-invoice and e-way bill APIs from 1 August 2026
9. CIAT, models for transmitting electronic invoice information and the Latin American origin of the clearance model
10. European Commission, eInvoicing in Italy, mandatory B2B invoicing through SdI since January 2019
11. European Commission, eInvoicing in Poland, KSeF phasing in 2026
12. European Commission, eInvoicing in Germany, receipt obligation 2025 and issuing obligations 2027 and 2028
13. Direction générale des Finances publiques, practical guide to facturation électronique, calendar 2026 and 2027
14. FPS Finance, official information on the Belgian e-invoicing obligation since 1 January 2026
15. HM Government, Tax Update 2026, Peppol as core network and the 2029 e-invoicing mandate
16. Digital Agency Japan, JP PINT and the Japan Peppol Authority
17. IRAS, FAQ on the GST InvoiceNow Requirement, phasing from November 2025
18. Australian Taxation Office, eInvoicing through the Peppol network
19. Overview of the Malaysian MyInvois phasing and MDEC’s role as Peppol Authority
20. Peppol, list of Peppol Authorities
21. European Commission, VAT in the Digital Age (ViDA), timeline and milestones
22. Directive (EU) 2025/516

Your next step

Companies making e-invoicing India and Peppol work inside one chain rarely need another portal. What helps is a solution that handles your Peppol traffic reliably in every country where you invoice and sits alongside a separate, well-monitored IRP integration. On Peppol.nu you can compare Peppol Serviceproviders by software environment, invoice volume, country coverage and organisation size, and see which of them support international mandates as well.