SAP Business One's E-Billing Connector talks to the IRP for you. A document stuck in the queue never gets there

SAP Business One's e-invoicing feature has gone through three generations in five years — a manual JSON-export step, a dedicated E-Billing protocol, and now a direct GSP connector. Only the newest one actually talks to the government's Invoice Registration Portal for you. Which one applies to a given installation isn't a choice — it's fixed by which SAP feature package it's running.

Three generations of the same feature, still in the documentation together

e-Invoicing itself is not a SAP feature — it is a reporting mechanism under Rule 48(4) of the CGST Rules. The rule fixes no threshold of its own; it delegates the coverage test to a notification. Under Notification 13/2020-Central Tax dated 21 March 2020, as amended most recently by Notification 10/2023-CT w.e.f. 1 August 2023, any registered person — other than a government department, a local authority, an SEZ unit, and the categories carved out under Rule 54(2)-(4A) (insurers, banks/NBFCs, goods transport agencies, passenger transport and multiplex-cinema suppliers) — whose aggregate turnover in any preceding financial year from 2017-18 onwards exceeds Rs 5 crore — unchanged since 1 August 2023 and current as of 18 September 2026 — must report B2B invoices, credit and debit notes, and exports through the portal. That "any preceding year" wording matters: once a business crosses Rs 5 crore in a single year, e-invoicing applies permanently, even if turnover later falls back below the line. Where a business to whom Rule 48(4) applies fails to comply — under Rule 48(5) — the document "shall not be treated as an invoice" at all, which is what eventually turns into a buyer's blocked ITC claim rather than just a supplier-side paperwork problem. Separately, since 1 April 2025 a taxpayer with aggregate annual turnover of Rs 10 crore or more cannot report an invoice, credit note or debit note to the IRP once it is more than 30 days old — a GSTN advisory (27 March 2025) states there is "no such reporting restriction" below that turnover "as of now". This is IRP portal validation resting on no rule or notification, and it can change without one (position as of 18 September 2026) — a stuck SAP Business One eDocument that sits unresolved past that window, on a business above the threshold, is one that can no longer be pushed through at all, not just a late one.

SAP Business One's own documentation for this has been rewritten twice as the feature matured, and all three versions are still findable on SAP Help Portal — which version applies is set by the feature package a given installation is running, not a setting to choose:

If your Business One instance is on FP 2405 or later, the Connector is the one worth setting up — it's the only version where "GSP configuration" is a meaningful phrase rather than a manual upload step you do outside the ERP entirely. On an older feature package, following a Connector-era walkthrough describes screens that don't exist yet on that installation.

Configuring the E-Billing Connector

Per SAP's own How to Work with Electronic Billing in the India Localization for SAP Business One 10.0 guide (document version 1.3, 2024-05-31), the Connector needs two separate pieces configured before a document can reach the IRP — the Business One side and the Electronic Document Service (EDS) side, which SAP requires for the XML Connector and the E-Billing Connector (not for plain JSON export on the generic protocol):

1. From the Main Menu, go to Administration > System Initialization > Document Settings, open the Electronic Documents tab, and in the E-Billing section select the Enable Protocol checkbox.
2. Double-click Processing Target Setup to open the Processing Targets for Protocol window, go to the E-Billing Connector tab, and select Active.
3. On the same tab, enter three fields exactly: ClearTax Base URL — https://api.clear.in; ClearTax URL for Generating IRN — /einv/v1/govt/api/Invoice/; and a ClearTax Client Secret, obtained from ClearTax's own "How to create an API client secret?" documentation, since SAP's guide defers to ClearTax for that credential and doesn't issue it itself.
4. Separately, the Electronic Document Service itself needs to be installed, configured and running — SAP Note 2952067 is the reference SAP's guide points to for that — and inside the EDS Dashboard, the ConnectorEBilling-1 (EBilling) connector panel needs its Activate option set to Auto.

Generating and sending the invoice

With the Connector configured, the day-to-day flow runs inside the ordinary sales document:

1. Create the A/R Invoice or A/R Credit Memo, and set Transaction Type to GST Tax Invoice (or GST Debit Memo for an A/R invoice representing one).
2. Confirm the series has a Digital Series checkbox selected — under Administration > System Initialization > Document Numbering, open the relevant GST Tax Invoice or GST Debit Memo subdocument and check it on the series you're using. A document created via Copy From disables the whole E-Billing section until you switch to a different numbering series in the header.
3. Check the E-Billing information on the Electronic Documents tab before saving, then choose Add.
4. Open Reports > Electronic Document Monitor, select E-Billing as the protocol. With the Connector active, a document that generated cleanly shows a Send option — choosing it pushes the e-billing information to the IRP for authentication. Once authenticated, the IRN, acknowledgement number and date, and the signed QR code are written back into the document automatically.

