FleetSync: Linking the Driving-Licence Check with Fleet-ID

Overview

The FleetSync service automatically reconciles the electronic driving-licence check from the provider Fleet-ID with FMWeb: successful checks are collected regularly and transferred into the driver file – you no longer maintain the check dates by hand.

For each check, FMWeb updates the matching driver:

• "Zuletzt vorgelegt am" (Last presented on) (the date of the last successful check)
• the next driving-licence check (calculated from the driver's licence interval)
• an entry in the Kontrollhistorie (check history) (source "Fleet")

Only checks that are newer than the date already stored are taken over. Without a valid FleetSync license, the service skips processing and logs this in the log (Article 112).

Configuration

Systemadministration → Hintergrundaufgaben (System Administration → Background Tasks) (/applications/backgroundtasks/dashboard) → "FleetSync Task" tab:

1. Switch on "Ist aktiv?" (Is active?) and set the waiting time between runs (in minutes).
2. Select the API Version:

• V2 (recommended): enter the Base URL (default https://my.fleet-id.de/) and the Bearer Token. The token comes from your Fleet-ID account.
• V1 (Legacy): enter the API Benutzer (API user) and API Passwort (API password).

1. Create assignments ("Zuordnung hinzufügen" / Add assignment):

• For V2, assign each FMWeb tenant its associated Fleet-ID customer ID ("Mandanten ↔ Fleet-ID Kunden-ID"). Only assigned tenants are synchronized.
• For V1, you simply select the tenants to synchronize.

1. Click "FleetSync Einstellungen testen" (Test FleetSync settings) – for V2, FMWeb saves the settings and checks the connection using the first assignment. As long as the test has not succeeded while the service is active, Speichern (Save) remains locked.

Driver assignment: the "Fleet-ID" field

The reconciliation is done via the Fleet-ID field in the driver file, which must contain the barcode/seal number of the driving licence (the number of the check seal registered with Fleet-ID). Drivers without a stored or non-matching number are not updated; Fleet-ID drivers without an issued barcode are skipped by the service.

Tip: In the driving-licence reminders you can use "Nur Mails versenden, wenn Fleet-ID eingetragen wurde?" (Only send mails if a Fleet-ID has been entered?) to limit the FMWeb reminders to drivers without an external check, or to combine them deliberately (Article 05).

Monitoring and troubleshooting

In the "Logs" tab of the background tasks dashboard you see a summary per run, e.g. "FleetSync v2: tenant 1: 42 drivers returned, 40 matched, 3 updated". You open error lines (invalid token, unknown customer ID) with a click to reveal the full error text (Article 15).

Frequently asked questions

A driver is never updated – what's the reason? Check: (1) the Fleet-ID field in the driver file = the barcode number of the seal, (2) the driver's tenant is assigned, (3) the driver's licence interval is maintained, otherwise the next check cannot be calculated.

V1 or V2? Always set up new installations with V2 (token-based, assignment per customer ID). V1 only remains for existing accounts on the old Fleet-ID API.

Related articles

• 05 – Tire-Change and Driving-Licence Reminders
• 15 – Background Tasks Dashboard
• 117 – Connecting YellowFox Telematics
• 20 – Managing Vehicles and Drivers