NEMT Trip Mileage Reconciliation Audit

Use this template for completed NEMT trips that have a claim or encounter record, a trip ID, and enough source data to compare billed miles to GPS route data. It works best for trips billed on loaded miles, but it also helps when deadhead miles or wait time are part of the payer policy and need to be classified correctly. Exclude trips with missing core identifiers until the record can be tied back to the claim and dispatch file.

Most organizations run it on a daily, weekly, or monthly cadence depending on trip volume and payer risk. High-volume brokers or providers often review a sample of trips continuously and then do a fuller monthly reconciliation for exception trending. The right cadence is the one that catches recurring variance patterns before post-payment audits or denial cycles build up.

This template is typically run by billing, compliance, operations, or quality staff who can access trip records, dispatch logs, and GPS traces. A reviewer should understand payer mileage rules, rounding practices, and the difference between loaded miles, deadhead miles, and wait time. If a variance suggests a systemic issue, operations and billing should both be involved in the follow-up.

Yes, it is designed to support documentation and internal control expectations commonly seen in Medicaid transportation programs, broker audits, and payer post-payment reviews. It also fits general compliance practices used in healthcare billing oversight and quality management. The template does not replace payer-specific policy, so mileage rules, tolerance thresholds, and documentation requirements should be configured to match the contract or state program.

Common findings include billed miles that do not match the shortest GPS route, inconsistent rounding or minimum-mile application, and missing explanations for detours or route changes. It also catches GPS gaps, device resets, and trips where pickup or drop-off times do not line up with dispatch records. Repeated variances tied to one driver, vehicle, or facility are another frequent pattern.

Set an internal exception threshold that reflects payer tolerance, your billing rules, and the level of risk you want to manage. Many teams use a tighter internal threshold than the payer’s allowed variance so they can investigate patterns before they become claims issues. The threshold should be documented in the template and applied consistently across all trips in the audit period.

Yes, and it should be. Different payers may use different mileage rounding rules, base-mile logic, minimum-mile rules, or documentation standards for variance justification. Add payer-specific fields, tolerance limits, and exception categories so reviewers can apply the correct policy without relying on memory.

Manual spot-checking often misses recurring patterns because it focuses on individual trips instead of the underlying cause. This template forces a consistent review of trip identity, billed miles, GPS route evidence, and exception follow-up, which makes it easier to defend decisions during an audit. It also creates a repeatable closeout trail instead of scattered notes across email or spreadsheets.

It is most useful when connected to dispatch, claims, GPS, and document storage systems so reviewers can pull the trip record, route trace, and supporting notes in one place. If your workflow uses a broker portal or billing platform, map the template fields to those records to reduce rekeying. Integrations are especially helpful when you need to trend exceptions by driver, vehicle, route, or facility.