What is an RCM glossary?
An RCM glossary is a reference of revenue cycle management terms — from Days in AR and denial rate to EOB/ERA, aging buckets, and write-offs — used by billing and RCM teams to measure, work, and report on claims. Clear definitions keep ops, finance, and vendor conversations aligned on the same metrics and workflows.
Core revenue cycle metrics
These are the KPIs most teams baseline, track, and report. Treat the definitions as measurement language — not guaranteed outcomes.
Days in AR
Average number of days from claim submission (or date of service, depending on your formula) until payment posts. Lower is generally healthier; rising Days in AR often signals backlog or payer delays.
Denial rate
Share of claims denied (or rejected) relative to claims submitted, usually expressed as a percentage. Track by reason and payer so you know whether the issue is front-end, coding, or follow-up.
Clean-claim / first-pass rate
Percentage of claims accepted and paid (or accepted for adjudication) without needing correction or resubmission. A proxy for front-end quality and claim scrubbing.
Net collection rate
Payments collected as a percentage of what was collectible after contractual adjustments. Distinct from gross collection rate, which ignores write-downs and contracts.
AR over 90 days
Dollar or claim volume sitting in aging buckets older than 90 days. A rising share usually means follow-up capacity or denial resolution is lagging.
Payment posting lag
Time between receipt of an ERA/EOB (or payment) and accurate posting to the patient account. Long lag distorts AR and cash reporting.
Claims, remittance, and account status
Day-to-day claim language — what the documents are called and what status terms mean on the account.
Claim / encounter
The billable record of services submitted to a payer (or patient). In many systems, an encounter becomes a claim once coded and submitted.
EOB (Explanation of Benefits)
Payer document explaining how a claim was adjudicated — allowed amount, patient responsibility, adjustments, and denial reasons. Often patient-facing; operations usually work from the ERA.
ERA (Electronic Remittance Advice)
Electronic version of remittance data (commonly 835). Used for automated or manual payment posting and denial reason capture.
Aging buckets
AR sorted by age — typically 0–30, 31–60, 61–90, 91–120, 120+. Teams prioritize older buckets and high-balance accounts to reduce write-off risk.
Write-off
Amount removed from AR as uncollectible or adjusted (contractual, small-balance, bad debt, or timely-filing). Policy should define who can approve write-offs.
Adjustment / contractual allowance
Difference between billed charges and the contracted allowed amount. Not the same as a denial or a bad-debt write-off.
Patient responsibility
Portion of the balance owed by the patient after payer adjudication — deductibles, coinsurance, copays, and non-covered services.
Denials, appeals, and follow-up
Terms used when claims are unpaid, underpaid, or rejected — the core of AR and denial workflows.
Denial
Payer decision not to pay (or to pay differently) for a submitted claim, with a reason code. Distinct from a clearinghouse rejection, which never reaches adjudication.
Rejection
Claim stopped before payer adjudication (clearinghouse or front-end edits). Usually fixed and resubmitted rather than appealed.
Appeal
Formal request to a payer to reconsider a denial, with documentation and clinical or billing rationale. Timelines and formats are payer-specific.
AR follow-up
Working unpaid or underpaid claims: status checks, payer calls/portals, documentation requests, corrections, and escalations before balances age out.
CARC / RARC
Claim Adjustment Reason Codes and Remittance Advice Remark Codes on the ERA that explain why payment differs from billed. Used to categorize and route denials.
Underpayment
Payment below the expected allowed amount per contract. Requires variance review, not just posting what arrived.
Front-end and access workflows
Work that happens before or at claim creation — where many avoidable denials originate.
Eligibility verification
Confirming active coverage, plan details, and benefits for a patient before or at the visit so claims are submitted to the right payer with accurate patient responsibility.
Prior authorization (prior auth)
Payer approval required before certain services, procedures, or medications. Missing or expired auth is a common denial reason.
Benefits verification
Checking what the plan covers for a specific service — limits, copays, deductibles, referrals — beyond simple active/inactive eligibility.
Credentialing
Enrolling providers with payers and networks so claims are accepted and paid under the correct contracted rates. Gaps cause demurrals and denials.
Coding accuracy
Correct CPT/HCPCS, ICD-10, modifiers, and units relative to documentation and payer rules. Measured as a quality metric, not a marketing claim.
Operating model terms
How teams talk about staffing and partnership models in modern RCM.
Co-managed RCM
Outside production capacity working inside your systems and SOPs while you keep ownership of decisions, payer relationships, and visibility. Distinct from full black-box outsourcing.
White-label RCM
Back-office capacity delivered under your brand to your clients — with branding, non-solicitation, and account-separation expectations spelled out in the engagement.
RCM back office
The production workflows behind the patient visit: AR, denials, posting, eligibility, auth, and related support — as opposed to front-desk or clinical ops.
Where these terms show up in Salt HealthOps services
If you are mapping glossary language to operational support, these pages go deeper by workflow and buyer type.
AR Follow-Up Services
Aging, statusing, and unpaid claim work.
Learn moreDenial Management
Reason codes, appeals, and prevention loops.
Learn moreEligibility & Benefits
Coverage checks before claims fail.
Learn morePrior Authorization Support
Auth submission and follow-through.
Learn morePayment Posting
ERA/EOB posting and variance capture.
Learn moreRCM Back-Office Support
Multi-workflow co-managed capacity.
Learn moreFor RCM Companies
Capacity for US RCM operators.
Learn moreFor Billing Companies
Back-office support under your model.
Learn moreRelated reading
Frequently asked questions
What is the difference between Days in AR and AR over 90 days?
Days in AR is an average aging metric across open balances. AR over 90 days is the slice of inventory that has already aged past ninety days. You can have acceptable average Days in AR while a dangerous tail builds in the 90+ bucket — which is why operators watch both.
Is a denial the same as a rejection?
No. A rejection usually means the claim never made it through clearinghouse or payer front-end edits. A denial means the payer adjudicated the claim and refused (or reduced) payment with a reason. Fixes and workflows differ: rejections are often corrected and resubmitted; denials may need appeal or clinical documentation.
What does clean-claim rate measure?
Clean-claim or first-pass rate measures how often claims go through without needing correction or resubmission. It reflects front-end quality — demographics, eligibility, coding, auth, and scrubbing — more than back-end follow-up skill.
Where should I start if our team uses these terms inconsistently?
Pick a short KPI set (Days in AR, denial rate, AR over 90, posting lag), write the exact formula your system uses, and use those definitions in weekly reporting. Align language before you change staffing or vendors — otherwise you will argue about numbers that were never comparable.