ABA Audits and the Growing Pressure to Support Every Claim

If your practice has ever felt confident about the care you delivered but less certain about whether your paperwork could hold up to a payer’s scrutiny, you’re not alone. A growing pattern of ABA audits suggests that gap is more common — and more costly — than most providers realize.

This isn’t about one report from one state. Since 2025, the HHS Office of Inspector General (OIG) has completed audits of Medicaid-funded ABA services in four states — Wisconsin, Indiana, Maine, and Colorado — and found the same story every time: nearly every sampled claim had a problem, and the problems were almost always documentation-related.

Federal oversight is also continuing. As of September 2026, the U.S. Department of Health and Human Services Office of Inspector General (HHS-OIG) lists four active projects in its Medicaid ABA audit series. Published findings offer a practical starting point for examining where a practice’s own processes may leave claims insufficiently supported.

The common thread across all four states isn’t fraud in the criminal sense — it’s a documentation standard that many practices weren’t built to meet. Auditors weren’t finding evidence that care didn’t happen. They were finding that the paper trail couldn’t prove, to a federal audit standard, that it happened the way it was billed.

That distinction matters. A practice can deliver clinically appropriate ABA and still generate an audit finding, because payment on a claim doesn’t mean the claim is settled. It can still be reviewed, questioned, and clawed back — sometimes years later, as these multi-year lookback audits show.

If documentation standards are already tightening, providers should also know a bigger structural change is arriving on top of it: the ABA CPT code set is being revised for the first time since 2019, effective January 1, 2027. The ABA Coding Coalition — representing ABAI, APBA, the BACB, and CASP — worked with the AMA CPT Editorial Panel to approve six new codes, revised descriptors for the existing 97151–97158 code family, and the removal of two temporary codes.

In practice, that means the exact codes practices use to justify billing today will look different in little over a year — and documentation practices built around the current code set will need to be revisited well before the changeover.

Looking across all four state audits, the same categories of documentation gaps keep surfacing:

• Signatures missing, late, or inconsistent across session notes
• Session notes that don’t fully support the billed code — describing that a session happened without clearly justifying the specific CPT code and time billed
• Unsupported or excessive units, including overlapping service times
• Ambiguity around billable time — no consistent internal standard for what counts
• Credential files that lag behind reality, so billed services don’t clearly map to a qualified, active provider

None of these require bad intent. They require busy staff, manual processes, and no consistent check before a claim goes out — which is exactly why the pattern repeats state after state.

The following practices are operational suggestions to adapt to your organization’s requirements.

Keep current payer guidance accessible to the people scheduling, delivering, reviewing, and billing services. Assign responsibility for checking updates and translating them into staff instructions.

Make exceptions visible. If an authorization, credential, or required record needs attention, staff should know who resolves it and whether it affects the planned service.

Use a defined review process to check that the documentation supports the proposed claim. Confirm that required records and signatures are present, then review the substance of the note.

Separate administrative completeness from clinical review. A form can contain an entry in every field and still leave the service unclear.

Give reviewers a consistent way to return documentation for clarification and track resolution. Corrections should follow the organization’s applicable amendment procedures and preserve an accurate record.

Sample records across providers, locations, payers, and service types. Look for patterns that suggest a process or training problem.

If several staff members interpret the same requirement differently, revise the guidance and work through examples together. Then review another sample to see whether the change helped.

This approach aligns with OIG’s voluntary General Compliance Program Guidance, which includes risk assessment, auditing, monitoring, and corrective action as elements of a compliance program.

Consistent review becomes easier when clinical and administrative teams can work from connected records.

ABA Matrix, for example, supports these workflows through features like AI-assisted note audits, QA sign-off before billing, signature collection, and credential tracking that connect back to the actual visit record. None of that replaces human clinical judgment or a real compliance review; it just gives your team more consistent visibility into where the small gaps are before they turn into a $77.8 million headline.

ABA audits are no longer an isolated event happening to one state — they’re a repeating pattern, with the same documentation gaps surfacing in Wisconsin, Indiana, Maine, and Colorado alike, and a major coding change already on the calendar for 2027. The practices that come through this cleanly aren’t necessarily the ones providing the best care. They’re the ones that can prove it, consistently, in writing, against whatever standard is current at the time.

If it’s been a while since your practice did an honest documentation self-check, now is a reasonable time to do one — before an auditor, or a new code set, does it for you.

What documentation may be requested during an ABA audit?

Depending on the scope and payer, requests may include session notes, treatment plans, authorizations, diagnostic or referral records, signatures, provider qualifications, and billing records. Follow the specific request and applicable program requirements. The OIG ABA audit series illustrates several areas reviewers examine.

Can a paid ABA claim still be reviewed?

Yes. Postpayment reviews examine claims after reimbursement. Wisconsin’s OIG audit specifically recommended reviews that include session notes and provider education. See the Wisconsin report.

Title for This Block

Description for this block. Use this space for describing your block. Any text will do. Description for this block. You can use this space for describing your block.

Does an improper payment finding mean fraud occurred?

No. Missing or insufficient documentation can contribute to an improper payment finding. CMS explicitly distinguishes improper payments from fraud.

How can software support ABA audit readiness?

Software can help teams collect signatures, monitor credentials, flag potential documentation gaps, and route notes for review. Its value depends on configuration, accurate information, and staff follow-through. Clinical and compliance decisions still require human review.