E-invoice fails with error “Recipient cannot be SEZ for B2B transaction”
Problem statement
An e-invoice generation attempt failed with the following error message:
Recipient cannot be SEZ for B2B transaction.
The customer linked to the transaction is marked as a Special Economic Zone (SEZ) unit. Users may encounter this error when attempting to generate an e-invoice for such customers and may want to understand when SEZ units are exempt from e-invoicing and why this validation error occurs.
Under Taxpayer type, it is mentioned as SEZ unit
Solution
The first step should always be to email Storecove and check the status, as we rely on Storecove as a third-party provider to verify e-invoicing status across various networks.
After confirmation from Storecove, checking the error message “Recipient cannot be SEZ for B2B TRANSACTION.” , this will typically be returned by the Invoice Registration Portal (IRP) in India during e-invoice validation. It indicates that:
-
The recipient’s GSTIN is marked as SEZ (Special Economic Zone).
-
However, the invoice is being submitted as a regular B2B (Business-to-Business) transaction, which is not allowed for SEZ recipients under this classification.
The failure you are viewing is Recipient cannot be SEZ for B2B TRANSACTION. This failure occurs due to misclassification of the invoice type during e-invoice generation via the IRP, particularly when the recipient is registered as an SEZ unit.
To resolve the issue, ensure that the SEZ configuration is properly set up in Chargebee for zero-rated GST transactions.
Steps to fix the issue
To resolve the issue, follow these steps:
- In Chargebee, go to Configure Chargebee > Taxes > Taxes for Special Economic Zone. Enable the option Zero-rated GST.

- Open the affected Customer record and update the Billing Information to correctly mark the customer as belonging to an SEZ unit.

- After saving the updates, retry sending the e-invoice.
- Once the zero-rated GST configuration is enabled and the customer details are updated, the e-invoice should be generated successfully.
Was this article helpful?