Non-emergency medical transportation providers live on thin margins, and billing is where many of them lose money. Each trip has to match a broker's authorization, carry the right codes and modifiers for the state, show mileage the payer will accept and prove the ride happened. A small error repeated across hundreds of trips a week adds up quickly.
This guide covers who pays for NEMT trips, how brokers work, which codes and modifiers claims use, what trip data a claim needs, how mileage should be calculated, how claims reach brokers and managed care plans, and how billing software should handle proof of service, denials and reconciliation.
What is NEMT billing software?
Choosing NEMT software?
Read Agnotic's buyer's guide to NEMT software, covering dispatch, driver apps, billing and broker integration.
NEMT billing software turns completed non-emergency medical transportation trips into claims for Medicaid, brokers and managed care plans. It matches each trip to its authorization, applies the payer's codes and modifiers, calculates billable mileage, attaches proof of service and tracks payment, so transportation providers are paid for every trip they complete.
Billing works best when it is part of the same system as scheduling, dispatch and the driver app. Then the trip record that the driver completes is the record that gets billed, with no re-keying between systems.
Who pays for NEMT trips?
Most NEMT trips are paid by state Medicaid programs, either directly, through a transportation broker, or through a Medicaid managed care plan that may itself use a broker. Each arrangement has its own claim format, portal and rules.
- Fee-for-service Medicaid: The provider bills the state Medicaid program directly using the state's codes and claim format.
- Brokers: A broker takes trip requests, assigns them to providers and pays providers, often through its own portal or file format.
- Managed care plans: The plan covers transportation for its members, directly or through a contracted broker.
- Other payers: Some Medicare Advantage plans, workers' compensation carriers and facilities pay for rides under their own contracts.
A single provider often works with several of these at once, so billing software must keep each payer's rules separate and apply the right set to each trip.
How do Medicaid NEMT brokers work?
Federal rules at 42 CFR 440.170(a)(4) let a state provide NEMT through a transportation broker that manages trips under a contract. The regulation sets requirements for broker programs, including how brokers are selected and how they oversee the transportation providers they use.
- Trip requests: Members or facilities request rides through the broker, which checks eligibility and authorizes the trip.
- Assignment: The broker assigns the trip to a contracted provider, with a trip or authorization number.
- Standards: Brokers check that providers meet requirements for drivers, vehicles and insurance.
- Payment: Providers submit completed trips to the broker, which pays at contracted rates.
For the provider, the broker's trip number is the key to payment. Billing software should import trip assignments from the broker and use that number throughout, so the completed trip matches the authorization exactly.
Which codes and modifiers do NEMT claims use?
NEMT claims usually use HCPCS codes for the type of trip and for mileage, plus modifiers for origin and destination, but the exact codes vary by state and payer. Software must hold code rules per payer rather than one national list.
- Colorado example: Colorado's NEMT billing manual lists A0130 for a wheelchair van trip, billed per one-way trip, with S0209 for wheelchair van mileage, and A0100 for taxi with S0215 for mileage.
- Origin and destination modifiers: Indiana Medicaid's transportation module uses one-letter codes such as R for residence, H for hospital, P for physician's office, J for a non-hospital-based dialysis facility and N for a skilled nursing facility, combined in pairs.
- Other services: Indiana's module also lists codes such as T2003 among the transportation services it covers, showing how code choices differ between states.
- Attendants and waiting time: Some programs pay separately for an attendant or wait time, each with its own code and rules.
Keep code rules in configuration tables, with effective dates, so a provider can add a new payer or apply a state manual update without a software release. Billing staff should be able to see which rule set produced each claim line, which makes it far easier to answer a payer's question later.
What trip data does a claim need?
A NEMT claim needs the member's identity and eligibility, the trip authorization, pickup and drop-off details, the level of service, mileage, and the driver and vehicle that performed the trip. Most of this should come straight from the dispatch and driver app records.
- Member: Medicaid ID, name and date of birth, checked against eligibility for the date of service.
- Authorization: Broker or plan trip number and any prior authorization reference.
- Locations: Pickup and drop-off addresses, with the facility type for origin and destination modifiers.
- Times: Scheduled times and actual pickup and drop-off times from the driver app.
- Level of service: Ambulatory, wheelchair, stretcher or other, which drives the base code.
- Driver and vehicle: Identifiers that link to credential and inspection records.
How should mileage be calculated?
Mileage should be calculated by the rule each payer sets, which is often loaded miles on the shortest practical route rather than the miles the vehicle actually drove. Colorado's manual, for example, ties billable mileage to the shortest route between pickup and drop-off.
- Routing engine: Calculate billable miles from the addresses with a mapping service, using the payer's route rule.
- GPS record: Keep the actual GPS trail as proof of the trip, separate from the billable figure.
- Variance checks: Flag trips where GPS miles and billed miles differ by more than a set margin, for review.
- Rounding: Apply each payer's rounding rule consistently.
Billing GPS miles when a payer expects shortest-route miles can lead to overpayments that must be returned, so the distinction needs to be built into the software, not left to staff.
Multi-passenger trips need their own rule. When a vehicle carries several members on overlapping routes, payers differ on how mileage is split or whether each member's trip is billed on its own route. Store the rule per payer and apply it automatically when trips are grouped in dispatch.
How do claims reach brokers and plans?
Claims reach brokers and plans through broker portals, broker-specific batch files or standard X12 837 professional claims sent through a clearinghouse. A provider working with several payers often needs all three.
- Portal entry: Some brokers require trips to be confirmed in their portal; software should export trip data in the portal's upload format to avoid manual entry.
- Batch files: Brokers with their own file formats receive scheduled batches of completed trips.
- 837P claims: State Medicaid programs and many plans accept standard electronic claims through a clearinghouse.
- Remittance: Payments come back as 835 files or broker statements, matched to the original trips.
The aim is one billing queue, whatever the route. Staff should see every completed trip, its payer, its submission status and its payment in one place.
Behind that queue sit several connections: broker trip feeds imported automatically, eligibility checks through X12 270 and 271 transactions or the state's portal, claims and remittances through a clearinghouse, posted payments exported to accounting, and driver credentials and vehicle inspections linked to each trip. Each one removes a manual step where errors creep in.
Submission timing matters too. Brokers and plans set deadlines for submitting completed trips, and a trip that misses its deadline may never be paid. Software that submits trips daily, as soon as they pass checks, shortens the gap between the ride and the payment.
What proof of service should the software capture?
Proof of service should show that the trip happened, when and where, and that the right member took it. Electronic capture in the driver app is faster and more reliable than paper trip sheets.
- Time stamps: Arrival, pickup and drop-off times captured by the app, not typed later.
- GPS points: Location at pickup and drop-off.
- Signatures: Member or facility signature on the device, where the payer requires one.
- No-shows and cancellations: Recorded with time and location, since many payers do not pay for them and some require documentation.
- Retention: Trip records kept for the period the state and broker contracts require.
Proof of service also protects providers in audits. Medicaid program integrity reviews often sample trips months later, and a provider that can produce time stamps, GPS points and signatures for each sampled trip is in a far stronger position than one relying on paper logs.
How should denials and reconciliation work?
Denials and reconciliation should be handled trip by trip, with every unpaid or underpaid trip traced back to a reason and a fix. Brokers often pay in bulk, so matching payments to individual trips is essential.
- Match payments: Link each payment line to its trip, and flag trips with no payment after the expected period.
- Reason codes: Group denials by reason, such as eligibility, missing authorization, mileage or duplicates.
- Corrections: Fix and resubmit within the payer's deadline, with the change recorded.
- Prevention: Feed common denial reasons back into checks that run before submission.
Many denials trace back to eligibility. Checking Medicaid eligibility the day before the trip, not after it, avoids completing rides that can never be paid.
Track a few numbers every week: trips completed, trips submitted, trips paid, average days to payment and the denial rate by reason. When one of them moves, the trip-level detail behind it should be one click away.
How Agnotic can help
Agnotic Technologies builds NEMT software for transportation providers and brokers, including billing that applies each payer's codes, modifiers and mileage rules, captures proof of service from the driver app and reconciles payments trip by trip.
Agnotic also builds the integrations NEMT billing depends on: broker trip imports and exports, eligibility checks, clearinghouse claims and remittances, and accounting feeds.
Get paid for every trip
Read the NEMT software buyer's guide, or browse the revenue cycle hub.
Related reading on Agnotic
Continue with why NEMT matters, AI in NEMT, insurance eligibility verification and revenue cycle management.
