FASTag Toll Reconciliation for Fleets: Trip vs Toll Matching

At month-end the fleet's FASTag account shows 1,840 debits, the transport management system shows 412 completed trips, and nobody can say which toll belongs to which trip. Finance books the whole ₹38.6 lakh to a single toll expense line. Hidden inside are a truck charged twice at the same plaza nine minutes apart, a tag debited while the vehicle sat in the yard for servicing, and a class adjustment that billed a 3-axle truck at the multi-axle rate.

Each of those debits can be recovered through the issuing bank, but only if someone finds it, ties it to a trip and submits the evidence NPCI now demands within the dispute timelines. A toll match that runs daily against trip and GPS records turns an unexplained cost line into a short exception list, and on a typical fleet it recovers around 1.5% of toll spend that would otherwise be written off.

• What this guide covers: the records a toll match needs, how to build an expected toll per trip, the matching rules, and how duplicate, class-mismatch and blacklist cases map to NETC chargeback codes.
• What it adds: a matching query, a worked monthly ledger in rupees with a US contrast in dollars, a timestamped double-payment case and a rollout checklist.
• Market note: FASTag and the National Electronic Toll Collection (NETC) network are Indian; the US has no single national equivalent, so US figures appear only as a contrast.

Why the FASTag statement and the trip sheet disagree on day one

A FASTag statement records when a plaza presented a transaction, not when the truck drove through. Until each debit is tied back to the reader read time, plaza and vehicle, the statement cannot be compared with trips at all.

The issuing bank's statement is a payments record. Each line comes from an acquiring bank serving the plaza, and lines can arrive hours after the passage, in a different order, with debit adjustments raised later for the same passage. Trip sheets and transport management systems, by contrast, record planned routes and dispatch times. The two only meet when both are keyed to the same vehicle, the same plaza and a time window around the passage.

• Posting lag: a transaction may be presented to NPCI well after the reader read time, so it lands on a different statement date from the trip.
• Debit adjustments: plazas can raise a later debit adjustment, for example when they classify the vehicle in a higher class than the tag's mapped class.
• Return-journey pricing: discounts depend on each plaza's return window, which NPCI's response codes show can be 24 hours, 12 hours or the same day.
• Shared wallets: fleet tags often draw from one prepaid wallet, so a low balance on Monday night can put every truck's tag into an exception status at once.

Four records every toll match depends on

A toll match needs the issuer's transaction lines, the trip record, the vehicle's GPS trace and the plaza fare for the vehicle's class. Each comes from a different owner, so the first task is agreeing who supplies which field and how fast.

The issuer statement or API feed should carry the transaction reference, reader read time, plaza ID and name, the vehicle class charged, the tag ID, the vehicle registration number (VRN), the amount and the transaction type, whether debit, debit adjustment or credit adjustment. The trip record supplies the trip ID, vehicle, driver, origin, destination and planned route. GPS gives the times the vehicle passed within a set radius of each plaza.

Our broader fleet management software architecture guide sets out how fuel, tyres, tolls and trip settlement fit together in one platform. This article goes deeper into the toll piece only: the matching keys, the NETC dispute rules and the arithmetic of recovery.

Expected tolls per trip and the rules for matching each debit

Build the expected toll for each trip before it runs, from its route and the vehicle's class, then match each debit to it on vehicle, plaza and time. A debit that fits all three and the fare is closed; anything else becomes a named exception.

The expected list is a sequence of plazas on the planned route, each with the fare for the vehicle's class and any return-journey or pass benefit that should apply. On a closed-loop expressway, the fare depends on the entry and exit pair rather than a single plaza. Storing the expected list on the trip lets dispatch approve the toll budget with the trip and gives the matcher something to compare against.

-- Match FASTag debits to trips (PostgreSQL style)
-- Window: reader read time within 10 minutes of the GPS passage at that plaza
SELECT t.txn_ref,
       t.vrn,
       t.plaza_id,
       t.reader_read_time,
       t.amount,
       tr.trip_id,
       e.expected_fare,
       CASE
         WHEN tr.trip_id IS NULL                 THEN 'NO_TRIP'         -- NETC 3001 candidate
         WHEN e.plaza_id IS NULL                 THEN 'OFF_ROUTE'       -- internal review
         WHEN t.amount > e.expected_fare + 1  THEN 'FARE_VARIANCE'   -- NETC 3006 / 3026 / 3027
         ELSE 'MATCHED'
       END AS match_status
FROM   fastag_txn t
LEFT JOIN trip tr
       ON tr.vrn = t.vrn
      AND t.reader_read_time BETWEEN tr.dispatched_at AND tr.closed_at
LEFT JOIN gps_plaza_pass g
       ON g.trip_id = tr.trip_id
      AND g.plaza_id = t.plaza_id
      AND abs(extract(epoch FROM (t.reader_read_time - g.passed_at))) <= 600
LEFT JOIN expected_toll e
       ON e.trip_id = tr.trip_id
      AND e.plaza_id = t.plaza_id
