ASP Insight · Payer Policy · Behavioral Health

The answer first: Optum Behavioral Health has told providers that every commercial behavioral health claim must carry the NPI plus the taxonomy code for both the billing provider and the rendering provider, validated against NPPES. Informational edits have flagged claims since Oct. 2025, and Optum says claims missing this information will be rejected or denied once the requirement takes effect. Optum has not yet announced that date and has promised an advance notice period. The claim build you fix now is the one that pays when enforcement starts.

Date TBAOptum has not yet announced when enforcement begins; advance notice promised
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, announced in Optum's September 2025 Top of Mind notice, commercial claims must include the NPI and taxonomy codes for the billing provider and the rendering provider on every claim. Once the requirement takes effect, Optum says claims missing this information will be rejected or denied.

Optum is not springing this overnight. Since Oct. 2025, claims that would fail the requirement receive informational edits, a warning label on claims that still pay. Practices that watch their remits and clearinghouse reports have free intelligence on exactly which claims would reject once enforcement starts.

Oct. 2025

INFORMATIONAL EDIT PHASE

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

Date TBA

ENFORCEMENT

Billing and rendering NPI plus taxonomy required on all commercial claims. Optum says claims missing this information will be rejected or denied, after an advance notice period.

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, will 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 Optum commercial remits since Oct. 2025 and isolate the informational NPI and taxonomy edits
  • Watch Optum's Top of Mind newsletter on Provider Express for the enforcement date and its advance notice
  • 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, Provider Express Top of Mind, September 2025, NPI requirements: billing and rendering NPI plus taxonomy codes on commercial claims, informational edits from Oct. 2025, effective date to be announced with an advance notification period.
  • 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 informational edits are showing up on your remits, or you would rather rejections never start, talk to us before the next filing deadline passes.

Request a roster scrub →