Reference · built on requestOperator by FibricFleet, routes & field

Toll Dispute

Matches toll transactions to telematics trips by plate, time, and location and proposes a dispute for charges with no matching trip.

Request accessPricing ↗

About

Toll accounts bill by plate or transponder; telematics records where each plate actually was. Toll Dispute reads each statement as it lands as a file on your SFTP drop or as a mailbox attachment, and for every transaction looks for a trip that put that vehicle at that plaza at that time: Samsara trips and vehicle locations, Geotab LogRecord positions, or Motive vehicle locations. The plate comes from the vehicle record in the telematics system or Fleetio.

A charge with no matching trip, a plate that maps to no unit, or a duplicate of a charge already paid becomes a proposed dispute with the trip evidence attached, and a proposed hold on the vendor bill line. Accounts payable approves.

This is a reference listing. It documents what Fibric would read from Toll Dispute and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Toll statements as files: new arrivals on SFTP through directory listings and SSH_FXP_READ, or Gmail attachments through users.messages.attachments.get
  • Each transaction's plate or transponder, time, and plaza as the statement lists them, kept as read
  • Trips from Samsara's /trips/stream with startLocation, endLocation, tripStartTime, and tripEndTime, and gps from the vehicle stats feed
  • Geotab LogRecord positions from GetFeed, and Motive vehicle_locations, for fleets on those systems
  • The plate on each unit: licensePlate on Samsara vehicles, license_plate on Fleetio vehicles, or license_plate_number on Motive assets
  • The vendor bill for the statement in NetSuite or QuickBooks Online, so a disputed line can be held rather than paid

Proposed actions

  • Target capability: propose a dispute as a Gmail draft through users.drafts.create, addressed to the toll account, with the transaction and the trip evidence
  • Target capability: propose a hold on the bill: a memo change through PATCH /services/rest/record/v1/vendorBill/{id} in NetSuite, or a Bill update in QuickBooks Online
  • Target capability: propose a plate correction through PATCH /vehicles/{id} in Fleetio when a plate maps to the wrong unit
  • Target capability: propose a Slack message to fleet administration through chat.postMessage listing the statement's unmatched charges
  • Target capability: propose moving a processed statement to an archive directory through SSH_FXP_RENAME

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Dispute charges the trucks never earned

    Read the statement from SFTP, match each charge to a Samsara trip by plate, time, and plaza, and propose a Gmail draft for every charge with no trip within the tolerance you set.

    With SFTP, Samsara, Gmail API

  • Hold the bill line until the dispute settles

    For each disputed charge, propose a memo on the NetSuite vendorBill naming the transaction and the dispute, so the bill is not paid in full by routine.

    With NetSuite

  • Fix the plate that bills the wrong unit

    When a plate on the statement maps to a unit whose Geotab positions never approach the plaza, but another unit's do, propose the license_plate change in Fleetio with both trips shown.

    With Geotab, Fleetio

  • Catch the double charge

    Compare each transaction against charges already matched on earlier statements by plate, time, and plaza, and propose a dispute for repeats, with the earlier statement named.

    With SFTP, NetSuite

Requirements

  • Toll statements delivered as files you can read: a CSV or PDF export to SFTP, or an emailed statement
  • Telematics with position history covering the statement period: Samsara, Geotab, or Motive
  • A plate-to-vehicle mapping kept current in the telematics system or Fleetio
  • The vendor bill for each statement in NetSuite or QuickBooks Online, if you want holds proposed
Authentication
SSH public-key or password credentials for the statement drop, or Gmail OAuth 2.0 consent with gmail.readonly and gmail.compose; a Samsara API token, MyGeotab API user, or Motive API key; NetSuite token-based authentication or a QuickBooks Online OAuth 2.0 grant; a Fleetio API key.

Limits

  • Toll agencies publish no common API here; the job reads the statement format you receive and each new format needs mapping
  • A charge inside a gap in position data is marked unverifiable, not disputed
  • The dispute itself is filed by a person through the toll account's own process; the job drafts the letter and the evidence
  • Plaza locations are matched by the coordinates you supply per plaza; an unmapped plaza cannot be matched

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Toll Dispute ↗

Questions and answers

What does accounts payable approve?
Per statement, a list: each unmatched or duplicate charge, the matching attempt, and the proposed dispute draft and bill hold. Approving a charge creates the draft in Gmail and the memo on the bill. Rejecting it marks the charge accepted with the approver's name.
What evidence travels with a dispute?
The transaction as printed, the plate and unit, the nearest trip before and after by time, its start and end locations, and the distance from the plaza at the charge time. The record keeps the same fields plus the decision, so an auditor can retrace it.
Does it pay, refuse, or file anything on its own?
No. It never touches payment. A draft, a memo, or a plate change exists only after approval, and each charge is proposed once per statement. Filing with the toll agency stays with a person.
Ask about Toll Dispute

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy