Fraud and anomaly detection in your vehicle fleet
A vehicle with no activity for 60 days, general maintenance invoiced twice in 90 days, a contractual mileage exceeded: Dadycar's business rules spot them before the accounts close.
Hosted in the European Union · GDPR · Flotauto 2025 Innovation Award · free up to 50 vehicles, then €6 excl. VAT per vehicle per month
What anomaly detection changes
- 19 anomaly types in three families: data integrity, potential fraud, contractual compliance.
- Three priority levels (high, medium, low), with a handling deadline and a notification channel.
- With no device: the rules apply to the management data already held in Dadycar.
What escapes a manual check
- A duplicated servicing expense disappears into the month's pile of supplier invoices.
- A vehicle that no longer runs keeps costing lease, insurance and fuel card.
- A contractual mileage overrun is discovered at return, together with the lessor's penalty.
What you get with Dadycar
The Anomalies module is a business rules engine applied to fleet data: vehicles, contracts, expenses, servicing, fuel cards, odometer readings. It is separate from the telematics alerts coming from sensors.
Potential fraud
Expenses repeated over a short period, such as general maintenance recorded twice in 90 days, or activity inconsistent with the vehicle's data.
Data integrity
A vehicle with no activity at all for 60 days, an inconsistent odometer reading, an incomplete record: wrong data is flagged before it distorts the reports.
Contractual compliance
Contractual mileage exceeded or about to be, according to the mileage terms, contract deadline approaching, gap between usage and contract.
Priority and deadline
Each anomaly type has a high, medium or low level; each instance has a handling deadline and a status.
Notification to the right channel
The notification channel is set per anomaly type; the owner receives what concerns them, the dashboard shows the rest.
Instances tracked
Every trigger creates an instance attached to the vehicle, with its history, to document internal control and exchanges with suppliers.
How it works
- 1Feed Dadycar with your management data. Vehicles, contracts, expenses, fuel cards and odometer readings: the rules apply to what is already entered or imported.
- 2Choose which anomaly types to switch on. Priority, deadline and notification channel for each type.
- 3Handle the instances. The dashboard shows open, overdue and resolved anomalies; sensor signals stay in the telematics alerts.
Who it is for
- Finance and management control: duplicated expenses and dormant vehicles spotted before the accounts close (see the role page).
- Fleet managers: contractual mileage monitored with no spreadsheet (see the role page).
- Transport and logistics: fuel cards and servicing checked across fleets of several hundred vehicles (see the industry page).
Your first anomalies, visible during the trial
Import your fleet and your expenses: the standard rules run on your data and show you what the spreadsheet was missing.
Your questions before getting started
- “Do I need a device?” No. Anomalies relate to management data; telematics enriches some rules with real mileage.
- “An anomaly is not proof of fraud.” Correct: the module flags a situation to check, with its priority; the decision stays with the manager.
- “How long does it take to start?” The anomaly types are predefined; they run as soon as the matching data is in Dadycar.