Payer-specific Clean-claim Status

A claim submitted successfully is not necessarily a clean claim. Applied Behavior Analysis (ABA) providers must verify payer requirements, authorization records, provider information, supporting documentation, and electronic claim acknowledgments before classifying a claim as clean.

For ABA practice owners and billing managers, accurate clean-claim reporting helps identify submission errors, monitor reimbursement delays, and improve revenue cycle performance. This guide explains how to distinguish 999 and 277CA responses, validate payer-specific requirements, and maintain reliable claim reporting.

What Is a Clean Claim in ABA Billing?

A clean claim is a healthcare claim that meets the applicable processing requirements without requiring additional information from the provider or another party. However, its definition depends on the payer, insurance program, provider contract, and applicable regulations.

Under 42 CFR §447.45(b), Medicaid defines a clean claim as one that can be processed without obtaining additional information from the provider or a third party. The definition includes claims with errors originating in the state’s claims system but excludes claims from providers under investigation for fraud or abuse and claims under medical-necessity review.

Commercial insurance contracts and Medicare may apply different definitions and processing requirements. Therefore, ABA billing teams should verify the controlling payer’s rules before calculating clean-claim performance.

Clean Claim Does Not Mean Paid Claim

A claim can pass electronic formatting checks and enter the payer’s adjudication system without being paid.

For example, an ABA claim may receive an acceptance acknowledgment but later encounter an authorization discrepancy, documentation request, coverage issue, or coding denial.

For accurate reporting, distinguish between:

Electronic transmission acceptance.
Payer receipt and claim acknowledgment.
Clean-claim classification.
Final adjudication.
Payment or denial.

Understanding 999, 277CA, 277, and 835 Transactions

Electronic claim transactions help billing teams identify where a claim stands in the revenue cycle. Each response confirms a different processing stage.

Transaction	Purpose	What it confirms
999	Functional acknowledgment	Electronic transaction syntax and implementation-guide validation
277CA	Claim acknowledgment	Claim-level receipt, acceptance, or rejection
276/277	Claim status inquiry and response	Status information about a previously submitted claim
835	Electronic remittance advice	Adjudication, payment, adjustments, and patient responsibility

1. 999 Functional Acknowledgment

The 999 acknowledgment confirms whether an electronic claim transaction passed applicable syntax and implementation-guide validation.

An accepted 999 does not independently prove that the payer received the claim on that date or accepted it for adjudication. X12 explains that the actual payer receipt date may be established through a business acknowledgment such as the 277CA.

2. 277CA Health Care Claim Acknowledgment

The 277CA provides claim-level information about whether claims were received, accepted into adjudication, or rejected.

Common acknowledgment category codes include:

Code	Meaning
A1	Claim received; not necessarily accepted for adjudication
A2	Claim accepted into the adjudication system
A3	Claim returned as unprocessable
A6	Rejected because of missing information
A7	Rejected because of invalid information

An A2 response indicates acceptance into adjudication, not guaranteed payment or universal clean-claim status. The claim must still satisfy the controlling payer’s clean-claim definition and any additional applicable requirements.

3. 276/277 Claim Status Inquiry and Response

The 276 transaction allows a provider to request information about a previously submitted claim. The payer responds through the 277 Health Care Claim Status Response.

ABA billing teams use this process to investigate pending claims, payment delays, denials, and requests for additional information.

Do not confuse the 277 response with the 277CA acknowledgment.

4. 835 Electronic Remittance Advice

The 835 provides payment and adjudication information after a claim has been processed.

Review the following information:

Paid and allowed amounts.
Contractual adjustments.
Patient responsibility.
Claim and service-line denial reasons.
Outstanding balances.

Claim Adjustment Reason Codes (CARCs) explain why a claim or service line was paid differently from the billed amount. Remittance Advice Remark Codes (RARCs) provide additional information about the adjustment.

For help comparing authorized, delivered, billed, and paid therapy units, read our guide to ABA payment reconciliation.

How to Validate Payer-Specific Clean-Claim Status for ABA Services

Before classifying a claim, identify the applicable payer definition and verify that the supporting claim information meets its requirements.

Step 1: Identify the Controlling Payer and Insurance Rules

Confirm the specific insurance arrangement:

Commercial, self-funded, or Medicaid plan.
Applicable provider contract.
Professional or institutional claim type.
Electronic submission route.
Date of service and payer receipt date.
Applicable clean-claim and prompt-payment definitions.

State insurance regulations do not necessarily apply to every employer-sponsored plan. Fully insured plans are generally subject to applicable state insurance regulation, while self-funded ERISA plans are generally exempt from state regulation of the plan itself.

Step 2: Verify Eligibility and ABA Benefits

Confirm active insurance coverage and applicable ABA benefits on the service date.

Check the member ID, effective dates, network participation, deductibles, cost-sharing, authorization requirements, and service limitations.

