Overview
The network status on a claim comes from the network or repricer that priced it and not from Yuzu. The repricer reports INN or OON in the repricing data returned on the claim, and Yuzu adjudicates under whatever status was returned. A provider appearing as in-network in a directory does not override the status the network sent on a specific claim.
Diagnosing an unexpected network result is therefore a matter of tracing where the claim went and what came back.
How the Claim Gets Routed
Routing begins with the payer ID on the member's ID card, which determines which clearinghouse or partner receives the provider's claim. From there, the plan's routing configuration determines what happens next: the claim may go to a network for repricing first, or arrive at Yuzu first.
In a network-first configuration, the claim reaches Yuzu with INN or OON already determined.
In a Yuzu-first configuration, the claim arrives unpriced, and Yuzu can only apply in-network cost sharing if the provider matches a network roster on the plan.
See the Payer ID guide for how the card's payer ID maps to these routes.
Because routing depends on the payer ID billed, two otherwise identical claims can take different paths. Establishing the claim's route is usually the first step in any investigation.
Common Causes of an Unexpected OON
When a claim returns OON that was expected to be INN, the usual explanations are:
The repricer returned OON: The repricing result on the claim is the source of truth, even if the provider appears on a roster today
The claim was never repriced: It was not routed to the network, or it was sent and returned without repricing attached
The TIN/NPI is not on the network roster: Roster matching uses the identifiers exactly as billed on the claim, evaluated against the dates of service. A provider added to the network after the service date, terminated before it, or billing under a different TIN will not match
The claim was priced by the wrong network or repricer: The claim may have routed through a wrap or affiliate network that repriced it OON, or the repricer's identifier on the claim may not be mapped to a network on the member's plan
Repricing is still pending: Some networks price claims manually. Until repricing is returned on the claim, it cannot adjudicate as in-network
Cigna-Specific Behavior
Claims routed through Cigna have a few behaviors worth understanding.
Cigna occasionally returns repricing where the allowed amount is below billed but the reported saving is $0. Yuzu derives the discount from the allowed amount rather than relying on the reported saving, so these lines still price correctly, though they can appear inconsistent on review.
On Cigna plans, an unpriced claim arriving through the clearinghouse may be denied as misrouted rather than processed as out-of-network, provided no routing rule could have forwarded it onward. The denial instructs the biller to submit to Cigna first. This is intentional: on a rented network arrangement, no claim should reach Yuzu unpriced.
When a Cigna network determination is disputed, resolution almost always sits with Cigna: the roster, the repricing, or the routing. Yuzu applies whatever status Cigna returns on resubmission, so reviews typically mean returning the claim to Cigna for repricing and setting partner expectations on timing accordingly.
Direct Contracts and Preferred Providers
Direct contracts and preferred-provider arrangements can change the outcome even when network repricing returns OON. A care event covering the provider and dates of service can determine the tier applied to the claim, overriding what the network match would have produced, while the network's repricing still supplies the price. Similarly, providers on a directly contracted internal roster may match in-network without an external repricer being involved.
When a claim shows OON but the provider is directly contracted, check for a care event or internal roster entry covering the service dates before escalating. See the Direct Contracts documentation.
Requesting a Review
When disputing a network result, collect the following before escalating:
Claim ID
Billing TIN and rendering/billing NPI exactly as billed on the claim, rather than what the provider reports them to be
Provider name and service address
Dates of service
The network shown on the member's ID card and the payer ID billed
What the claim actually returned: whether repricing is present, the INN or OON status, and which network's name appears
That last point is usually decisive. Whether the claim carries repricing, and who issued it, typically identifies where the process broke down before any roster lookup is needed.