Rendering provider vs billing provider: what is the difference on a claim?
The billing provider is the person or organization asking to be paid for a claim. The rendering provider is the clinician who performed or supervised the service. On a professional claim they sit in different fields, carry different NPIs when they differ, and both must pass payer checks before the claim leaves your system.
Where do the rendering and billing provider sit on a claim?
Quick answer
Rendering provider vs billing provider is a question of roles on one claim: the rendering provider performed or supervised the care, and the billing provider requests payment. When they differ, the claim carries both, each with the right NPI and taxonomy. Agnotic Technologies builds claim engines and scrubbers that map and validate both identities.
| Criterion | Rendering provider | Billing provider |
|---|---|---|
| Role | Rendered or supervised the care | Requests payment for the services |
| Usual entity | An individual clinician | Often a group or organization; can be a solo clinician |
| Entity type in X12's published 837P examples | NM1*82 with entity type 1 (person) | NM1*85 with entity type 2 (non-person entity) |
| CMS-1500 item | 24J (NPI) with 24I qualifier, reported only when different from 33a and 33b | 33 name, address and phone; 33a NPI; 33b other ID |
| 837P loop | 2310B Rendering Provider, at claim level | 2010AA Billing Provider |
| Taxonomy | PRV*PE with the rendering taxonomy code | PRV*BI with the billing taxonomy code |
| Address | Not the billing address | A street address or physical location, per 5010A1 and NUCC |
| When both are the same | Omit; the billing provider stands for both | Reported alone |
| Medicare payment to another party | Assigns payment through a reassignment | Receives it as employer or contracted entity (42 CFR 424.80(b)) |
What they are
What is Rendering provider
The National Uniform Claim Committee defines the rendering provider as the person or company (laboratory or other facility) who rendered or supervised the care. On the CMS-1500 it goes in item 24J, and only when it differs from the billing provider.
What is Billing provider
The billing provider is the provider requesting to be paid for the services, reported in CMS-1500 item 33 with its NPI in 33a, and NUCC says item 33 should always be completed. In the 837P it is the billing provider loop, 2010AA.
Key differences
Why does the NPI type matter?
45 CFR 162.410(a)(2) requires a covered health care provider to use its NPI to identify itself on every standard transaction where a provider identifier is required, and (a)(5) requires any business associate conducting transactions on its behalf to use its NPIs appropriately. A claim engine therefore needs both NPIs on file and must place the organization's NPI in the billing loop and the individual's in the rendering loop.
How does each one appear in the 837P?
The professional claim standard is the ASC X12 837 Professional, 005010X222, adopted in 45 CFR 162.1102. X12's published examples show the billing provider in loop 2010AA as NM1*85 with a PRV*BI taxonomy segment, and the rendering provider in loop 2310B as NM1*82 for a person with PRV*PE. When the two are the same, the example claim carries no 2310B at all.
When can a group bill for a clinician's work?
Under 42 CFR 424.80, Medicare generally does not pay amounts due to a supplier to anyone else, with exceptions that include payment to an employer and payment to an enrolled entity under a contractual arrangement. Where a contractual arrangement applies, the entity and the clinician are jointly and severally responsible for any Medicare overpayment, so the reassignment record is worth checking before the claim is built.
What about supervision and substitutes?
NUCC's 1500 instruction manual says the rendering provider is whoever rendered or supervised the care, and that a substitute provider (locum tenens) is entered in 24J. Your encounter model needs a field for the supervising clinician and one for the substitute, not only the scheduled clinician, or the wrong NPI lands on the claim.
When to use each
When to use Rendering provider
- A clinician in a group practice sees the patient and the group bills: report the clinician as rendering.
- A locum tenens covers a shift: NUCC says to enter the substitute provider in 24J.
- A supervising clinician is the one the payer credits for the service.
- The payer needs the individual's taxonomy to price or route the claim.
When to use Billing provider
- Every claim: the billing provider is always present.
- A group, clinic or facility bills under its organization NPI for its clinicians' work.
- A solo clinician bills under their own NPI, and no separate rendering provider is needed.
- Medicare payment goes to an employer or contracted entity under a reassignment.
What should a claim scrubber check about provider identity?
These checks cover provider identity only. They belong in the scrubber that runs before a claim reaches the clearinghouse.
1. Billing provider present. Every claim carries a billing provider with a 10-digit NPI and a street address, not a post office box.
2. Rendering provider only when different. If the rendering NPI equals the billing NPI, drop the rendering loop; if it differs, the rendering loop must be present.
3. NPI type matches the loop. An individual NPI in the rendering loop and, for a group, the organization NPI in the billing loop.
4. Taxonomy present and consistent. Each provider's taxonomy code matches the specialty the payer has on file for that NPI.
5. Reassignment on file. For Medicare claims where the billing provider is not the rendering clinician, confirm the reassignment before release.
6. Rendering NPI enrolled with the payer. A clinician who is not yet enrolled or credentialed with that payer holds the claim, rather than letting it deny.
7. Supervision and substitutes resolved. If the encounter records a supervising clinician or a locum tenens, the rendering provider follows NUCC's rule, not the schedule.
Which sources does this comparison rely on?
- NUCC 1500 Claim Form Reference Instruction Manual, version 13.0 (nucc.org)
- X12 837P example 01: billing provider loop 2010AA (x12.org)
- X12 837P example 09: rendering provider loop 2310B (x12.org)
- 45 CFR 162.410: NPI implementation specifications for providers (eCFR)
- 42 CFR 424.80: reassignment of claims (eCFR)