Ethical ABA billing means that every claim reflects a service that actually occurred and is supported by the applicable authorization, payer rule, qualified provider, time record, and clinical documentation. Build the charge from verified care, preserve the evidence trail, stop questionable claims before release, and investigate and correct discovered errors through the route required by the payer, program, contract, and law.
Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.
Define the claim standard before reviewing claims
An audit-ready claim has a traceable chain from the governing rule to the money received. Define that chain in writing for each payer product, state, service, provider role, location, and date of service.
Use six separate decisions:
- Service occurred: Reliable schedule, attendance, and time evidence shows who delivered what service, to whom, where, and when.
- Service was permitted: Eligibility, authorization, network, enrollment, credential, supervision, location, and other preconditions were satisfied when required.
- Record supports care: The contemporaneous clinical record identifies the service and shows individualized, relevant work consistent with the treatment plan.
- Charge is accurate: The submitted code, units, date, rendering and billing identifiers, place of service, modifier, and other claim fields follow the applicable source.
- Payment is reconciled: The adjudication, adjustments, patient responsibility, denials, and money received match the remittance and contract logic.
- Problems are resolved: Holds, corrections, refunds, notices, investigations, and escalations have an owner, evidence, due date, and closure record.
A paid claim is not proof that all six decisions passed. A clean claim shows that a payer accepted it for processing. A compliant claim requires support under the rules that governed the service.
The Behavior Analyst Certification Board Ethics Code requires covered behavior analysts to identify services accurately, include required billing and reporting information, inform relevant parties about discovered inaccuracies, correct them in a timely manner, and document actions and outcomes. The BACB Code governs covered certificants and applicants. Organizational and legal duties also require their own controls.
Build one governed payer-rule record
Ethical ABA billing starts with a versioned rule inventory. A generic coding sheet cannot resolve differences among products, contracts, states, and dates.
Create one record for each meaningful payer configuration:
| Rule field | Required operational detail |
|---|---|
| Scope | Payer, legal entity, product, line of business, state, network, client population, service, and setting |
| Authority | Contract, provider manual, medical policy, authorization notice, fee schedule, code source, portal instruction, or written payer clarification |
| Version | Source URL or stored file, section, publication date, effective dates, retrieval date, and superseded version |
| Service logic | Covered service category, permissible provider role, direct or indirect status, participants, location, time basis, unit conversion, and concurrency rule |
| Claim logic | Code, required claim fields, modifiers, billing and rendering identifiers, place of service, submission window, attachments, and corrected-claim route |
| Authorization logic | Approved services, roles, units, frequency, settings, effective dates, conditions, and notice identifier |
| Governance | Interpretation owner, clinical approver when needed, RCM approver, legal or compliance escalation trigger, and next review date |
The ABA Coding Coalition publishes ABA code information and points users to licensed American Medical Association sources. Its frequently asked questions explain that payer reporting policies vary and distinguish some direct patient services from indirect work. Obtain the current licensed code source and payer rules for operational decisions. This page omits proprietary code descriptors.
The CMS Prior Authorization API FAQ describes response and data requirements for payer categories covered by the federal rule. It does not create one ABA authorization standard for every payer. Preserve the actual approval notice and map its client, services, roles, dates, units, settings, and conditions into the rule record.
Run the pre-claim checklist in delivery order
The most reliable control sequence follows the service. Each gate should produce a durable result that the next owner can verify.
Before the service date
- [ ] Confirm the correct client, payer product, active coverage, coordination-of-benefits information, and benefit limitations for the date.
- [ ] Verify that required referral, assessment, plan, consent, authorization, network, enrollment, credentialing, and location conditions are current.
- [ ] Map authorization units by service, provider role, setting, and date range. Record the source and any conditions or frequency limits.
- [ ] Confirm that the assigned clinician or technician holds the required credential, license, supervision relationship, payer-effective status, and internal competency approval.
- [ ] Check federal and applicable state exclusion sources at the cadence required by the practice's programs and policy.
- [ ] Block scheduling combinations that conflict with known payer concurrency, staffing, travel, location, or client-attendance rules.
The HHS Office of Inspector General exclusions page states that federal health care program payment is unavailable for items or services furnished, ordered, or prescribed by an excluded person and recommends routine checks of the List of Excluded Individuals/Entities. OIG's general guidance also addresses applicable state Medicaid exclusion lists. Practices need a documented screening policy tied to the programs in which they participate.
At service delivery
- [ ] Capture actual start and stop times or the required duration measure, setting, client presence, provider, participants, and interruptions.
- [ ] Record cancellations, late arrivals, early departures, breaks, travel, non-service activity, and handoffs according to the governing rule.
- [ ] Detect overlapping provider or client time across schedules, time records, notes, and charge candidates.
- [ ] Route concurrent services for review using the exact payer and code policy plus distinct clinical documentation for each reported service.
- [ ] Escalate any mismatch in provider, role, location, service, or authorization before a charge is created.
Concurrency review needs more than two appointments on a calendar. The reviewer should identify each service, provider, participant, time interval, clinical purpose, authorization condition, and payer rule. The result can be permitted, prohibited, unclear, or outside the reviewed rule's scope. Unclear belongs on hold until a qualified owner resolves it.
Documentation and charge capture
- [ ] Complete the record from the care delivered and the data observed. Avoid writing a note to fit a desired charge.
- [ ] Identify the client, service date, author, credentials, setting, participants, time or units, treatment-plan connection, interventions, response, data, material events, and next clinical action as applicable.
- [ ] Preserve signature, completion, addendum, correction, and version history according to current requirements.
- [ ] Derive the charge candidate from verified service data and the governed payer-rule record.
- [ ] Reconcile the service, code, units, provider role, rendering identifier, location, modifier, authorization bucket, and note before claim release.
- [ ] Confirm that each unit conversion uses the applicable definition and rounding rule. Keep raw minutes or the underlying measure beside submitted units.
Use explicit arithmetic. If the governing rule permits four 15-minute units for 60 reportable minutes, store the 60-minute source interval, the rule version, the calculation, and the four-unit result. That illustration shows the control structure rather than a rule for every service or payer.
Submission and adjudication
- [ ] Require a release status from each applicable gate:
pass,hold,not applicable, orunable to determine. - [ ] Prevent edits after release without a documented reopen reason, approver, timestamp, and version trail.
- [ ] Preserve the exact claim sent, clearinghouse acceptance or rejection, payer receipt, attachments, and submission identifier.
- [ ] Reconcile electronic remittance advice or other adjudication to the submitted claim, expected contract result, payment, adjustment, and patient responsibility.
- [ ] Classify rejections, denials, underpayments, duplicate payments, credit balances, and other exceptions by root-cause category.
- [ ] Keep appeal, corrected-claim, void, refund, and recoupment activity linked to the original claim and payment.
CMS's administrative simplification transactions overview identifies standard electronic transactions used for eligibility, claims, claim status, and payment and remittance advice. Transaction acceptance still leaves clinical support, authorization, coding, and contract questions to the applicable authorities.
Give corrections and overpayments a controlled route
Every credible concern needs triage. Preserve the original record, protect relevant evidence, restrict routine claim release when exposure may continue, and assign clinical, RCM, compliance, privacy, and legal owners according to the issue.
Use this response record:
| Field | What to capture |
|---|---|
| Trigger | Audit finding, denial, staff report, payer notice, credit balance, data alert, complaint, or legal inquiry |
| Initial scope | Claims, dates, clients, payers, services, people, locations, and systems potentially affected |
| Immediate safeguard | Claim hold, schedule block, access restriction, evidence preservation, supervision change, or other approved action |
| Investigation | Governing sources, facts tested, reviewers, sample method, findings, legal involvement, and scope expansion decision |
| Financial action | Claim correction, void, refund, offset, recoupment, reserve, or other payer-approved route |
| Reporting action | Contractual notice, payer or program report, licensing or credential report, or counsel-directed disclosure |
| Prevention | Root cause, policy or configuration change, training, accountable owner, due date, and new-record monitoring |
| Closure | Amounts reconciled, receipts, correspondence, approvals, unresolved items, and verifier sign-off |
Deadlines and processes vary. The July 2025 CMS Medicare Overpayments fact sheet, for example, describes Medicare requirements and contractor routes. Its timeframes should not be copied into a commercial or state Medicaid workflow without confirming the authority that governs that payment.
OIG's voluntary General Compliance Program Guidance calls for investigation, remediation, root-cause analysis, and appropriate reporting. Potential fraud or serious legal exposure requires experienced counsel and the proper authority. The OIG Health Care Fraud Self-Disclosure Protocol is a specific federal process for eligible conduct. It is not a substitute for ordinary payer refunds or other required routes.
Audit a claim from source to deposit
Use both a reproducible random sample and a separate risk-targeted sample. Define the eligible universe, payer products, dates, services, locations, claim statuses, exclusions, selection method, and replacements before looking at results.
For each sampled claim, trace this evidence:
- client coverage and payer product for the service date;
- referral, plan, consent, authorization, and approved conditions;
- provider identity, role, credential, license, payer status, supervision, and exclusion screening;
- schedule, attendance, actual time, setting, participants, and overlap review;
- signed clinical record, underlying data, correction history, and treatment-plan connection;
- charge calculation, code source, units, modifier, identifiers, location, and release approvals;
- submitted claim, acknowledgments, payer adjudication, contract expectation, payment, and ledger posting; and
- any denial, appeal, correction, refund, disclosure, remediation, and closure evidence.
Report at least four denominators separately:
- Claim pass rate: claims passing every applicable test divided by claims reviewed.
- Line defect rate: claim lines with one or more findings divided by lines tested.
- Dollar exposure rate: paid dollars associated with supported findings divided by paid dollars tested, with estimation methods disclosed.
- Recurrence rate: new exposed claims repeating the defect after remediation divided by new exposed claims reviewed.
An auditor should label not applicable and unable to determine distinctly. Missing evidence is a finding or limitation. It should not become a passing result.
The OIG General Compliance Program Guidance recommends risk assessment, scheduled audits, routine monitoring, data analysis, qualified clinical review where medical necessity is tested, and short-term monitoring after remediation. OIG labels the guidance voluntary and nonbinding, so the practice still needs its own current obligations and risk analysis.
Work a synthetic claim through the checklist
Assume an ABA practice audits a paid line for a hypothetical client. The stored authorization permits the service, provider role, setting, and four units on the date. Eligibility and payer enrollment were verified. The schedule shows 2:00 p.m. to 3:00 p.m.; the attendance record, provider time record, and note show the same interval. No provider or client overlap appears. The note identifies individualized work and links to the current plan. The charge engine converts 60 source minutes to four units under the archived payer rule. The submitted claim matches the charge candidate, and the remittance matches the ledger deposit.
The line passes the defined tests, subject to the auditor's source validation. During the same audit, an overlap alert for another claim lacks an archived payer concurrency rule. That claim receives unable to determine and moves to hold. The RCM owner retrieves the contract and manual version; the clinical reviewer checks whether distinct services occurred; compliance decides whether the sample or exposure period must expand. Payment status alone does not close the alert.
Use stop-ship and escalation rules
Write thresholds before a problem occurs. The following routing model needs adaptation by counsel and current payer or program sources.
| Level | Example trigger | Immediate route |
|---|---|---|
| Routine correction | Isolated clerical issue with a known approved correction path and no continuing exposure | Claim owner documents and completes the correction; supervisor verifies closure |
| Compliance review | Repeated unit, modifier, credential, authorization, documentation, or overlap finding | Hold related claims as scoped; compliance leads investigation and root-cause work |
| Clinical and compliance review | Record raises medical-necessity, treatment-integrity, provider-role, or client-welfare questions | Qualified clinician reviews care; compliance and operations protect continuity and claim integrity |
| Legal escalation | Possible fraud, excluded or unlicensed service, altered evidence, retaliation, systemic overpayment, government inquiry, or uncertain reporting duty | Preserve evidence, limit exposure, and involve experienced healthcare counsel promptly |
Staff need a good-faith reporting channel, a nonretaliation policy, a named intake owner, and a documented response. OIG's small-entity guidance supports an accessible reporting and investigation process. Compensation plans should also reward accurate work, timely escalation, and durable correction. Targets based only on units, collections, utilization, or note volume can encourage unsafe shortcuts.
Owner sign-off checklist
- [ ] A named compliance owner reports to leadership with enough independence and time to challenge billing decisions.
- [ ] Current rule records cover every material payer product, service, role, state, and setting.
- [ ] Scheduling, documentation, authorization, credentialing, charge capture, claim, remittance, and ledger systems share stable record identifiers.
- [ ] Claim release requires evidence-based gates and documented exception approval.
- [ ] Overlap, unusual units, authorization gaps, expired credentials, late or changed records, denials, and credit balances enter monitored queues.
- [ ] Corrections preserve originals and link every action to the responsible person, time, reason, and outcome.
- [ ] Refund and disclosure routes come from current program, payer, contract, state, and legal sources.
- [ ] Random and targeted audits use separate denominators, reproducible selections, qualified reviewers, and documented limitations.
- [ ] Root-cause remediation includes a new-record test for recurrence.
- [ ] Vendor agreements preserve practice access to source data, audit evidence, configuration, and correction history.
- [ ] Incentives include quality and compliance balancing measures.
- [ ] Leadership reviews unresolved high-risk findings, scope decisions, money at risk, action aging, and recurrence.
The Small Business Administration business guide can support general planning, finance, staffing, and launch work. It supplies no ABA billing rule. Use it for the operating plan while clinical, payer, coding, program, legal, and ethics sources govern claim decisions.
Related resources
- Billing, RCM, Denials, Appeals and Revenue Integrity
- ABA Claim Denials: How to Classify, Work and Prevent Them
- ABA Revenue Cycle Management: From Eligibility to Payment
- ABA Documentation Quality Audit Checklist
- Multi-State ABA Expansion Checklist
Sources
- U.S. Small Business Administration business guide
- CMS Prior Authorization API FAQ
- ABA Coding Coalition
- HHS Office of Inspector General compliance resources
- HHS OIG General Compliance Program Guidance landing page
- HHS OIG General Compliance Program Guidance PDF
- BACB ethics codes
- BACB Ethics Code for Behavior Analysts
- ABA Coding Coalition frequently asked questions
- HHS OIG Exclusions Program
- CMS Medicare Overpayments fact sheet
- HHS OIG Health Care Fraud Self-Disclosure Protocol
- CMS administrative simplification transactions overview