Where you deliver ABA changes what you get paid.

Why a paid claim is the most expensive false signal

In revenue-cycle work, the sentence that costs the most is a comforting one: it paid. A paid claim feels like a closed loop. The therapy was delivered, the note was written, the money hit the bank, the report looks clean. But a place-of-service error does not always announce itself. Get the configuration wrong and one of two things happens. The claim denies outright, which is annoying but visible, and your system is now catching the error for you. Or, worse, it pays under a mismatched configuration, books as revenue, and quietly replicates across every claim of that type until a reviewer looks backward.

That second scenario is the one that hurts, because the damage compounds in the dark. A single mis-set place-of-service default, multiplied across months of caregiver-training sessions, is not a coding typo. It is a liability sitting on the balance sheet disguised as collected revenue. This is why an operator who tells us they have never had a telehealth denial has told us less than they think. Denials are the system working. It is the wrong-but-paid claim that becomes the recoupment.

What place of service actually encodes for ABA

Place of service is a two-digit code on the claim that tells the payer where care was delivered. It is not decorative. For ABA it interacts with the fee schedule, because many payers price the same procedure differently by setting, and it interacts with the payer's own coverage policy, because some settings are covered and some are not. The settings that recur in ABA billing are the office or clinic, the patient's home, the school, and, as its own category, telehealth.

• Office or clinic (POS 11). Care delivered in the practice's own space. Under Medicare's facility versus non-facility logic, services delivered where the practice carries the overhead are frequently priced at the higher non-facility rate, and many Medicaid and commercial schedules echo that structure. The specifics are payer-set.
• Home (POS 12). Care delivered in the patient's home, a common and often clinically preferred setting for early intervention. Whether the home pays the same as the clinic, more, or less, is a payer-and-state question, not a national constant.
• School and community. Care delivered in a school or other community setting, where coverage can turn on whether the service is educational or medical, and where a separate set of consent and access questions attach.
• Telehealth (POS 02 and POS 10). Care delivered over real-time audio and video. CMS distinguishes telehealth furnished in the patient's home (POS 10) from telehealth furnished somewhere other than the home (POS 02), and the correct choice, plus the telehealth modifier, is where clean claims most often break. This is the axis worth the most attention, so it gets its own section next.

The single most costly generalization in this space is the phrase the same service is covered. It treats a per-code, per-payer, per-state, per-setting question as if it had one answer. It does not. The same 97153 session can be a paid, correctly configured claim in one setting and an uncovered or mis-priced claim in another, for the same patient, under the same plan.

Telehealth: the sharpest place-of-service axis

Telehealth is where place of service does the most work, because the setting is not just a price input, it is a coverage question that turns on the specific service. Not all ABA services travel over video equally, and the divide is clinical before it is administrative.

Widely circulated ABA telehealth guidance walks through how each of these codes can map to telehealth, and it is worth reading in full, but note its vintage: the most-cited version was written in April 2020, mid-emergency. It tells you how the codes can map to telehealth. It does not tell you what your specific payers will pay for today. That second question is the one that determines whether your revenue is real.

The mechanics that quietly kill clean claims

Even when the service is eligible, telehealth claims fail on plumbing. A telehealth claim can require a specific place-of-service code and a telehealth modifier, and the exact combination is payer-set, not a single national standard. For synchronous telehealth submitted to Medicare, modifier 95 signals that the service was delivered by real-time interactive audio and video rather than in person, and CMS made that designation permanent for the ABA codes effective January 2026 (CMS, final 2026 Medicare Physician Fee Schedule). Commercial payers and state Medicaid programs set their own telehealth modifier and place-of-service rules, so the Medicare configuration is a reference point, not a rule you can carry across payers.

Get the configuration wrong and, again, either the claim denies, which is visible, or it pays under a mismatched setup and replicates. A default place-of-service value set once in the billing system, and never reconciled against each payer's actual policy, is the classic silent failure: correct-looking, paid, and wrong across an entire book of caregiver-training claims until someone reviews it.

The 2026 divergence: federal, state, and commercial

The 2026 landscape did not simply expand or contract. It diverged, which is harder to manage than either, because a federal approval, a state manual, and a commercial contract can now point in three different directions on the same code, and only one of them is the rule you actually bill under.

The January 2027 code overhaul

The ground shifts again soon. In September 2025 the AMA CPT Editorial Panel approved a full revision of the adaptive-behavior code set, effective January 1, 2027 (AMA CPT Editorial Panel; ABA Coding Coalition). The change is not cosmetic: the eight existing Category I codes (97151 through 97158) receive revised descriptors and guidelines, the two Category III temporary codes (0362T and 0373T) are deleted, and six new codes are added. The revised set will appear in the 2027 CPT Professional Edition, expected to publish in late 2026.

The specifics are becoming visible but are not yet final. CMS published proposed descriptors in the proposed 2027 Medicare Physician Fee Schedule in July 2026, still as placeholders rather than final numbers, readable but not billable, and the wording can change through finalization later in 2026. One telehealth question is expressly open: CMS proposes keeping the existing 97151 through 97158 on its permanent telehealth list for 2027, but the proposal does not address whether the six new codes will be telehealth-eligible, and the ABA Coding Coalition has indicated it plans to request that they be added before the final rule (CMS, proposed 2027 Medicare Physician Fee Schedule).

The operational point is blunt: any telehealth cheat-sheet, billing rule, or automation built on today's codes will need rebuilding, and code transitions are exactly when miscoding spikes. Practices that hardcoded the current code logic into their workflows will find those workflows fail when the new codes land. This is another argument for teaching a method rather than memorizing a table, because the method survives the transition and the table does not.

Two practice archetypes, two different answers

Place-of-service and telehealth questions do not resolve the same way for every practice, and the split that matters most is whether the practice performs its own diagnostic evaluations in house.

A practice with in-house diagnostics, meaning a psychologist or physician on staff who performs the diagnostic evaluation, faces the remote-delivery question at the evaluation layer as well as the treatment layer. The assessment code (97151) delivered over video raises setup, medical-necessity, and prior-authorization questions specific to the diagnosing clinician's own licensure and the payer's assessment-telehealth policy. A practice without in-house diagnostics, an ABA-only model that receives the diagnosis from an outside referring clinician, meets the telehealth question mainly at the treatment and caregiver-training layer, and its assessment exposure is narrower. The same 97151 telehealth policy reads differently against these two models, and it is worth mapping your practice to the correct one before you assume an assessment-over-video posture.

The operator's actual job here

You do not need to become a coder. You need a defensible, current, written answer to a single question, held per payer: which ABA services will this payer reimburse when delivered in each setting, under what place-of-service and modifier configuration, for which patients? If you can produce that, dated and sourced to the payer's own current policy, and reconciled against what your billing system is actually submitting, you have a process. If you cannot, you do not have a place-of-service process. You have a set of assumptions that happen to be paying, for now.

The fix is unglamorous and entirely doable.

1. Pull each payer's current policy in writingFor every payer you bill, obtain the current, written place-of-service and telehealth policy for ABA, dated. Public guidance is a starting reference; your contract is the binding document.
2. Confirm the eligible codes and required configurationFor each payer, record which services are reimbursable in each setting, and the exact place-of-service code and modifier each requires. Note any patient-eligibility conditions on telehealth direct therapy.
3. Reconcile against a sample of submitted claimsPull a sample of what your system actually sent, and compare the place-of-service and modifier values against the policy. This is where the silent, wrong-but-paid claims surface.
4. Remediate the gaps before a reviewer finds themFix the defaults, correct the configurations, and, where a book of claims paid wrong, address the exposure deliberately rather than waiting for a post-payment review to do it for you.

How this connects to your state's Medicaid rules

This page is the framework. The specific answers, which settings your state's Medicaid program reimburses, whether the home is priced differently from the clinic, and what the state manual says about telehealth for ABA, live on each state's Medicaid page, because those are the citable, state-specific facts. State fee schedules illustrate how much the setting can matter: Oregon's Medicaid ABA fee schedule, for example, sets published per-code rates that a practice can read directly, while other states manage rates inside managed-care plans where the number is harder to pin down. The point of comparison is not to assemble a single cross-state table here; it is to send you to the one page that governs your billing.

Place of service also reaches past the Medicaid pillar. Who is credentialed to deliver and bill a remote service is a licensing and credentialing question before it is a billing one, and whether your entity and structure support multi-setting delivery across state lines is the question upstream of both. The place-of-service configuration is the visible tip; the licensing, credentialing, and structure decisions underneath it are what make a given setting billable in the first place.

Common questions about POS and telehealth