ABA Revenue Cycle Management: From Eligibility to Payment

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

This guide helps U.S. ABA practice owners map the full cycle, define controls, and choose metrics. Payer contracts, products, state rules, coding instructions, and client facts vary. Qualified billing, coding, credentialing, clinical, compliance, accounting, and legal professionals should review decisions within their scope.

Run one record through the entire revenue cycle

A practice can divide work among employees, a billing company, and software while keeping one accountable operating record. The practice remains responsible for vendor oversight, clinical accuracy, contract interpretation, access controls, and final financial reporting.

Treat every release condition as a gate. An unresolved exception moves to a named queue with a next-action date. It never disappears into a free-text note.

Set credentialing and contract controls before scheduling

Build a payer master by legal entity, product, state, line of business, provider, group, location, and service setting. Attach the current contract, fee schedule or pricing method, billing manual, effective dates, filing limits, appeal routes, portal access, electronic data interchange setup, and payment enrollment. Version the record when a contract or policy changes.

An individual or organization National Provider Identifier (NPI) supplies an identifier. CMS states that NPI issuance does not validate licensure or credentialing. The current NPPES notice explains this distinction. Your scheduling gate therefore needs the applicable license, payer enrollment, network or participation status, group affiliation, service location, and written effective date in addition to the NPI.

Use an effective-date matrix to stop a provider from appearing available for a product or location before activation. The same matrix should drive claim edits. A credentialing spreadsheet that never reaches the scheduler and biller leaves the revenue cycle exposed.

Verify eligibility and benefits as dated evidence

At intake, before an authorization period, and again at a practice-defined interval near service, verify the member, exact product, coverage dates, ABA benefit, network status, deductible, copay or coinsurance, visit or unit limits, referral and prior authorization requirements, coordination of benefits, and the correct payer route. Save the response, source, timestamp, staff member, and reference number.

CMS describes the 270/271 transaction as the adopted electronic inquiry and response for eligibility and benefit information. Its operating rules can return financial information such as deductibles, copays, coinsurance, and service-type coverage. See the CMS eligibility and benefits overview. A portal response, call, or 271 is a dated input to the workflow. Reverify after a family reports a plan, employment, custody, address, or other coverage change.

Keep the original benefit evidence beside any staff interpretation. Give families careful estimates that identify assumptions and unresolved items. Final member responsibility usually comes from adjudication and the governing contract or program rules.

Connect authorization, scheduling, and units

Authorization and claim adjudication are separate decisions. CMS describes an impacted payer's prior authorization API response as an approval, denial with a reason, or request for information. A health care claim is a separate request for payment with accompanying information. Compare the CMS prior authorization FAQ with the CMS claim transaction definition. Plan-specific rules still govern each case.

Convert the written authorization into structured fields: payer, product, member, authorization number, provider, location, service, applicable modifiers, approved units or hours, frequency limits, start and end dates, and special conditions. A second person should verify the transcription.

At scheduling, compare each session with eligibility, credential effective dates, authorization dates, approved service, provider, location, and remaining units. Track approved, delivered, scheduled, reserved, voided, and remaining units separately. Delivered units come from completed clinical records; the schedule is a forecast. Require a documented reason and narrow permission for overrides.

Turn the signed record into an accurate charge

Clinical staff own the truth of what happened: date, time, location, participants, service, rendering professional, work performed, and required clinical content. The clinical leader owns documentation standards and corrections. Billing staff translate the completed encounter into claim data under the current payer contract and licensed code set.

A charge-release check should reconcile:

• client and payer identifiers;
• service date, start and end times, duration, and calculated units;
• rendering, supervising, billing, and referring provider fields when applicable;
• service location and place-of-service reporting;
• current authorization number, dates, services, and unit balance;
• diagnosis and service codes, modifiers, and other payer-required fields;
• signature, completion status, and any approved correction history.

The ABA Coding Coalition maintains current resources for adaptive behavior coding at ABACodes.org. Use authorized code publications, payer instructions, contracts, and qualified review. This page omits licensed Current Procedural Terminology descriptors and cannot determine the correct code for an encounter.

Measure charge lag from the service date to charge release. Segment delays by missing note, signature, authorization, credential, or billing data so the clinical and operational owners see the specific blockage.

Release clean claims and prove payer receipt

Define a clean claim internally as a claim that is complete, internally supported, and accepted through the practice's submission edits. Payer and legal definitions may differ. Passing the internal edit means the claim can move forward; payment still depends on adjudication.

