ASP Insight · Payer Policy · Behavioral Health

The answer first: since Jan. 1, 2026, every Optum Behavioral Health commercial claim must carry the NPI plus the taxonomy code for both the billing provider and the rendering provider. Claims that arrive without all four values, or with taxonomy values that do not line up, reject at the front end before they ever reach adjudication. Optum signaled this in advance, issuing informational edits from Oct. 2025. The warning phase is over. The claim either carries the data or it does not pay.

Jan. 1, 2026Hard enforcement begins on all Optum Behavioral Health commercial claims

Oct. 2025Informational edits begin flagging claims that would fail the new requirement

2 providersBoth the billing provider and the rendering provider must be identified

4 valuesBilling NPI, billing taxonomy, rendering NPI, rendering taxonomy, every claim

Optum's taxonomy mandate: what changed, and when

Under the Optum taxonomy code requirement for behavioral health, effective Jan. 1, 2026, commercial claims must include the NPI and taxonomy codes for the billing provider and the rendering provider on every claim. This sits inside the UnitedHealthcare reimbursement policy framework published on uhcprovider.com, and it is not a soft edit. A claim missing any of the four values is stopped at the front-end gate.

Optum did not spring this overnight. From Oct. 2025, claims that would have failed the requirement received informational edits, a warning label that still paid. Practices that watched their 277CA acknowledgments and clearinghouse reports through the fall had a full quarter of free intelligence on exactly which of their claims would start dying in January. Practices that did not are finding out now, one rejection at a time.

Oct. 2025

INFORMATIONAL EDIT PHASE

Claims missing NPI plus taxonomy values are flagged but still processed. Every flag was a free preview of a 2026 rejection.

Jan. 1, 2026

HARD ENFORCEMENT

Billing and rendering NPI plus taxonomy required on all commercial claims. Missing or mismatched values reject at the front end.

The life of a claim under the mandate

Front-end rejections behave differently from denials, and the difference is what makes this policy dangerous. Trace the path.

Your 837 leaves the clearinghouse

Billing provider identified in the billing loop with its PRV taxonomy segment, rendering provider in loop 2310B with its own NPI and PRV taxonomy value.

Optum front-end edit gate

Four checks, all must pass:

BILLING NPI PRESENTBILLING TAXONOMY PRESENTRENDERING NPI PRESENTRENDERING TAXONOMY PRESENT

ALL FOUR PASS

Claim enters adjudication
Processes under your contract terms
Remit arrives on the normal cycle

ANY VALUE MISSING OR MISMATCHED

Rejected before adjudication
No EOB, no denial code, no appeal path
The claim does not exist in the payer system
Your timely filing clock keeps running

That last point deserves its own sentence. A front-end rejection never becomes a denial you can appeal. If nobody is working the clearinghouse rejection queue, the claim silently ages past timely filing while your aging report shows it as billed. The revenue does not fail loudly. It just never arrives.

Who gets hurt: group practices and multi-credential staff

Solo practitioners with one NPI and one taxonomy mostly sail through. The casualties concentrate in two archetypes that dominate behavioral health and ABA.

The group practice with a shared NPI habit

Agencies that historically billed everything under the group NPI, with the rendering loop empty or repeating the organizational NPI, now fail the rendering-provider checks. Each rendering BCBA needs their own Type 1 NPI and taxonomy on the claim line, not a pass-through of the group identity.

The multi-credential renderer

A BCBA who also holds a state behavior analyst license, an LBA, may have enumerated in NPPES years ago under a different or outdated taxonomy than the one your billing system transmits. When the taxonomy on the 837 does not match the record the payer resolves against, the mismatch rejects even though the NPI itself is valid.

The stale roster

Staff who changed credentials, moved from RBT-supervised rendering models to independent BCBA rendering, or were set up in the EHR by hand carry whatever taxonomy someone typed at onboarding. Nobody has reconciled those values against NPPES since, and the mandate is now the audit nobody scheduled.

The fix: a one-time roster scrub

This is not an ongoing burden if you do it once, properly. The whole repair is a reconciliation between three sources of truth: your roster, the NPPES registry, and what your 837 actually transmits.

Export the full rendering roster

Every BCBA and every billing entity that touches an Optum commercial claim. Include the NPI and the taxonomy value stored in your EHR or practice management system for each.

Pull the NPPES record for every NPI

Use the CMS NPI Registry at npiregistry.cms.hhs.gov. Capture the primary taxonomy on file for each individual and organizational NPI. This is the record the ecosystem resolves against.

Compare against your live 837 output

Open a recent 837 file. Check the billing provider PRV segment and the rendering values in loop 2310B against the NPPES pull. Every discrepancy is a future rejection.

Fix at the source, not per claim

Where NPPES is wrong, update NPPES. Where the EHR provider record is stale, correct it there so every future claim inherits the fix. Hand-editing individual claims is a treadmill, not a repair.

Verify and gate

Watch the next remittance cycle for zero taxonomy rejections, then add NPI plus taxonomy verification to your new-hire credentialing checklist so the roster never drifts again.

Operator to-do list

Run this week

Pull your clearinghouse rejection report for all Optum commercial claims since Jan. 1, 2026 and isolate NPI or taxonomy edits
Check every rejected claim against its timely filing deadline and resubmit the fixable ones first
Run the five-step roster scrub above for every rendering BCBA and billing entity
Confirm each rendering BCBA has an individual Type 1 NPI, no group-NPI pass-throughs in loop 2310B
Reconcile any BCBA and LBA dual-credential staff against their NPPES primary taxonomy
Review any informational edits received from Oct. 2025 onward, they are a pre-built list of your at-risk claims
Add NPI plus taxonomy verification to the onboarding checklist for every new BCBA and RBT

Sources

Optum Behavioral Health commercial claim requirement, effective Jan. 1, 2026: billing and rendering NPI plus taxonomy codes on all claims, with informational edits issued from Oct. 2025.
UnitedHealthcare reimbursement policy framework, uhcprovider.com.
CMS NPPES NPI Registry, npiregistry.cms.hhs.gov.

ASP-RCM runs the scrub so your claims never see the gate

ASP-RCM Solutions performs the NPPES-to-837 roster reconciliation as a standard part of behavioral health and ABA revenue cycle onboarding, monitors clearinghouse rejection queues daily so a front-end rejection never ages past timely filing, and keeps rendering rosters synchronized as your BCBAs and RBTs join, credential up, or change status. If Optum rejections have started appearing in your queue, or you would rather they never do, talk to us before the next filing deadline passes.

Request a roster scrub →