What to Do When an ABA Claim Is Denied After Services

Confirm the denial artifact

Ask for the EOB, formal denial, claim number, service lines, dates, provider, billed and allowed amounts, reason and remark codes, patient responsibility, and appeal instructions. CMS explains that an EOB is not a bill and shows claim and cost information. A clearinghouse rejection, payer front-end rejection, pending request for information, adjudicated denial, and provider statement are different artifacts. Use the payer's current state before choosing a remedy.

Compare the denial with the actual service

Check schedule, actual visit date and time, service type, setting, provider, authorization, clinical record, cancellation, and family payment. A clinician handles any permitted clinical correction under the provider's policy while preserving history. Billing staff select claim corrections from verified source evidence. Families can identify factual discrepancies without changing clinical content. For covered behavior analysts, the BACB Ethics Code addresses documentation and accuracy.

Separate provider correction from member appeal

Wrong member data, duplicate claim, missing reference, transmission problem, or another billing defect may use the provider's correction route. A coverage, medical-necessity, benefit-limit, network, or authorization decision may use reconsideration, grievance, or appeal under the plan. Some issues involve both. Ask the provider and plan to name the route, owner, deadline, and required evidence. Avoid filing a broad appeal before learning whether the payer has a valid adjudicated claim to review.

Read the plan-specific denial basis

HealthCare.gov defines an appeal as review of a decision denying benefit or payment. Obtain the exact plan provision, policy, guideline, authorization record, and clinical rationale cited. Ask for codes and meanings. For an ERISA-covered plan, DOL's benefit-claim guide describes denial-notice content, relevant documents, and appeal procedures. It does not set the route for every plan type, so use the actual notice and governing source.

Protect deadlines and continuity

Record the denial date, date received, appeal or correction deadline, next service date, authorization end, provider billing deadline, and any collections notice. Ask which action preserves the family's rights. A provider promise to handle it may not extend a member deadline. Discuss clinical continuity and risks with the qualified team, while the family considers cost and alternate routes. An urgent health or safety concern follows the applicable clinical or emergency pathway rather than an ordinary claims queue.

A fictional denied claim

Tessa receives an EOB denying four visits. The provider finds that one claim carried the wrong location and sends a corrected claim; three visits share a coverage rationale that the family may appeal. The family reports 1 of 4 lines in provider correction and 3 of 4 in member decision review. It does not combine the two routes into one denial rate. The balance remains disputed in the provider ledger until the corrected claim and appeal reach final decisions.

Reconcile the family balance

Ask the provider to identify undisputed and disputed amounts, family payments already received, credits, contractual adjustments, and collection status. Compare the later EOB with the revised statement. Do not assume the EOB's patient-responsibility field reflects a payment the family already made. Request a hold or review under provider policy where appropriate, but obtain the terms in writing. Keep paying or arranging undisputed amounts according to the agreement while preserving the contested portion and deadlines.

Close every downstream state

Track provider correction submitted, payer acknowledgment, new adjudication, appeal submitted, decision, payment, adjustment, refund, family statement, and collections update. Record reference numbers and dates. A paid claim can still leave a wrong family credit; a zero family balance can hide an unresolved clinical-record error. Compare the final result with actual services and the requested remedy. Escalate a missed deadline, contradictory notice, or unresolved harm through the plan, provider, benefits office, regulator, or qualified legal route that applies.

Send a focused first request

Ask: Which claim and lines were denied? Is this a rejection, information request, or adjudicated denial? What exact reason and source apply? What provider correction is possible? What member action and deadline apply? What happens to the current family balance? Who owns each next step? When will we receive written confirmation? This request produces the minimum record needed to choose a route without circulating the person's full clinical history unnecessarily.

Follow the denied claim from service evidence to final ledger

Create a denied-claim correction and appeal register for the exact service line. Record service date, provider, site, code and units, authorization, clinical documentation reference, original claim, acknowledgment, adjudication, EOB, denial code and explanation, provider ledger, and family balance. Identify which receiver issued each artifact. A clearinghouse rejection, payer front-end rejection, and adjudicated denial require different responses.

Compare the claim with source evidence before choosing a route. Confirm that the service occurred, the record supports the submitted facts, the provider and site were eligible for the route, the authorization matches, and the claim used the correct member and product. A qualified clinician makes any permitted record correction under documentation policy. A qualified billing reviewer decides whether the next action is a corrected claim, replacement, reconsideration, provider appeal, member appeal, refund review, or another payer-specific path.

Track the route, deadline, submission proof, receipt, completeness, new decision, corrected EOB, payment, adjustment, and provider ledger. Ask the provider to document whether collection of the disputed amount is paused. Preserve the original claim and denial rather than replacing them with only the latest state.

Use a release gate and a written fallback

Release a correction or appeal only when the denial layer and reason are defined, the source evidence is intact, the responsible author has approved any change, the route and deadline are confirmed, and the requested remedy is explicit. If the family may appeal, verify who is authorized to act and which records are needed. Keep provider correction work separate from member clinical or benefit arguments.

If the deadline is near, the claim file is incomplete, or the payer introduces a new rationale, protect the available route with a timely, accurate submission and document any request to supplement the record. Give the family the disputed amount, collection status, and financial exposure in writing. Do not ask the family to pay a balance solely to make an operational problem disappear.

Verify one complete real-world cycle

Follow the corrected claim or appeal through the final EOB and provider ledger. Reconcile plan payment, contractual adjustment, patient responsibility, family payments, credits, refunds, and remaining balance. A favorable appeal that never changes the claim or statement is not closed. If the denial remains, preserve the written rationale and next-review deadline so the family can decide whether to continue, escalate, or close the matter.

Choose the response from the denial layer and evidence

Start with a decision table. If a claim never passed local validation, the provider corrects its own work before transmission. If a clearinghouse or payer front end rejected the transaction, follow the artifact's route and confirm whether a replacement or new submission is required. If the payer adjudicated the claim and denied coverage or payment, use the plan's correction, reconsideration, provider-dispute, or member-appeal process as applicable. If the service record itself is incomplete or inaccurate, a qualified clinician reviews any permitted late entry or correction under policy while preserving the original history.

For each route, state the desired outcome. Examples include accepting the original claim, processing a corrected claim, applying an authorization, recognizing the correct provider or site, overturning a benefit denial, removing family responsibility, or issuing a corrected EOB. Match each reason to one piece of responsive evidence. Avoid resubmitting the same unchanged claim when the payer has already adjudicated it, because the duplicate can create another denial without addressing the first one. Avoid changing clinical facts to satisfy a claim edit.

Give the family a financial-status summary while work proceeds. It should show the denied amount, provider collection status, amount the family agrees is supported, appeal or correction deadline, and next update date. If the provider requests payment, ask how the amount will be held, credited, or refunded if the claim changes. After the response is filed, monitor receipt and final disposition rather than counting submission as resolution. The complete file should show why the route was chosen and how the result reached the family balance.

Prevent the same denial from reaching the next claim

After resolving the claim, identify the source rule and workflow version that produced the problem. If the location was wrong, inspect how scheduling supplies location to billing. If authorization data failed, inspect how approved dates and units reach claim release. If provider eligibility was wrong, inspect the configuration and effective-date gate. If the denial concerned coverage or medical necessity, preserve the plan decision and any appeal result without turning it into an automatic rule for another member or product.

Test the correction on the next eligible claim and record the outcome. Measure repeated errors among claims exposed to the same rule and workflow version, not across unrelated claims. Keep pre-adjudication rejections separate from adjudicated denials. A clean next claim supports the operational fix, while one success does not prove that every payer and configuration is correct. Assign a recheck date when a contract, policy, authorization, or system version changes.