How to Audit Meter History

When reports of meter readings look wrong or “out of sequence,” this guide walks through how to investigate, clean up, and help prevent future issues by following the process below:

1. Understand Where Meter Readings Come From

Before you start auditing, identify the source of each reading. In Meter History, use the Source column and (when applicable) the Conflict Source tag to see how values entered Fleetio.

Common sources:

• Manual entries
  • Services
  • Issues
  • Fuel entries
  • Direct “Add meter” entries
  • Imports (CSV)
• Telematics
  • Providers like Geotab, Samsara, etc.
• Fuel system imports
  • Fuel card providers (e.g., Fleetcor, WEX)

Why this matters: You can only fix the problem at its root. For example, a bad telematics device will keep sending bad readings until it’s corrected, regardless of how many times you edit Fleetio.

2. Do a Quick Visual Scan for Red Flags

Open the asset’s Meter History and look for obvious anomalies:

• Repeating telematics readings
  • The exact same value, reported over many days
  • Often indicates a non-working or improperly provisioned device
• Impossible hour readings
  • Hours in the hundreds of thousands (e.g., 333,000 hours) that look like mileage or kilometers
• Unrealistic mileage
  • Extremely low mileage on an older asset (e.g., a 2015 vehicle with only a few hundred miles)
• Outlier manual entries
  • A single manual reading that is much lower or higher than the surrounding telematics readings

If you see any of these patterns, note:

• Which asset is affected
• What source is involved (manual, telematics, fuel import)
• When the anomaly first appears (date/time)

You’ll use this information later as your audit “starting point.”

3. Check Telematics Device Health and Assignment

If telematics appears as the source of conflict, confirm that the device itself is functioning properly and correctly associated with the asset.

Check the telematics record:

• VIN present
  • A missing VIN often indicates the device was never fully provisioned (did not complete its first activation/power-on cycle).
• Device serial present
• Device type that is not “None” can often indicate a non-powered asset and/or an inactive transponder.
• Device assigned to the correct asset

Red flags:

• Device shows no VIN and/or no serial
• Asset is receiving readings from a device that now appears unassigned
• Device type is None while still sending readings

Actions:

• Review the following:
  • Has this tracker been replaced on the vehicle?
  • Is this device newly installed?
• If Fleetio shows readings from a device that is not currently assigned, or behavior seems inconsistent with assignments:
  • Gather details (asset, device, timestamps)
  • Escalate to Support for deeper investigation

4. Verify Primary vs. Secondary Meter Configuration

Many meter issues stem from mismatches between primary/secondary meters in Fleetio and the telematics system.

Confirm the Intended Configuration

Review:

• What do you use as your primary meter?
  • Miles, kilometers, or hours?
• Are you actively tracking hours, or only distance?

Compare Fleetio vs. Telematics

• In Fleetio, check the asset’s primary and secondary meter settings.
  • On the Vehicle Details page, click the More Actions Button and select Edit Settings:
    
• In the telematics system, confirm how meters are configured for that asset.

Red flags:

• “Hour” readings that are extremely high and clearly look like mileage
• Users manually entering miles into a field that is actually configured as hours (or vice versa)
• Telematics is sending one meter as primary, but Fleetio is expecting another

Actions:

• Consider swapping primary and secondary in Fleetio to match telematics.

For Example, if the primary meter is configured as hours, entering miles as the primary will cause conflicts.

5. Isolate the First Point of Conflict

A successful audit depends on finding the first incorrect reading in the sequence.

Steps:

1. Open Meter History for the asset.
2. Scroll to find where readings begin to look wrong (e.g., the first unrealistic hour reading, or the first manual entry that doesn’t align with telematics).
3. Make a note of:
   • The date/time of that reading
   • The source (manual, telematics, fuel)
   • Any related records (e.g., associated fuel entries or issues)

This “first bad record” is your pivot point:

• Readings before it may need to be deleted or permanently voided.
• Readings after it are potentially salvageable once the configuration is corrected.

6. Clean Up Conflicting Meter Records

Always fix the configuration first, then clean up data.

Correct Configuration

Before editing history:

• Ensure primary/secondary meters in Fleetio match the actual use and the telematics setup.
• Confirm the telematics device is:
  • Properly provisioned (VIN and serial present)
  • Correctly assigned to the asset

