To close ABA claims after a payer contract terminates, separate the contract end date from service authority, member coverage, authorization, filing, correction, appeal, recoupment, refund, and continuity timelines. Lock all affected services and claims, map each payer product and provider configuration, preserve the former route, communicate verified status, and keep a runout register until every claim, credit, dispute, client balance, and record obligation reaches supported closure.
Define Kellan's payer-contract termination claim close control
Kellan's runout register covers services before, on, and after the contract boundary. It records which source controls each decision and avoids treating contract termination as automatic claim denial, discharge, client liability, or permission to rebill another route.
Build the contract-termination claim runout register
Record contract and amendment; termination notice; entity; payer and product; provider and location; member; service date; authorization; continuity or transition source; claim; filing and correction windows; appeal; remittance; recoupment; refund; client balance; communication; owner; and closure. Structured fields preserve identity, source, version, authority, state, clock, calculation, money movement, action, hold, retest, and closure. Narrative captures clinical meaning, uncertainty, disagreement, accessibility, family communication, legal deferral, and each accountable owner's rationale.
Run Kellan's workflow
Kellan inventories affected relationships and service-date cohorts, preserves claim routes and access, then assigns runout, clinical continuity, contracting, client-account, and legal work to qualified owners. Each claim follows the source applicable to that exact product and date.
Assign each decision to its proper authority
A network contract end and a clinical service end are different events. Coverage, authorization, provider participation, claim payment, continuity rights, and client financial responsibility also require their own evidence.
Work through Kellan's fictional example
Kellan tracks a fictional 60-claim runout cohort. Forty-two adjudicate, eight remain pending, four need corrected claims, three enter appeal, two have recoupments, and one has an unresolved client balance. Fifty-four have a supported current route; six remain held with deadlines and owners. This synthetic scenario tests control logic and arithmetic only. It creates no coding, coverage, authorization, payment, client-balance, refund, reserve, accounting, disclosure, contract, or legal conclusion for a real person, provider, payer, claim, or entity.
Calculate Kellan's measures
Route completeness is 54 of 60 claims, or 90.0%. Final closure uses the original 60-claim cohort and occurs only when every item reaches an evidenced final state. Service-continuity measures use a separate client cohort.
Address the main payer-contract termination claim close risk
Closing accounts on the contract end date can abandon timely claims or shift unsupported balances to families. Leaving system access open indefinitely creates privacy and control risk.
Test the contract-termination claim runout register against exceptions
Kellan tests pretermination service, boundary-day service, posttermination authorization, continuity arrangement, late claim, corrected claim, appeal, recoupment, refund, inactive portal, and member complaint. Every fixture retains the source version, expected state, actual state, affected unit, safeguard, owner, repair, retest, and disposition. Failed, unknown, quarantined, pending, excluded, and held items remain in the predeclared cohort.
Document the stop condition
Hold final closure when a claim route, service authority, continuity issue, deadline, credit, recoupment, client balance, records access, or accountable owner remains open.
Hand off open work with evidence
Kellan's runout package lists every affected product and configuration, cohort rule, contract source, claim state, clock, clinical-continuity owner, family communication, access plan, and closure evidence.
Communicate the current state accurately
Families receive accurate network, service, coverage, cost, and transition information within the communicator's authority. Staff avoid promises about payment or future care until the relevant source is verified.
Verify Kellan's acceptance evidence
An independent reviewer samples each date cohort and claim state, reproduces the selected route, and confirms that clinical continuity and financial close remain separately owned.
Maintain Kellan's control over time
Kellan reviews the register until all runout items close, then retains the source, portal evidence, exports, and contacts for later audit, appeal, refund, or record-access needs.
Monitor Kellan's operational results
Report claims by state and age, deadlines at risk, correction and appeal yield, recoupments, credits, unresolved client balances, service transitions, and access dependencies. Keep original cohort counts beside percentages.
Make the contract-termination claim runout register implementation-ready
Create a termination calendar with separate dates for notice, new-service restrictions, contract end, roster changes, claims submission, corrected claims, appeals, portal access, record retention, and final reconciliation. Test claims on both sides of every boundary. If a payer redirects work to a new portal or identifier, preserve written evidence and keep the previous transaction history linked to the same claim episode.
Run Kellan's independent review
Kellan assigns a reviewer who did not build the contract-termination claim runout register. The reviewer reconstructs the payer-contract termination claim close source, state, calculation, money movement, action, and close. Earlier versions, failed tests, unknowns, credits, exclusions, pending items, and holds remain available. Missing authority, unexplained amounts, overwritten history, concealed exceptions, or unsupported action fail review.
Anchor claim transactions to the adopted standard
Current 45 CFR 162.1102 identifies the adopted professional-claim standard. Kellan preserves the relevant claim identities and versions throughout the contract-termination claim runout register. Internal financial, migration, or ownership labels never replace the actual transaction and source evidence.
Separate claim processing, remittance, and money
The CMS electronic-claims page illustrates front-end Medicare claim processing, while the CMS remittance page separates claim, line, adjustment, and payment information. Kellan uses those examples within their scope and verifies every payer's current route before deciding payer-contract termination claim close.
Use published rates within their stated scope
The CMS PFS overview says its tool provides Medicare payment information and directs users to the MAC for official definitive files. The 2026 national payment file page provides versioned Medicare files. Kellan does not treat either source as a commercial contract, accounting rule, or universal ABA rate.
Classify credit recipients before financial action
The CMS-838 instructions define a Medicare credit-balance reporting mechanism and distinguish amounts due to Medicare, another insurer, or a patient. Kellan carries that classification discipline into the contract-termination claim runout register while verifying the actual program, contract, entity, state, recipient, and accounting duties.
Escalate potential overpayments through current authority
Current 42 CFR 401.305 governs specified Medicare overpayments and includes identification, investigation, deadline, reporting, and lookback provisions. Kellan keeps that Medicare scope visible and routes other payer, client, credit, refund, and accounting conclusions through their own controlling sources.
Interpret adjustment codes with complete context
The X12 external-code-list index defines code-list scopes. Kellan reads group codes, CARCs, RARCs, provider adjustments, payer messages, claim history, and payment evidence together before assigning a financial or operational meaning in the contract-termination claim runout register.
Protect payment and account information
HHS payment guidance and minimum-necessary guidance apply when their HIPAA conditions are met. Kellan limits access and disclosure to approved purposes and recipients while preserving the evidence needed for payer-contract termination claim close.
Keep professional and compliance authority visible
The CASP public summary and BACB Ethics Code retain their stated scopes. The voluntary OIG GCPG supplies a compliance framework rather than a payer, contract, coding, or accounting rule. Kellan routes clinical, billing, payer, finance, privacy, compliance, and legal decisions to qualified owners.
Related resources
- Reconcile Legacy ABA Claims After a Payer Product Migration.
- Preserve ABA Claim Evidence During a Billing System Migration.
- Build an ABA Billing Control Ownership Matrix.
- Resolve Small ABA Claim Balances Without Hiding Root Causes.
Sources
- Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary.
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
- Electronic Code of Federal Regulations, 45 CFR 162.1102, standard for health care claims.
- Centers for Medicare and Medicaid Services, Electronic Health Care Claims.
- Centers for Medicare and Medicaid Services, Health Care Payment and Remittance Advice.
- Centers for Medicare and Medicaid Services, Physician Fee Schedule Look-up Tool Overview.
- Centers for Medicare and Medicaid Services, Physician Fee Schedule National Payment Amount File.
- Centers for Medicare and Medicaid Services, Medicare Credit Balance Report, Form CMS-838 instructions.
- Electronic Code of Federal Regulations, 42 CFR 401.305, reporting and returning overpayments.
- X12, External Code Lists.
- U.S. Department of Health and Human Services, Uses and Disclosures for Treatment, Payment, and Health Care Operations.
- U.S. Department of Health and Human Services, Minimum Necessary Requirement.
- U.S. Department of Health and Human Services Office of Inspector General, General Compliance Program Guidance.
