Concurrent ABA Billing: A Decision Guide for Overlapping Services

Define the overlap before deciding whether it is billable

Concurrent billing ABA questions begin with time, people, and services. Calendar overlap alone can be a scheduling artifact. Matching claim dates can represent services hours apart. Rebuild each actual interval at minute-level precision when the governing source uses time.

Classify the event into one of these patterns:

Keep four concepts separate: two people being present, two clinical services occurring, two charge candidates existing, and two claim lines being payable. Evidence for one concept does not establish the others.

The ABA Coding Coalition frequently asked questions distinguish professional direction of a technician during a patient service from employment or credential supervision outside direct patient care. The resource also says payer policies vary. Clinical supervision duties therefore cannot be assumed to create a second billable service.

Use a seven-gate decision sequence

Apply the gates in order to every overlapping interval. A failed or unresolved gate prevents claim release until the approved owner resolves it.

Gate 1: What actually happened?

Collect source evidence from both services: client, date, actual start and stop, setting, rendering provider, credentials, participants, attendance, service activity, clinical purpose, interruptions, and signatures. Reconcile discrepancies among the schedule, electronic visit record, timecard, clinical data, note, and charge.

Split partially overlapping services into a timeline. For a 2:00 p.m. to 3:00 p.m. technician service and a 2:30 p.m. to 3:15 p.m. BCBA service, the shared interval is 30 minutes. The full 60 and 45 minutes are separate durations; only 30 minutes are concurrent.

Gate 2: Does each service independently fit its reporting definition?

Use the current licensed code source, payer manual, and contract. Identify the required provider type, patient or caregiver presence, face-to-face or indirect status, time basis, group size, clinical work, and documentation for each code.

The ABA Coding Coalition publishes code identifiers and directs users to licensed American Medical Association materials. This guide avoids proprietary descriptors. A practice should maintain versioned access to the governing code source and record which version was used.

Ask what each professional did during the shared minutes. A note that says only “supervision occurred” leaves the underlying service unresolved. The BCBA record should identify the clinically skilled work that supports the BCBA-reported service, when one is proposed. The technician record should show the work that supports the technician-reported service. Employment oversight belongs in the supervision record even when it produces no claim.

Gate 3: Is the combination permitted for this payer product and date?

Locate the exact code pair and scenario in the contract, provider manual, medical policy, state program rule, written payer instruction, and applicable claim edits. Record the source, section, version, effective date, and scope.

A concurrent billing ABA decision cannot come from the code pair alone. The payer product, participant pattern, provider roles, setting, authorization, and service date determine which rule applies.

Current public examples show material variation:

• The Texas Medicaid Provider Procedures Manual ABA section, in the version checked August 13, 2026, says Texas Medicaid does not reimburse multiple ABA providers during one session with a child or youth. It describes a limited exception for separate family and child services when the child is absent from the family session.
• A dated Oregon Health Authority notice from January 12, 2024 says Oregon Health Plan permits concurrent reporting of 97153 and 97155 when listed clinical, scope, targeted-supervision, time, and documentation conditions are met. Providers should confirm that the notice still governs the member's current delivery system and product.

These examples point in different directions for similar-looking services. Neither rule transfers to another state, Medicaid managed-care plan, commercial product, or service date.

Gate 4: Does the authorization cover both services as delivered?

Match the authorization to client, service, provider role, units, frequency, setting, effective dates, and any concurrency or supervision condition. Confirm whether concurrent services draw from separate service buckets or a shared cap. Preserve the approval notice and payer clarification.

The CMS Prior Authorization API FAQ addresses decisions and data exchange for specified impacted payers. It does not define concurrent ABA billing across all products. An authorization can permit a service category while a separate billing rule restricts the overlapping combination.

Gate 5: Are provider and claim fields accurate?

Verify the rendering professional for each service, billing entity, National Provider Identifier when applicable, provider taxonomy or role, payer-effective enrollment, place of service, telehealth field, and required modifier. Compare those fields with the authorization and documentation.

A modifier communicates a supported claim circumstance under a governing rule. It cannot manufacture a distinct service, coverage, authorization, medical necessity, or documentation. When an edit rejects a pair, research the edit and facts before adding or changing a modifier.

CMS's Medicare NCCI and Medicaid NCCI FAQ describe program-specific procedure-to-procedure and unit edits. The April 2026 CMS modifier booklet says NCCI-associated modifiers should not bypass an edit unless the proper criteria are met and the record supports their use. Confirm whether and how NCCI applies to the claim and obtain payer-specific direction for other edits.

Gate 6: Does the record explain the concurrency?

Each rendering provider should create the record required for that provider's service. The combined record should allow a reviewer to answer:

• Who was present for each interval?
• What did each provider do during the shared minutes?
• Which client or caregiver received each service?
• What distinct clinical purpose and treatment-plan connection did each service have?
• Why was simultaneous delivery clinically appropriate or necessary when the governing rule asks for that rationale?
• How did the providers coordinate without duplicating the same work?
• Which data, observations, protocol decisions, instruction, client response, and follow-up belong to each service?
• Which payer rule, authorization condition, code, units, provider, and modifier support each proposed line?

Matching prose across two notes weakens the evidence of distinct work. Each author should document their own observations and actions. References to the other service should agree on participants and time while preserving the separate clinical record.

Gate 7: Can a qualified reviewer release both lines?

Assign a result to every proposed line: release, hold for facts, hold for source, correct, do not bill, or escalate. Record the reviewer, rationale, source version, decision time, and linked evidence. A payer's earlier payment does not convert a weak line into a compliant one.

