Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian fleet operators running 50 to 500 trucks face a structural FASTag reconciliation gap — NETC daily MIS files arrive per issuer bank with 0.1-0.4% double-deduction incidence, blacklisted-tag deductions at 2x, wallet topups split across UPI/IB/auto-topup channels, plaza-vs-route exceptions on unplanned diversions, and a GST split (toll exempt under Notification 12/2017 entry 23 vs NETC switching fee taxable at 18% SAC 998599) that breaks single-line journal entries.
Reconcile vehicle ID and tag ID against trip sheet route per day with each MIS deduction tied to a planned plaza, flag same-tag-same-plaza events inside the re-read tolerance as double-deduction disputes, separate the wallet topup ledger (UPI/IB/auto-topup) from the toll deduction ledger and tie both to bank statement debits, split each deduction into exempt toll plus taxable switching fee for GSTR-3B classification, and maintain the Section 393 code 1002 transporter TDS ledger with PAN-based nil-deduction declarations under the legacy 194C(6) framework refreshed at every FY boundary.
Vehicle master keyed by registration number with tag ID, vehicle class and issuer bank, plaza master with plaza code, location and acquirer bank, route master with planned plaza sequence per origin-destination pair, MIS ingest from each issuer bank's daily file, dispute register with NETC dispute reference and ageing, wallet topup channel mapping (UPI VPA, IB beneficiary, auto-topup mandate), GST line tax-treatment table (toll exempt, switching fee SAC 998599 18%), and transporter vendor master with PAN, 393/1002 default rate and 194C(6) declaration flag.
A daily reconciled view per vehicle showing planned plazas vs deducted plazas with double-deduction exceptions coded by reason, monthly tag-wise toll spend tied to bank statement debits, GST split between exempt toll and taxable switching fee feeding GSTR-3B 3.1(d) and 4(A)(5) respectively, a transporter payment ageing showing TDS deducted at 1%/2% under code 1002 or 194C(6) nil-deduction flag, and a wallet float position by issuer-bank by truck class with low-balance alerts.
A logistics company in Bhiwandi operating 180 trucks on the Mumbai-Surat-Ahmedabad-Vapi corridor closes its books for May and pulls the FASTag spend: ₹42 lakh deducted across 5,440 toll events, against an expected ₹39.8 lakh inferred from the trip sheets. The ₹2.2 lakh delta — a 5.5% variance — breaks down across four reconciliation rails. Anyone running FASTag toll reconciliation India at scale recognises the pattern. The plumbing looks simple from the dashboard. The leakage hides in the join.
Quick reference
| Item | Value |
|---|---|
| Programme | NETC (National Electronic Toll Collection) — managed by NPCI under NHAI |
| Mandatory for | All commercial four-wheeler vehicles since the 2021 NHAI mandate |
| Tag-issuing banks | 30+ NPCI member banks (HDFC, ICICI, SBI, Axis, IDFC First, Kotak, Paytm Payments Bank, etc.) |
| Toll GST treatment | Exempt — Notification 12/2017-Central Tax (Rate), entry 23 |
| NETC switching fee GST | Taxable at 18% under SAC 998599 (where levied by issuer) |
| Vehicle classes | Class 4 (LCV) through Class 16 (oversize) — each plaza-rate matrixed |
| Transporter payment TDS | Section 393, code 1002 — 1% individual/HUF, 2% company/firm |
| Legacy nil-deduction route | Section 194C(6) — small transporter PAN declaration (preserved under Act 2025) |
| Typical fleet leakage band | 0.5% to 1.5% of monthly toll spend |
How does the NETC settlement architecture work?
NETC sits in the middle. A fleet operator’s truck approaches a plaza acquired by Bank A. The truck carries a tag issued by Bank B. The lane antenna reads the tag, queries NPCI’s NETC switch, which routes to Bank B for authorisation, which checks the wallet balance and either authorises or declines. On authorisation, Bank B debits the operator’s prepaid wallet (or the linked current account on auto-topup) and remits the toll to Bank A net of the switching fee. Bank A credits the plaza concessionaire on its own settlement cycle. The fleet operator sees only two artefacts: a daily MIS file from Bank B (issuer) listing the deductions, and a bank statement debit on T+1.
Reconciliation has to cover the loop from end to end — and the MIS file is the only granular record the operator gets per toll event. Bank A’s settlement to the concessionaire is invisible to the truck owner. NPCI’s interchange ledger is invisible. The MIS file is the source of truth for vehicle-level toll cost.
What are the four reconciliation rails?
Rail 1 — Vehicle-tag-plaza-trip matching
The MIS file lists, per deduction, the tag ID, plaza code, lane, timestamp, vehicle class as read at lane, and amount. The fleet operator’s planning system holds the trip sheet for each truck: origin, destination, dispatch time, expected route, expected plazas in sequence. Reconciliation ties each MIS deduction back to a trip — if a truck dispatched from Bhiwandi at 04:00 to Surat is supposed to cross five plazas in sequence (Vasai, Manor, Charoti, Karambele, Bhilad), but the MIS shows a deduction at a sixth plaza on a different highway, that is either a route diversion (driver took a longer route — log and recover from driver advance), a stolen-tag event (rare but exists), or a duplicate-vehicle exception (two trucks registered with overlapping tag-vehicle mapping). Without the trip-plaza join, the fleet operator cannot tell legitimate spend from leakage.
Rail 2 — Double-deduction and re-read disputes
NETC’s gantry specification provides a re-read suppression window — typically four minutes — within which a second read at the same plaza on the same tag should not result in a fresh deduction. In practice, lane-to-lane crossover between read antennas, micro-clock drift between gantries, and operational restarts create cases where the same tag-plaza pair shows two deductions within a few minutes. Each such pair is a double-deduction candidate. The fleet operator runs the test: same tag ID, same plaza code, time difference under the operator’s threshold (4 minutes is the conservative bar). Each candidate is filed as a dispute via the issuer bank’s NETC dispute portal. The recovery typically takes 7 to 21 working days. A 180-truck fleet running on a 1,200-plaza network generates 100 to 400 double-deduction candidates per month. Industry-typical recovery rate is 70% to 85% on filed disputes.
See 3PL settlement reconciliation for Indian logistics operators for the downstream settlement view when the fleet operator is itself a 3PL serving multiple cargo clients.
Rail 3 — Wallet topup and bank statement reconciliation
A fleet operator’s FASTag spend is funded by wallet topups. Topups come through four channels: manual UPI from the operator’s current account, internet banking NEFT/IMPS, auto-topup mandates triggered when wallet falls below a threshold, and corporate-card load (where the issuer offers a corporate-account-linked tag). Reconciliation must tie each topup to the bank statement debit on the operator’s current account, and tie each daily aggregate deduction in the MIS to the wallet balance change. A topup that hits the bank but does not reflect in the wallet (rare but happens with channel API timeouts) creates a stuck-float exception. A wallet debit that does not show in the bank for a corporate-linked tag is the inverse case.
Rail 4 — GST and TDS overlay
Toll itself is GST-exempt under Notification 12/2017-Central Tax (Rate), entry 23. The deduction recorded by the issuer is an exempt supply from the concessionaire to the road user.
NETC switching/processing fees levied by some issuer banks on the wallet float (a periodic maintenance fee, or a per-transaction processing line where applicable) are a taxable supply at 18% under SAC 998599 (other support services). The fleet operator is the recipient and claims ITC on this taxable component, while the toll component flows into the exempt-supply box of GSTR-3B.
Transporter payments — when the fleet operator is being paid by a manufacturer or 3PL principal for transportation services, the principal deducts TDS under Section 393 of the Income Tax Act 2025, payment code 1002, at 1% (individual/HUF transporter) or 2% (company/firm). The legacy Section 194C(6) nil-deduction route for small transporters owning ten or fewer goods carriages — backed by a PAN declaration furnished to the deductor — is preserved under the Act 2025 framework. The fleet operator’s reconciliation must keep the declaration register live: who has been issued a non-deduction status, when the declaration was filed, when it expires (typically refreshed at every FY boundary), and which principal is the deductor.
Cross-era note: For TDS credits already deducted under the legacy Section 194C (pre-1 April 2026) and reflected in Form 26AS under the old section code, the reconciliation must keep the legacy section cross-reference live for at least one full tax-year cycle. See TDS payment codes 1001-1092 India for the full code map.
Worked example — 180-truck Bhiwandi fleet, May 2026
A 180-truck fleet running predominantly NH-48 (Mumbai-Ahmedabad-Vapi) and NH-66 (Mumbai-Pune) corridors books ₹42 lakh of FASTag deductions for May 2026 against 5,440 toll events.
Decomposition:
- Expected toll spend (planned plazas × planned trips × class-wise plaza rate): ₹39.8 lakh.
- Double-deduction candidates flagged: 312 events, ₹3.42 lakh aggregate. Filed as disputes; expected recovery at 78% recovery rate is ₹2.67 lakh, leaving ₹0.75 lakh permanent leakage.
- Plaza mis-classification (truck read as Class 7 four-axle at plazas where the truck is actually Class 6 three-axle): 84 events, ₹0.62 lakh. Filed with the issuer bank and plaza authority; recovery typically 50-60%.
- Route-diversion events (deductions outside planned corridor — driver took toll road instead of state-highway alternative): 47 events, ₹0.41 lakh. Recovery from driver advance against the trip-sheet variance.
- Blacklisted-tag double-pay (3 tags blacklisted mid-month on low balance — cash paid at plaza at 2x): ₹0.18 lakh. Reimbursed to drivers; tag remediated.
- Net leakage to recover: ₹2.20 lakh on the month, or 5.5% of the gross deduction. After dispute recovery, permanent leakage is approximately ₹1.05 lakh — 2.6% of toll spend.
The fleet operator pays Section 393 code 1002 TDS at 2% on every payment it receives from its principal manufacturers and 3PLs. On a turnover of ₹4.8 crore for the month from principal contracts, TDS withheld is ₹9.6 lakh. The reconciliation against Form 26AS at quarter-end ties the 26AS credit by deductor TAN, principal contract reference, and quarter — variances here are the most common cause of working-capital lock for road-transport businesses.
Quantify your TDS mismatch against Form 26AS
For transporters and fleet operators where TDS withheld at source by principals is the single largest working-capital lock, the estimator quantifies the gap, the chase hours required, and the rupee value of the lock.
Open the TDS Mismatch Estimator →What are the operational controls that close the gap?
The fleet operator who runs a clean FASTag reconciliation does five things:
- Daily MIS ingestion per issuer bank — the file lands on T+1; ingest it nightly, do not batch weekly. The dispute window with issuers tightens after 30 days.
- Tag-vehicle master under change control — when a tag is replaced (damaged, fallen off, blacklisted-and-reissued), the master must reflect the change before the new tag’s first deduction lands.
- Trip-plaza expectation table per origin-destination pair — pre-computed plaza sequence and class-wise toll, so MIS deductions can be compared to expectation without manual lookup.
- Double-deduction detection cron at 4-minute or operator-chosen tolerance, filing disputes through a single named NETC dispute account per issuer bank.
- Wallet float dashboard — visibility into low-balance trucks before they get to the plaza, eliminating the 2x cash-pay loss on blacklisted-tag events.
These are operational controls, not technology controls. The reconciliation layer makes them auditable and chase-able. Without the layer, the controls degrade to spot-checks and the 1.5% leakage band becomes 3% to 4%.
How does FASTag reconciliation interact with the broader logistics tax stack?
A fleet operator does not run FASTag in isolation. The same operator carries:
- Freight GST liability under the GTA framework — see freight GST reconciliation: RCM, GTA election and ITC for Indian manufacturers for the forward-charge vs RCM decomposition that operates upstream of the toll cost.
- Vehicle fuel and DSF (driver settlement float) reconciliations — fuel-card spend ties to truck and trip; the same trip-vehicle key drives the FASTag reconciliation.
- 3PL settlement liabilities where the fleet operator is itself a 3PL — see 3PL settlement reconciliation for Indian logistics and supply-chain operators for the multi-client revenue side.
The FASTag reconciliation is one rail in a four-rail stack — toll, fuel, freight billing, and statutory. A clean rail-by-rail close is what auditors look for in a CARO 2020 IFC walk-through for a transport company. See bank reconciliation in India for the foundational bank-side discipline that ties all four rails to the audit trail.