Preserve ABA Claim Evidence During a Billing System Migration

Define Jonas's billing-system migration evidence preservation control

Jonas treats migration as a controlled translation between data models. A successful login or matching dashboard total is only one test. The practice must also prove record lineage, version history, relationships, financial meaning, and retrievability.

Build the claim migration control book

Record source and target system; object type; source identifier; target identifier; claim and line versions; payer control number; service record; authorization; acknowledgment; remittance; EFT; adjustment; appeal; client account; attachment; note; audit event; access role; count; amount; exception; owner; and acceptance. 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 Jonas's workflow

Jonas freezes the conversion scope, inventories dependencies, documents transformations, runs trial conversions, and compares locked extracts. Qualified owners validate coding, billing, finance, clinical-record, privacy, security, and legal domains separately.

Assign each decision to its proper authority

Migration may change storage and identifiers. It cannot silently change clinical content, service facts, claim intent, adjudication, client responsibility, accounting treatment, retention, or access authority.

Work through Jonas's fictional example

Jonas migrates a fictional cohort of 1,200 claims containing 3,480 service lines, 1,110 remittances, 980 deposits, 84 corrections, 31 appeals, and 46 open credits. Counts match except for six historical claim versions rejected by the target schema. Those six remain quarantined with complete source exports and block final acceptance for their affected cases. 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 Jonas's measures

Claim-count completeness is 1,200 of 1,200. Line-count completeness is 3,480 of 3,480. Version-history completeness is 78 of 84 corrected-claim histories, or 92.9%. Separate denominators expose the defect that one aggregate claim count would miss.

Address the main billing-system migration evidence preservation risk

Flattening claims to current state can erase the history needed for corrections, appeals, audits, refunds, and client explanations. Broad migration access can also expose protected or financial information.

Test the claim migration control book against exceptions

Jonas tests original and corrected claim, void, split remittance, provider adjustment, recoupment, appeal attachment, client credit, duplicate legacy ID, inactive payer, late record, and access-role denial. 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

Pause cutover when a material population, relationship, source export, reconciliation, access control, rollback path, or owner acceptance is missing. Preserve live filing and appeal clocks during the hold.

Hand off open work with evidence

Jonas's control book includes inventories, mappings, transformations, rejected rows, reconciliation results, acceptance owners, access tests, retention plan, cutover checklist, rollback criteria, and postcutover monitoring.

Communicate the current state accurately

Staff receive clear rules for system of record, downtime, legacy lookup, duplicate-entry avoidance, escalation, and client communication. Claims and records retain their original dates and authorship.

Verify Jonas's acceptance evidence

Reviewers reconstruct sampled cases end to end in both systems, including every version and money movement. They also verify searches, exports, access denial, audit logs, and rollback evidence.

Maintain Jonas's control over time

Jonas retains migration artifacts for the applicable period, closes legacy access through an approved schedule, and records every postcutover correction against the frozen baseline.

Monitor Jonas's operational results

Track reconciliation defects, missing relationships, duplicate identifiers, access failures, user workarounds, rejected transactions, posting variance, and time to retrieve legacy evidence. Segment by conversion wave and mapping version.

Make the claim migration control book implementation-ready

Use control totals at object and relationship levels. A claim row can survive while its authorization, attachment, prior version, or remittance link disappears. Keep a crosswalk from every source key to target key, plus a quarantine state for values the target cannot represent. Final acceptance should require both technical validation and qualified domain signoff; production availability alone does not complete the migration.

Run Jonas's independent review

Jonas assigns a reviewer who did not build the claim migration control book. The reviewer reconstructs the billing-system migration evidence preservation 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. Jonas preserves the relevant claim identities and versions throughout the claim migration control book. 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. Jonas uses those examples within their scope and verifies every payer's current route before deciding billing-system migration evidence preservation.

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. Jonas 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. Jonas carries that classification discipline into the claim migration control book 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. Jonas 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. Jonas reads group codes, CARCs, RARCs, provider adjustments, payer messages, claim history, and payment evidence together before assigning a financial or operational meaning in the claim migration control book.

Protect payment and account information

HHS payment guidance and minimum-necessary guidance apply when their HIPAA conditions are met. Jonas limits access and disclosure to approved purposes and recipients while preserving the evidence needed for billing-system migration evidence preservation.

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. Jonas routes clinical, billing, payer, finance, privacy, compliance, and legal decisions to qualified owners.

Related resources

• Close ABA Claims After a Payer Contract Terminates.
• Resolve Small ABA Claim Balances Without Hiding Root Causes.
• Reconcile Legacy ABA Claims After a Payer Product Migration.
• Investigate Unapplied ABA Payer Cash.

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.