How to Coordinate ABA Billing When a Child Has Two Health Plans

Verify both coverage records

List each plan, product, member ID, policyholder, effective dates, employer or program, provider network, authorization contact, and claim address. Ask each plan to confirm its current other-insurance record. Coverage by two plans does not mean either one automatically pays half, and payer order should come from the governing coordination rules rather than family preference.

Understand coordination of benefits

CMS explains that COB applies when a person has more than one health plan and involves determining relative payment responsibility. The page also describes secondary claims carrying prior-payer adjudication information. Its transaction standards do not supply every plan's payer-order rule. Ask both plans for the determination and source that apply to the child.

Keep authorizations separate

Ask whether each plan requires its own assessment, prior authorization, provider enrollment, or network exception. HealthCare.gov notes that preauthorization is not a promise of cost coverage. An approval from the primary plan does not automatically authorize the secondary plan. Record services, units, dates, provider, and conditions for each authorization.

Follow claims in order

Track primary submission, receipt, decision, EOB, secondary submission or crossover, secondary receipt, decision, and EOB. A secondary plan may need the primary EOB or structured adjudication information. Ask the provider who handles the sequence and how reprocessed primary claims reach the secondary plan. Avoid sending the same claim as primary to both plans unless their rules direct that route.

A fictional two-plan register

Noah has 10 service lines. The primary plan adjudicates all 10; eight cross to the secondary plan and two need manual submission. COB completeness is 8 of 10 secondary routes complete. The family keeps both manual lines open, compares both EOBs, and waits for the provider ledger to apply plan payments and prior family deposits before paying the final balance.

Recheck after any change

Update both plans and the provider after coverage, employment, custody, address, policyholder, or payer-order changes. Preserve confirmation and effective dates. Reconcile later recoupments, reprocessed claims, refunds, and credits. Clinical care decisions remain with qualified professionals, while payer order and payment follow the applicable plan and program rules.

Build the two-plan coordination register

Create one two-plan coordination register for the family task: establish member-specific payer order and move each ABA service line through both plans without combining their benefits, authorizations, or decisions. Use a locked cohort or date range so every relevant item remains visible. The record should name the person, plan product, provider and site, service dates, current state, source, timestamp, owner, due date, next artifact, family-balance effect, and closure evidence. Keep a compact family-facing view beside the detailed operational evidence.

Gather the records that actually support the decision: both plan cards and products; policyholder and effective dates; each plan's other-insurance record and payer-order determination; provider network and enrollment evidence; separate authorizations; primary claims and EOBs; secondary submissions or crossover records; family payments; and the provider ledger. Label each item by author or issuing party, effective date, scope, and version. A call note proves what was said during that contact. A portal screen proves what the portal displayed at that time. Neither silently replaces the governing plan, contract, decision notice, clinical record, claim artifact, or later correction.

Walk the process in order. Confirm both coverage records first. Obtain each plan's determination of which payer is primary for the person and period. Verify the ABA provider and service under each product, secure each required authorization, submit to the primary route, wait for primary adjudication, transmit the required prior-payer information to the secondary route, and reconcile both decisions before final family billing. Preserve the original state when a correction occurs. Use a new event with its own date, author, reason, and evidence. Store health and financial information only in approved systems, limit access by role and purpose, and give the family an accessible way to review the facts that affect its choices.

Keep each decision with the responsible role

Start by writing the authority beside every open question. Each plan controls its own coverage, network, authorization, claim, and COB decision under governing sources. The provider controls claim sequencing and ledger posting. The qualified clinician keeps clinical recommendations separate from payer order. The family reports accurate coverage and can question contradictory determinations without choosing payer order by preference. Operations can collect evidence, surface conflicts, calculate from sourced inputs, and route work. Software can support those tasks. It should not invent a clinical judgment, decide a plan benefit, create legal authority, or convert an unverified assumption into a release decision.

Translate the record into a real family choice. The family needs an estimate that shows primary and secondary assumptions, possible noncovered amounts, deposits, and timing. It can compare the administrative workload and residual exposure with access, fit, travel, and continuity. A second plan may reduce a balance, leave it unchanged, or require additional steps, so the decision should not assume automatic payment. Explain which facts are confirmed, which remain provisional, what could change, and the consequence of waiting or proceeding. Use the person's preferred communication and provide language, disability, and AAC access throughout the process. Preserve dissent, questions, and the right to reconsider as new evidence arrives.

Use a short preparation script before the next contact: Which plan is primary, according to whom, and for what dates? Does each plan require separate authorization or provider enrollment? Who submits the secondary claim? Which primary adjudication fields must accompany it? How will a primary reversal reach the secondary plan and the family statement? Read the answers back at the end, naming the responsible person and next date. Send a written summary through an approved channel. If the representative lacks authority to answer, ask for the department or formal route that owns the state instead of treating a general call-center response as final.

Use a release gate and a documented fallback

A release gate prevents administrative progress from being mistaken for a completed decision. Before billing the family, verify member-specific payer order, both plan records, required authorizations, primary final adjudication, secondary receipt and final adjudication when applicable, every plan payment and adjustment, family payments, and the remaining supported balance. Keep incomplete secondary routes visible by line and age. Recheck any field that could have changed before the service, claim, payment, refund, transfer, or collection action occurs. A passed gate applies only to the named person, product, provider, site, service, route, and period.

Plan for the ways the process can break. Watch for both plans recorded as primary, an authorization obtained from only one plan, a secondary claim missing the primary EOB, a crossover that never arrives, a primary reprocessing event that fails to reach the secondary plan, provider payments posted twice, or a family deposit left unapplied after both plans finish. Record the observed failure rather than assigning an assumed cause. Preserve both conflicting artifacts, stop the affected release when appropriate, assign the correct owner, protect every live deadline, and tell the family what remains safe and available during review.

Work through one realistic complication

Noah's provider receives primary EOBs for ten service lines. Eight cross automatically and two require manual secondary submission. The register keeps all ten lines in the secondary due cohort, records the two manual receipts, and waits for both secondary decisions before calculating Noah's final balance. The family records each numerator and denominator before reporting progress. Items waiting on another party remain in the due cohort unless a prewritten eligibility rule excludes them. A status percentage never substitutes for the age, amount, clinical or financial significance, and next action of each open item.

Now add an adverse turn. Imagine that a later payer message, corrected EOB, enrollment update, provider posting, or missing record changes one of the facts. Reopen the two-plan coordination register, link the new artifact to the affected item, and determine which downstream decisions relied on the earlier state. Avoid overwriting the old evidence. The history should show what the family and provider knew at each point and why they acted.

Verify a complete real-world cycle

Select one service date and trace it through the primary claim and EOB, secondary claim or crossover and EOB, provider ledger, family payment, credit, refund, and final balance. The two-plan cycle closes only when both payer states and the ledger agree. Technical submission, portal acceptance, a phone confirmation, or a staff note is an intermediate event. Closure requires the expected downstream artifact and a reconciled family-facing result. Name who checks that artifact and how quickly a mismatch returns to the active queue.

Measure only the events and units defined for this two-plan coordination register. Keep open items visible beside completed work, and retain the raw counts behind every rate. Do not pool claim lines, claims, requests, authorizations, EOBs, payments, statements, households, payer products, or maturity windows unless the measure was designed for that exact cohort.