An ABA billing audit checklist should trace each delivered service from current eligibility and authorization through the schedule, attendance evidence, signed note, charge, claim, remittance, and ledger. The audit should compare client, date, time, units, provider, service, modifier, place of service, authorization, and signature at every handoff. Run the trace in both directions to find missed charges and charges that lack support.
Charge capture converts evidence of a billable service into an internal charge. It should occur only after the practice can show what happened, who delivered it, where and when it occurred, and which current rule supports the proposed claim line.
Keep ten events separate
Each event answers a different question. One owner may perform several tasks in a small practice, while accountability should remain visible.
| Event | What it establishes | Accountable owner | Required evidence |
|---|---|---|---|
| Eligibility and benefits | The payer's response about enrollment and benefit information for the requested date or service type | Intake or RCM | Dated response, payer, product, member, service inquiry |
| Authorization | The payer's decision and approved scope, when authorization applies | Authorization team | Decision, identifier, dates, service, provider or setting limits, units |
| Schedule | What the practice intended to occur | Scheduling | Client, provider, planned service, date, time, setting, status |
| Service evidence | What actually occurred | Rendering professional and supervisor | Attendance, actual times, setting, participants, contemporaneous data |
| Signed note | The responsible professional's authenticated clinical record | Author and clinical reviewer | Encounter facts, service content, response, signature, date |
| Coding decision | Why the service maps to the selected code, modifier, provider, units, and place of service (POS) | Qualified coder or RCM lead | Versioned payer matrix, licensed code reference, documentation crosswalk |
| Charge | The practice's internal billable line | Charge-capture owner | Encounter ID, line fields, amount, source version, creator, timestamp |
| Claim and acknowledgement | What was transmitted and whether the transaction passed an initial acceptance step | Billing | Claim version, transmission record, payer control numbers, response |
| Adjudication and remittance | How the payer processed each claim line | Payment posting | Line status, allowed and paid amounts, adjustment codes, remittance |
| Reconciliation | Whether claim, remittance, deposit, adjustment, and accounts receivable agree | RCM and finance | Posted ledger, electronic funds transfer (EFT), open balance, disposition |
CMS describes eligibility responses as coverage information, the X12 837 claim as a request for payment, and electronic remittance advice (ERA) as the explanation of a claim payment or adjustment. Those current eligibility, claim, and ERA and EFT pages support the distinction. An eligibility response or transmission acceptance is therefore an earlier event than adjudication.
CMS's current Prior Authorization API FAQ applies to specified impacted payers and describes authorization decisions, duration, denials, and requests for more information. It does not replace service evidence, coding rules, or claim adjudication.
Audit the fields across every handoff
Use the governing payer matrix to decide which fields are required. The table identifies common comparisons without prescribing a code or modifier.
| Field | Compare across | Pass condition | Failure owner |
|---|---|---|---|
| Client and payer | Eligibility, authorization, encounter, claim | Same person, payer, product, and member identifier for the date | Intake or RCM |
| Date of service | Authorization, schedule, evidence, note, charge, claim | Same actual service date inside the applicable period | Scheduling and billing |
| Actual time and units | Attendance, data, note, charge, claim | Actual supported duration converts to units under the current payer rule | Clinician and RCM |
| Service | Plan, authorization, note, licensed code source, claim | Work performed supports the selected reporting category | BCBA and qualified coder |
| Rendering and billing provider | Schedule, credential file, note, charge, claim | Correct person, role, identifiers, group relationship, and eligibility | Credentialing and RCM |
| Modifier | Provider role, modality, payer rule, claim | Every modifier has a current documented reason | Qualified coder or RCM |
| POS and modality | Actual setting, note, payer matrix, claim | Claim setting reflects where the service occurred and payer instructions | Clinician and billing |
| Authorization use | Decision, prior claims, current charge | Service fits applicable scope and available units; ledger avoids double decrement | Authorization team |
| Diagnosis or clinical link | Current plan, payer rule, claim | Current supported link appears where required | Clinical and coding |
| Signature | Note, credential, completion policy | Responsible author and required reviewer authenticate within the applicable rule | Clinical lead |
| Claim identity | Charge, claim version, acknowledgement | One intended original, replacement, or void path with traceable control numbers | Billing |
| Financial result | Claim, ERA, EFT, contract, ledger | Each line and adjustment posts to the correct account and deposit | Payment posting and finance |
CMS maintains POS codes for professional claims and says they indicate the setting where a service was provided. Consult the current CMS POS source, then apply the payer's instructions. For adaptive-behavior coding, use the licensed current code set and payer materials. The ABA Coding Coalition can alert teams to code developments, while the contract and controlling code source govern reporting. This article does not reproduce CPT descriptors.
The CASP ABA Practice Guidelines summary describes standards for planning, implementing, and evaluating ABA assessment and treatment. Its full text carries licensing terms. Charge review should preserve clinical meaning and avoid turning the note into a list of billing fields.
Combine pre-bill controls with retrospective testing
Pre-bill controls stop a questionable line before submission. Require a signed note, supported actual time, resolved provider and setting, current authorization check where applicable, duplicate and overlap screen, and versioned code/modifier/POS selection. Route overrides to a named approver and retain the original result, reason, user, and time.
Retrospective audits test whether the controls worked. A two-way ABA billing audit checklist reveals different errors in each direction. Use two populations:
- Schedule to claim: Start with delivered encounters after the documentation and charge lag has closed. Find encounters with no supported charge or no claim.
- Claim to note: Start with submitted or paid lines. Confirm a matching delivered encounter, signed record, authorization check, coding decision, and financial disposition.
Add 100% review for high-risk flags such as concurrent services, manual unit changes, late or corrected notes, claim replacements or voids, credential gaps, unusual utilization, and repeated overrides. Draw a random or stratified sample from the remaining population by payer, service category, provider role, setting, and location. Record the population dates, exclusions, sample method, selected records, failed fields, reviewer, and evidence. A statistical extrapolation requires a qualified methodology; HHS-OIG provides RAT-STATS as one claims-review resource.
The HHS Office of Inspector General's compliance resource page routes providers to current guidance. Its voluntary General Compliance Program Guidance recommends risk-based auditing and monitoring, data analysis for outliers, clinical review of medical necessity in claims audits, and corrective action when an audit identifies a problem.
Route exceptions by severity
Severity reflects patient, compliance, and financial risk. It does not predict a payer outcome.
| Level | Examples | Immediate action | Route |
|---|---|---|---|
| Critical stop | No evidence the service occurred; wrong client; impossible provider overlap; suspected fabrication; paid duplicate | Stop or contain billing, preserve records, investigate scope | Compliance officer, RCM lead, clinical leader, counsel as needed |
| High hold | Unsigned note; unsupported units; provider, modifier, POS, date, or authorization mismatch | Hold claim or adjustment until authoritative evidence resolves the field | RCM lead plus the owning clinical or operational role |
| Moderate correction | Complete service evidence with a fixable pre-submission charge field; unposted remittance; aging complete note | Correct through the controlled workflow and verify downstream state | Billing or payment-posting owner |
| Process signal | Repeated late notes, frequent overrides, rising mismatch rate | Trend, identify root cause, retrain, and retest the control | Process owner and compliance monitor |
Potential overpayments, false records, or systemic issues need the practice's compliance and legal response process. Keep the audit reviewer from silently fixing the source record because that erases evidence about why the control failed.
Use denominator-based metrics
Counts alone hide volume changes. Define each denominator and aging cutoff:
- Missed-charge rate: delivered, charge-eligible encounters without a charge after the approved lag divided by delivered, charge-eligible encounters after that lag.
- Unsupported-line rate: audited claim lines missing required service or documentation support divided by audited claim lines.
- Field-mismatch rate: audited lines with at least one specified mismatch divided by audited lines tested for those fields.
- Timely-signature rate: notes authenticated within the governing deadline divided by delivered encounters requiring a note and due by the measurement date.
- Initial-acceptance rate: accepted original claim transmissions divided by original claim transmissions, with acceptance kept separate from adjudication.
- Remittance-reconciliation rate: adjudicated lines linked to the correct ERA, ledger disposition, and EFT where paid divided by adjudicated lines due for posting.
Publish results by payer, service, provider role, setting, and location only when the group size supports responsible interpretation. Track both record count and dollar exposure. A low error count can still contain a high-risk unsupported service.
Synthetic trace: scheduled time differs from delivered time
This fictional example contains no protected health information and uses invented rates and field labels.
Payer M authorizes a technician-delivered service in the home. The payer matrix for this example uses 15-minute units, a technician modifier labeled T, and a home POS labeled H. The schedule shows 3:00 to 5:00 p.m. The attendance record and signed note show that care occurred from 3:05 to 4:50 p.m., or 105 minutes, because the family arrived late.
An automated charge used the scheduled duration and created eight units. The pre-bill comparison flags the 15-minute difference. The clinician confirms the actual times without altering the original attendance evidence. RCM changes the charge to seven units, retains the audit event, confirms authorization availability, and submits one claim line with the supported provider, T, and H fields.
The claim acknowledgement reports acceptance. A later ERA shows a synthetic $560 allowed amount, $500 payer payment, and $60 patient responsibility. Payment posting links the line to the ERA, matches the $500 to its EFT trace, applies the contractual adjustment, and leaves the supported $60 balance under the practice's financial policy. The audit closes only after those records reconcile.
Protect record integrity during corrections
Documentation corrections and claim corrections are separate. A note correction should identify the author and date, preserve the original content, explain the change under the governing policy, and add facts that were true at the time of service. It cannot create a service that did not occur.
CMS's current Medicare signature fact sheet and Medicare Program Integrity Manual are Medicare-specific examples. The manual says the date and author of an amendment, correction, or delayed entry should be identifiable and the change should be clearly and permanently denoted. Other payers and states may apply different requirements.
Before transmission, correct the controlled charge and preserve its change history. After transmission, use the payer's exact corrected-claim, replacement, void, or appeal route and reference the original control number when required. Keep the original claim, response, reason, replacement, remittance, and ledger entries connected. A second original claim can create duplicate risk.
The BACB Ethics Code landing page points to the current requirements. The Ethics Code for Behavior Analysts requires accurate service billing and reporting and timely correction of discovered inaccuracies. Clinical and billing leaders should investigate pressure to inflate time, select a higher-paying service, reuse another client's note, or ignore setting, provider, supervision, and concurrency facts.
NC Medicaid supplies a current program example. Its August 5, 2026 RB-BHT provider bulletin applies to NC Medicaid Direct and Managed Care. It describes monitoring for inappropriate concurrent billing, clinically unlikely utilization, telehealth patterns, provider proximity, nonindividualized plans, and lapsed credentials. Use those flags only within that stated scope and verify the controlling policy and health-plan instructions.
Reusable charge-capture checklist
- [ ] Define the audit period, closed lags, population, exclusions, and sample method.
- [ ] Run schedule-to-claim and claim-to-note traces.
- [ ] Verify eligibility and authorization evidence for the applicable date and service.
- [ ] Reconcile actual attendance, time, setting, participants, and provider with the signed note.
- [ ] Validate code, units, modifier, POS, provider, diagnosis link, and authorization against the current matrix.
- [ ] Confirm the charge and claim preserve source and version history.
- [ ] Separate acknowledgement, claim status, adjudication, remittance, and payment.
- [ ] Match each adjudicated line to ERA, EFT where paid, adjustment, ledger, and remaining balance.
- [ ] Route exceptions by severity and retain evidence of resolution.
- [ ] Review corrections, late entries, replacements, voids, duplicates, and overrides.
- [ ] Calculate rates with named denominators and stratify meaningful results.
- [ ] Expand the review when findings suggest a systemic or high-risk issue.
- [ ] Record corrective action, owner, due date, retest date, and closure evidence.
Related resources
- Parent topic: ABA Billing, Coding and Revenue Integrity
- Concurrent ABA Billing: A Decision Guide for Overlapping Services
- ABA CPT Codes and Documentation: Aligning 97151, 97153, 97155 and 97156
- ABA Session Note Checklist: What a Defensible Note Should Show
- Using AI for ABA Clinical Documentation Safely: Human Review, Privacy and Audit Trails
Sources
- BACB Ethics Codes
- CASP ABA Practice Guidelines Version 3.0 public summary
- CMS Prior Authorization API FAQ
- ABA Coding Coalition
- HHS-OIG compliance resources
- BACB Ethics Code for Behavior Analysts
- HHS-OIG General Compliance Program Guidance
- CMS Health Plan Eligibility Benefit Inquiry and Response
- CMS Health Care Claim or Equivalent Encounter Information
- CMS Place of Service Codes
- CMS Health Care Payment and Remittance Advice and EFT
- CMS Complying With Medicare Signature Requirements
- CMS Medicare Program Integrity Manual, Chapter 3
- NC Medicaid updated RB-BHT requirements bulletin, August 5, 2026
Sources were checked August 13, 2026. Confirm the current payer, plan, state, code-set, authorization, provider, and contract requirements before use.
