New Validations and API - Dec 2020
Changes in DLL and Library:
1. class ReqPlGenIRN -> Property ItemList of Type ItmList
sub-class ItmList -> Property SlNo -> changed from string to int
2. Added new properties in Generate e-Way Bill by IRN Request Model ReqPlGenEwbByIRN -> ExpShipDtls, DispDtls
Release Notes
IMPORTANT: eInvoice Sandbox UserID / Password / AuthToken is working on EWB Sandbox also. i.e. Both eInvoice and EWB Sandbox merged.
1.The following improvements will not affect the ongoing IRN generations. These improvements are made to handle the exceptional cases of invoices which needs the IRN generation.
2.These improved versions of APIs will be released on the production on 7-Dec 2020. You are requested to test these APIs on the sandbox.
3.The Direct E-Waybill generation through Web/Offline/API will be blocked for the taxpayers who are generating IRN as per the notification. However, they will be allowed to generate the e-waybill directly which are not covered under IRN generation like Import/Job Work/Exhibition/Own Use etc
4.There are some changes in validations for direct e-waybill generation using e-waybill APIs. Please click here https://docs.ewaybillgst.gov.in/apidocs for more details.
5.E-way bill print will have the IRN , Acknowledgement no. and date
6.Detailed E-waybill print will also have the IRN , Acknowledgement no. and date , but it will not have the Item details. Officers will be intimated to see the IRN copy for the item details.
7.A new API GetIRNByDocDetails is made available in the Sandbox. This will help in fetching the details of IRN based on Document type, document date and document number.
8.A Health API is made available in the Sandbox.
9.JSON Schema of the ‘Generate IRN’ and ‘Generate EWB by IRN’ APIs have been improved by adding the “Patterns” for some of the attributes.
10.Descriptions for some of Error Codes have been improved & also new Error Codes have been defined in the APIs.
11.The following changes have been made in ‘Generate IRN’ API
* IRN requests with Document Date from 01/10/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 case of B2B and SEZ invoices also.
* Recipient GSTIN should be registered and active, on the date of preparation of the document by the supplier.
* If the PIN Code does not exist in the master database of the e-invoicing system but however if the first 3 digits of the PIN code matches with the respective State as per the pattern of PIN code-to-State mapping pattern defined by postal department, then IRN gets generated .
* In case of Reverse charge and Export transactions (EXPWP), Total value of Item should match either with tax values or without tax values. That is, the total value of item can include or exclude the tax values as per the business requirements.
12.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 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 auto-calculated PIN-PIN distance.
13. IRN details can be fetched using 'Get IRN' API within 3 days from the date of generation of IRN.
* The following improvements in 'Generate EWB by IRN' API
If the PIN Code does not exist in the master database of the e-invoicing system and the first 3 digits of the PIN code matches with the respective State as per the pattern of PIN code-to-State mapping pattern defined by postal department, then IRN gets 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 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 auto-calculated PIN-PIN distance.
* If the distance of transportation is passed as 0 (zero), then the system will consider it as request made by the tax payer, to consider the auto-calculated PIN-PIN distance for the generation of e-way bill and generate the e-way bill along with IRN. The actual distance is passed in "Info. Message" column for reference.
* If the dispatching address and/or shipping address have not been passed during generation of IRN, then the respective addresses can be passed here.