Know which toll charges your fleet can verify.

Where we track passages today

Every country your fleet drives through, scored honestly: do we record a toll passage when one of your tracked vehicles crosses a toll point, or do we silently miss it?

Where the data comes from

Each covered country has a documented origin source — operator CSV, official API, OSM extract, or manually-maintained PDF. We re-fetch on the cadence shown so 2026 coverage doesn't quietly become 2028 coverage. Community-edited sources (OSM) queue deltas for admin review; official APIs auto-apply.

How Resource Coordinate actually reduces toll cost

One real mechanism that ships today, three roadmap items that don't. Honest about both.

Today — GPS toll shadow-billing

Your fleet's existing GPS trackers (Teltonika, OBD2, SinoCastel) report position. When a tracked vehicle's coordinates fall inside a known toll station geofence, Resource Coordinate records a TollPassage with the calculated fee, the driver who was assigned at that moment, the trip ID, and the time of day. That gives you:

• An independent toll number derived from your own GPS — reconcile against the operator's invoice each month, flag the gap.
• Per-driver private-vs-business split for company-car tax (DE Finanzamt, SE Skatteverket, FR URSSAF).
• Per-trip cost attribution so you know which routes are bleeding money.
• Time-of-day rates applied automatically (Stockholm, Oslo, London peak/off-peak).

Roadmap — not built yet

• Invoice ingestion from Toll Collect, Vinci, Telepass, ASFINAG — automatic reconciliation instead of manual.
• Km-on-tolled-network detection for Germany Maut, Austrian GO-Maut, Polish e-TOLL — these are per-km charges that geofences can't capture.
• VAT recovery package generation — 8th-Directive XML format ready for your accountant; no auto-submission.
• Vignette expiry tracker for Austria, Switzerland, Czech Republic, etc.