Why a trip was excluded from billing

The specific gaps that hold a trip back, and how to clear each one.

Written for
Billing
Reading time
1 min
Last reviewed
August 7, 2026

Exclusion is always for a stated reason against a specific trip. The list below covers effectively all of them, and every one is fixable while the trip is still yours.

ReasonFix
No proof of service capturedAsk the driver to add it while the trip is fresh, or record the exception and why
Trip not in a terminal stateClose out trips left open at end of shift — an in-progress trip cannot be billed
No payer on the tripSet the payer; trips created in a hurry frequently miss it
No rate for this service type and payerAdd the missing rate to the payer's rate table
Missing authorization numberAdd it to the trip where the payer requires one
Mileage outside toleranceCheck the odometer readings and the geocoded addresses; a bad geocode produces impossible mileage
Service type does not match the vehicle usedCorrect whichever of the two is wrong, so the record reflects the service actually delivered

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator