Skip to main content

Secondary balance after primary

Outcome​

You understand how the platform computes residual balance after primary adjudication, how secondary (and tertiary) absorb the patient liability the primary surfaced, and what the patient AR looks like at each step.

Prerequisites​

ScopeWhat it lets you do
billing.claim.readView claim relationships
billing.cob.readSee the COB waterfall
billing.receivable.readWatch posting effects

The waterfall​

At each level, the platform computes:

residual = billed − sum(payments) − sum(contractual adjustments) − sum(prior-payer impact)

Patient AR doesn't "fill" until the chain completes for that line.

Why primary's PR-* doesn't immediately bill the patient​

When a member has a secondary, the primary's PR-* is expected to move down to the secondary. The platform:

ActionWhen
Holds the patient AR routingUntil secondary submits / adjudicates.
Releases to patient ARIf secondary genuinely doesn't cover.
Closes the lineIf secondary fully covers the residual.

Tenants without held-routing (the simpler model) post PR-* immediately and reverse later if secondary covers. Read your tenant's policy.

Reading the COB tab on a claim​

/claims/:id → Relationships → COB waterfall:

SectionContents
PrimaryAdjudication summary + residual.
SecondaryIf applicable; same shape.
TertiaryIf applicable; same shape.
Patient ARFinal residual, who's on the hook, what's been paid.

The shape repeats per claim line where applicable.

Working a stuck COB chain​

Common patterns​

PatternRead
Secondary built immediately, paid the residualStandard happy path.
Secondary built, pended for medical reviewTertiary doesn't auto-trigger; track follow-up.
Secondary denied for "no primary EOB attached"The 837 to secondary lacked the primary CAS — re-check the build.
Tertiary built unexpectedlyMember had a tertiary the COB tab missed; verify Coverage.
Patient AR shows full liability while secondary still pendingTenant policy is "release immediately"; will reverse on secondary post.

Validation​

CheckExpected
Primary post triggers secondary build (where applicable)Yes.
Secondary 837 carries primary CAS / AMT*F2Yes (visible on Submission tab).
Tertiary auto-triggers after secondary PAID/PARTIALYes.
Patient AR equals final residual after chain completesYes.

Troubleshooting​

SymptomCauseFix
Patient is being billed for amounts secondary should cover"Release immediately" policy; secondary hasn't paid yetWait for secondary 835; balance will reverse.
Secondary built with wrong primary CASPrimary's CAS wasn't snapshotted correctlyReverse + rebuild secondary; investigate.
COB tab shows tertiary but member has only two coveragesStale member recordRefresh eligibility; re-snapshot COB.
Long-pended secondaryPayer's queueSend 276 inquiry on the secondary claim.

Where to next​