Trip reconciliation in NEMT is the practice of matching every trip you completed against what the broker or payer actually paid — line by line, leg by leg. It catches unpaid legs, short-paid mileage, and completed trips wrongly marked as no-shows, then turns each gap into a dispute filed inside the window. Done daily or weekly, it recovers revenue that otherwise disappears, because remittances do not correct themselves.
The remittance arrives, the deposit hits, and the number looks roughly right — so it gets filed and the week moves on. That is how most NEMT providers handle broker payments, and it is exactly how completed trips go unpaid without anyone ever noticing. "Roughly right" is not a payment status. Somewhere in that remittance, a return leg is missing, a mileage tier got knocked down, and a trip you completed is sitting in the broker’s system as a no-show.
Trip reconciliation is the discipline that replaces "roughly right" with a line-by-line answer. It is not glamorous work, but among the back-office habits an NEMT provider can build, it has one of the most direct paths to money you have already earned.
What is trip reconciliation in NEMT?
It is the process of comparing three records that should agree but often don’t: the trips the broker assigned you, the trips your drivers actually completed and logged, and the payments on the broker’s remittance. Reconciliation walks the trip log against the remittance line by line and asks one question of every leg: were we paid what this trip should have paid? Every "no" becomes a documented discrepancy, and every discrepancy becomes either a correction, a resubmission, or a dispute filed with the broker.
The word "leg" matters in that definition. NEMT trips are usually multi-leg — an outbound A-leg and a return B-leg, often booked as a will-call — and brokers pay by the leg. A reconciliation that only counts trips will happily miss the return legs that never made it onto the remittance at all.
Why doesn’t the remittance just match the trip log?
Because assignment, completion, and payment run through separate steps of the broker’s system, and every handoff between them is a place where the record can drift from reality. None of these mismatches are exotic; they are the routine friction of high-volume trip data moving through portals:
- A completed leg missing from the remittance entirely — most often a will-call return whose completion was never confirmed back through the portal
- A trip paid at a lower mileage tier than the run actually covered, because the broker’s mapping calculation disagreed with the logged route
- A completed trip sitting as a provider no-show in the broker’s system, unpaid, because the completion status never posted
- A same-day schedule change that was run correctly but paid against the original, pre-change trip details
- A rate applied that doesn’t match the rate on the accepted offer
Why are return legs the most common unpaid trip?
Because the B-leg lives a more complicated life than the A-leg. The outbound run is scheduled, assigned, and completed in one clean arc. The return is often a will-call — dormant until the member calls ready, reactivated mid-day, sometimes reassigned to a different vehicle — and every one of those extra steps is a chance for the completion to miss the portal. The leg ran, the member got home, and the broker’s system never heard about it.
A provider who reconciles by leg catches this within days: the A-leg paid, the B-leg is absent, the dispute goes in with the trip log attached. A provider who eyeballs the deposit total donates that leg — and at dialysis-schedule volumes, the same three-times-a-week rider can generate the same silent gap again and again.
Pre-trip payment collection, payment processing, bookkeeping support, and accounts reconciliation.
What does the daily discipline actually look like?
Reconciliation works when it is a standing routine with a set cadence, not a quarterly archaeology project. The mechanics are plain:
- Keep the trip log airtight during the day — completions, times, and mileage confirmed through the broker’s portal as trips finish, because reconciliation is only as good as the log it checks against
- When each remittance posts, match it against the trip log line by line, leg by leg — per broker, since each runs its own remittance format and cycle
- Log every discrepancy with the evidence attached: the leg, the expected amount, the paid amount, the trip-log proof
- File disputes and resubmissions immediately — brokers set windows for payment disputes just as payers set filing windows, and an unpaid leg discovered after the window closes is usually unrecoverable
- Track discrepancies by type and broker over time, so a recurring pattern — will-call completions not posting, one contract’s mileage always calculating short — gets fixed at the source instead of disputed forever
What is broker payment reconciliation worth?
Run one honest test: pull last month’s remittances for a single broker and match them against your own trip log, leg by leg. The lines that fail to match — the absent B-legs, the short-paid miles, the phantom no-shows — are what the absence of reconciliation cost you in one month, on one contract. For most providers who have never done the exercise, the number is not zero, and it repeats every month the discipline doesn’t exist.
The gap compounds quietly because nothing about it rings a phone. A missed pickup generates a complaint the same day; a missing payment generates silence. Reconciliation is how you give the silent losses a voice, and catching them inside the dispute window is the difference between a recovery and a write-off.
Can you outsource trip reconciliation?
Yes — reconciliation is one of the most outsourceable jobs in NEMT precisely because it is defined, repetitive, and relentlessly deadline-driven. A trip reconciliation service works inside your own broker portals and billing records: confirming completions during the day, matching each remittance against the trip log when it posts, filing disputes with documentation inside the window, and reporting the discrepancy pattern back to you by broker and by type.
The honest case for outsourcing it is the same as for the rest of the NEMT back office: capacity, not skill. The work is not hard — it just never gets done by whoever is also dispatching vans and answering phones, because it can always wait one more day, and the dispute windows can’t. A desk whose job is the reconciliation, every day, is how "roughly right" stops being your payment standard. That is exactly the kind of standing back-office work TransportBPO runs for NEMT providers, inside the client’s own systems.
Common questions
Where this guide fits: it is part of the full NEPT & patient transport dispatch desk. Next step: try the desk free for your first week.
Daniel Okoro is TransportBPO's Content Editor and Dispatcher — a former dispatcher who moved into editorial after years running live boards for taxi, NEMT and trucking accounts. He writes from dispatch-floor experience, not the marketing department, on what actually keeps a 24/7 desk running.
Connect on LinkedIn