TollMatch FAQ

No. TollMatch works with the accounts you have, whether you hold them directly with each agency or through a toll management provider. Nothing changes about how tolls are paid or which discounts you get. TollMatch audits what those accounts bill you.

Twelve flags in two buckets. Agency side: max tolls, duplicates, misclassifications, tolls overpaid on closed systems, express lane overcharges and violations. Fleet side: misreads, plate overcharges where a tag was present, non-optimal tags, unassigned tolls, unmatched tolls and potential misuse. Each transaction carries the expected amount, the overpaid amount and the reason.

The full reference, with causes and what to do, is on Mismatch types.

Weeks, not months. The history run on your last 30 to 90 days of toll and GPS data comes back within five to ten business days of complete data. Going live from there is a median of five business days from the data connections being confirmed. Disputes can be filed from the first week.

Each posted toll transaction against the GPS crossing it belongs to. From your GPS, TollTally reconstructs every trip and prices each crossing for that unit's class and payment method at that time. TollMatch matches the posted line to the crossing on unit, facility and timestamp and compares the two amounts. Same inputs, same result; every finding carries the GPS behind it.

Both are matched transactions. GPS + Rate Match means the charge fits the toll rules for that facility, class and time, and a GPS crossing by the paired unit confirms the truck was there. Rate Match means the amount fits the rules but there is no GPS crossing to confirm presence, usually because GPS was missing around that time. Everything else is a Mismatch with a reason.

No. A mismatch is a charge that does not fit the crossing, and the mismatch type says why. Agency-side types usually are overcharges and get disputed. Fleet-side types are charges your own tag and plate setup caused; the money is real, but the fix is inside the fleet, not a refund. A few, like a non-optimal tag, were billed correctly and simply cost more than they needed to.

Across fleets that have run TollMatch, 5 to 15 percent of toll spend carries an error of some kind, and the manual reconciliation it replaces runs to 40 to 80 hours a month. Your own history run is the number that matters; that is why we start there.

Two places, kept separate on the dashboard. Toll refunded: credits that come back after disputes. Tolls overpaid, month over month: the amount flagged each month, which falls once pairings are fixed, dead tags are pulled and the right tag type is in each truck. The second is usually larger over a year because it stops the leak rather than recovering it.

Max tolls on closed systems and non-optimal tags, for most fleets. Max tolls are refunded readily when entry and exit are shown on GPS. Non-optimal tags are not disputable but are a lasting saving once the right tag is in the truck for the lanes it runs.

Yes. TollMatch audits the statement after your discounts are applied. Max fares, duplicates, plate charges and misclassifications happen on discounted accounts just the same.

The evidence is generated for you: GPS route, entry and exit timestamps, billed versus expected, your notes. For max tolls, Create request sends the dispute to your toll management provider from the dashboard, and automatic disputes can be switched on for your fleet. For other categories you send the report to the agency or your provider, or export a batch as CSV. Where a provider holds the account, the provider files with the agency; you remain the account owner throughout.

For max tolls, duplicates and misclassifications with GPS entry and exit on the report, yes, routinely. Refunds are recognized automatically from later statements and tied back to the original transaction, so you see credit status and the percentage refunded without keeping a separate list.

Trailer tags and plates are audited alongside the tractor. TollMatch flags a trailer tag or plate charged separately for a crossing the tractor tag already covered, and trailer plate tolls where the tractor tag should have read. If you lease trailers, the per-trip attribution lets you rebill their tolls. For fleets that do not tag trailers, the view is mostly about violations on trailer plates.

Yes. A tag billing charges that follow no fleet unit's GPS, a tag whose share of transactions without GPS jumps, or a tag active in two places at once shows up in the Tag/Plate view and as Potential misuse. Deactivate it with your provider the same day. Toll charges on a stolen trailer's plate have also been used to trace where the trailer went.

The Non-optimal tag recommendation weighs each unit's toll spend and travel frequency by state and facility and says whether a different tag type would pay less for the lanes that unit runs. Whether managing two tag types is worth the spread is your call; the dashboard gives you the dollar figure per unit.

Whoever owns toll spend today, usually the toll or fuel tax manager, with accounts payable and the operations lead who moves tags between trucks. The weekly review is about thirty minutes. No new hire; the point is to replace the spreadsheet reconciliation, not add to it.

Yes, where trip data is provided. The overview breaks toll spend down by cost center and each transaction carries its trip and cost center, with the overpaid and refunded amounts already separated, so audited tolls flow into your allocation. Unassigned tolls sit outside any cost center until the tag is mapped, which is one reason to clear them.

No. TollMatch audits what you were billed. TollTally calculates the toll for each trip from GPS and lets you rebill it to a customer or reimburse a driver. They run on the same account and the same GPS feed; many fleets use both.

The Refunded tab lists every credited transaction with the original amount, the credit and the percentage refunded, for any date range. The Disputed tab shows what is still open and how old it is. Both export.

Agencies and providers post transactions weeks after travel, often 30 to 60 days. A range that ends today is still filling in. For monthly reporting use a range that is fully posted; the trend view makes the lag visible.

