Skip to main content

What IRP reporting is

India requires B2B invoices above the turnover threshold to be reported to the Invoice Registration Portal (IRP), which returns a signed IRN and a QR code. Recurso submits finalized B2B invoices to the IRP automatically and retries transient failures.
This is India’s IRN clearance — separate from EU e-invoicing. Concept detail + statuses: E-Invoicing (India). Assumes GST is set up.

Prerequisites

  • India GST configured — this guide adds IRN clearance on top.
  • IRP/GSP credentials: client id, client secret, username, password, and your GSTIN.
  • B2B customers with valid GSTINs, and invoice lines carrying HSN/SAC codes.
  • An API key for the API call below, or dashboard access to Settings.

Step 1: Connect your IRP credentials

Provide your IRP/GSP connection. In the dashboard, go to Settings → E-Invoicing (IRP); or via the API:
Test with environment: "sandbox" first — sandbox submissions are not reported to the GST portal. Switch to production only once test invoices clear cleanly.

Step 2: Keep customer + line data complete

The IRP rejects incomplete invoices. Make sure B2B customers have a valid GSTIN and address, and that lines carry HSN/SAC codes — the most common failures are a wrong buyer GSTIN or a missing field.

Step 3: Finalize a B2B invoice

Once enabled, every finalized B2B invoice is submitted to the IRP; on success the IRN, acknowledgement number, and signed QR are attached. Transient failures are retried automatically with backoff.

Verify your setup

1

The connection tests clean

Recurso can reach the IRP with your credentials (sandbox first).
2

A B2B invoice gets an IRN

A finalized B2B invoice shows e-invoice status generated with an IRN + QR.
3

Failures retry, not stick

A transient failure reschedules and recovers rather than staying failed.

Next steps