To govern ABA claim write-offs and adjustments, define each adjustment class, required source, authorized role, financial account, client effect, payer or contract impact, approval threshold, and audit evidence. Separate contractual allowance, correction, timely-filing loss, administrative write-off, financial assistance, small balance, bad debt, refund, and recovery. Never use a generic write-off to hide unresolved claims, unsupported services, overpayments, or client credits.
Define Diego's claim write-off and adjustment governance control
Diego's register records the business reason and authority behind every financial change. It preserves the original charge, claim, adjudication, payment, balance, adjustment, approval, and later reversal.
Build the financial adjustment authorization register
Record person; claim; service; original charge; payer result; payment; client balance; adjustment class; reason; source; contract term; policy; authority; amount; account; threshold; approval; client impact; refund; recovery; effective date; reversal; audit; owner; and close. Structured fields preserve identity, authority, source, version, clock, evidence, 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 Diego's workflow
Diego verifies the underlying claim and account, assigns the correct class, and routes approval by threshold and authority. Accounting posts the approved entry while billing retains open payer work where needed.
Assign decisions to qualified owners
A write-off changes accounting and may change a client balance. It does not correct the clinical record, resolve payer liability, return an overpayment, waive a contract rule, or prove an appeal is finished.
Work through Diego's fictional example
Diego reviews 28 fictional adjustments. Ten are contractual, four corrections, three financial assistance, three small balances, two timely-filing losses, two bad debt, one refund, one recovery, and two lack authority. Twenty-six classify and approve or reject correctly. Two remain held. This synthetic cohort tests control logic and arithmetic only. It creates no coding, coverage, authorization, payment, client-balance, refund, recovery, overpayment, accounting, disclosure, or legal conclusion for a real person, provider, payer, claim, contract, or account.
Calculate Diego's measures
Disposition completeness is 26 of 28 adjustments, or 92.9%. Adjustment rates are reported by class against the relevant eligible charges or balances, never against one mixed dollar pool.
Address the main claim write-off and adjustment governance risk
Generic adjustments can conceal root causes and shift responsibility. Reversing a balance without preserving approval can break audit and refund reconciliation.
Test the financial adjustment authorization register against exceptions
Diego tests contractual allowance, correction, filing loss, assistance, small balance, bad debt, refund, recovery, duplicate entry, and reversed adjustment. Each fixture retains 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
Block posting when class, source, authority, amount, account, or client effect is unclear. Preserve active appeal, refund, and overpayment workflows.
Hand off open work with evidence
Diego's handoff includes the source account, adjustment class, calculation, evidence, approvals, financial and client effects, related open work, and owner.
Communicate the current state accurately
Client-facing explanations use understandable balance reasons and keep internal loss classifications out of the message unless relevant and accurate.
Verify Diego's acceptance evidence
A reviewer traces the adjustment from source through approval, posting, statement, and ledger. Reversals and refunds must link to the original entry.
Maintain Diego's control over time
Diego reviews adjustment mix, aging, overrides, reversals, and root causes monthly. Policy changes create versioned rules and tests.
Monitor Diego's operational results
The register reports counts and dollars by class, payer, location, age, approver, and workflow version. Timely-filing and administrative losses trigger corrective analysis, while contractual adjustments are compared with the correct contract rate. Hidden or uncategorized entries remain exceptions.
Define adjustment classes by business meaning and evidence, then restrict who may select each class. A contractual adjustment should reconcile to the applicable rate. A payer correction should link to its remittance and original claim. Charity, bad-debt, small-balance, refund, and administrative-loss entries need the policy, approval, and accounting treatment that apply to that category. Keep reversals paired with the original entry. Reporting should show gross charges, contractual adjustments, other adjustments, payments, refunds, and remaining balance separately so an adjustment code cannot conceal a workflow failure or move liability to a family without authority.
Run Diego's independent review
Diego assigns a reviewer who did not build the financial adjustment authorization register. The reviewer reconstructs the claim write-off and adjustment governance source, state, calculation, money movement, action, and close. Earlier versions, failed tests, unknowns, credits, exclusions, pending items, and holds remain available. Hidden exceptions, missing authority, unexplained amounts, overwritten history, or unsupported financial action fail review.
Anchor released claims to the adopted standard
Current 45 CFR 162.1102 identifies the adopted professional-claim standard. Diego preserves exact service and claim identities throughout the financial adjustment authorization register. A financial estimate, schedule, or rate table never substitutes for the transaction or source record.
Separate front-end claims evidence from adjudication
The CMS electronic-claims page describes a Medicare route with batch and claim edits. The CMS remittance page separates claim, line, provider adjustment, and payment information. Diego keeps those Medicare examples scoped while verifying each payer's current route for claim write-off and adjustment governance.
Use fee schedules 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 exposes versioned Medicare files. Diego does not treat either source as a commercial contract or universal ABA rate.
Keep credit-balance pathways program-specific
The CMS-838 instructions define a Medicare credit-balance reporting mechanism and explicitly distinguish amounts due to Medicare, another insurer, or a patient. Diego uses that lesson to classify recipients while verifying actual entity, program, payer, contract, state, and account 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. Diego does not generalize that rule to every credit, refund, payer, or client account and routes legal conclusions to qualified owners.
Interpret adjustment codes with the complete remittance
The X12 external-code-list index defines code-list scopes. Diego reads group codes, CARCs, RARCs, provider adjustments, and payment evidence with the full claim and payer context before deciding claim write-off and adjustment governance.
Protect payment and account information
HHS payment guidance and minimum-necessary guidance apply when their HIPAA conditions are met. Diego limits access and disclosure to the approved purpose and recipient while preserving evidence for the financial adjustment authorization register.
Keep clinical and compliance authority visible
The CASP public summary and BACB Ethics Code retain their stated scopes. The voluntary OIG GCPG is a compliance framework rather than a payer or accounting rule. Diego keeps clinical, billing, contract, payer, accounting, privacy, compliance, and legal decisions with qualified owners.
Related resources
- Close an ABA Revenue Cycle Period Without Hiding Exceptions.
- Return an ABA Client Credit or Refund Safely.
- Reconcile ABA Services to the Complete Claim Inventory.
- Roll Out ABA Fee-Schedule and Rate Changes Safely.
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.