WHERE  t.txn_type = 'DEBIT';

The 10-minute GPS window and the ₹1 fare tolerance are policy choices, not NPCI rules; set them from your own data after a month of shadow running. Run a separate pass for debit adjustments and credit adjustments, because they refer back to an original transaction rather than a new passage, and a second pass that groups debits by vehicle and plaza to catch repeat reads.

Duplicate debits and NPCI's 15-minute and 10-minute tests

NPCI defines when two debits at one plaza count as a duplicate. Same plaza and same direction within 15 minutes, or opposite directions within 10 minutes, qualifies for chargeback reason 3002, provided no credit adjustment has already reversed one of them.

The rule comes from Annexure II of NPCI circular NPCI/2025-26/NETC/005 dated 28 October 2025. The issuing bank must include the transaction reference, reader read date and time and plaza ID of the original transaction. The acquiring side is expected to raise a credit adjustment on its own for a duplicate under the duplicate policy, and should not contest a chargeback that meets the time test. Reads further apart need a different argument, usually that the truck never made a second passage.

FASTag duplicate debits qualify for NETC chargeback reason 3002 under NPCI circular NPCI/2025-26/NETC/005 when two reader reads at one plaza fall within 15 minutes in the same direction or 10 minutes in opposite directions. The fleet toll ledger should flag every such pair daily, with zero tolerance on the time test.

• Repeat read, same lane: two debits seven minutes apart at one plaza, both northbound; raise reason 3002 with the original transaction's details.
• No passage at all: a debit while GPS shows the truck parked 200 km away; raise reason 3001, toll services not availed, with a front image of the vehicle showing the tag and the RC copy, as NPCI now requires.
• Paid twice by different means: a FASTag debit for a passage the driver also paid by UPI or cash; raise reason 3011 with the plaza's receipt.
• Acquirer's counter-evidence: for reason 3001, the plaza must show a passage image with a legible plate and a timestamp within 5 minutes of the reader read time, so check that window before escalating.

Class-mismatch adjustments and the evidence banks now demand

Plazas can raise a debit adjustment when they judge a vehicle to be in a higher class than its tag's mapped class. To dispute one, the fleet must produce RC or Vahan proof of gross weight, axles and seating; from 1 December 2025, chargebacks without the listed evidence are rejected.

NPCI introduced three debit adjustment codes in the same circular: 1008 for a vehicle class mismatch where the passing vehicle's number matches the tag, 1009 where the number differs, and 1010 for plazas whose concession agreement uses a non-standard classification. The matching chargeback codes are 3023, 3024 and 3025. Code 1009 usually points to a tag fitted to the wrong truck, which is a fleet problem before it is a plaza problem.

• Evidence for 3023 and 3024: an RC copy or Vahan record showing gross vehicle weight, number of axles and seating capacity; for 3024, also an image of the vehicle with a legible number plate.
• Only RC or Vahan counts: NPCI's guidelines state that only RC or Vahan proof is valid for these class disputes, so a fleet register or invoice for the vehicle will not do.
• Rejection without evidence: a chargeback or representation submitted without the evidence is rejected with NRCS reason code 5225, and NPCI said such cases would attract a negative verdict if they go further.
• Tag-to-vehicle audit: before disputing a 1009 adjustment, confirm in your own register that the tag ID on the debit is fitted to the vehicle it is mapped to.

Class-mismatch debit adjustments under NETC codes 1008 and 1009 can be reversed through chargebacks 3023 and 3024 only with an RC copy or Vahan record of gross weight and axles, per NPCI circular NPCI/2025-26/NETC/005 effective 1 December 2025. Fleets should keep 100% of vehicle RC scans linked to tag IDs.

Blacklisted tags, unpaid passages and the e-notice clock

When a tag is in an exception status such as low balance or blacklist, the passage can be declined and the vehicle charged as a non-FASTag user. Unpaid passages recorded by toll equipment now also trigger an e-notice with a 72-hour discount window.

Three sets of rules overlap here. Under the National Highways Fee (Third Amendment) Rules, 2025, in force from 15 November 2025, a vehicle without a valid, functional FASTag pays twice the fee in cash or 1.25 times via UPI. Under the Second Amendment Rules, 2026, in force from 17 March 2026, an unpaid user fee recorded by electronic toll equipment is notified to the registered owner and payable at twice the toll, or at the original fee if paid within 72 hours.

• Representation window: an aggrieved owner or driver may submit a representation through the designated portal within 72 hours of the e-notice; it must be decided within five days, or the claim lapses.
• VAHAN restriction: dues unpaid after 15 days with no representation pending are recorded in VAHAN, and vehicle-related services may be restricted until they are cleared.
• Cooling period for chargebacks: for debits on tags in exception status, NPCI's Annexure III requires the issuer to wait 15 days in several scenarios and not to raise a chargeback at all if the tag was reactivated, for example by a recharge.
• Cash at plazas: NHAI announced in February 2026 that it was considering ending cash payments at national highway fee plazas, leaving FASTag and UPI; check the current position before relying on cash.