Retain the verification record and payer reference number. Eligibility verification supports claim validation but does not guarantee payment.

Step 3: Match Prior Authorization With Billed Services

Verify that the authorization matches the claim’s:

Authorization number.
Approved CPT codes.
Service dates.
Authorized and remaining units.
Rendering-provider requirements.
Approved service location.

For example, a claim for CPT 97153 may encounter problems when the payer’s authorization record does not include the corresponding service or sufficient remaining units.

Resolve discrepancies before assuming the claim qualifies as clean.

Step 4: Validate CPT Codes, Modifiers, and Units

Confirm that reported CPT codes, diagnoses, modifiers, and units match the actual documented service and payer requirements.

Review:

Correct procedure code selection.
Documented time and reported units.
Individual or group service reporting.
Rendering-provider information.
Required modifiers.
Diagnosis and place-of-service details.
Applicable payer claim edits.

The 2027 adaptive behavior CPT updates also require billing teams to review revised descriptors and coding instructions. See our guide to ABA insurance changes in 2027 before updating billing workflows.

Medically Unlikely Edits (MUEs) and National Correct Coding Initiative (NCCI) edits should be reviewed when applicable. They should not be treated as universal ABA billing limits across every commercial and Medicaid plan.

Step 5: Verify Provider and Rendering NPI Information

Check the billing and rendering NPIs, taxonomy, enrollment status, effective dates, and any required supervising-provider information.

ABA agencies should pay particular attention to payer-specific requirements involving BCBAs, BCaBAs, and RBTs.

An active organizational enrollment does not automatically establish that every individual provider is eligible to render services under the payer contract.

Step 6: Review Session Notes and Supporting Documentation

Before submission, verify that clinical and administrative records support:

Patient identity and date of service.
Service delivered and treatment-plan alignment.
Start and end times where required.
Billed CPT codes and units.
Rendering-provider identification.
Required signatures.
Applicable supervision and clinical analysis documentation.

Billing staff should identify missing information rather than alter clinical records to make claims appear complete.

Medicare Claim Status: A Useful Example of Separate Processing Stages

CMS’s March 2026 Medicare Learning Network guidance explains that Original Medicare claims pass through two levels of electronic edits.

First, the Medicare Administrative Contractor (MAC) performs front-end file checks and issues a 999 acknowledgment. Next, claims undergo additional validation, with individual claim-level rejection information reported through the 277CA.

Once claims pass these stages, the MAC assigns a tracking identifier:

Document Control Number (DCN) for Medicare Part A and Home Health and Hospice claims.
Internal Control Number (ICN) for Medicare Part B claims.

CMS states that the two editing stages can take up to three days. Providers should avoid unnecessary resubmission while claims are being processed because duplicate submissions may result.

This is a Medicare-specific workflow. Do not automatically apply it to commercial or Medicaid payers.

Reference: CMS Checking Medicare Claim Status, March 2026.

Medicaid Clean-Claim Definitions and Prompt-Payment Requirements

Medicaid has a specific federal clean-claim definition under 42 CFR §447.45(b).

For eligible practitioner claims, Medicaid agencies generally must pay:

Requirement	Federal timeframe
90% of clean claims	Within 30 days of receipt
99% of clean claims	Within 90 days of receipt

The requirements apply to the specified practitioner claims, including practitioners in individual or group practice and shared health facilities.

Under 42 CFR §447.46, Medicaid managed care organization contracts must also provide for these applicable clean-claim payment standards. However, an MCO and its provider may mutually agree to an alternative payment schedule, provided it is stipulated in their contract.

This means ABA billing teams should examine the controlling Medicaid program, provider contract, claim type, and applicable state requirements before applying a payment clock.

For commercial insurance, prompt-payment deadlines vary according to applicable state law, insurance arrangements, and provider contracts. Self-funded ERISA plans require particular care because state insurance prompt-payment rules generally do not regulate the plan itself.

Useful references:

How to Maintain an ABA Clean-Claim Evidence Register

A claim-level evidence register helps billing managers explain why a claim received a particular clean-claim classification.

Recommended fields include:

Field	Information to record
Payer and plan	Insurance company and product
Program	Commercial, Medicaid, or other applicable program
Contract	Relevant provider agreement or policy reference
Claim information	Claim ID, type, and submission version
Service date	Date the ABA service was delivered
Submission date	Date sent through the electronic route
999 response	Acceptance or rejection information
277CA response	Payer receipt and claim-level status
Payer control number	Assigned claim tracking identifier
Authorization	Approved codes, units, and dates
Documentation	Additional information requests or identified defects
Clean-claim rule	Source, effective date, and qualifying event
Classification	Clean, nonclean, rejected, or unknown
Follow-up	Responsible person, action, and due date
Adjudication	Final payment or denial information

Keep the source and effective date attached to each classification. When payer rules change, update affected claims without overwriting historical reporting records.

Claims with insufficient evidence should remain classified as unknown rather than automatically being counted as clean.