Processing, administrative and missing-transponder fees appear as Unmatched tolls, because they match no posted rate for any class. The dashboard shows them so you can decide whether each is legitimate and fix the cause when it is a missing tag or unregistered plate.

Every view exports as CSV for the selected range: Invoices with match status and mismatch status, Unit Summary, Tag/Plate, Off Policy Tolls. Dispute evidence reports download as PDF per transaction.

Three streams: GPS tracks from your telematics, posted toll transactions from your agencies or toll management provider, and the unit to transponder and plate pairing list. Trip data from your TMS is optional and enables cost center and off-policy views.

Methods, formats and naming are on Get started.

Samsara, Geotab, Motive and Platform Science through their APIs with a read-only token you issue, and other providers where an API or export exists. If there is no API, a daily file push to your MapUp SFTP folder or a shared drive works.

One to two minute pings are ideal. Five minutes works. At ten minutes and above a truck covers enough ground between pings that some crossings cannot be placed, so fewer mismatches are flagged and some max tolls cannot be evidenced. If your provider supports it, raise the ping rate in toll corridors only.

Preferred: an API pull from your toll management provider where one exists. Otherwise a read-only login to the provider or agency portal so we pull statements as they post, or you drop the daily, weekly or monthly export to SFTP or a shared folder. Some agency portals send a one-time code to the account email when a new session signs in; forward it to us or we schedule the pull for a time you can approve it.

CSV with a pipe separator is preferred; comma-separated CSV, JSON and Parquet all work. Name files with the fleet, the stream and the date they run to, for example FleetName_TollProvider_Invoice_12022024. Send one sample file before automating so we confirm the columns.

No. Everything is read-only. Telematics access uses the provider's own token or OAuth flow. Portal logins are shared through a password-manager share, never email or chat.

TollMatch uses GPS by unit, toll transactions and tag and plate pairings. It does not need driver names, licenses or HOS. If your GPS export includes a driver field it is not used in matching.

In MapUp's production environment on AWS, encrypted in transit and at rest, with role-based access and audit logging. MapUp maintains a SOC 2 report and the TollMatch web application is penetration tested annually by an independent firm. Data is used only for your audit and deleted on request at the end of the engagement.

United States and Canada. Coverage follows where toll authority data is available.

TollMatch is delivered as the web dashboard with full table exports. Toll calculation from GPS tracks and route polylines is available by API through TollTally and TollGuru on the same account.

Median five business days from complete data to a live dashboard, most fleets under eight. Access to the dashboard within a day of sign-up; automatic disputes on the day after the onboarding call. The history run before that is five to ten business days from complete data.

You stay the account owner. TollMatch prepares the evidence. If you hold agency accounts directly, you file with the agency. If a provider holds the accounts, the provider files with the agency on your behalf; Create request sends max toll disputes to them from the dashboard and automatic disputes can be switched on. MapUp's team supports the documentation and the weekly sync tracks what is open.

The GPS route on a map with the actual entry and exit marked, timestamps, the billed and expected amounts, the unit, transponder and plate, the notes you enabled for dispute, and your name and phone from your profile. One file per transaction, or a batch.

TollMatch recognizes credits on later statements, ties each to the original transaction and moves it to Refunded with the percentage refunded. You do not keep a separate list.

Set the status to Denied and add the reason in the notes. Denials are rare where GPS shows entry and exit; where they happen it is usually because the GPS gap at the crossing left the evidence thin, which points back to ping frequency or a unit that lost GPS.

File weekly. Recent trips are resolved faster, and the max toll evidence is strongest while the agency's own records for that day are fresh. Automatic disputes remove the question for max tolls.

No. The crossing was priced correctly for the tag that was used. The saving is forward-looking: put the better tag in the truck for the lanes it runs.

Use Report feedback on the row and say what you know. It logs under the transaction's notes and reaches the TollMatch team the same day. The usual causes are a GPS gap at the crossing or a pairing change we do not have yet.

No. Fleet Resolved records that the fleet-side cause is fixed: the tag replaced, the pairing corrected, the plate registered. It stops the charge recurring. The historical charge is recovered only if it was also disputed and the agency credited it, which shows as Refunded or Partially Refunded on the same row.

The row moves to Partially Refunded with the percentage, and the open balance stays visible for follow-up. Recovered is what the agency credited, not what was charged and not what was requested.

Where the tag or plate was valid and the account in good standing, yes, with the same evidence report. Where the violation was earned, the fix is inside the fleet: register the plate, replace the tag, keep the account funded.

They sign up at platforms.mapup.ai with a work email; you or they tell tollmatch@mapup.ai; we activate TollMatch on the account, usually within a few hours. If the list is empty after login, the sign-up email is different from the one we were given.

Your TollMatch manager, on the weekly thirty-minute sync for the first months and then as needed. Tickets go to the support address with the fleet name in the subject and, for a transaction, the unit, transaction ID and date.

P0, dashboard down or a data stream stopped: acknowledged within a business day, fixed within five. P1, a class of findings wrong or statements missing: next sprint, with releases every two weeks. P2, questions and requests: scheduled into the release train.

The forty-five minute onboarding call covers the dashboard and the dispute workflow end to end, and these pages are the written version. New users can join any weekly sync for a walkthrough.