NEMT billing
Bambi billing services
Bambi billing services from Remitwright give the Get Paid side of your account a dedicated owner.
Tell us your trips per month and brokers.
A biller works in Bambi on a login you create, reads each completed trip for its pickup and drop-off signatures, GPS-stamped status times and odometer readings, then builds the invoice for each broker, health plan or facility from those verified trips. Every invoice is followed until it is paid or disputed, short payments are taken up with the payer, and documentation gaps go back to dispatch with the trip named. Bambi billing is one part of our NEMT billing services.
Independent: Remitwright is not affiliated with or endorsed by Bambi Health. Bambi is a trademark of its owner, named here to describe the system we work in.
Last reviewed by the Remitwright billing team. Editorial policy
- NEMT dispatch and billing
Every day
What your biller does in Bambi every day
- Open each completed trip before it goes on an invoice and confirm the pickup and drop-off signatures are present, with the signer recorded as passenger, guardian, facility employee or unable to sign
- Check the authorization ID and insurance policy ID on the trip against what the broker or plan assigned, so a claim does not go out under a stale number
- Set, with your administrator, which signatures each payer requires in Bambi's payer settings, so the Driver App asks for them at drop-off instead of billing finding the gap later
- Compare the odometer readings the Driver App captured and the loaded miles Bambi estimated with the miles the payer pays on, and settle any difference before the invoice is built
- Check trips that arrived by broker connection, live API for MTM, Modivcare, Verida and Alivi or a CSV upload for others, against what the driver ran, including cancellations and no-shows and their recorded reasons
- Build each payer's invoice from the Add Trips list filtered by payer and trip date; Add all Invoiceable Trips adds every trip not yet invoiced and a trip can go on only one invoice, so the biller checks each invoice's trip list before it is sent and confirms no completed trip is left unbilled
- Keep the Get Paid pricing schemes current by payer, space type and service type, and bill wait-and-return trips on the actual wait Bambi calculates
- Send each invoice the way its payer accepts it, as a Bambi PDF, a broker portal upload or a claim through your clearinghouse, and follow every one marked Unpaid until it is paid, short-paid or denied
- Export invoices to QuickBooks as the report CSV, by invoice or by payer and date range, once payments are applied, and pull the Audit log PDF when a broker or Medicaid reviewer asks for trip records
Access
Access and security
Your data, your systems
Patient data stays in your systems. Your biller works inside your own software, clearinghouse and payer portals and never exports, downloads or stores claim files, remittances or patient lists on Remitwright devices or systems.
- BAA signed before any access
- A user you create and can remove
- MFA on every login that supports it
- No claim files or patient lists exported
In Bambi
- Bambi stays licensed to you and the trip data stays in your account; you add the biller yourself under Team, Accounts
- In Bambi's published user types, only Owner and Admin include Billing (Dispatcher excludes it), so the biller is added as an Admin, which also reaches team accounts and settings; you can change or remove that login at any time
- Multi-factor authentication on the biller's login wherever Bambi offers it
- Bambi signs a business associate agreement with each customer; Remitwright signs its own BAA with you before the biller's account exists
- Nothing is copied into systems of ours; invoices and claims to payers are the only things that leave the account
Where the biller steps in
What Bambi does not do, and the biller does
Bambi builds an invoice to a broker's format; whether it is inside that broker's filing window and carries its documentation list is checked by the biller, who keeps both per broker
Where a payer wants an electronic 837P claim rather than an invoice, the biller confirms how your account produces it or files it through the clearinghouse or state portal you already use
An invoice marked paid is not proof it was paid in full; the biller sets each payment against the pricing scheme trip by trip and disputes the difference
The QuickBooks export runs one way, so a correction made in QuickBooks never reaches Bambi; the biller keeps the two records in step
A trip can close with the passenger recorded as unable to sign; what each payer accepts in that case differs, and the biller checks it before the trip is billed
Worked example: a dialysis subscription missing drop-off signatures
A hypothetical provider runs a standing dialysis schedule booked as a trip subscription in Bambi, three days a week, for a member whose trips arrive from a broker by live API. Before the month's invoice for that payer is built, the biller pulls its invoiceable trips and finds four completed legs with a pickup signature but none at drop-off, each recorded as passenger unable to sign. The payer's documentation list asks for a signature from an authorized signer. The biller holds those four legs back, sends the trip IDs to dispatch with the missing field named, and checks the payer's rule for a passenger who cannot sign before releasing them. The rest of the invoice goes out without waiting on the four.
Questions
Questions about billing in Bambi
Do we need new billing software to work with Remitwright?
Which brokers can you bill from Bambi?
What does Bambi record that matters at billing time?
How are HCPCS codes and modifiers handled?
What access do you need?
Does the biller dispatch trips or change routes?
Next step
Tell us your trips per month and brokers.
Three quick questions. No patient data. A billing specialist reads every request and replies in writing, with notes on how the work would run inside Bambi.
- Three questions, about two minutes
- No patient data, no software to buy
- A written reply from a biller, not a sales deck
You answer three questions
A billing specialist reads them
A written reply by email
Prefer email? sales@remitwright.com
Request received
Thanks. Your review request is in.
Reference . Quote it if you write to us about this request.
- A billing specialist reads your answers and replies by email.
- If a look at real claims makes sense, we agree read-only access under a BAA first.
- You get a written summary of what is worth working and what it would take. No commitment.
While you wait: see the sample weekly report or read the NEMT billing guide. You can also download the sample weekly report (PDF).