India’s GST ecosystem continues to evolve with periodic updates aimed at improving compliance, reducing tax evasion, and enhancing the efficiency of goods movement across the country. One such important compliance requirement that businesses and transporters need to be aware of is the E Way Bill 180 Day Rule.
While many businesses focus on generating e-Way Bills correctly, fewer realize that an e-Way Bill cannot be generated using an invoice or document that is more than 180 days old. This rule is designed to ensure that transportation documents reflect current business transactions and prevent the misuse of outdated invoices.
What is E-Way Bill 180 Day Rule?
The E-Way Bill 180 Day Rule 2026 restricts taxpayers from generating an e-Way Bill using a tax invoice or relevant document whose date is more than 180 days prior to the date of e-Way Bill generation.
It amends the e-way bill generation logic under Rule 138 of the CGST Rules, 2017 to add a e way bill document date validation: the date on the source document used to generate the e-way bill must not be earlier than 180 days from the date of EWB generation.
The E-Way Bill 180 Day Rule was introduced via CBIC Notification No. 17/2024-Central Tax, clarified through the GSTN Advisory dated December 17, 2024, and made live on the portal from January 1, 2025.
In simple terms: How the e way bill 180 days from invoice date works is if an invoice is older than 180 days, it cannot be used to generate a fresh e-Way Bill.
This means businesses must ensure that goods are transported within a reasonable timeframe after issuing the relevant document or generate the required transportation documents before the 180-day limit is exceeded.
Why Was the E-way Bill 180-Day Rule Introduced?
The rule was introduced to strengthen GST compliance and improve the integrity of goods movement under the GST framework.
Its key objectives include:
- Preventing the misuse of old invoices for unauthorized transportation
- Reducing tax evasion through recycled or outdated documentation
- Encouraging timely movement of goods after invoicing
- Improving transparency in logistics and supply chain operations
- Strengthening audit trails for tax authorities
By limiting the use of older documents, the GST system better aligns transportation records with actual business transactions.
When Does the E-way Bill 180 Day Rule Apply?
The 180-day restriction applies when generating an e-Way Bill based on eligible documents such as:
- Tax Invoice
- Bill of Supply
- Delivery Challan (where applicable)
- Other prescribed documents permitted under GST rules
The system checks the document date at the time of e-Way Bill generation. If the document is older than 180 days, the portal will not allow an e-Way Bill to be generated against it.
Does the Rule Affect Existing e-Way Bills?
No. The rule applies only at the time of generating a new e-Way Bill.
It does not reduce or alter the validity period of an e-Way Bill that has already been generated.
For example:
- An e-Way Bill generated today remains valid according to the standard distance-based validity rules.
- The 180-day restriction relates only to the age of the supporting document used to create the e-Way Bill.
What Documents Does It Apply To?
The 180-day restriction applies to all documents used as the basis for e-way bill generation:
| Document Type | Subject to the 180-Day Rule? |
|---|---|
| Tax invoice | ✅ Yes |
| Bill of supply | ✅ Yes |
| Delivery challan | ✅ Yes |
| Credit note | ✅ Yes |
| Part-A slips | ✅ Yes |
| Consolidated e-way bills (EWB-02) | ✅ Yes — Applies to the underlying Part-A slips |
| EWB generated alongside IRN (e-invoice API) | ✅ Yes — Error Code 4043 applies if the invoice is older than 180 days |
The Error Codes to Know
| Error Code | Trigger | Meaning |
|---|---|---|
| 820 | Standard portal or manual E-Way Bill generation | The document date is older than 180 days, so E-Way Bill generation is not allowed. |
| 4043 | E-Way Bill generation through the e-invoice API | The document date is older than 180 days, so E-Way Bill generation is rejected through the API. |
| 821 | E-Way Bill validity extension request | The requested extension would increase the total validity beyond 360 days from the original E-Way Bill generation date. |
How the 180-Day Window Is Calculated
The calculation
Of 180-day window of eway bills is calculated as follows:
Earliest eligible document date = Date of EWB generation − 180 days
The document date must fall on or after this calculated date.
Calculation Scenarios
Scenario 1 — Basic invoice scenario:
E-way bill generation date: June 29, 2026
Earliest eligible document date: December 31, 2025 (180 days before)
An invoice dated January 15, 2026 → ✅ Eligible — within 180 days
An invoice dated December 20, 2025 → ❌ Blocked — older than 180 days (e way bill error code 820)
Scenario 2 — Quarterly stock reconciliation:
A Mumbai trader does a quarterly audit in June 2026 and finds undispatched stock tied to invoices raised in November 2025 (7+ months ago).
❌ Cannot generate e-way bill — those invoices are beyond 180 days.
Resolution: Issue fresh invoices in June 2026 against the same stock (with appropriate accounting adjustments), then generate EWBs against the new documents.
Scenario 3 — Year-end pending dispatches:
A manufacturer closes FY 2025-26 with a batch of invoices from September 2025 that were never dispatched due to a buyer’s warehouse being under renovation. In June 2026, the buyer is ready to receive goods.
September 2025 invoices are exactly 9 months old → ❌ beyond 180 days → Error 820.
Resolution: Cancel the old invoices (if still within cancellation window on IRP) or issue fresh credit/debit notes with a current-dated replacement invoice.
Scenario 4 — Delivery challan for job work:
A textile manufacturer sends fabric for embroidery work using a delivery challan dated January 5, 2026. The job work takes longer than expected and the goods are ready to be returned in July 2026 — 6+ months later.
The return delivery challan is new (current date) → ✅ The return EWB uses the new challan date and is eligible.
But if someone tries to generate the outward EWB belatedly using the January 5 challan → ❌ Blocked.
The Companion Rule: 360-Day Extension Cap
The 180-day generation rule has a companion: the 360-day extension cap, effective from the same date (January 1, 2025).
Before this rule: E-way bills could be extended indefinitely. Stranded shipments — due to vehicle breakdowns, natural disasters, or border delays — could have their validity renewed over and over.
After this rule: The total validity of any e-way bill, including all extensions, cannot exceed 360 days from the original generation date. The portal enforces this with Error Code 821.
Extension Cap Example
An e-way bill is generated on January 1, 2026.
The maximum permissible validity (including all extensions) ends on December 27, 2026 (360 days later).
If a transporter attempts to extend beyond December 27, 2026, the portal caps the validity to December 27 regardless of the distance entered.
Partial Extension Scenario
An e-way bill is generated on January 1, 2026 and extended on December 20, 2026 (354 days later).
The transporter enters a 2,000 km distance, which would normally give a 10-day extension (until December 30, 2026).
But the 360-day cap (December 27, 2026) overrides the distance calculation.
The portal grants validity only until December 27, 2026 — not December 30.
Operational Impact: Who Is Most Affected?
High-impact business scenarios of e-way bill 180-day rule 2026:
| Business Type | Risk Scenario | Recommended Action |
|---|---|---|
| Seasonal goods traders (apparel, agri-inputs) | Invoices raised at order booking but dispatch delayed by months | Align invoice dates closer to dispatch dates; use delivery challans for goods held pre-dispatch |
| Manufacturers with slow-moving SKUs | Old stock invoiced but never dispatched | Quarterly review of open invoices; cancel and re-issue if approaching 180 days |
| Job work operations | Delivery challan raised at goods pickup; return delayed beyond 180 days | Use fresh return delivery challan; do not rely on the original outward challan for return EWB |
| ERP/API-integrated businesses | Batch-processing systems that queue old invoices for EWB generation | Add e-way bill document date validation in pre-submission logic; surface e invoice error 4043 e way bill clearly to operators |
| Multi-location stock transfers | Intra-company stock moves documented months after the internal transfer decision | Generate delivery challans contemporaneously with actual stock movement, not at the point of accounting |
What Happens When You Hit Error 820: Step-by-Step Recovery
If you encounter Error Code 820, the portal has already blocked generation. Here is the recovery path:
Step 1 — Confirm the document date
Verify the exact date on the source invoice or challan. Confirm it is indeed older than 180 days and not a data entry error.
Step 2 — Assess the original invoice status
- Is the invoice still within the 24-hour IRN cancellation window on the IRP? (Only for e-invoice-mandated businesses.) If yes, cancel and reissue.
- Is it past 24 hours? You cannot cancel the IRN. Issue a credit note against the original invoice to nullify it.
Step 3 — Issue a fresh invoice with the current date
Create a new invoice for the same supply. This new invoice is the source document for your e-way bill. The e-way bill document date is current — within 180 days — so EWB generation proceeds normally.
Step 4 — Address the accounting and GST implications
A new invoice in the current period means the supply is now declared in the current GSTR-1, not the original period. If GST was already paid in the original period, the credit note and new invoice must be reconciled carefully. Consult your CA or GST consultant if this crosses financial year boundaries.
Step 5 — Update your dispatch controls
Implement an invoice-to-dispatch SLA in your operations — ideally 30 to 60 days. Any open invoice approaching 150 days should trigger an internal alert before it becomes ineligible.
Critical: There is no government escalation path, no portal override, and no exception application for Error 820. The block is absolute. Recovery always requires a fresh document.
E-Way Bill180 Day Rule + E-Invoice: The Double Constraint
For businesses above the ₹5 crore e-invoice threshold, the 180-day rule creates an additional complexity: the e-invoice and the e-way bill must both use documents within 180 days.
Key interactions:
- When generating an EWB via the IRP/e-invoice API, the same 180-day check applies — but returns Error Code 4043 instead of 820
- You cannot cancel an IRN if an active e-way bill exists against it
- If an old IRN is beyond the 24-hour cancellation window and also beyond 180 days, the entire transaction needs to be reversed via credit note and re-invoiced
Best practice for e-invoice-mandated businesses:
Generate the IRN and EWB in the same session, on the same day the invoice is raised. Never queue IRNs for EWB generation at a later date without tracking document age.
Related Article
E-way bill Changes 2026 | Transshipment of Goods Under E-Way Bill | Calculating E-way Bill Validity Period