How to Calculate and Report ABA Clean-Claim Performance

A reliable clean-claim rate requires a defined reporting population, denominator, and qualifying event.

A clearinghouse acceptance rate is not equivalent to a payer clean-claim rate or a first-pass payment rate.

Consider this hypothetical example:

Claim classification	Number
Total claims submitted	100
Rejected before payer intake	10
Confirmed payer-received claims	90
Confirmed clean claims	68
Confirmed nonclean claims	14
Unknown classification	8

For an internal operational measure, the confirmed-clean share of payer-received claims is:

68 ÷ 90 × 100 = 75.6%

Classification completeness is:

(68 + 14) ÷ 90 × 100 = 91.1%

The pre-intake rejection rate is:

10 ÷ 100 × 100 = 10%

These are separate operational measures, not universal payer-required formulas. If the controlling contract or regulation specifies another calculation, follow that definition.

Keep rejected and unknown claims visible in reporting. Excluding unresolved claims without disclosure can make clean-claim performance appear artificially high.

Common Clean-Claim Problems and Corrective Actions

Problem	Recommended action
Accepted 999 treated as clean status	Verify payer-level acknowledgment
Missing 277CA response	Check clearinghouse and payer records
A1 mistaken for A2	Confirm the correct acknowledgment status
Authorization mismatch	Reconcile approved codes and units
Provider information error	Verify NPI, taxonomy, and enrollment
Documentation request	Track missing information and response dates
Duplicate resubmission	Check original claim status before resubmitting
Incorrect classification	Recheck the payer’s clean-claim definition

Handling Corrected and Void Claims

Do not automatically submit a corrected or voided claim when the original claim is still pending.

X12 RFI 2060 explains that replacement or withdrawal/void transactions after final adjudication use the original payer claim control number. When the original claim is still processing, payer procedures can differ.

Before making a correction, establish whether the original claim is pending, rejected, or finalized. Follow the payer’s replacement, adjustment, or void instructions and retain the related claim identifiers.

See X12 RFI 2060: Withdrawal/Void Claim and Response.

Audit and Data Security Considerations

Clean-claim reporting should be supported by consistent records and secure billing procedures.

ABA practices should preserve claim acknowledgments, payer responses, authorization information, and remittance records. Access to patient and payment information should be restricted according to job responsibilities, with appropriate HIPAA safeguards and business associate agreements.

Periodically review a sample of clean, nonclean, rejected, and unknown claims. An independent reviewer should be able to reproduce the classification using the retained evidence.

This helps identify reporting errors and unresolved claims before they affect financial decisions.

How Cloud RCM Solutions Supports ABA Clean-Claim Validation

CloudRCM Solutions provides medical billing and revenue cycle management services to help healthcare practices improve claim accuracy and financial visibility.

For ABA practices, our billing support can include:

Pre-submission claim validation and coding review.
Eligibility and authorization coordination.
Provider information and enrollment checks.
Clearinghouse rejection monitoring.
Payer acknowledgment and claim-status follow-up.
Denial identification and corrective action coordination.
ERA/EOB payment posting and reconciliation.
A/R monitoring and billing performance reporting.

Our approach focuses on connecting claim submission, payer responses, outstanding documentation, and payment records so practice owners can better understand where claims are getting delayed.

Conclusion

Validating payer-specific clean-claim status requires more than checking whether a claim was accepted by a clearinghouse. ABA practices must understand electronic acknowledgment stages, verify authorization and provider information, review supporting documentation, and apply the correct payer or program definition.

A structured evidence register and consistent reporting process help practice owners identify claim issues, monitor payment timelines, and make more reliable revenue cycle decisions.

Cloud RCM Solutions supports ABA practices with medical billing services, claim validation, payer follow-up, denial management, and payment reconciliation. Schedule an appointment to discuss your ABA clean-claim workflow and billing performance.

FAQ’s

Is a 999 acknowledgment proof that an ABA claim is clean?

No. An accepted 999 confirms that the electronic transaction passed applicable syntactic validation. It does not independently establish payer-level business acceptance, the actual payer receipt date, or clean-claim status.

Does a 277CA response mean the claim is clean?

Not automatically. A 277CA provides claim-level acknowledgment. For example, A2 means the claim was accepted into the adjudication system, while A1 indicates receipt without acceptance for adjudication. Neither code independently guarantees payment or universal clean-claim status.

What is the difference between a clean claim and an accepted claim?

An accepted claim has passed a defined processing or intake stage. A clean claim must satisfy the applicable payer or regulatory definition for processing without additional information. The exact qualifying event depends on the controlling rule.

What is the Medicaid clean-claim payment deadline?

Under 42 CFR §447.45, Medicaid agencies generally must pay 90% of eligible practitioner clean claims within 30 days and 99% within 90 days of receipt. Related MCO requirements are addressed in §447.46, which also permits mutually agreed alternative payment schedules stipulated in the contract.