If an ABA payer reviewed your organization tomorrow, how quickly could your team show what happened from authorization through billing? Most practices would start with the clinical record. That makes sense. Session notes, treatment plans, signatures, service times, and medical necessity are important parts of supporting the services billed. But from what we see across ABA operations, documentation is only one part of the story. A payer may also need to know whether the provid

A referral is not complete when it enters the inbox. It is complete when the family reaches a defined outcome. For an ABA clinic, that outcome may be a scheduled first session, placement on a documented waitlist, transfer to another provider or a clearly recorded reason the referral did not proceed. Until then, the referral remains open work. The problem with many referral spreadsheets is that they record names and dates but do not manage movement. Effective ABA referral mana

A denial log should do more than prove that a claim was denied. If the tracker contains only the client, payer, claim number and denial code, it may help the billing team rework individual claims. It will not show why the same denial keeps returning or which upstream process needs to change. An effective ABA denial management tracker must support two jobs at once: Recover the claim currently at risk. Prevent the same root cause from affecting the next claim. The template belo

An active insurance policy does not automatically mean ABA services are covered, authorized or payable. A basic eligibility response may confirm that a member has active coverage. An ABA benefits verification workflow must go further. It needs to identify the correct plan, the entity managing the ABA benefit, network status, authorization rules, covered service types, family cost-sharing and the documentation your team must retain. This ABA insurance verification checklist gi

Hiring a provider and being able to bill for that provider are two different milestones. A new BCBA may have completed onboarding, received a caseload and started seeing families, but that does not automatically mean every payer will reimburse the resulting claims. The provider may still be waiting for enrollment, an effective date, a group affiliation or confirmation that the correct service location has been loaded. That is why an ABA provider credentialing checklist must t

Nobody lets an authorization expire on purpose. It happens because the auth lives in an email thread, the units live in the EHR, the renewal date lives in someone's head, and no single view puts all three together. By the time anyone checks, the units are gone or the renewal window has closed, and you're writing off sessions your team already delivered. An ABA authorization tracking spreadsheet fixes the visibility problem, at least until your caseload outgrows it. The free t

A parent mentions at pickup that they switched jobs in January and the insurance is different now. Someone writes it down. The new card gets scanned. Everyone feels like the thing was handled. Three months later you're looking at 40 denied claims across one client, and every one of them is correct according to the information the payer had. An ABA insurance change workflow exists because one piece of information has to land in six places, and human memory reliably lands it in

Claims don't age because they're hard. They age because nobody owns them. A claim sitting at 90 days is almost never a claim someone tried three times to collect. It's a claim that got submitted, didn't pay, and never got assigned to a human with a date attached. ABA accounts receivable follow-up is mostly an ownership problem dressed up as a volume problem. The fix isn't working faster. It's making sure no open claim exists without a next action and a next follow-up date. Wh

Reworking a claim fixes one claim. Categorizing why it denied fixes the next fifty. Most ABA denial management is claim repair: the denial comes in, someone corrects it, resubmits, and closes the task. The claim gets paid. The process that produced the denial stays exactly as it was, and the same denial shows up next month under a different client name. The difference between a clinic that rebills forever and one that gets quieter is a single habit. They record the root cause

Ask most ABA clinics where a client’s benefits verification stands and you’ll often get a person’s name instead of a status. Dana called the payer Tuesday. Mike is waiting for a callback. Billing should have it somewhere. That isn’t really a workflow. It’s a process being held together by people remembering what happened last. A reliable ABA insurance verification workflow should tell you three things without asking anyone: where the verification stands, who owns the next ste

Most ABA clinics don't lose authorization revenue because someone forgot to request an authorization. They lose it because the authorization was approved, then quietly ran out while sessions kept happening. Good ABA authorization tracking should answer one question at any moment: how many units are left on this authorization, for which code, until what date, and who is handling the renewal. If your team has to open three systems and ask two people to answer that, the answer u

A parent calls to say their child has new insurance. Maybe a job changed, maybe the family moved to a different state, maybe it's just the plan renewing on January 1. It sounds like a five-minute update. In practice, insurance changes in ABA therapy are one of the most underestimated causes of billing disruption, because a single change has to land correctly in four or five different places before a claim will actually pay. Miss one of those places, and the clinic keeps deliv

What if I told you that many ABA clinics do not lose revenue when a claim is denied, but weeks before that denial ever appears? I have seen the same pattern happen again and again. An authorization quietly reaches its end date, sessions continue as scheduled, and no one realizes there is a problem until the claim comes back unpaid. By then, the therapy has already been provided, the documentation may be complete, and everything may look correct on the clinical side. The probl

An ABA prior authorization renewal doesn't usually fail because a payer changes its mind. It fails because a date passed, a unit count ran dry, or a reauthorization sat in someone's inbox one day too long. All three are predictable. All three are catchable, if someone in your practice is watching for them before the deadline instead of after the denial. That's the real difference between clinics that lose revenue to expired authorizations and clinics that don't. It's not luck

Every ABA clinic starts on spreadsheets. One tab for the schedule, one for authorizations, one for who still needs a CAQH attestation. It works fine at twelve clients. The trouble is that ABA clinic operations don't fail loudly when they outgrow that setup. They fail quietly, in the form of a claim nobody followed up on and an authorization that expired on a Thursday. Here's the short answer. If you're missing revenue you already earned, and nobody on your team can tell you w

EVV for ABA therapy is electronic visit verification applied to sessions delivered in a client's home. Federal law does not require it for ABA. A small group of state Medicaid programs do require it, and several states switched from warning flags to automatic claim denials in 2026, so home-based practices need matching visit records now. What is EVV for ABA therapy? EVV stands for electronic visit verification. It's a digital check-in and check-out system that records who del

Two numbers from a sample ABA practice audit. 90+ days: collecting at 99.08%.0 to 30 days: collecting at 48.46%. Read that the way most people read an aging report, oldest first, and the practice looks outstanding. Nearly everything old has been collected, which is usually the hardest part of the job. Read it the other way and the picture inverts completely. That practice had stopped billing. The excellent 90+ numbers were residue from work done months earlier, and the collap

Almost every deadline in billing has a way out. Denied for auth, you appeal. Denied for coding, you correct and resubmit. Denied for eligibility, you rebill the right payer. Timely filing is the exception. Miss that window and the claim is gone. Not disputed, not pending, not worth a phone call. Gone. Which makes it strange how casually most practices arrive at the number. In one sample ABA audit, a ABA billing team had been working to a 90-day filing limit on a payer that wa

Open your AR report and read the comments column. Not all of it. Five notes, picked at random. For each one, ask a single question: could you set a deadline based on what this says? Most practices fail that test badly. In one sample ABA audit, 47 AR follow-up notes were scored and two of them had an expected payment date on them. Two. The other 45 described activity without ever committing to a checkable outcome. That's not a documentation problem. It's a collections problem

There's a category of lost revenue that no report in your billing stack is built to display. It isn't denials. Denials are visible, coded, and countable, and every billing system in the world has a screen for them. It isn't slow payers either, since those show up as aging balances you can watch and chase. It's the claims that were never filed at all. A visit happened. The session was documented. The service was billable. And then the claim didn't go out, and because it didn't