ABA authorization unit tracking works best when a practice keeps approved units and dates in a versioned ledger, then reconciles that ledger to the clinical plan, schedule, rendered-service record, claim family, and remittance. Operations owns data freshness and alerts; the BCBA owns care decisions. Each calculation must use the same authorization line, unit definition, provider, setting, date span, and denominator. Escalate projected gaps or overruns before they can interrupt care or create billing risk.
This guide addresses non-drug ABA authorization tracking in the United States. The member's notice, plan terms, payer manual, contract, current code source, state rules, and service record control an actual case. It gives no care-hour recommendation or assurance of approval, coverage, or payment.
Protect the clinical, authorization, and billing boundaries
A unit tracker has three jobs. It preserves the clinician's current recommendation, enforces the payer's stated approval parameters, and keeps billing tied to the service that actually occurred. Combining those jobs into one “hours used” cell makes errors difficult to locate.
Keep these records separate:
| Record | Question it answers | Decision owner |
|---|---|---|
| Clinical plan | What services does the qualified clinician currently recommend, and why? | BCBA or other qualified treating clinician |
| Payer authorization | What service, quantity, dates, provider, setting, and conditions did the payer approve? | Payer decision, transcribed and verified by authorization operations |
| Schedule | What future service events are planned? | Scheduler within clinical and authorization constraints |
| Rendered-service record | What occurred, for how long, with whom, and where? | Rendering staff and clinical documentation owner |
| Charge and claim | What documented service was released for billing and submitted? | Revenue cycle management (RCM) |
| Remittance and correction | How did the payer adjudicate the line, and what later transaction changed it? | RCM under the payer's correction rules |
Approved quantity is a coverage boundary. It does not direct a clinician to consume every unit. Low utilization can reflect a late start, staffing loss, family availability, illness, a clinical change, transition, or faulty data.
The Behavior Analyst Certification Board's current Ethics Code for Behavior Analysts addresses accurate service billing and reporting, timely correction and documentation of inaccuracies, conditions that interfere with service delivery, and efforts to facilitate continuity during planned or unplanned interruptions. The code applies to certificants. Practices also need the governing payer, contract, law, and organizational procedures.
Build the authorization as a multidimensional record
An authorization is more than a unit total. Create one versioned line for each approved service configuration and attach the source decision.
| Field | Minimum control |
|---|---|
| Member and coverage | Member ID, payer legal entity, plan or product, state or program, eligibility-check date |
| Authorization identity | Authorization number, decision date, request type, status, version, superseded record |
| Service identity | Current code, applicable modifier, service label used internally, code-set effective date |
| Quantity | Approved amount, unit definition, rounding rule, daily or weekly constraints when stated |
| Effective period | Start date, end date, whether dates are inclusive, amendments, gaps, and overlaps |
| Provider | Billing and rendering group, approved provider type or identifier, supervision condition |
| Setting | Approved location, place of service when stated, telehealth or community conditions |
| Concurrency | Named combinations, overlap, group, multiple-provider, or same-day conditions |
| Decision details | Approved, partially approved, denied, or pending lines; information requests; notice reason |
| Source and verification | Original notice, portal export, policy or manual, file hash or version ID, verifier, timestamp |
Use the unit definition from a current licensed code source and the controlling payer instruction. The ABA Coding Coalition is an industry resource. CMS explains that the existence of a code does not determine coverage or payment in its coding overview.
Do not assume that every ABA service uses the same time unit. A unit can also be constrained by date, provider, setting, frequency, or combination with another service. Two lines with the same authorization number may need separate balances.
Use one ledger with linked source objects
The ledger should connect source records without overwriting them. Give every authorization line, clinical-plan version, appointment, rendered event, charge, claim line, remittance line, and reauthorization case a stable internal ID.
| Object | Source of truth | Required relationship | Operational owner |
|---|---|---|---|
| Authorization version | Payer notice or verified portal record | Member, service line, effective period, prior version | Authorization team |
| Clinical-plan snapshot | Signed current plan and clinician update | Recommended service, goals, setting, planned cadence, review date | BCBA |
| Appointment | Published schedule and change history | Authorization line, plan version, staff, location | Scheduling |
| Rendered event | Signed service evidence | Appointment when one existed, actual provider, date, time, place | Clinical documentation |
| Charge | Passed pre-bill review | Rendered-event ID and authorized configuration | Charge capture or RCM |
| Claim family | Original claim plus replacements, reversals, or voids | Charge ID, payer claim ID, prior transaction | RCM |
| Remittance | Electronic or paper payer response | Claim-family member and line outcome | RCM |
| Reauthorization case | Payer checklist and clinical review plan | Current authorization, next requested period, dependencies | Prior-auth team and BCBA |
CMS explains how electronic remittance information reports adjudication and adjustment reasons in its payment and remittance guidance. Preserve that response as a financial event, not a clinical record.
Reconcile at four operating moments
Each reconciliation has a named owner, input cutoff, exception route, and evidence of completion.
1. When the decision arrives
Two people should verify the transcription of material fields against the notice. Record partial approvals line by line. Preserve the requested quantity and clinical recommendation as earlier states. If the notice is unclear, escalate to the payer and keep the line on hold until a qualified owner documents the answer.
2. Before a service is delivered
Compare the appointment with the authorization effective dates, service identity, remaining approved quantity, provider, setting, and other stated conditions. Recheck eligibility according to practice policy and after known coverage changes. The scheduler may resolve a calendar issue. A BCBA resolves clinical fit. Authorization or RCM staff resolve payer configuration.
3. After service and before claim release
Replace planned duration with the supported rendered quantity. Link the signed note or other required evidence, then apply the verified unit and rounding rule. Compare provider, date, time, location, service, and any overlap with other events. A late entry or corrected note gets its own version and review trail.
4. After submission and adjudication
Post the payer claim ID, accepted or rejected status, paid or denied units, adjustment reason, and any correction. Reconcile the latest active claim-family state to the rendered event. A denial does not erase delivered care, and a paid line does not revise the clinical plan.
The HHS Office of Inspector General provides voluntary compliance resources for health-care organizations through its compliance portal. Those materials support organization-specific controls and monitoring for federal health-care programs. They do not replace a payer's exact submission, correction, retention, or disclosure rules.
Calculate utilization pace with explicit denominators
All quantities in a formula must share the same member, authorization version, service line, unit basis, approved provider or setting dimensions, and as-of timestamp. Label every formula as an operational alert. A BCBA decides whether care should continue, change, fade, pause, or transition.
Core quantities
Remaining approved units = approved units - net eligible rendered units
The numerator uses supported service events that fit the authorization dimensions. Do not substitute billed units or paid units. Pending notes belong in a separate exception count.
Authorization quantity utilization = net eligible rendered units ÷ approved units
State the numerator and denominator beside the percentage. A 50% result has little meaning until the period, line, and causes are known.
Authorization period elapsed = completed eligible calendar days ÷ total eligible calendar days
Define whether the payer counts both boundary dates. Use the same convention throughout the ledger. Maintain a second late-start measure when access began after the effective date:
Late-start exposure = calendar days from authorization start to first feasible service date ÷ total authorization calendar days
This measure describes time exposure. It does not judge the family or clinician.
Schedule and forecast quantities
Delivery rate = net eligible rendered units ÷ scheduled eligible units
Exclude canceled units from the numerator. Keep cancellation reasons separately so the practice can distinguish staffing, family choice, illness, authorization holds, and clinical changes.
Scheduled overrun exposure = net eligible rendered units + future scheduled eligible units - approved units
A positive result means the current calendar exceeds the remaining authorization boundary. Place affected appointments in a review queue before service. Do not automatically shorten or cancel clinically indicated care without the BCBA and appropriate payer escalation.
Illustrative end-of-period forecast = net eligible rendered units to date + (future scheduled eligible units × comparable delivery rate)
Choose the comparable window before calculating. Record its dates, scheduled-unit denominator, rendered-unit numerator, and excluded anomalies. Use several scenarios when the future calendar is unstable.
Separate underuse, overuse, and late-start risks
One red utilization flag can produce the wrong action. Use a cause-based queue.
| Signal | Questions to investigate | Primary route | Unsafe shortcut |
|---|---|---|---|
| Forecast below the current clinical plan | Did care start late? Were sessions canceled? Did staffing, access, health, preference, or the clinical plan change? | BCBA plus scheduling or access owner | Packing missed units into longer sessions solely to use approval |
| Rendered plus future scheduled units exceed approval | Is the ledger current? Did an amendment arrive? Does the schedule use the right line, dates, provider, and setting? | Authorization team, scheduler, BCBA | Silently reducing clinically recommended care or billing beyond approval |
| Effective period is passing before first service | Is the barrier authorization, provider capacity, family availability, credentialing, setting, or another dependency? | Access and prior-auth escalation | Treating the authorization date as proof that staff were available |
| Pace changes abruptly | Was there a correction, void, duplicate, schedule import, unit conversion, or real service change? | Data owner first, then clinical or RCM owner | Assuming the child or family caused the variance |
| Authorization ends before scheduled care | Is a continuation request due, pending, incomplete, or denied? | Prior-auth lead and BCBA | Delivering under an expired approval without a verified rule or exception |
Include client and caregiver communication in the continuity plan. Explain administrative risks plainly and keep payer decisions separate from clinical conclusions.
Handle concurrency, corrections, and voids as controlled events
Concurrency and overlap
Two events that overlap in time are not automatically duplicates. They may represent an error, an allowed combination, a prohibited combination, a caregiver service occurring separately, or a documentation problem. Capture the actual people, services, time intervals, settings, and activities. The BCBA reviews clinical feasibility. A qualified RCM or coding reviewer checks the current payer rule, contract, code source, modifier instruction, and claim edits.
Texas Medicaid provides one scoped example. Its July 2026 manual states that it will not reimburse multiple ABA providers during one ABA session with a child or youth, with a stated exception when the family and child receive separate services and the child is absent from the family session. That rule belongs to Texas Medicaid's named program and dates. See the current Texas Medicaid Provider Procedures Manual landing page and Children's Services Handbook.
Corrected and voided claims
Treat the original claim, replacements, reversals, and voids as one claim family. Store the current active state and retain every transaction. CMS uses a similar claim-family concept in its March 2026 T-MSIS instructions for void, reversal, and cancel records. That document governs state Medicaid data reporting. This article adapts the relationship concept as an internal control.
Never add all raw transaction quantities to calculate utilization. Some systems represent a void as a flag, a negative amount, a zeroed record, or a linked cancellation. Determine the payer's transaction semantics. Use the final supported rendered event for care utilization and the latest active claim-family state for submitted-claim reconciliation.
Example: an original claim reported eight units, but the signed evidence supports six. RCM follows the payer's correction route and links the replacement or void to the original. The rendered ledger shows one six-unit event after clinical documentation review. The claim-family total also resolves to six active units. It never becomes fourteen from adding the original and replacement.
Trigger reauthorization from dependencies
A reauthorization alert should open a case with tasks. A date banner alone gives no assurance that the packet will be ready.
Track these trigger classes:
- Time and quantity: days to the end date, submission window, forecasted balance, and the first line likely to reach its limit
- Clinical: reassessment, progress, barriers, treatment integrity, transition planning, and the BCBA's next-period recommendation
- Administrative: eligibility, referral, form version, enrollment, signatures, outcome measures, and attachments
- Decision and schedule: submission reference, response or information deadline, decision status, appeal route, and appointments crossing the end date
TRICARE's July 2026 Autism Care Demonstration manual gives a program-specific timing example: the provider submits a continuation request 60 to 30 days before a six-month period ends. Apply that window only to the TRICARE ACD case it governs and verify current regional instructions. See the TRICARE ACD manual, Change 161.
For payers covered by CMS's current interoperability rule, a prior-authorization response can approve with a duration, deny with a reason, or request more information. The CMS Prior Authorization API FAQ also describes decision timeframes for specified impacted payers. Those federal provisions do not set a universal ABA reauthorization window, and they do not cover every commercial plan.
Reconcile payer counters without outsourcing the ledger
Portal balances are evidence to reconcile. A payer may count accepted claims, adjudicated claims, or a program allocation that differs from one authorization line. Record the portal label, retrieval time, data-through date, and scope before comparison.
Texas Medicaid offers another scoped control. Its current prior-authorization chapter says that claims for services requiring authorization must carry specified details from the authorization letter, including authorization number, provider identifier, procedure code, dates, required modifiers, and units as applicable. Its claims chapter says prior authorization is a condition for reimbursement for specified services and does not guarantee payment. Review the Texas prior-authorization chapter and Texas claims-filing chapter for the current program rules.
Worked synthetic ledger review
This fictional example contains no patient information and represents no payer policy or care recommendation.
Authorization: Fictional Harbor Plan approves 720 units of Service A for 84 days. For this example only, one unit is 15 minutes. The line is limited to a named provider type and clinic setting. The BCBA's signed plan supplies the clinical schedule.
As-of record: At the end of day 42, 300 eligible units were scheduled and 255 occurred with signed evidence. The client began on day 11 after a staff vacancy. The next 42 days contain 360 scheduled units. The comparable delivery window uses all 300 scheduled units to date, with no excluded anomaly.
| Calculation | Result | Meaning |
|---|---|---|
| Remaining approved units | 720 - 255 = 465 | Maximum authorization balance for this line before other conditions |
| Quantity utilization | 255 ÷ 720 = 35.4% | Rendered share of approved quantity |
| Period elapsed | 42 ÷ 84 = 50.0% | Calendar share completed under the stated convention |
| Late-start exposure | 10 ÷ 84 = 11.9% | Period share before the first feasible service date |
| Delivery rate | 255 ÷ 300 = 85.0% | Rendered share of scheduled eligible units to date |
| Scheduled overrun exposure | 255 + 360 - 720 = -105 | Current future calendar remains 105 units below the approval ceiling |
| Base forecast | 255 + (360 × 85.0%) = 561 | Operational projection if the comparable delivery rate continued |
The 561-unit forecast is an alert. Scheduling reviews the vacancy and future coverage. The family can describe availability and preferences. The BCBA decides whether the plan remains appropriate. The prior-auth lead checks amendment and reauthorization rules. Nobody adds dense replacement sessions merely to consume the 159-unit difference.
Later, RCM finds one eight-unit claim whose signed evidence supports six. The payer-specific correction creates a linked claim-family transaction. After review, rendered utilization decreases by two once, and the active claim-family state becomes six. The ledger records the reason, approvers, timestamps, and downstream recalculation.
Run alerts through named owners
| Alert | Default severity | Owner and expected output |
|---|---|---|
| Appointment outside effective dates | Stop before routine service | Authorization owner documents current approval or escalation |
| Wrong service, provider, or setting dimension | Stop before routine service | RCM or prior-auth owner resolves configuration; BCBA reviews care impact |
| Rendered plus scheduled units exceed remaining approval | Urgent review | Scheduler, prior-auth lead, and BCBA produce a dated plan |
| Reauthorization dependency late | Urgent review | Task owner completes or escalates the missing item |
| Forecast below current clinical plan | Cause review | BCBA and relevant access owner document the clinical and operational response |
| Duplicate, overlap, or claim-family ambiguity | Billing hold | RCM resolves source events and payer rules before release |
| Portal and internal balance disagree | Data exception | Authorization and RCM owners reconcile scope, data-through date, and transactions |
| Coverage or eligibility changed | Immediate case review | Eligibility, authorization, scheduling, and clinical owners assess affected dates |
An override needs a named approver, source, reason, affected dates, expiration, and follow-up. Keep sensitive-data access role-based.
Measure the system with auditable denominators
Use measures that expose record quality and continuity risk:
Authorization transcription accuracy = sampled authorization lines matching the source on every material field ÷ authorization lines sampledPre-service match rate = audited appointments passing all applicable authorization dimensions before service ÷ appointments auditedOn-time reauthorization readiness = cases packet-ready by the payer-specific internal target ÷ continuation cases dueAuthorization-gap exposure = scheduled service days blocked by an authorization gap ÷ all clinically planned service days in the measurement periodClaim-family resolution age = calendar days from correction detection to verified active claim-family state, reported by median and aging bandsUnit reconciliation variance = absolute difference between net eligible rendered units and active submitted units ÷ net eligible rendered units, with zero-rendered cases reported separatelyAlert recurrence rate = cases repeating a confirmed cause within 90 days ÷ cases reviewed for that cause
Publish the as-of date, inclusion rules, exclusions, source systems, and owner with each metric. Split results by payer, product, service line, location, and reason only when sample size and privacy permit. A low authorization-gap rate says little about clinical quality, family experience, or treatment outcomes.
ABA authorization unit tracking checklist
- [ ] Every authorization line preserves the original notice and later versions.
- [ ] Member, product, service, unit basis, dates, provider, setting, limits, and conditions are structured fields.
- [ ] Clinical recommendation, approval, schedule, rendered event, charge, claim, remittance, and correction remain separate records.
- [ ] Unit conversions and rounding rules cite the current controlling source.
- [ ] Pre-service checks use the appointment date and the current authorization version.
- [ ] Rendered units come from supported service evidence and retain revision history.
- [ ] Original, replacement, reversal, and void transactions link inside one claim family.
- [ ] Concurrency and overlap questions route to the BCBA and a qualified payer or coding reviewer.
- [ ] Utilization formulas show the numerator, denominator, dimensions, and as-of time.
- [ ] Underuse, overuse, late start, and data error have different alert routes.
- [ ] Forecasts trigger review and never set care intensity automatically.
- [ ] Reauthorization cases open from payer-specific dependencies before the current period ends.
- [ ] Portal balances are reconciled with internal rendered and claim records.
- [ ] Every override, correction, and escalation has an owner, evidence, deadline, and outcome.
- [ ] Monthly metrics examine continuity, data integrity, authorization readiness, and billing risk together.
Use this checklist when designing or auditing ABA authorization unit tracking. It preserves the BCBA's clinical role while giving operators a defensible view of authorization exposure and handoffs.
Related resources
- Parent topic: ABA Operations, Scheduling and Facilities
- ABA Scheduling: Matching Clinical Needs, Staff and Authorized Hours
- Opening an ABA Center: Facility and Operations Checklist
- ABA Prior Authorization: A Guide for Practice Owners and Operators
- Common ABA Authorization Denial Reasons and How to Reduce Preventable Risk
Sources
- U.S. Small Business Administration business guide
- CMS Prior Authorization API frequently asked questions
- ABA Coding Coalition
- HHS Office of Inspector General compliance resources
- BACB Ethics Code for Behavior Analysts, updated August 2024
- CMS overview of coding and classification systems
- CMS health-care payment and remittance advice
- CMS T-MSIS instructions for void, reversal, and cancel records, updated March 2026
- Texas Medicaid Provider Procedures Manual, updated June 30, 2026
- Texas Medicaid prior-authorization chapter
- Texas Medicaid claims-filing chapter
- Texas Medicaid Children's Services Handbook
- TRICARE Autism Care Demonstration manual, Change 161, July 2026
