Fleets and operations
No. TollTally works from the GPS your telematics or ELD platform already produces. Nothing is installed in the vehicle and no transponder reader is involved.
Geotab, Motive, Samsara, Platform Science and Wialon, each with its own partner page. Fleets on other systems, and fleet technology providers, send GPS directly by API, SFTP, webhook or file upload, or run the customer-hosted SDK. Every source is normalized into one trip model before any toll is calculated.
First-time setup on a marketplace add-in takes 2 to 3 hours. A live dashboard is up within 12 to 24 hours of the telematics connection, and a completed trip's tolls are in the dashboard within 24 hours. API integrations go live the same day the key is issued; direct feeds take days to weeks, paced by the customer's IT and security review.
Self-serve from the Subscriptions tab at platforms.mapup.ai: TollTally Dashboard under TollTally Web for the connected dashboard, TollTally Route Specific Tolls for the API. Enterprise fleets email tolltally@mapup.ai and we enable it. Geotab fleets can also start from the MyGeotab Marketplace.
Every 24 hours by default. Fleets whose billing needs it are set to refresh every 30 minutes.
Yes. Send past GPS and TollTally calculates tolls for trips already driven, on the same engine and on the rates in force at the time of each crossing. Most fleets check one full statement period this way before they change a billing process.
Axle count, weight, height, length, vehicle class, tractor and trailer configuration, payment method (tag or plate), transponder ID and plate, and emission class where a country prices on it. The telematics platform supplies what it holds; you confirm the rest in the Unit view. The same road prices differently by axle count, weight or tag type, so this is a setup step, not a detail.
A unit whose transponder is mapped and confirmed shows a verified tag badge and is priced at the tag rate. A unit without one is priced at the plate rate, which is the honest number for a vehicle that has no working tag.
Yes. Set a managed-lane policy and any leg that uses an express lane, HOV or HOT lane the policy does not authorize carries a flag in the Trip view. The flag does not change the toll; it changes who pays it. Fleets use it for driver charge-back, coaching, or to keep the leg off the customer invoice.
Yes. Exclude the trip and it drops out of the billable export while staying in the record and the unit total.
The toll data covers 900 plus toll authorities in 100 plus countries, including European distance-based truck tolls priced by emission class, congestion charges and vignettes, as well as US tag and plate systems.
TollTally computes the expected toll from where the vehicle went. TollMatch compares that expected toll line by line against what the authority or transponder program actually charged, classifies every posted transaction and files the disputes. TollTally is what you bill from; TollMatch is what you recover with.
Yes. TollTally does not pay tolls; your transponders and toll accounts keep working as they do today. TollTally gives you the crossing, the trip and the expected toll within the refresh window instead of weeks later on a statement, and TollMatch reconciles the statement when it arrives.
Trucking, rideshare, last-mile and delivery, rental, field service and mobility fleets, from a few vehicles on a marketplace add-in to platforms pricing millions of trips through the API and SDK. Anywhere a toll has to be billed to a customer, reimbursed to a driver or allocated to a job.
The same GPS that TollTally prices is the basis for jurisdiction mileage. Ask ifta@mapup.ai to enable IFTA on the same account once the telematics connection is live.
TollTally is MapUp's GPS-based, real-time toll billing platform for commercial fleets.
Toll agencies typically take 30–60 days to issue an invoice, with inconsistent formats. TollTally produces the toll cost instantly right after the trip using the GPS instead of weeks later.
TollGuru is MapUp's underlying toll routing/pricing engine and API.
No — TollTally calculates and reports what a vehicle owes in tolls; it doesn't remit payment to the tolling agency itself.
TollTally gets the GPS route, matches it to the road network, and calculates the tolls on that route.
Typically within 24 hours of trip completion — most trips show toll information within just a few hours.
Toll costs in Europe can depend on vehicle type, number of axles, weight, height, Euro emission class and CO₂ emission class, depending on the country and toll road.
Yes — managed and express lane tolls are calculated and shown alongside standard tolls.
Typically within 95–98% of the actual toll charge. Accuracy depends on the vehicle type being configured correctly, GPS data quality, and how closely the modeled lane/time assumptions match what actually happened on the road.
Yes, directly — vehicle type affects toll calculation, so it needs to be set correctly to get accurate costs.
You can update it any time in Vehicle Settings. The change only affects future toll calculations — it does not retroactively recalculate historical trips.
This can happen when GPS data quality was poor or the tracking device wasn't reporting reliably during the trip. Check whether the GPS route is complete, then contact support if the toll is still missing.
Yes — timestamps are captured at each toll gantry/plaza the vehicle passes.
Yes. You can select your preferred currency in Vehicle Settings for whichever currency you want the tolls to come in.
Go to platforms.mapup.ai, sign in with your MapUp credentials (email and password), and you land on the Home Page and from there you can go to TollTally Dashboard. A signup option is available on the same page for new accounts.
Yes — a 14-day free trial of the TollTally Dashboard plan.
The trial activates automatically the first time you successfully connect a supported telematics/marketplace account — for any provider except Geotab (Geotab-connected accounts follow a separate path and aren't trial-gated this way).
Access to the dashboard and the ability to make API calls are blocked once the trial period ends, with no grace period. You'll need to upgrade to a paid plan to regain access.
No — some enterprise/pre-arranged accounts are provisioned directly onto an active paid plan and skip the trial entirely.
Yes — contact support to add additional users for your team; each person gets their own login credentials.
No — TollTally is web-based and works on any device with a modern browser, including phones and tablets, but there's no dedicated mobile app.
Settings → Vehicle Settings shows a table of all fleet vehicles.
Click "Edit Vehicle" on that vehicle's row, update the relevant fields (type, name, height, weight, etc.), then click "Update Vehicle" to save.
Both — vehicles sync automatically from a connected telematics provider, and you also have the option to add a vehicle manually.
That's the role of TollMatch, a related but separate MapUp product built specifically around agency invoice reconciliation and dispute workflows.
Finance and billing
As soon as the crossing is in the dashboard, which is within the refresh window (24 hours by default, 30 minutes on request). Billing cycles compress from 30 plus days to under one hour. The billable toll per trip is in the scheduled export with the job reference carried through.
The tag rate, for a unit with a verified tag. Every crossing carries both the tag rate and the plate rate; the plate rate is what the statement will show if the tag was not read, and that difference is a dispute for TollMatch, not a cost to pass on.
Every transaction carries the facility, the direction and a facility-local timestamp, which is how statements are stamped. Export with facility-local timestamps and match on unit, facility and time. Differences fall into a short list of causes; the fleet guide lists them with an owner for each.
Yes. Trips are reconstructed from GPS and costed per leg, so a multi-stop day is allocated to the job, customer or cost center each leg served. Cost-center allocation, per-trip billing and reporting come from the same records.
Whatever columns you choose: unit, facility, direction, facility-local timestamp, class applied, tag rate, plate rate, trip and leg, job reference, flags. Scheduled SFTP to your TMS, ERP or payroll system, or the same records by API. From the dashboard: CSV or Excel of any filtered view, and a Toll Activity report as PDF to send a customer with the invoice.
Export the Vehicles list (vehicle name, VIN, plate) as CSV and join it to your roster on VIN or plate.
Every toll walks back to a crossing on a map: the trace, the facility, the class applied and the rate version. An auditor can go from an invoice line to the evidence without a spreadsheet in between.
Carriers that bill tolls from the trip record recover 80 to 90 percent of toll costs as accessorial charges to shippers. What you recover depends on your contracts; what TollTally supplies is the per-load toll, on time, with the evidence.
Yes. Trip-level history by lane and unit is what you price bids on. For a lane you have not driven, the same engine prices a route polyline through the API.
Not guaranteed to be identical — it's a GPS-based estimate, which is why it's labeled "GPS Toll" rather than a confirmed charge. TollTally states its calculation is typically within 95–98% of the actual toll agency charge.
An auto-generated PDF proving what toll charges a vehicle incurred — with a branded header, vehicle information, itemized toll transactions (location, date, time, amount), totals, and a route map — used for customer billing, driver reimbursement, and internal recordkeeping.
Go to the Trips tab, find the trip, click "Toll Activity Report," then click the download button - the PDF downloads automatically. You can also download reports for multiple trips at a time from the Units view.
Yes — click "Export" on the relevant table, set your date range and filters, choose CSV or Excel, and click Export.
Generate the PDF Toll Activity Report for the relevant trip(s) - which includes the plaza-level breakdown and route map - or generate a unit breakdown for multiple trips across custom dates, and attach it to the customer's invoice as documentation for toll charges, without waiting on the agency's own invoice.
Drivers and reimbursement
From the TollTally record, per trip or per settlement, at the tag rate, on your payroll cycle. Nobody waits for the authority statement and nobody pays out of pocket.
No. TollTally works from the vehicle's GPS. Drivers do nothing.
Open the crossing in the Transaction view. The map shows the trace through the plaza and the time. If the trace supports it, the toll stands; if the record carries a quality flag, review it before you settle. Six steps are in the fleet guide.
The leg carries a policy flag. The toll is priced at the rate in effect; the fleet decides whether to charge it back, coach, or keep it off the customer invoice.
Yes. The same per-trip record, exported per unit or per driver, on whatever settlement cycle you run.
Fleets report saving 15–30 hours per week on reimbursement processing, and typically reducing reimbursement costs by 20–25%, by removing the wait on agency invoices.
IT and integrations
Read access to vehicle position and vehicle attributes for the units in scope. Geotab and Motive are connected in the dashboard with your platform credentials; Samsara with an API token shared through the secure channel we set up. Credentials are never exchanged by email or chat.
Create a View Only service account in MyGeotab, authenticate it in TollTally under My integrations, download the add-in package TollTally generates for your database, and upload it under Administration, System Settings, Add-Ins. Your team then opens TollTally from the MyGeotab Add-Ins menu with their MyGeotab login. Steps in the setup guide. The marketplace path starts free for 14 days.
No. On the Geotab Order Now path you enroll the units you want processed; enrollment is what starts processing and billing for those units. Enrolled units appear in the Vehicles view with trips once data flows.
Anyone in the same Geotab database the service account is connected to. An administrator installs; standard users then open it from the Add-Ins menu. A user who sees a Contact Us page instead of the app is in a different database.
Yes. Connect each database with its own service account and install the add-in in each.
The Geotab service account is not connected. Re-authenticate it in TollTally under My integrations and reopen the add-in. If it worked before and stopped, the service account password changed: reconnect it and the add-in picks up the new credentials.
Yes. Send GPS tracks with timestamps to the GPS tracks endpoint and get tolls back; fleets that will not share vehicle data run this way without vehicle identity. Direct feeds by SFTP, webhook or file upload are also supported.
Scheduled SFTP with a column selector and facility-local timestamps, or by API for a system that pulls. Both are configured once at setup.
In MapUp's production environment. MapUp holds a SOC 2 report and runs GDPR-aligned controls. Fleets with data-residency requirements can run the customer-hosted SDK inside their own cloud account, where trip inputs never leave their boundary.
The device is not reporting position on the telematics side: not paired, powered down, or not yet transmitting. Confirm the unit reports in the provider portal. TollTally cannot price GPS it does not receive.
The credential's scope or the vehicle list on the telematics side does not include them. Check the vehicle list and the group or scope of the credential; we resync.
Nothing on your side. Each provider is an adapter into one common trip model; the calculation layer never sees the provider format.
Yes. Providers integrate by API or SDK and price trips or reimburse drivers inside their own product; several telematics and mapping platforms do. Write to tolltally@mapup.ai.
No separate sandbox. An account is a live production account with standard rate limits and plan caps; tell us the volumes you plan to test and we raise the caps for the evaluation.
Go to Settings → My Integrations, find your provider's card, and click "Add Account" (or "Authenticate") to start the connection flow.
Most providers (Motive, Samsara, FTS, Wialon, Echoes) connect via a standard OAuth2 flow.
Yes — a single TollTally account can have multiple marketplaces/telematics integrations connected at the same time, and Geotab specifically supports connecting multiple sessions.
You'll see a notification in TollTally. Go to Settings → My Integrations and click "connect" to re-authenticate — your historical data remains intact through a disconnect/reconnect.
Yes, Motive customers can access TollTally directly through the Motive App Marketplace via the dedicated integration, or connect via the main TollTally dashboard.
There's a "contact us" option at the bottom of the Marketplace Integrations page specifically for requesting a provider that isn't yet supported.
Developers
Points a vehicle produced need map matching: send them as a file to GPS tracks, or as a polyline to polyline map matching. A route from a mapping service goes to the complete polyline endpoint and is priced as drawn. A GPS trace sent to the complete polyline endpoint can miss a plaza.
No. TollTally has its own key, in the TollTally API Keys section of the dashboard once you subscribe or we enable the product; up to 10 keys per account. Both go in the x-api-key header.
By endpoint and route distance. Complete polyline: 1 transaction up to 300 miles, 2 from 301 to 1,000, 3 above. GPS tracks and polyline map matching: double that, because map matching and pricing count separately. Any input or routing error counts as one. Full table on the transaction counting page.
ISO 8601, YYYY-MM-DDThh:mm:ssZ, for example 2023-07-17T13:40:42Z. Local times without an offset are the most common upload error.
Send a timestamp per point along the route (locTimes) on the time-aware polyline form. Each crossing is then priced at the time the vehicle reaches it. Without locTimes the request falls back to departure_time, and without that to the current time, which is the wrong rate window for a historical trip.
On a ticket system the track has to cover both the entry and the exit plaza. Extend the track, or on a live feed start capture before the vehicle enters the system.
Any. OSM, Google, HERE, TomTom, Mapbox, Bing, Apple, Esri and others; send the encoded polyline or the path. Examples for Google, HERE and TomTom are on GitHub, linked from the developer guide.
Support
tolltally@mapup.ai, +1 510 766 0570, or the shared channel your fleet was given at onboarding. Include the fleet name, the unit, the facility and the time. First response within one business day.
Under Usage and Invoices in the dashboard, with each invoice available to download. Subscription and billing questions go to billing@mapup.ai; toll questions go to tolltally@mapup.ai.
Geotab and your reseller handle platform checks (MyGeotab or the marketplace slow or down). TollTally handles the add-in and the tolls. Send the database name, the unit and the time and we take it from there.
Unit ID, facility and direction, approximate time and time zone, what you expected and why (statement line, tag rate, class), and a screenshot. A specific crossing is reconstructed the same day.
Facility, direction, date and the amount you expected. The toll data team corrects the rate table or geometry and the affected trips are regenerated.
P0, no toll records for the fleet or the dashboard down: worked immediately, fixed within five business days. P1, a feature not working for some units or users with a workaround: fixed within one sprint, with a build every two weeks. P2, cosmetic or usability: scheduled in the release plan. Enterprise agreements carry their own terms and apply where stricter.