ABA Billing, Coding and Revenue Integrity links the service that actually occurred to an accurate claim representation. A defensible workflow preserves the clinical record, verifies the provider, client, date, time, location, participants, service, authorization, code, units, and payer route, and requires qualified review before release. It keeps authorization, coding, transmission, claim acceptance, adjudication, remittance, and payment separate so one successful stage never becomes proof of another.
Begin with source-to-claim traceability
Build every charge from reviewed source evidence. The completed clinical record should identify the actual service date and time, author, rendering person, setting, modality, participants, plan connection, work performed, and client response. Use schedule and authorization records as comparison sources rather than substitutes for the clinical record.
Create a source-to-claim map for member, payer, billing provider, rendering provider, service facility, authorization, code, modifier, units, diagnosis, place of service, and date. Record which source controls each field, who reviewed it, and what happens when sources disagree.
The current BACB Ethics Code addresses accuracy, documentation, billing and reporting, confidentiality, and delegation for covered behavior analysts. Clinicians document and correct clinical facts under applicable policy. Qualified coding and billing reviewers select the claim representation from verified evidence.
Use current licensed coding materials
CPT content is proprietary. The AMA CPT licensing FAQ explains licensing responsibilities. This page gives workflow guidance and does not reproduce licensed descriptors, parenthetical instructions, or full coding rules.
The ABA CPT codes and documentation guide helps practices align common adaptive-behavior service families with actual work and documentation. For each service date, verify the current licensed code set, payer or trading-partner guide, covered provider, face-to-face or other required component, time convention, concurrent-service rule, authorization, and documentation.
The ABA Coding Coalition FAQ offers stakeholder guidance on adaptive-behavior coding. It is neither the AMA nor a payer. Use it to orient operational questions, then confirm licensed CPT and the applicable payer source.
Avoid choosing a code from job title or note template. The same professional may perform different services, and the same activity can fall outside a billable service depending on purpose, participant, timing, and payer rules. Standalone scheduling, quality assurance, administrative work, and unsupported report writing do not become billable clinical service merely because they support care.
Control charge capture from schedule to signed record
The charge-capture audit checklist reconciles expected visits with actual services and released charges. A useful daily worklist shows:
- visits scheduled, canceled, held, completed, or changed
- source documentation complete and attributable
- signatures or attestations present when required
- authorization, provider, setting, date, and service gates
- charge proposed, held, corrected, released, or removed
- owner, age, and next action for every exception
Use unique service events as the denominator. A corrected charge is another state for the original event, not a second service. Keep sessions without a mature documentation window visible rather than labeling them missing too early.
Separate completion from quality. A signed note can still conflict with time, location, provider, or authorization. A scheduled appointment can be canceled or clinically changed. Release only after the required evidence agrees.
In a fictional daily review, 30 scheduled events reach the mature documentation cutoff. Twenty-four are completed services with source records, three were canceled, two are documented clinical holds, and one remains unresolved. Of the 24 completed services, 22 pass every release gate. Report 22 of 24 as completed-service release readiness and 22 of 30 as original-worklist yield. Keep the eight unreleased events visible by their actual state.
Treat overlapping services as a decision tree
The concurrent ABA billing guide asks whether two services truly occurred during overlapping time, who participated, what each qualified person did, whether the code and payer permit the arrangement, and whether each record supports distinct work.
Check actual timestamps, provider roles, client presence, group or individual structure, protocol-modification activity, supervision, caregiver work, and payer edits. Never shift time, split notes, or change clinical facts to make an overlap look payable. If the permitted route remains uncertain, hold the affected charge and seek source-based review.
An overlap alert is a signal. It may represent duplicate scheduling, documentation error, allowed concurrent work, nonbillable supervision, or separate services with a payer-specific rule. Preserve the evidence and the qualified decision.
Keep authorization and claim states separate
Authorization defines a payer's approval for a described service and period when required. Before charge release, match the member, provider, service, code, units, location, modality, and date with the applicable authorization and payer instructions. A broader clinical recommendation does not expand an authorization.
Track claim stages individually: created, transmitted, interchange checked, transaction acknowledged, claim acknowledged when applicable, adjudicated, remitted, paid, and reconciled. A clearinghouse acceptance, TA1, 999, or 277CA has its own technical or business meaning and does not itself establish final payer adjudication.
When a claim rejects or denies, identify the receiver, artifact, reason, original source, allowed correction route, and owner. Avoid resubmitting blindly. Duplicate submissions can create repayment and patient-balance problems.
Correct records, charges, and claims through separate controls
A clinician makes any permitted late entry, amendment, or correction under the documentation policy, preserving authorship, dates, reason, and required audit history. A coding or billing reviewer determines whether the change affects authorization, charge, claim, refund, disclosure, or reporting.
Record the original claim state before choosing replacement, void, appeal, corrected claim, or another payer route. Use the payer claim control number or other required reference from the proper artifact. Never substitute an internal account number or clearinghouse identifier when the route requires the payer's reference.
Reconcile downstream effects: remittance, payment, patient balance, refund, recoupment, secondary claim, and financial reporting. Close the episode only when the final payer and ledger state is verified.
Use NCCI and payer edits within their actual scope
The cited CMS Medicaid NCCI FAQ addresses correct-coding edits. It does not determine coverage, medical necessity, prior authorization, or utilization. State Medicaid programs can add more restrictive edits, and private insurers may adopt methods in ways CMS does not control.
Treat an edit as one sourced control for a named payer, product, route, service date, and code-set version. Record the edit result and any allowed review. Passing an edit does not prove that the claim is covered or payable.
Audit the system and learn from recurrence
Sample charges across payers, services, providers, locations, modifiers, and high-risk conditions. Trace each from clinical evidence through authorization, claim, remittance, and payment. Calibrate reviewers and preserve findings, clarification, correction, owner, and validation.
Useful measures include source-complete events divided by events due for review, release-ready charges divided by mature proposed charges, first-pass pre-adjudication rejects, adjudicated denials, corrected-claim episodes, refunds due and completed, and repeated errors among events exposed to the same rule and workflow version.
The OIG General Compliance Program Guidance is voluntary and nonbinding. Its risk assessment, reporting, auditing, training, corrective-action, and accountability ideas can help shape a revenue-integrity program. It does not validate a code or payer route.
Clinicians who want billing expectations aligned with clinical reality can explore clinical roles at Finni practices and ask about documentation time, coding support, correction policy, productivity pressure, and escalation.
Related resources
- Ethics, Compliance and Client Rights
- Clinical Documentation and Quality
- Denials, Appeals and Continuity of Care
Sources
- American Medical Association, CPT Licensing Frequently Asked Questions
- ABA Coding Coalition, Frequently Asked Questions
- Centers for Medicare & Medicaid Services, Medicaid NCCI FAQ Library
- Behavior Analyst Certification Board, Ethics Code for Behavior Analysts
- HHS Office of Inspector General, General Compliance Program Guidance