Before submission, check member and payer routing, billing and rendering identities, provider and location effective dates, service date, claim type, codes, units, modifiers, place of service, authorization data, coordination of benefits, filing limit, duplicate history, and required attachments. Preserve the exact outbound claim and its source encounter.

HHS adopted the ASC X12N 837 Version 5010 for electronic professional, institutional, and dental claims. The same federal framework includes 270/271 eligibility, 276/277 claim status, and 835 payment or remittance transactions for covered entities conducting those transactions. The current CMS standards table lists each adopted transaction. Implementation specifications and payer companion guides remain the working sources for technical fields.

Reconcile three milestones for every submission: transmitted, accepted by the clearinghouse or gateway, and accepted by the payer for adjudication. A rejection at either acceptance layer belongs in a correction queue. Claims without a payer response need follow-up. For a Medicare-specific example, CMS explains that providers can send a 276 status inquiry and receive a 277 response; other plans may expose status through another supported route. See CMS claim status options. Verify the current method and timing for each payer.

Reconcile ERA, EOB, payments, and adjustments

Electronic remittance advice (ERA) reports how a plan adjudicated claims. Post at the service-line level when available: paid amount, allowed amount, contractual adjustment, payer-initiated adjustment, patient responsibility, denial reason, remark, and any interest or recoupment. Keep claim adjustment reason codes and remittance advice remark codes in the structured record.

CMS explains that an ERA describes claim-payment adjustments and that the trace information in the electronic funds transfer (EFT) should match the associated ERA for reassociation. Read the CMS payment, remittance, and EFT guidance. Reconcile the bank deposit to the EFT, the EFT to the ERA, the ERA to the claim lines, and the claim lines to the ledger. Route any unmatched cash, missing remittance, zero-payment claim, credit, or reversal to an exception queue.

When the payer supplies an explanation of benefits (EOB), use it to help trace a family's question to the same adjudication. Reconcile any difference with the provider remittance and payer before changing the ledger or family balance.

Secondary claims should use the primary adjudication and current coordination-of-benefits rules. Keep contractual adjustments, payer denials, patient responsibility, bad debt, charity, refunds, and administrative write-offs in distinct categories with approval rules.

Work denials, A/R, and underpayments by cause

Open denial and accounts receivable (A/R) work from the payer's source response. Preserve the remittance, portal notice, claim history, amount, dates, deadline, and correspondence. Separate clearinghouse rejection, adjudicated denial, information request, partial payment, underpayment, recoupment, and missing response because each needs a different action.

Assign queues by confirmed cause: eligibility or coordination of benefits, credentialing, authorization, documentation, coding or claim data, filing, contract pricing, payer processing, posting, or compliance. Each item needs an accountable owner, next action, external deadline, internal due date, amount at risk, evidence, and disposition. Use the payer's current corrected-claim, reconsideration, appeal, payment-dispute, or record-response route.

For underpayments, calculate the expected allowed amount from the versioned contract and the claim's actual provider, location, service, date, and configuration. Compare that amount with the payer-adjudicated allowed amount, then account for payer payment and valid patient responsibility. Billed charge alone is a weak benchmark. Escalate uncertain contract interpretations and material patterns to the contracting, RCM, and finance owners.

Age A/R by claim status and next action, not days alone. A 45-day claim with no payer acceptance is a different problem from a 45-day appeal awaiting a documented decision.

Communicate and collect patient responsibility carefully

Use benefit information for a pre-service estimate, then update the family account from the payer's adjudication, contract, applicable law, and financial policy. Show the dates of service, payer activity, adjustments, payments, credits, and balance in language the family can follow. Pause collection when responsibility is disputed or another payer may be liable, according to policy and governing rules.

For people in the United States who are uninsured or choose not to use insurance, federal good faith estimate rules may apply. CMS says providers usually must give an estimate when care is scheduled at least three business days ahead or when the person asks, subject to the rule's scope and exceptions. CMS's current consumer guidance describes these conditions. Have counsel confirm federal and state notice, estimate, collection, refund, and balance-billing requirements for the practice.

Reconcile family payments to open balances. Review credits promptly, document refund decisions, and separate payment plans from contractual adjustments or write-offs.

Use KPIs with stable cohorts and denominators

