Linking Of E-Way Bill and IRN APIs

Learn the Linking of E-Way Bill and IRN APIs

On 7 December 2020, new and enhanced APIs of e-Invoice and e-Way Bill systems are expected to be released (production). These APIs are already available on the sandbox for testing. In this article, we will elaborate on the implications of this modification.

How Will The Linking Of E-Way Bill APIs and IRN APIs Affect The Taxpayers?

Taxpayers will not be able to generate e-Way bills directly henceforth. The Web/Offline/API systems will be blocked for the taxpayers who are generating #IRN (e-Invoice). That means EWBs will have to be generated through the IRN APIs. Note:

• These enhanced APIs will not affect the ongoing generation of IRN and other activities. However, the e-Way Bill schema will be mapped with the e-Invoice schema.
• For invoices that do not need an IRN, Taxpayers can know how to generate e-Way bill with IRN number directly (ex: Import/Job Work/Exhibition/Own Use etc.).

Changes In E-Way Bill

With the merger of the APIs:

• E-Way Bill (EWB) print will have the IRN e-way bill, Acknowledgement number and date.
• Detailed EWB print will also have the IRN, Acknowledgement number and date. However, it will not have the Item details. Officers will be intimated to refer to the IRN copy for the item details.

Changes In the ‘Generate IRN’ API

• Invoices (IRN requests) with Document Date from 1 October 2020 only will be accepted and processed for IRN generation. IRN requests belonging to previous dates will be rejected.
• The Item serial number (i.e. attribute ‘SlNo’) can be numeric only.
• ‘Reverse Charges’ can be set as ‘Y’ in the case of B2B and SEZ invoices.
• In case the PIN code does not exist in the master database of the e-Invoicing system, but if the first 3 digits of the PIN code match with the respective State code (as per the PIN code-to-State mapping pattern defined by the postal department), then the IRN will be generated.
• In the case of Reverse charge and Export transactions (EXPWP), the total value of the item should match either the tax values or the values without tax. That means the total value of an item can include or exclude the tax values as per the business requirements.
• The distance of transportation is validated against the auto-calculated PIN-PIN distance stored in the system. The allowed distance for transportation should be between +/- 10 % of the auto-calculated PIN-PIN distance. If the auto-calculated distance is less than 100 KMs, then the allowed distance for transportation should be between 1 and +10 % of the auto-calculated PIN-PIN distance.

Note:

• The recipient’sGSTIN should be registered and active on the date of preparation of the document by the supplier.
• IRN details can be fetched using the 'Get IRN' API within 3 days from the date of IRN generation.

Improvements In the ‘Generate EWB By IRN’ API

• In case the PIN code does not exist in the master database of the e-Invoicing system, but if the first 3 digits of the PIN code match with the respective State code (as per the PIN code-to-State mapping pattern defined by the postal department), then the IRN will be generated.
• The distance of transportation is validated against the auto-calculated PIN-PIN distance stored in the system. The allowed distance for transportation should be between +/- 10 % of the auto-calculated PIN-PIN distance. If the auto-calculated distance is less than 100 KMs, then the allowed distance for transportation should be between 1 and +10 % of the auto-calculated PIN-PIN distance.
• If the distance of transportation is passed as 0 (zero), then the system will consider it as a request made by the taxpayer, to consider the auto-calculated PIN-PIN distance for the generation of the e-Way Bill and generate the EWB along with the IRN. The actual distance is passed in the "Info. Message" column for reference.
• If the dispatching address and/or shipping address have not been passed during the generation of the IRN, then the respective addresses can be passed here.

Mapping Of Notified Schema With API (IRN) Schema