Downcoding Isn't the Safe Choice. It's Still the Wrong Code.

Some billing mistakes in applied behavior analysis (ABA) come from reaching too high in terms of what codes are assigned to a service encounter. Here, a provider may bill a longer session than the documentation supported, or select a code that pays more than the work justified, and everyone understands why that's problematic. Sometimes, though, the instinct to avoid scrutiny runs deep and can lead to other coding errors. When a clinician feels unsure, they may make an error in the other direction and pick a lower code (often a cheaper code) than the service actually delivered. 

That instinct feels responsible. It usually isn't. And it can cause you compliance problems.

Picking a lower code than your service supports has a name: downcoding. And while it rarely gets talked about in ABA, it carries real compliance risk of its own. Your obligation never runs toward billing low or billing high. It runs toward billing accurately. The service you actually delivered determines the code. Nothing else does.

What downcoding actually is

Downcoding means reporting a service with a code that reflects less than what you provided, usually a lower-paying or lower-intensity code. Sometimes it happens by accident, but sometimes it happens on purpose, often because someone believed the lower code would attract less attention.

The logic feels intuitive. A smaller claim seems easier to defend. A cheaper code seems less likely to trigger a review. If the goal is simply to keep claims moving and avoid denials, downcoding can look like the cautious path.

Here's the problem. A claim represents a factual assertion you make to the payer about what occurred. When the code doesn't match the service, the claim misstates the record, and the direction of the mismatch doesn't rescue it. An inaccurate claim is inaccurate whether it overstates or understates the work.

Where it shows up in ABA

A few patterns come up again and again.

The BCBA's own work, billed as the technician's. Consider a behavior analyst who drives to a client's home and works directly with the client, adjusting the program in real time as the session unfolds. That work fits 97155 (the protocol-modification code). The client has to be present; a technician does not. Yet a provider who feels uneasy might bill that hour as 97153, the technician's direct-treatment code, on the theory that the smaller code feels safer when no technician was in the room.

It isn't safer. A BCBA-level service got reported as a technician-level one. The record now understates who did the work and what the work was. If a payer later asks why a technician code appears for an hour no technician attended, the "playing it safe" explanation collapses, because the code never described what happened.

Assessment, billed as treatment. A behavior analyst spends a session on assessment work best described under CPT code 97151, reviewing records, conducting and scoring assessments, and drafting the plan, then bills it under a treatment code like 97153 or 97155. The reasons may vary. Maybe the assessment authorization ran out. Maybe treatment codes pay more predictably. Maybe it just felt like "We were with the kid, so it counts." Whichever way the value happens to fall, assessment remains its own service with its own code, and reporting it as treatment misrepresents what occurred.

Notice what ties these together. None of them turns on whether the chosen code pays more or less. Each one turns on a code that doesn't match the service. That's the whole issue.

Why "safer" is mostly a myth

Three things tend to get overlooked when downcoding feels like the cautious move.

First, it doesn't lower your audit exposure the way people assume. Auditors look for patterns that don't reconcile, not just for high-dollar claims. A technician code on a date with no technician, or assessment work that never appears under an assessment code, can flag just as readily as an inflated unit. You haven't ducked scrutiny. You've changed the shape of what gets questioned.

Second, it can carry the appearance of fraud, even when the intent felt protective. When a provider systematically reports services under codes that don't match, in order to keep claims paid or to dodge review, that pattern can read as a knowing misrepresentation of what services were furnished. A reviewer doesn't sit inside your good intentions. They see claims that don't line up with the record, and "I was trying to be careful" rarely reads as innocent once a pattern emerges.

Third, downcoding quietly corrupts your own data. Your service mix, your authorization usage, and your clinical record start to disagree with your claims. That gap can undermine medical-necessity arguments later, distort your understanding of your own utilization, and make a future audit harder to defend, because your records no longer tell one consistent story.

What to do instead

When it comes to coding, the rule stays simple, even when the situation feels murky: Bill the service you actually delivered. Document what you did clearly enough that the code follows from the note rather than the other way around.

When a code genuinely feels uncertain, the answer isn't to default to a lower code, it's to resolve the uncertainty. Check the code's definition, check the payer's written policy, and get the relationship between what you did and what you're reporting right. If a payer maintains a rule that diverges from the standard code definition, get that rule in writing and bill to it knowingly. "Conservative" coding chosen out of fear isn't a safe harbor. Accurate coding supported by documentation is.

If you're looking at your own claims and not feeling sure they'd hold up, that's worth a closer look before a payer does it for you. We help agencies work through exactly these questions, whether that's a focused review of your documentation and billing practices through Project-Based Support, or ongoing guidance inside the Compliance Collective. Either way, the goal stays the same: claims that say what actually happened.