Publish the formula, period, source system, owner, exclusions, and whether the metric counts claims, claim lines, encounters, units, or dollars. Use both volume and dollar views where concentration matters.

Define “matured,” “expected collectible,” and every excluded payer or claim status. Current-month collections mixed with older charges can distort results. Trend the same formula and restate history when a material definition changes.

Build audit controls around the handoffs

Use access by role, separation of duties for payment posting and refunds, versioned payer rules, approval limits, change logs, daily interfaces, reconciliation reports, and sampled record-to-claim audits. Monitor vendor service levels against the same evidence and queues used by employees.

The HHS Office of Inspector General (OIG) publishes a compliance resource library. Its General Compliance Program Guidance describes voluntary, nonbinding compliance-program infrastructure and adaptations for organizations of different sizes. Use it as a federal compliance reference, then map controls to the practice's actual programs, contracts, states, risks, and legal advice.

A weekly RCM review should cover missing eligibility evidence, upcoming authorization exhaustion, credentialing holds, unsigned records, charge lag, rejected or unacknowledged claims, high-risk deadlines, denial clusters, underpayments, unmatched cash, credits, and control failures. A monthly review should reconcile the subledger to the general ledger and bank, approve reserves and write-offs, review vendor performance, and assign prevention work.

The SBA Business Guide offers general planning and financial-management resources. Healthcare RCM adds clinical records, payer contracts, privacy, transaction standards, and compliance obligations that need specialized ownership.

Synthetic example: follow one encounter to cash

Harbor ABA and Plan S are fictional. Plan S has confirmed the clinician, group, location, and product effective dates. A dated eligibility response shows active coverage, a deductible, and an ABA authorization requirement. The authorization record contains 96 approved units for the period. Before the session, the schedule shows 24 delivered units, four scheduled units, and 72 remaining units. The planned four-unit session passes the date, service, provider, location, and unit checks.

After care, the clinician signs a record supporting four delivered units. Billing validates the encounter against the current code source and Plan S instructions, releases a $150 claim, and saves the outbound file. The clearinghouse accepts it, then the payer acknowledges it for adjudication. Those two receipts close the submission gate.

The fictional contract model calculates an expected allowed amount of $120 for this exact configuration. The ERA later reports $90 from Plan S, $10 of patient responsibility, and a $50 contractual adjustment. The adjudicated allowed amount is therefore $100. Posting balances the $90 EFT to the ERA and records the $10 family balance. It also opens a suspected $20 underpayment because the contract model expected $120.

The payment-integrity owner checks the contract effective date, provider, location, service, and pricing method. The source records still support $120, so the owner sends Plan S a payment inquiry through its fictional process and retains the confirmation. If Plan S later pays $20, the team posts the additional remittance and closes the variance. If the contract interpretation changes, finance corrects the expected amount with an approved, versioned explanation.

This example keeps clinical facts, authorization units, submission acceptance, adjudication, patient responsibility, cash, and contract variance connected. Every payer rule, amount, service label, and timeline in it is invented for illustration.

Related resources

Use the parent topic, Billing, RCM, Denials, Appeals and Revenue Integrity, to browse the full owner and operator collection.

• ABA Claim Denials: How to Classify, Work and Prevent Them
• Ethical ABA Billing and Audit Readiness Checklist
• How to Choose an ABA EHR and Practice Management System
• ABA Practice KPIs: The Metrics Owners Should Track

Sources

Sources were checked August 13, 2026. Verify current payer, product, contract, code, state, and client-specific requirements before using the workflow for a live case.

1. U.S. Small Business Administration, Business Guide
2. Centers for Medicare & Medicaid Services, Prior Authorization API FAQ
3. ABA Coding Coalition, ABACodes.org
4. HHS Office of Inspector General, Compliance Resources
5. Centers for Medicare & Medicaid Services, Adopted Standards and Operating Rules
6. Centers for Medicare & Medicaid Services, Health Plan Eligibility Benefit Inquiry and Response
7. Centers for Medicare & Medicaid Services, Health Care Claim or Equivalent Encounter Information
8. Centers for Medicare & Medicaid Services, Health Care Payment and Remittance Advice and Electronic Funds Transfer
9. Centers for Medicare & Medicaid Services, Claim Status Request and Response
10. Centers for Medicare & Medicaid Services, NPPES NPI Files notice
11. Centers for Medicare & Medicaid Services, Know your rights when you are not using insurance
12. HHS Office of Inspector General, General Compliance Program Guidance