Goods and Services Tax (GST) e-Invoice System and API Developer’s Portal will implement new validations in the E-Waybill System starting January 1, 2025. These changes aim to enhance compliance and integration. Key updates include: (1) Restricting E-Waybill generation for documents older than 180 days from the generation date. This applies to both E-Waybills and Part-A slips. For example, an E-Waybill generated on January 1, 2025, must have a document date no earlier than July 5, 2024. (2) Limiting E-Waybill extensions to 360 days from the original generation date. If an E-Waybill’s extended validity exceeds 360 days, it will be capped. For instance, an E-Waybill generated on December 28, 2023, extended on December 17, 2024, will be valid only until December 22, 2024. (3) Integration with the Railways mandates specific formats for transport documentation based on the mode of goods shipment (Parcel, FOIS, or Leased Wagons). Valid formats, such as PWB (10 digits for PMS) and RR (9 digits for FOIS), are now compulsory for E-Waybill generation when using rail transport. Alerts currently indicate errors but will soon enforce compliance. (4) New error codes and alerts guide users in rectifying document date and transport details discrepancies. Errors like “document date older than 180 days” or “extension limit exceeding 360 days” will block E-Waybill generation. Alerts will notify users of mismatches in transport document formats or data discrepancies.
GOODS AND SERVICES TAX
e – Invoice System
e – Invoice API Developer’s Portal
New Validations in E-Waybill System (18-12-2024)
As per the latest advisory issued, the following new validations will be implemented in the E Way Bill API System including E Way Bill generation with IRN as reference in the e-Invoice System with effect from 1st January 2025. The same are available in testing environments also.
1. Generation of E Way Bill within 180 days from Document Date:
a. E Way Bill cannot be generated for document date (“docDate”) which is more than 180 days before the E Way Bill generation date.
Ex: For E Way Bill being generated on 1st Jan. 2025, “docDate” should not be earlier than 05/07/2024
b. Similarly, in case of Part-A slips, the document date (“docDate”) that was provided while generating Part A slip should not be older than 180 days on the current date. Same is applicable if Part A slips are being consolidated by updating Part B details as part of generation of consolidated E Way Bill
2. Extension of E Way Bill limited to 360 Days:
E Way Bills cannot be extended beyond 360 days from the date of generation of the E Way Bill.
1. On the day of extension, if the difference between the existing validity date and ewayBillDate is more than 360 days, extension is not allowed.
2. If on the date of extension, the difference between current date and “ewayBillDate” is less than 360 but after extension, the new validity date is going to be more than 360 days, then new validity date will be limited to 360 days
Ex: If the E Way Bill generated on 28/12/2023, and is being extended on 17/12/2024, 355 days have passed since generation. If remaining distance is 2000 Kms then the new validity date will be limited to 360 days i.e. 22/12/2024.
3. Integration with Railways for PWB/RR/Leased Wagon Receipt No:
E-Waybill has been integrated with Railways for goods sent through Parcel and FOIS system. Hence, it is mandatory to specify the category of goods sent. They can be classified as P-PMS, F-FOIS and L-Leased Wagons. During generation of E Way Bill, if the mode of transport is Rail (“transMode” = 2) then “transDocNo” should be passed with the following format only. The same validations are applicable for all functionalities where Part-B is updated. The PWB for PMS is 10 digits and RR No. for FOIS is 9 digits
Note: Presently, PWB/RR/LWR No format are being verified and alerts are given in response. In few days, instead of alerts, it will be made mandatory to pass the valid PWB/RR/LWR No and also in the specified format.
| Category | Format | Example |
| Parcel System | P<station code><PWB> | PSBC1234567890, where SBC is the station code |
| FOIS System | F<station code><RR> | FSBC123456789, where SBC is the station code |
| Leased Wagon | L< RR No.> | L123456789 |
4. Error Codes & Alerts:
Errors:
Following are the new error codes with descriptions for the above changes
| E Way Bill API | ||
| Sl. No | Error Code | Description |
| 1 | 820 | You cannot generate E Way Bill with document date earlier than 180 days |
| 2 | 821 | E Way Bill cannot be extended as allowed limit is 360 days |
–
| E Way Bill through e-Invoice API | ||
| Sl. No | Error Code | Description |
| 2 | 4043 | You cannot generate E Way Bill with document date earlier than 180 days |
Alerts:
Following messages are provided in the “alert” parameter in the response payload for Trans Doc No. validation in case of Transportation Mode is Railways
| Sl. No. | Condition | Alert Message |
| 1 | The format of the TransDocNo is not as per the format mentioned above | Incorrect RR No. format. |
| 2 | If the format matches but anyone of the following parameters provided for E Way Bill System do not match with the details provided for Railways while generating PWB/RR/LWR No. (Parameters being matched: TransDocNo, TransDocDate, DocNo, DocDate, fromGstin, toGstin, totInvValue) | EWB Generation:
{not matched fields} values are not matching with the given RR No details. |
| Part B/Consolidate EWB/Extension:
{not matched fields} values of ewb no: {} are not matching with the given RR No details. |
||
| 3 | If all, the TransDocNo and the parameters match (Parameters being matched:
TransDocNo, TransDocDate, DocNo, DocDate, fromGstin, toGstin, totInvValue) |
The RR No. details are matched with EWB details. |