Delete or Void Incorrect Readings

Once the configuration is correct, work from your pivot point:

• Review what can be safely removed vs. what must remain:
  • Telematics-only readings that are clearly wrong can often be deleted.
  • Readings tied to other system records (e.g., a fuel entry) may need to be left voided, not deleted. These readings cannot be removed in a bulk action.

Typical approach:

1. Delete clearly bad telematics readings
   • Example: a block of Geotab hour readings around 300,000 that are actually mileage.
   • Limit your delete range to a known-bad portion of history (by date/source).
2. Preserve system-related records
   • If meter values come from fuel entries, services, or issues, you may:
     • Leave them voided to avoid impacting those primary records.
     • Optionally edit/update if the record has the correct values, and this won’t create new conflicts.
3. Bulk delete carefully
   • Only use bulk deletion when you have:
     • A clear scope (e.g., all telematics meter records before a certain date)
     • Confirmed that they aren’t linked to critical records.

Unvoid and Rebuild a Clean Sequence

After removing the initial conflict(s):

• Unvoid good records that follow your corrected configuration.
• Confirm that:
  • The readings increase logically over time.
  • No new conflicts are introduced.

Refresh From Telematics (If Applicable)

When you’re confident the configuration is correct:

• Use Refresh Meter via Telematics Device for that asset.
• Verify that:
  • New readings align with expectations.
  • No new conflicts are created.

7. Handling Fuel History and Meter Conflicts

If fuel history looks wrong, or distance/fuel metrics don’t match expectations.

Confirm Integration Status

• Check if the fuel integration (e.g., Fleetcor) is Active with transactions appropriately assigned.

Identify the Source of Fuel Entries

In fuel records and their meter history, determine:

• Are the entries manual fuel entries created directly by users?
• Are they imported from a fuel card provider?

Common Root Causes

• Staff keying incorrect odometer values at the pump
• Meters misconfigured:
  • User believes they’re entering miles, but the primary meter is set to hours
• Telematics sends bad or recycled meter readings, which can skew distance and fuel calculations

Guiding users with best practices:

Help the team understand where to focus:

• At the pump:
  • You may need to retrain drivers or staff on accurately entering odometer readings and hours.
• In telematics:
  • You may need to fix device provisioning, asset assignments, or primary/secondary configuration.

If fuel entries are tied to the bad meter readings:

• Leave incorrect meter values voided rather than deleting them if you must preserve the fuel record itself.

8. Preventing Future Meter Issues

Most audits are preventable with better upfront setup and communication.

During Onboarding

• Confirm primary/secondary meters before telematics activation:
  • Align on whether the primary is miles, km, or hours.
• Align telematics and Fleetio configs:
  • Make sure both systems treat the same metric as primary.
• Avoid importing historical meter readings in initial CSVs unless absolutely necessary:
  • Bulk-imported meters can be stale or inaccurate, complicating future audits.

Before Full Rollout

• Validate that telematics devices are fully provisioned:
  • VIN and serial populated.
• Perform spot checks:
  • Review the Meter History for several assets after the first readings appear.
  • Look for stuck values or obviously incorrect data early.

Ongoing Best Practices

• Encourage users to:
  • Periodically review Meter History for anomalies.
  • Provide internal training for accurate pump entry if drivers manually record meters.
• Internally, coach teams to:
  • Use 'source' and 'conflict source' consistently during troubleshooting.
  • Escalate patterns that suggest systemic telematics issues rather than one-off data errors.

9. When to Consider a “Clean Slate”

In severe cases, historical data may be too inconsistent to repair record by record.

A “clean slate” approach may be appropriate when:

• Primary/secondary or telematics assignments were incorrect for a long period.
• You have a clear date after which the configuration is correct, and readings look reliable.

Typical clean slate steps:

1. Identify a cutoff date after which data should be trusted.
2. Bulk delete or permanently void meter records prior to that date, focusing on:
   • Telemetry-based records, where possible.
3. Use telematics to rebuild meter history from the cutoff date forward.

Set expectations clearly with the user:

• This is a manual, one-time cleanup to resolve legacy issues.
• Correct setup and adherence to best practices should prevent the situation from recurring.