The BACB Ethics Code for Behavior Analysts requires covered behavior analysts to identify services accurately, include required information, and address discovered billing or reporting inaccuracies. The BACB ethics page advises readers to check for current code versions and applicable regulation.

Work common ABA overlap scenarios

Use the table to triage. The “likely route” is an operational starting point, followed by the exact current source review.

The Council of Autism Service Providers practice-guideline page is a clinical source for ABA service delivery. Payer reimbursement decisions still require the payer's own authority. Clinical appropriateness and payment permission are separate decisions, and both deserve qualified review.

Use interval math instead of daily totals

Daily unit totals can hide overlapping minutes. Store raw intervals and calculate intersection before unit conversion.

For intervals A = [A start, A end] and B = [B start, B end]:

overlap minutes = max(0, min(A end, B end) - max(A start, B start))

Hypothetical service A runs from 9:00 to 10:30, or 90 minutes. Service B runs from 9:45 to 10:15, or 30 minutes. Their overlap is min(10:30, 10:15) - max(9:00, 9:45) = 30 minutes. Review the 30-minute shared interval under the concurrency rule. Convert each supported duration to units only after applying the code and payer's time rule.

Track these measures with explicit denominators:

• Overlap alert rate: service pairs with actual intersecting minutes divided by pairs tested by the detection rule.
• Supported concurrency rate: reviewed overlap events where both lines pass every gate divided by resolved overlap events.
• Unresolved aging: open overlap events by age band divided by all open overlap events.
• Post-payment defect rate: paid overlapping lines with a confirmed defect divided by paid overlapping lines audited.
• Recurrence rate: new exposed events repeating a corrected root cause divided by new exposed events reviewed.

Exclude test records, voided appointments, scheduling placeholders, and events outside the detector's defined scope. Report each exclusion and avoid combining alerts with confirmed defects.

Trace a synthetic decision

Assume a hypothetical commercial product has a written rule allowing one specified technician and BCBA code pair during the same client interval when each provider performs a distinct covered service. The authorization includes both services and roles. A technician works with the client from 1:00 to 2:00. A BCBA joins from 1:30 to 2:00 to observe implementation, test a protocol change, direct implementation, and assess the client's response.

The practice confirms 30 shared minutes. Both rendering providers are eligible for the product and setting. The current licensed code source and archived payer rule support the proposed services. Authorization balances cover the calculated units. The technician note documents implementation and client response. The BCBA note documents the specific protocol analysis, change, direction, observation, and response. Claim fields match the two providers, services, units, place, and required modifier. A qualified reviewer can release both lines with the source snapshot and decision attached.

Now change one fact: the same service occurs for a product whose manual prohibits that pair during the same client interval. The clinical record stays accurate, and the practice follows the payer's billing rule. Staff should not shift timestamps, add a modifier, change participants, or rewrite the notes to make the claim pass. RCM holds the unsupported line, follows the approved disposition, and routes prospective scheduling and authorization changes to clinical and operations leaders.

Investigate denials without forcing a claim through

A concurrent-service denial can arise from a code-pair edit, unit edit, modifier, authorization, provider, participant, place-of-service, or documentation issue. Classify the payer response, retrieve the submitted claim, reconstruct the actual service, and compare it with the rule version in force on the date.

Use this order:

1. preserve the original claim, response, records, and configuration;
2. identify the exact payer product and edit or denial reason;
3. validate actual intervals, people, services, authorization, and documentation;
4. determine whether the original claim was accurate under the governing source;
5. choose the permitted corrected claim, appeal, void, refund, write-off, or escalation route; and
6. fix the source process and test new exposed claims for recurrence.

The HHS Office of Inspector General compliance resources and voluntary General Compliance Program Guidance support risk-based auditing, investigation, remediation, root-cause analysis, and monitoring. A repeated overlap pattern may require an expanded audit and counsel-directed action rather than isolated denial work.

Pre-bill concurrency checklist

• [ ] Actual intervals were reconstructed from service evidence.
• [ ] Client, caregiver, providers, participants, locations, and service activities are consistent across records.
• [ ] Each service independently fits the current licensed code and payer reporting rule.
• [ ] The exact payer product permits the combination for the service date.
• [ ] Authorization covers each service, role, setting, date, unit, and concurrency condition.
• [ ] Each rendering provider is properly credentialed, enrolled, licensed, supervised, and identified as required.
• [ ] NCCI or payer edits were checked in the correct program and current version.
• [ ] Every modifier has a governing reason and documentation support.
• [ ] Separate records show each provider's distinct clinical work and client or caregiver response.
• [ ] Units derive from supported raw intervals under the applicable time rule.
• [ ] The reviewer recorded release, hold, correct, do not bill, or escalate with evidence.
• [ ] Any changed decision preserves the original claim and documentation history.

Related resources

• ABA Billing, Coding and Revenue Integrity
• ABA Charge-Capture Audit Checklist: From Schedule to Signed Note
• ABA CPT Codes and Documentation: Aligning 97151, 97153, 97155 and 97156
• The New ABA Clinical Director's First 90 Days
• Treatment Integrity and IOA: What Each Measures and When You Need Both

Sources

• BACB ethics codes
• Council of Autism Service Providers practice guidelines
• CMS Prior Authorization API FAQ
• ABA Coding Coalition
• HHS Office of Inspector General compliance resources
• BACB Ethics Code for Behavior Analysts
• ABA Coding Coalition frequently asked questions
• CMS Medicare National Correct Coding Initiative
• CMS Medicaid NCCI FAQ
• CMS proper use of NCCI-associated modifiers
• Texas Medicaid Provider Procedures Manual ABA section
• Oregon Health Authority concurrent ABA billing notice
• HHS OIG General Compliance Program Guidance