Fleet Fraud Detection

Filters records based on the ChargePoint card serial number used in the transaction, useful for tracking unauthorized card use.

Filters records by the system-calculated travel distance between plug-in and plug-out locations, helping detect anomalies in reported vs. actual movement.

Filters by the vehicle’s current operating state.

Filters by specific types of fleet activity events (for example, Session Start, Session End) to isolate suspicious actions.

Filters data by the exact time of the event, used to identify transactions outside expected hours.

Filters based on the fee charged for a session—useful in identifying unexpected costs or billing issues.

Filters by the name of the fleet, helping narrow down fraud checks within a particular fleet.

Filters by vehicle license plate, helping detect mismatched vehicle identities.

Filters by the backend system’s logged time.

Filters by anomaly descriptions or system-generated flags, ideal for quickly reviewing suspected fraud cases.

Filters by the organization the fleet belongs to, for group-specific fraud analysis.

Filters by the EVSE (charging station) port used helps to identify possible port misuse.

Filters by system-suggested next steps (for example, Review, Block Card) for suspected fraud incidents.

Filters by the unique session identifier, critical for reviewing specific charging sessions.

Filters based on the total energy consumed during the session, helping flag unusually high or low consumption.

Filters by the latitude of the charging station, useful for geographic correlation of vehicle activity.

Filters by the longitude of the charging station, paired with latitude to detect location fraud.

Filters by the name of the station that helps to isolate sessions from unfamiliar or suspicious locations.

Filters by power delivered at the station, used to detect inconsistencies in power draw.

Filters by the specific ID of the vehicle’s telematics unit, useful for identifying spoofed or missing devices.

Filters whether the vehicle was reported as charging, helping detect mismatches between vehicle and station data.

Filters based on vehicle GPS latitude, used to confirm if the vehicle was near the station.

Filters based on vehicle GPS longitude. Pairs with latitude for geo-fencing validation.

Filters the power draw as reported by the vehicle, useful in identifying differences from station-reported data.

Filters by the third-party provider of vehicle telematics data. Useful when comparing data quality or discrepancies.

Filters by the time the vehicle telematics data was captured and used to sync with event timestamps.

Filters by the transaction ID, which is useful when comparing billing or investigating a specific charge.