Revenue cycle management

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

RCM follows evidence from referral through final disposition

The CMS Administrative Simplification program administers requirements for the format and content of electronic administrative transactions such as claims and payments. An ABA practice still needs a local operating record that connects each transaction to the person, service, provider, clinical record, payer rule, and financial result.

The CMS electronic billing page is scoped to Medicare fee-for-service contractors. It explains that a clearinghouse or billing service may sit between provider and payer. That intermediary adds a transmission layer; the payer's product and claim rules remain separately traceable.

Common revenue-cycle states answer different questions

• Eligibility reports a person's enrollment status for a payer or plan at a stated time.
• Benefits describe plan terms, exclusions, cost sharing, and conditions reported by the source.
• Prior authorization records a prospective payer decision for defined services and parameters. The clinician retains the clinical recommendation, and payment remains downstream.
• Charge ready means the practice's clinical, authorization, provider, coding, and documentation gates for claim creation have cleared.
• Submitted means a transaction left the practice through a named route.
• Accepted for adjudication means the claim passed the identified intake layer. Coverage and payment remain unresolved.
• Clean claim has a source-specific meaning under the applicable law, contract, or payer definition.
• Adjudicated means the payer applied its rules and issued an outcome.
• Remitted means the payer supplied claim and adjustment information. Money movement has its own evidence.
• Reconciled means the remittance, deposit, claim ledger, adjustment, and remaining balance agree.

CMS's electronic health care claims page illustrates separate batch, claim-level, coverage, and payment-policy edits in Medicare. Use the payer's actual reports and definitions instead of extending that sequence to every route.

Each role owns a different part of the record

The clinician documents the actual service and makes permitted clinical corrections while preserving authorship and history. A qualified coding or billing reviewer selects the claim fields from verified evidence. Operations confirms payer, authorization, provider, scheduling, and setting gates. Finance matches remittance, funds, ledger entries, patient balances, refunds, and recoupments. Compliance monitors trends, audits controls, and routes possible overpayments or inaccurate claims under applicable requirements.

Software can surface missing fields, conflicting dates, expired rules, unresolved acknowledgments, and aging work. It should preserve the source record and each human decision. Clinical content, units, and service facts stay with the appropriately qualified owner.

The HHS OIG General Compliance Program Guidance is voluntary and nonbinding. It describes general compliance risks and infrastructure rather than an ABA payer rule. A practice can use that framework alongside controlling law, payer contracts, professional duties, and a documented response process.

Remittance and payment need separate reconciliation

The CMS ERA and EFT page defines an electronic remittance advice as the payer's explanation of claim payment and adjustments. An electronic funds transfer orders funds to a provider's financial institution. Matching the transaction reference supports reassociation of the ERA and EFT.

One deposit may cover many claims, and an ERA may report several claims or lines. Reconcile at the needed levels: payer, deposit, remittance, claim, service line, adjustment, responsibility, and ledger posting. Keep denials, zero-pay outcomes, takebacks, refunds, interest, and patient balances in their own states.

For unresolved payer status, the CMS claim-status page describes the adopted 276 inquiry and 277 response. A claim-status response supplies evidence for follow-up; it carries no automatic instruction to duplicate, replace, appeal, or write off the claim.

A fictional cohort shows where denominators change

A fictional ABA practice follows 20 planned visits whose reporting window has closed. Eighteen occur and two are cancelled. Of the 18 delivered visits, 17 have completed records by the internal target: 17/18, or 94.4%. The cancellations sit outside the documentation denominator.

Fifteen of the 17 documented visits clear charge review: 15/17, or 88.2%. Two stay held for an authorization conflict and a rendering-provider mismatch. The payer accepts 14 of the 15 released claims for adjudication: 14/15, or 93.3%. One pre-adjudication rejection remains open with an owner and due date.

At the defined payer-specific maturity cutoff, 12 of those 14 accepted claims have adjudicated. Nine show payable outcomes and three are denied. First-adjudication payable yield is 9/12, or 75%; denial rate is 3/12, or 25%. Two pending claims remain visible outside the mature denominator. Eight of the nine payable outcomes match deposits, so deposit reconciliation is 8/9, or 88.9%. These fictional rates describe this cohort and set no benchmark.

Useful RCM measures preserve stage and maturity

Track completed records divided by delivered services due for documentation; charge-ready services divided by documented services reviewed; payer-intake acceptance divided by released claims; mature first-pass adjudication yield; denial rate by reason; remittance-to-deposit match; unresolved work by age; days from service to claim release; and open accounts receivable by payer-defined stage.

Define the cohort, event, numerator, eligible denominator, clock, maturity window, exclusions, source version, workflow version, and owner. Report counts with percentages. Segment by payer, product, service, provider, location, authorization, claim route, denial family, correction type, and appeal outcome while protecting privacy and avoiding tiny identifiable groups.