Whose NPI goes where: billing and rendering providers on a transportation claim
On a claim, the billing provider is the enrolled company that gets paid: CMS-1500 item 33, 837P loop 2010AA. The rendering provider is whoever actually furnished the service, entered in item 24J or loop 2310B, and only when that is someone other than the billing provider. A NEMT company that runs and bills its own trips normally leaves the rendering fields blank.
On this page
Two roles on every claim
A claim names who gets paid and who did the work. For a NEMT company those are usually the same business, but the claim form still treats them as two separate roles.
| Billing provider | Rendering provider | |
|---|---|---|
| Who it is | The provider asking to be paid | The person or company that performed the service |
| CMS-1500 | Item 33 (name, street address, phone), 33a (NPI), 33b (other ID) | 24J holds the ID and 24I its qualifier, on each service line |
| 837P | Loop 2010AA | Loop 2310B for the whole claim, or 2420A for one line |
| When to fill it in | Always | Only when different from the billing provider |
The NUCC instructions are explicit on both points. Item 33 identifies the provider requesting payment and “should always be completed.” The ID in 24I and 24J goes in “only when different” from what is in 33a and 33b. Electronic 5010 claims need a physical location for the billing address, and the NUCC advises paper claims to follow suit. The other boxes are covered in the CMS-1500 guide, and the 837P guide covers the electronic loops.
How transportation companies usually fill it in
When one company enrolled with the payer, ran the trip, and collects the money, it fills both roles. Its identifiers go in item 33 and loop 2010AA, and 24J and loop 2310B stay empty.
The harder question is which identifier to use. Federal rules require covered health care providers to get an NPI, but state Medicaid programs differ on whether they treat a non-ambulance transportation company as one:
- Indiana calls transportation providers other than ambulances atypical providers. They are not required to have NPIs and use their IHCP Provider ID in place of one. On the 837P, the companion guide has atypical billing providers send that ID in loop 2010BB with qualifier G2.
- Arizona lists the enrollment type for provider type 28 (non-emergency transportation) as atypical and states that no NPI is required.
- On paper, a provider without an NPI reports its payer-assigned ID in item 33b with a qualifier such as G2 (provider commercial number) or 0B (state license number).
If you hold an NPI, use it wherever the payer asks for one, and keep the taxonomy code consistent with your enrollment. The Medicaid provider number entry explains how the state’s own ID relates to it.
When a payer repurposes the fields: New York
Payer instructions override the general rules, and New York shows how far they can go. Under its transportation billing guidelines (version 2026-02, August 5, 2026), a non-emergency transportation provider identifies itself in loop 2010AA with the eight-digit Medicaid ID the state assigned, not an NPI. For ambulette, taxi, and livery trips, the service provider field, mapped to loop 2310B, carries the plate number of the vehicle that made the trip. The referring provider field (loop 2310A) carries the driver’s license number, trimmed or zero-filled to nine characters.
A claim that follows the generic NUCC rules would leave both fields blank there. Read the transportation section of each payer’s billing manual before you build a claim template.
Mismatches that stop payment
Payment stops when the IDs on the claim do not line up with the payer’s records. Four common ways it happens:
- The NPI matches more than one enrollment. Indiana matches each claim to a single enrollment using the NPI, the taxonomy code, and the billing location’s nine-digit ZIP code. If it cannot find a unique match, the claim denies and the error comes back on a 277U rather than the remittance.
- An ID is not linked to your submitter. New York rejects claims unless the billing provider’s NPI, the group NPI, and the rendering provider’s NPI are linked to the electronic transmitter ID (ETIN) used to send them.
- The rendering and pay-to details disagree. Remark codes spell this out: N198 says the rendering provider must be affiliated with the pay-to provider, and N852 says the pay-to and rendering tax IDs do not match.
- The identifier itself is bad. N257 flags a missing or invalid billing provider identifier, N290 the same for the rendering provider, and CARC 208 an NPI that does not match the payer’s records.
A front-end mismatch can produce a claim rejection, so check acknowledgments as well as the remittance. The remark codes entry explains how to read those codes next to their reason codes.
Frequently asked questions
- Do my drivers need their own NPIs as rendering providers?
- Generally no. Under the NUCC instructions, the rendering provider is whoever rendered or supervised the care, and for a trip that is normally the transportation company itself, the same entity that bills. Some states do not treat non-ambulance transportation companies as health care providers for NPI purposes at all. Indiana and Arizona both enroll them without an NPI. Follow your payer's instructions if it asks for driver details elsewhere on the claim.
- What goes in item 33b if my company has no NPI?
- The payer-assigned ID, with a qualifier in front and no space or hyphen between them. The NUCC lists G2 for a provider commercial number and 0B for a state license number. In Indiana, atypical transportation providers use their IHCP Provider ID in place of an NPI, and on the 837P they send it in loop 2010BB with qualifier G2.
- Can one NPI cover two locations or two Medicaid enrollments?
- Sometimes, as long as the payer can tell the enrollments apart. Indiana matches each claim to one enrollment from three data points: the NPI, the billing location's nine-digit ZIP code, and the taxonomy code. It also lets a provider name an NPI default location. If the match is not unique, the claim denies and the error comes back on a 277U, not the remittance.
