How Camber Handles Denials

Most ABA billing denials are preventable. The majority trace back to configuration errors, modifier mismatches, and data gaps that can be caught before a claim ever reaches a payer. What separates billing partners is how much of that work happens upstream, and when denials do occur, how quickly they're identified and whether appeals are pursued systematically.

Camber's pre-submission workflow is built around catching errors before they become denials, through system-level validation, payer-specific configuration, and eligibility checks that run before any claim goes out. Across Camber's current portfolio, 95% of first-submission claims are paid without requiring correction or resubmission.

Pre-Submission Validation on Every Claim

Before any claim is submitted to a payer, Camber runs a pre-billing audit. This is part of the standard workflow. The checks include:

• Modifier accuracy: ABA modifier requirements vary by payer and by rendering provider credential. A single-character error (e.g., HM vs. HN on an H2019 claim, or the letter O vs. the number 0 in a modifier code) can generate systematic denials across hundreds of claims before anyone notices. Camber maintains payer-specific modifier rules in its system and validates them on every claim.
• Authorization matching: Claims are checked against active authorization records before submission. For payers with strict auth matching, Camber has built Intelligent Claim Rules (ICRs) that validate auth data before the claim leaves the system.
• Procedure code and unit review: Units are checked against authorization limits. Codes are validated against payer-specific fee schedules and coverage rules.

When a claim fails any of these checks, Camber surfaces it as a Task linked directly to the relevant entry in the EHR, with a description of what needs to be corrected. The claim does not go out until the issue is resolved.

Payer-Specific Configuration

Camber maintains a payer crosswalk for each active payer, a set of rules that maps the payer's specific modifier requirements, authorization rules, place-of-service logic, and submission pathways. When a clinic's EHR settings change, the crosswalk is updated to match.

Some examples of payer-specific configuration:

• CalOptima does not accept clearinghouse submission. Claims must go through CalOptima's portal, which requires OTP (one-time passcode) authentication per session. Camber manages this as a standard workflow. In 2025, Camber finalized claims across CalOptima and IEHP with $7.24M collected combined.
• IEHP requires that the rendering provider NPI on the claim match the exact provider named on the authorization. A mismatch denies, regardless of whether the provider is credentialed and contracted. Camber validates this match before submission.
• TRICARE TriWest applies strict authorization matching and does not accept portal-based corrections. Camber's auth-matching ICR was developed specifically from working through TRICARE denials. In 2025, Camber processed 168,000+ finalized TRICARE TriWest claims and collected $26.5M.

Same-Day Session Handling and Duplicate Prevention

A specific source of ABA billing denials is same-day, same-client sessions: an AM session in one setting and a PM session in another, or sessions with different rendering providers on the same date. Payers often flag these as duplicates on receipt.

Camber handles this at the claim generation level. By default, AM and PM service lines for the same client and date of service are combined into a single claim with distinct service lines, correct place-of-service per line, and the appropriate modifiers for each session. This eliminates the most common trigger for false duplicate denials: separate claim headers arriving for the same date of service.

When a specific payer requires separate claims because of its own rules around code combinations, supervision, or place of service, Camber applies the payer-specific logic automatically rather than using the default bundling behavior.

Beyond bundling, Camber enforces a duplicate check at submission: if more than one active claim exists for the same underlying sessions, submission halts and the duplicate is surfaced for review before anything reaches the payer. When a payer still returns a duplicate denial despite clean submission, Camber resolves it directly with the payer or corrects the submission accordingly.

Proactive Eligibility Checking

Camber runs eligibility checks for active patients. This catches coverage lapses before claims are submitted, preventing denials that would otherwise arrive weeks after service dates. When a patient's eligibility status changes, Camber flags it before the next claim is generated.

New Payer Onboarding

When a clinic adds a new payer relationship, Camber runs a structured onboarding process before any claims are submitted: crosswalk configuration, validation rule setup, test claim submission, and a monitoring window on the first two weeks of production claims. Credentialing verification is part of this process. Payers added without this step are the source of some of the most predictable denial patterns in ABA billing (zero-payment claims, credentialing failures, EDI routing errors).

Even with strong upstream controls, some denials will get through. Payers update rules without notice, credentialing statuses change, and edge cases in authorization records don't always surface until a claim comes back. When that happens, what matters is how quickly the issue is diagnosed and whether it gets routed to the right fix.

How Denials Are Handled

When a denial comes back, Camber's system reads it, categorizing every denial by its CARC (Claim Adjustment Reason Code) and RARC (Remittance Advice Remark Code), and takes action automatically. Most common denial types are resolved programmatically: the system identifies the root cause, applies the appropriate correction, and resubmits without anyone touching it. A human biller only steps in when the resolution requires something the system can't apply on its own, like documentation that needs to be retrieved from outside the EHR or a payer dispute that requires a call.

Common denial types Camber manages and how they're routed:

• CO-4 (modifier issue): Flagged for root cause analysis. If a modifier denial pattern is emerging from a specific payer, Camber investigates whether it's a payer rule change or a configuration error and updates the crosswalk automatically.
• CO-197 / CO-15 (auth absent / expired): Queued for authorization documentation retrieval or correction before resubmission.
• OA-18 / CO-18 (duplicate): Because Camber bundles same-day sessions at claim generation and enforces a duplicate check at submission, most duplicate denials that arrive are payer-side errors rather than actual double-submissions. Camber confirms against submission logs and resolves directly with the payer or corrects the submission accordingly.
• CO-29 (timely filing): Flagged separately and tracked by date of service to preserve the appeal window.
• CO-50 (medical necessity): Claims requiring supporting clinical documentation are tracked with payer-specific deadlines. If the documentation is in the EHR, Camber retrieves it. If it isn't, the clinic's account manager requests it.

Partial Payment Detection

One of the less visible denial categories is the partial payment. The payer sends something, and the claim closes. Without an explicit review step, the residual balance disappears into the AR without further action.

When a payer payment comes in below the expected contracted rate, Camber's system flags it and holds it in a dedicated partial payment triage queue. Camber recovers the revenue that would typically be marked as paid and disappear from view in a standard billing workflow.

AR Visibility

The full claim lifecycle is visible in Camber's platform in real time: claim phase, denial codes, outstanding AR, tasks assigned. Clinics have full visibility without having to manage it themselves.

When a denial comes back, Camber evaluates the specific basis for overturn: an incorrect denial reason, a payer processing error, a valid authorization that wasn't recognized, or medical necessity where the documentation supports what was billed. For denials where an appeal is the right path, Camber's team manages the full process: collecting documentation, drafting a cover letter that references the specific denial codes, and submitting through the payer's required channel.

The Appeal Process

Camber handles appeals without involving the clinic unless clinical documentation is missing from the EHR. When documentation is needed, the clinic's dedicated account manager reaches out. The standard workflow:

Timely Filing Appeals (CO-29)

Timely filing denials require early action. When CO-29 AR accumulates for months before it's worked, overturn rates collapse. Payers don't treat 12-month-old appeals as viable regardless of the merits. Camber tracks timely filing AR by date of service and works it within a window where payers actually process appeals, using standardized appeal templates applied consistently across accounts.

Recoupments

When a payer issues a recoupment notice attempting to recover previously paid claims, Camber reviews the basis for recoupment before processing it. Some recoupments are legitimate; others aren't. One documented example: Carelon issued a recoupment notice citing a supervision percentage threshold, with original payments dating back 12-20 months. Camber reviewed the claim history against applicable state recoupment rules and flagged the timing issue to the clinic before any funds were returned.

Recoupment notices are tracked in Camber's support system. The full recoupment history for any clinic is available on request.