The case below, with illustrative times and references, shows how a low wallet balance turned one passage into two payments, and how the evidence kept on the trip recovered the extra one.

1. 21:05, wallet below threshold: the fleet's shared prepaid wallet drops below the issuer's minimum; tags on 25 trucks move to low-balance exception status.
2. 22:40, passage at plaza P-114: truck MH-04-AB-4471 on trip TR-2611-0381 reaches the plaza; the tag read is declined and the driver pays the non-FASTag rate by UPI, ₹1,350 against a FASTag fare of ₹1,080, keeping the plaza receipt.
3. 23:10, top-up: fleet finance recharges the wallet and the tags return to active status.
4. Next day 09:30, late presentation: the plaza's acquirer presents the 22:40 passage again and the tag is debited ₹1,080; the daily match flags transaction FT-88231904 as FARE_VARIANCE with a UPI payment already on the trip.
5. Day 3, 11:00, chargeback: the toll desk raises reason 3011, paid by other means, attaching the UPI receipt and the passage time; the ₹1,080 credit posts to trip TR-2611-0381 and the extra ₹270 surcharge is charged to the wallet-monitoring cost centre.

Unpaid user fee e-notices under the National Highways Fee (Second Amendment) Rules, 2026 cost twice the toll unless paid within 72 hours, and representations share that 72-hour window. Fleet toll desks should route every e-notice to the trip ledger within 24 hours, leaving two days to check GPS and decide.

Worked monthly toll ledger in rupees, with a US fleet contrast

In the illustrative month below, about 1.5% of an Indian fleet's FASTag debits were recoverable through chargebacks and a further 1.1% needed internal review. The US column shows a similar exercise on transponder statements, where disputes go to each toll agency instead of through a national network.

The Indian fleet runs 25 multi-axle trucks between Bhiwandi and Bengaluru, completing 412 trips in the month. The US contrast is a 25-tractor fleet using E-ZPass transponders on interstate routes. The E-ZPass Group describes itself as an interoperable network across 20 states whose member agencies hold the customer accounts, so each dispute is handled by the agency that billed it. All amounts are illustrative.

The recoverable share looks small, but on a fleet spending ₹4.6 crore a year on tolls it is about ₹6.9 lakh, more than the cost of one analyst running the match part-time. The off-route line is not a loss until someone checks it: some deviations are approved diversions, others are personal use or a toll-heavy route chosen against instructions, and the driver settlement process decides which.

Auditing toll charges on a transporter's freight invoice

A shipper or freight buyer paying tolls as a pass-through should check them against the route and vehicle class, not just the total. Ask for the FASTag lines behind each trip's toll charge as a standard invoice attachment.

Where a transporter bills tolls separately from the freight rate, the buyer is effectively paying the carrier's FASTag statement. The same expected-toll logic applies: the lane's plazas, the fare for the declared vehicle class and any return-journey benefit if the truck came back within the plaza's window. A billed toll above the expected figure is either a different vehicle class, a longer route or a charge that the carrier should have disputed itself.

• Vehicle class declared: the toll should match the class of the vehicle named on the e-way bill or lorry receipt for that trip.
• Route evidence: plazas on the toll lines should follow the agreed lane; ask for an explanation of any plaza not on it.
• Duplicates passed through: repeat reads within NPCI's windows are the carrier's to dispute, so they should not appear on your invoice.
• Tax treatment: access to a road or bridge on payment of toll is exempt under Sl. No. 23 of Notification 12/2017-Central Tax (Rate), so the toll debit itself carries no GST credit to chase.

For drivers who still pay some tolls from cash advances, those amounts belong in the trip settlement rather than the FASTag match; our guide to reconciling driver advances and trip expenses covers that side.

Which toll checks run as fixed rules and which need a controller

Matching and duplicate detection are arithmetic and should run without anyone touching them. Deciding whether an off-route toll was justified, or whether to dispute a class adjustment that might be correct, needs a person with the trip context.

Software that reads images, such as a model that extracts the plaza name, time and amount from a photo of a UPI receipt, saves typing and speeds up chargebacks. It should fill a draft case for the analyst to confirm, because a misread timestamp can push a claim outside the 5-minute evidence window and lose it. The table sets out which tasks belong where.

Rollout checklist for fleet and procurement teams

Start in shadow mode for one month, matching every debit but disputing only clear duplicates. Turn on the full exception workflow once the match rate on clean trips is stable and the evidence store is complete.

The checklist covers both owners of toll cost: fleets that hold the FASTag accounts and buyers that pay tolls through freight invoices. For fuel, which follows a similar receipt-against-trip logic but different measurement problems, see our guide on investigating fuel variance. More transport and freight guides are collected in the logistics and supply chain library.

If you want this match built into your transport or fleet platform, with daily feeds, expected tolls per trip and chargeback case files ready for the issuing bank, send your fleet size and lanes in a request for proposal.