FICO India e-Invoicing Part 1: IRP, IRN and the Signed QR Code

📌 KEY POINTS
✅ Businesses above the notified turnover threshold must report B2B invoices, credit/debit notes and exports to an Invoice Registration Portal (IRP).
✅ The IRP validates the data and returns an Invoice Reference Number (IRN) and a digitally signed QR code.
✅ An in-scope invoice without an IRN is not a valid tax invoice, so the IRN must exist before the invoice is sent.
✅ Data reported to the IRP flows into the supplier's GSTR-1, reducing manual return preparation.
⚠️ Thresholds and scope are changed by notification — keep them configurable and verify current values.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
This series covers e-invoicing and e-way bills. Part 1 explains the model; Part 2 the SAP solution; Parts 3–4 operations.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHAT E-INVOICING IS
E-invoicing in India does not mean creating invoices on a government site. The business still creates invoices in SAP, but for in-scope documents it reports the invoice data in a standard JSON schema to an Invoice Registration Portal. The portal validates, registers and digitally signs it. Scope covers B2B supplies, exports and credit and debit notes for businesses above a notified aggregate turnover threshold, which has been lowered several times.

━━━━━━━━━━━━━━━━━━━━
▶ 2. IRN AND QR CODE
The IRP generates an Invoice Reference Number — a unique hash based on the supplier GSTIN, document type, number and financial year — and returns it with a signed JSON and a QR code containing key invoice details. The QR code must be printed on the invoice. Because the IRN is derived from the document number, the same number cannot be registered twice in a financial year.

━━━━━━━━━━━━━━━━━━━━
▶ 3. VALIDITY OF THE INVOICE
For in-scope transactions, an invoice without a valid IRN is not a valid tax invoice, and the buyer may not get credit. This changes the business process: the invoice output to the customer should be triggered only after the IRN has been received, and any failure must be visible quickly.

━━━━━━━━━━━━━━━━━━━━
▶ 4. LINK TO RETURNS AND E-WAY BILL
Registered invoices are passed by the system to GSTR-1, so outward supply reporting increasingly comes from the IRP rather than manual uploads. Where transport details are provided, an e-way bill can also be generated from the same data. Reconciliation between SAP, IRP and GSTR-1 becomes the control.

━━━━━━━━━━━━━━━━━━━━
▶ 5. WHO IS INVOLVED
Billing users create documents, the compliance solution or GSP/ASP partner connects SAP to the IRP, IT operates the interface, and the tax team owns scope and exceptions. Clear ownership of failed documents is the most important organisational decision.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Identify which document types and business places are in scope.
2. Trace the round trip: billing → JSON → IRP → IRN and QR → print.
3. Decide when invoice output is released relative to IRN receipt.
4. Assign owners for failed submissions.

✅ CHECKPOINT: you can explain the IRN round trip and why output must wait for the IRN.

A company printed and emailed invoices immediately on billing, before IRN registration. When the IRP rejected 3% of invoices for HSN and GSTIN errors, customers already had invoices without QR codes and could not claim credit. Output was changed to trigger only after successful registration, and a daily report of pending and failed documents was introduced.

• Sending invoices to customers before IRN is received.
• Hard-coding thresholds and scope.
• No owner for rejected documents.
• Reusing a document number after cancellation in the same financial year.

• Trigger output after IRN receipt.
• Configurable scope per business place and document type.
• Daily monitoring of pending and failed submissions.
• Reconcile SAP, IRP and GSTR-1 monthly.

Interviewers ask what an IRN is, how it is generated, and how you change the billing process so customers only receive valid e-invoices.