The Connector adds three statuses to the Electronic Document Monitor on top of the generic-protocol set: New (ready to send to EDS — the status SAP's guide says usually appears when EDS isn't configured for the connector), In Process (EDS is talking to the authorities), and Authorized (accepted by the IRP). Generated — the status that exposes the Send option above — still applies. The older manual options — Generate Report, Change Status to Error, Update Doc. with Responses — drop out of the You Can Also menu entirely once the Connector is in use; they belonged to the JSON-export workflow the Connector replaces.

The IRN failures that actually matter, and what blocks GSTR-1

Most of what stops an invoice reaching a valid IRN traces to one of two places — data quality on the document itself, or the Connector/EDS wiring above — and they fail differently.

Data-quality rejections come from a set of prerequisites SAP's own documentation lists as best practice, and they apply whichever generation of the feature you're on: the base amount must match across all tax types in a document row (checkable via the Define Tax Amount Distribution window); the Reverse Charge % on every tax code used must be either 0 or 100; every document needs at least one row; freight tax codes must follow the ordinary GST rule — IGST for inter-state, CGST+SGST for intra-state; and a document's freight value must equal that freight's own tax base amount. A document that violates any of these doesn't reach the IRP with wrong data — the JSON generation itself produces an Error-status document under the generic and dedicated E-Billing protocols, or fails before EDS ever sends it under the Connector.

Wiring failures are quieter. SAP's own guide says the New status usually means EDS isn't configured for the e-billing connector — but it doesn't document a way to tell that apart, from inside Business One's own screens, from a Connector tab that was simply never activated in the first place; either leaves the document waiting with no error message pointing at which of the two systems is actually broken.

Either failure mode has the same downstream shape as the equivalent gap on other ERPs: an invoice that never reaches a valid IRN — from a supplier to whom Rule 48(4) applies — has, under Rule 48(5), never been treated as an invoice at all, which fails the buyer's ITC claim under Section 16(2)(a) regardless of what a GSTR-2B reconciliation later shows. Separately, and independently of the IRN question, GSTN's advisory on auto-population of e-invoice details into GSTR-1 confirms that an invoice which never clears the IRP does not auto-populate into the supplier's GSTR-1 — but the supplier is still obliged to key it in by hand, since the advisory says "taxpayers are required to add details of supplies made in respective tables of GSTR-1, other than those auto-populated from e-Invoices". So a stuck IRN doesn't automatically keep an invoice out of the buyer's GSTR-2B — it does that only where the supplier never keys it in by hand either. Where the supplier does add it manually, the GSTR-1 entry carries no 'Source', 'IRN' or 'IRN date' at all — the advisory records those three fields only for auto-populated documents, and provides that where an auto-populated document is edited those fields "will be reset to blank in respective tables of GSTR-1" and the document "will be treated as if they were not auto-populated but uploaded separately by taxpayer". Either way it reaches GSTR-2B under Rule 60(7) and matches cleanly on a reconciliation screen; but it is still, under Rule 48(5), a document that was never a valid invoice, so the real exposure sits in Section 16(2)(a), not somewhere a 2B match would ever surface it. Where the supplier never adds it back, the invoice never reaches 2B under Rule 60(7) at all, and the buyer's ordinary vendor-credit claim fails under Section 16(2)(aa) read with Rule 36(4)(b) instead. A supplier whose SAP Business One instance keeps generating documents that sit at New or Error in its own Electronic Document Monitor — invisible from the buyer's side until a return is filed — is exactly the kind of gap that's painful to catch by hand across a purchase register with any real vendor count.

Where this sits against SAP's other e-invoicing path

SAP Business One's E-Billing Connector is a distinct integration from e-invoicing setup on SAP ERP and S/4HANA, which routes through SAP Cloud Integration or SAP Integration Suite to a GSP of the customer's choosing, rather than a built-in connector to one named provider. The two share the same underlying government requirement — Rule 48(4), the same IRP, the same IRN and QR code mechanics — but nothing about a Business One implementation transfers directly to an ERP/S/4HANA one, or the reverse; they're separate configurations against separate SAP products. Once IRN generation is reliably clearing the IRP on the outward side, the inward half of the same reconciliation problem — matching what actually lands in GSTR-2B against your purchase register — is covered in our guide to GSTR-2B reconciliation in SAP, and at the level of the full reconciliation cycle in our guide to Input Tax Credit.

Related guides