Logistics teams frequently encounter situations where roving tax squads intercept a commercial truck claiming that the vehicle never crossed a designated highway toll plaza. Officers rely on portal dashboards that aggregate electronic toll collection feeds from the National Highways Authority of India network. When an RFID scanner suffers network latency, hardware misalignment, or reader downtime, the electronic trail breaks, creating an apparent tracking mismatch.
Statutory rules governing RFID verification and vehicle transit
The legal framework for electronic tracking and verification rests on two provisions of the Central Goods and Services Tax Rules:
- Rule 138A, CGST Rules establishes documents and devices carried by the person in charge of a conveyance. Sub-rule (1) requires carrying the invoice or delivery challan, plus a physical copy of the e-way bill, the e-way bill number electronically, or mapped to a Radio Frequency Identification Device embedded on the vehicle. Sub-rule (4) empowers the Commissioner to require specific transporters to obtain an RFID device and map the e-way bill prior to goods movement.
- Rule 138B, CGST Rules directs verification. Rule 138B(2) provides that the Commissioner shall install RFID readers at places where transit verification is required, and verification shall be conducted through such readers where the e-way bill is mapped.
Common mistake: Assuming that a missing RFID toll plaza scan automatically empowers an intercepting officer to impose detention penalties. Under Section 129(1)(a), CGST Act, detention applies only when goods are transported in contravention of statutory rules. If Part A and Part B are validly updated and documentation is complete, reader failures at toll plazas do not constitute legal contravention.
Common causes of RFID read failures at toll plazas
Electronic toll data flows from commercial FASTag RFID tags affixed to vehicle windscreens into the National Payments Corporation of India switch, which then syncs with the goods and services tax portal. Tracking discrepancies generally originate from four practical causes:
- Vehicle number typography mismatch: The vehicle number in Part B of Form GST EWB-01 contains formatting errors, such as typing DL01AB0001 instead of DL-01-AB-0001, preventing automated database reconciliation with the FASTag chassis record.
- Toll reader hardware downtime: Extreme weather, local power outages, or lane reader maintenance at toll plazas force plaza operators to clear vehicles manually without triggering the RFID transceiver.
- Damaged or shielded windshield tags: Metallic sun protection films, dirty glass, or cracked RFID internal chip aerials cause reader timeout errors at high-speed ETC lanes.
- Transshipment without Part B update: Transferring cargo to a relief vehicle following mechanical trouble without executing a Part B update under Rule 138(5), CGST Rules. If vehicle B crosses the plaza while the e-way bill still lists vehicle A, tracking reports show zero movement for the consignment. For extended delays, see guidance on e-way bill expiry extension under Rule 138.
- Portal blocking status: If the supplier GSTIN was blocked for non-filing of returns under Rule 138E, no valid Part A or e-way bill could be generated; check portal status following the official GSTN E-Way Bill Unblocking Guide.
Step-by-step reconciliation protocol during transit interception
If an enforcement squad stops your consignment citing an RFID non-detection alert or missing toll log, follow this operational sequence immediately:
- Verify active Part B details: Confirm that the vehicle registration number on the physical truck matches the active Part B record on the official e-way bill system.
- Pull real-time FASTag statement: Access the issuing bank portal or mobile application for the vehicle FASTag wallet. Download the deduction log showing the exact transaction reference, plaza identification code, and timestamp.
- Gather secondary trip proof: Collect the driver physical toll payment slip (if cash or manual lane processing occurred), driver trip sheet, fuel card logs, and GPS telematics exports matching the route.
- Request statutory inspection recording: Remind the inspecting officer that under Rule 138C(1), CGST Rules, a summary report of inspection must be recorded online in Part A of Form GST EWB-03 within 24 hours of interception, and the final report in Part B within 3 days. Presenting contemporaneous toll proof prevents arbitrary detention allegations.
Worked example: resolving a tracking discrepancy and computing penalty exposure
Consider an industrial engineering supplier in Pune dispatching precision machinery to a manufacturing facility in Ahmedabad. The consignment is covered by a valid tax invoice and Form GST EWB-01.
| Consignment parameter | Declared value / detail | Statutory reference |
|---|---|---|
| Consignment taxable value | ₹15,00,000 | Tax invoice particulars |
| Applicable IGST rate (18%) | ₹2,70,000 | IGST Act Section 5(1) |
| Assigned vehicle number (Part B) | MH-12-RN-4589 | Form GST EWB-01 Part B |
| Toll plaza RFID scan status | Failed / Not recorded at Khed Shivapur plaza | Portal vehicle tracking log |
| FASTag bank wallet debit log | ₹280 debited at 04:12 AM (Lane 04) | Issuing bank statement |
| Improper penalty demand under Section 129(1)(a) | ₹5,40,000 (200% of tax: 2 × ₹2,70,000) | Section 129(1)(a), CGST Act |
| Reconciled liability after presenting bank proof | ₹0 (Consignment released unconditionally) | Rule 138A and Rule 138B compliance |
The inspecting officer initially alleges non-movement because the e-way bill dashboard did not register the automated RFID trigger. The transporter produces the FASTag transaction ID from the issuing bank wallet showing ₹280 debited at the exact plaza at 04:12 AM, backed by the vehicle GPS breadcrumb log. Because all requirements of Rule 138A(1) were met, no contravention occurred, saving the taxpayer from an improper penalty demand of ₹5,40,000.
Template response to tax officer on RFID tracking discrepancy
Frequently asked questions
Can an officer detain a truck solely because a toll plaza RFID reader failed to log the e-way bill?
No. Under Rule 138A(1), carrying a valid physical copy or electronic e-way bill number alongside the tax invoice or delivery challan satisfies transit compliance. Technical reader failure at a toll plaza is not a contravention when documentation is complete.
How does FASTag integrate with the GST e-way bill system?
The e-way bill system links Part B vehicle registration numbers to National Payments Corporation of India FASTag toll records. Each toll plaza crossing logs vehicle timestamps to verify actual commercial transit.
What should the transporter do if Part B vehicle details do not match the truck at the toll plaza?
The transporter or generator must update Part B of Form GST EWB-01 on the e-way bill portal with the new vehicle registration number before continuing movement, as required by Rule 138(5).
Reconcile your inward logistics and purchase records
Ensure that commercial invoices match your supplier outward filings and GSTR-2B before closing month-end accounts. Your GSTR-2B and purchase register files are read in your browser and never uploaded to any server.
Last checked: 22 October 2026. Sources: CBIC CGST Rule 138A, CBIC CGST Rule 138B, CBIC CGST Rule 138C, CBIC CGST Act Section 129, GSTN E-Way Bill Portal User Guide.