# RCM Benchmarks & Billing Cost Calculator | rcm.today > Work out your practice cost to collect with HFMA-aware definitions, compare billing models, and use sourced RCM benchmarks — every formula published. ## About this site rcm.today is a revenue-cycle decision and benchmarking resource for outpatient practice owners, administrators, and billing leads — not a daily news product. It is operated by AdvancedCare USA Inc., which sells RCM software and services (including RCMBoost); that relationship is disclosed on every page. Every benchmark, formula, and cost figure here is sourced to a named publisher with an as-of date, and the site does not score AdvancedCare or RCMBoost against named competitors. Billing/coding utilities (BCBS prefix lookup, appeal letters, NPI lookup) live on the separate rcm.tools app, not here. ## Pages - Home: https://rcm.today/ - Cost to collect: https://rcm.today/cost-to-collect - Benchmarks: https://rcm.today/benchmarks - RCM software: https://rcm.today/rcm-software - Denials: https://rcm.today/denials - CO-16: https://rcm.today/denials/co-16 - CO-97: https://rcm.today/denials/co-97 - CO-45: https://rcm.today/denials/co-45 - CO-22: https://rcm.today/denials/co-22 - CO-96: https://rcm.today/denials/co-96 - OA-23: https://rcm.today/denials/oa-23 - CO-109: https://rcm.today/denials/co-109 - PR-204: https://rcm.today/denials/pr-204 - Prior auth: https://rcm.today/prior-auth - About: https://rcm.today/about - Contact: https://rcm.today/contact --- ## What is your revenue cycle actually costing you? URL: https://rcm.today/ Last reviewed: 2026-07-18 Most outpatient practices have never computed cost-to-collect with a named denominator. Here is the arithmetic — using published industry definitions, every constant sourced and dated — so you can check it before you talk to anyone selling a fix, including us. ### Key facts - **2.5–8%** — Illustrative cost-to-collect bands used in the calculator for independent practices (method: RCM expense ÷ cash collections) (source: HFMA cost-to-collect better practices; model bands on /cost-to-collect) - **$33.40** — CY2026 non-qualifying-APM Medicare PFS conversion factor (from $32.35; +3.26%) (source: CMS-1832-F fact sheet, 31 Oct 2025) - **+126%** — Coding-related denials over three years (MDaudit data cited in HFMA roundtable) (source: HFMA / MDaudit, 2025 roundtable article) - **$57.23** — Average cost to adjudicate a single claim (hospital survey sample) (source: Premier Inc. claims adjudication survey) ### What this site is, and what it is not **rcm.today is not a news site.** It used to describe itself that way — "curated daily," a morning digest, Medicaid bulletins "tracked" alongside CMS updates. Those claims were false: there was no daily feed, no newsletter form, and no state-by-state Medicaid tracker. That framing is retired. What this domain is now: a small set of **dated reference pages** and a **free cost-to-collect calculator** for practice owners and administrators who suspect billing is leaking money and need arithmetic before they take another vendor call. What it is not: - A daily or weekly newsroom - An independent consumer magazine with no commercial interest - A directory of "billing companies near you" - A replacement for `rcm.tools` (utility tools for billers and coders live there) Dated long-form notes still appear under [News](/news) when we publish them — each one sourced, none of them a promise of cadence you cannot hold us to. ### Who operates this — stated up front **AdvancedCare USA Inc.** operates rcm.today. AdvancedCare sells EHR, revenue cycle services, ClinicPay.ai, and RCMBoost to outpatient practices — including the same buyer this site is written for. That is not a footer apology. It is the reason every formula and source is published: so you can disagree with an assumption, re-run the math, and decide whether our commercial interest distorts the answer. A page that pretends to be a neutral newspaper while functioning as a sales funnel is worse than a page that says "we sell this work — here is checkable arithmetic anyway." ### Cost-to-collect bands (preview — no gate) HFMA's [cost-to-collect better practices](https://www.hfma.org/wp-content/uploads/2025/09/Cost-to-Collect-Better-Practices.pdf) define the KPI as **RCM expense divided by cash collections**, with inclusions stated explicitly. Public HFMA discussion of hospital-style cost-to-collect often centres near the low single digits of net collections; independent outpatient practices collecting more patient-responsibility balances typically run **higher** once statements, staff time, and card fees are counted. The free calculator on this site estimates the **patient-responsibility collection** slice of that problem — statements, staff touches, and card fees — as cents per dollar collected and as a rate. It will not invent your payer mix. It will suppress a number rather than fabricate one. | Rough placement | What it usually means | | --- | --- | | Better-performing territory | Low single-digit % of collections under a named method; measure before celebrating | | Median / common | Mid single-digit % when patient balances and multi-cycle statements are real | | Needs attention | High single digits — check what is in the numerator before changing vendors | | Investigate now | Double-digit % of collections — usually a definition problem, a volume problem, or both | **[Run your own numbers →](/cost-to-collect)** — no email gate, results from defaults on first paint. ### Questions this site answers - [What is billing actually costing us?](/cost-to-collect) — Free calculator: statements, staff time, and fees as ¢ per patient dollar collected — then compare models in plain language. - [What do the KPIs mean?](/benchmarks) — Days in A/R, cost-to-collect, first-pass, denial rate — formulas, denominators, and why vendors redefine them. - [How should we evaluate RCM software?](/rcm-software) — Criteria and demo questions — not a scorecard where our own product wins. - [Why are denials getting harder?](/denials) — Sourced industry data, prevention vs appeal, and a link to appeal utilities on rcm.tools. - [Where do prior auths fail?](/prior-auth) — The eligibility-to-claim walkthrough: why auths fail, the CO-197-class denial surface, and the prevention checklist. - [Who runs this and how does it make money?](/about) — Operator, funding model, sourcing policy, corrections. - [Dated notes (when published)](/news) — Sourced articles on prior auth, denials, and fee-schedule changes — no daily promise. ### Biller and coder tools live on rcm.tools If you need a **BCBS prefix lookup**, **appeal letter generator**, **NPI lookup**, patient payment estimator, or similar utility, use **[rcm.tools](https://rcm.tools)** — a separate, live app. This site is for the practice owner / administrator deciding what billing costs and whether to change models. Routing the utility audience there keeps both products honest. ### Questions Q: Is rcm.today a news site? A: No. It used to describe itself that way and did not publish on that cadence. It is now a set of dated reference pages and a cost calculator. There is no newsletter. Occasional sourced articles appear under /news when they are written — that is an archive, not a daily desk. Q: Who runs this? A: AdvancedCare USA Inc., which sells revenue cycle software and services. That is why every formula and source is published — so you can check the arithmetic against our commercial interest. Details on /about. Q: What is cost to collect, and what should mine be? A: Under HFMA framing, cost-to-collect is RCM expense divided by cash collections, with inclusions stated. There is no single correct percentage for every specialty and size. Use /benchmarks for definitions and /cost-to-collect for your own arithmetic on the patient-responsibility slice. Q: Is outsourcing billing cheaper than in-house? A: It depends on volume, payer mix, and what your in-house cost actually includes — which most practices undercount (loaded labour, software, write-offs, management time). Work the calculator and the model-comparison table on /cost-to-collect before you trust a vendor percentage alone. Q: What should an outsourced billing company charge? A: Public list prices are rare; rates are contracted. Marketed full-cycle outpatient RCM often lands in the mid-single-digit percent of net collections, but inclusions vary (patient balances, denial work, coding). Compare against a fully loaded in-house number, not base salary alone. We do not publish named competitors’ contract rates. Q: Do you cover state Medicaid changes? A: No. Fifty state programmes change faster than we can track honestly. We do not claim to track Medicaid bulletins. Federal fee-schedule and prior-auth notes appear when we publish sourced articles under /news. Q: Do you have billing tools? A: Not on this domain. rcm.tools has a BCBS prefix lookup, appeal letter generator, NPI lookup, and related utilities. Q: Will you look at my numbers? A: Yes, if you ask — and we will tell you when the answer is that your billing is fine. Use the contact form; we sell RCM services and disclose that before we talk shop. Sources: - Calendar Year (CY) 2026 Medicare Physician Fee Schedule Final Rule (CMS-1832-F) fact sheet (Centers for Medicare & Medicaid Services): https://www.cms.gov/newsroom/fact-sheets/calendar-year-cy-2026-medicare-physician-fee-schedule-final-rule-cms-1832-f - HFMA Guide to Better Practices in Measuring Cost-to-Collect (HFMA): https://www.hfma.org/wp-content/uploads/2025/09/Cost-to-Collect-Better-Practices.pdf - HFMA MAP Keys — industry-standard revenue cycle KPIs (HFMA): https://www.hfma.org/data-and-insights/map-initiative/map-keys/ - Reshaping revenue cycle strategy (HFMA roundtable; MDaudit-sponsored) (HFMA / MDaudit-cited data): https://www.hfma.org/technology/reshaping-revenue-cycle-strategy/ - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense - MGMA Stat: medical practice operating costs still rising in 2025 (MGMA): https://www.mgma.com/mgma-stat/medical-practice-operating-costs-are-still-rising-in-2025-heres-how-to-control-them --- ## What does your billing actually cost you? URL: https://rcm.today/cost-to-collect Last reviewed: 2026-07-18 Most practices compare a vendor’s percentage against billing salaries and get the comparison wrong — salaries are not the whole in-house cost. Work the patient-responsibility arithmetic first, then judge the models. ### Direct answer **Cost-to-collect** is, under HFMA-style measurement, **revenue-cycle expense divided by cash collections** — with every inclusion named. For independent outpatient clinics, the patient-responsibility slice alone (statements, staff follow-up, card fees) commonly lands from a few cents to low double-digit cents per dollar collected once multi-cycle billing is counted. In-house salary is not a full denominator; outsourced % of collections is not automatically more expensive either. Use the free calculator below for *your* volumes. This is an estimate, not a quote and not an audit. ### What actually counts as billing cost Four components dominate. Most practices undercount at least two of them. **1. Staff — fully loaded, not base salary.** Wage plus benefits, payroll tax, and PTO coverage. A $48,000 base is not a $48,000 cost. Use a loaded hourly figure in the calculator; do not paste W-2 wages alone into a vendor comparison. **2. Software and clearinghouse.** Practice management / billing module, clearinghouse per-claim or monthly fees, statement and e-statement costs, patient payment processing. Outsourced proposals often bundle some of these and leave others with you — read the SOW. **3. Write-offs traceable to process.** Timely-filing losses, unappealed denials, and uncollected patient balances that a better front end would have caught. This line often dominates the true comparison and almost never appears in a "billing salary vs 6%" spreadsheet. **4. Management time.** Owner or administrator hours on billing escalation, payer calls, and vendor management. Cheap to ignore; expensive when it is every Friday afternoon. An outsourced percentage typically bundles (1), parts of (2), and some of (3). That is why a naïve "6% vs my biller's salary" comparison is almost always wrong in both directions. [HFMA's cost-to-collect guide](https://www.hfma.org/wp-content/uploads/2025/09/Cost-to-Collect-Better-Practices.pdf) exists because two organisations can report the "same" KPI with different numerators. The calculator on this page models the **patient-balance** stack (statements + staff minutes + card fees) using sourced constant bands. It does not invent insurance claim adjudication cost — for that world, see Premier's [average $57.23 per claim](https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense) as a separate construct. ### Three billing models — structural comparison | Model | Typical pricing structure | Usually covers | You usually keep | Tends to suit | | --- | --- | --- | --- | --- | | Fully in-house | Salaries + software + clearinghouse + statement fees | Whatever you staff and train for | All process design, hiring, and denial strategy | Stable volume, strong internal lead, willingness to manage people | | Fully outsourced full-cycle | Often % of net collections, sometimes tiered; contracted — not public list price | Charge entry through payment posting for agreed payers; sometimes patient AR | Front-desk eligibility habits, clinical documentation, contract negotiation | Groups that want one throat to choke and can audit the vendor | | Hybrid | Mix: e.g. coding or AR follow-up only at % or flat; software stays yours | Named slices only — read the scope line by line | Everything outside the SOW (often patient balances or complex denials) | Practices testing outsourcing without full exit | Every cell is structural, not a quote. Named vendor rates are contracted and not published here. Confirm inclusions in writing before you compare percentages. ### What to refuse to sign These terms show up often enough that a practice administrator should recognise them cold. Including them here is intentional — they constrain our own sales motion as much as anyone else's. - **Percentage of collections applied to patient payments the practice collected itself** at the front desk or portal, with no carve-out. You are paying for work you already did. - **Auto-renew with a long notice window** (e.g. 90–180 days) buried in a multi-year term. Put the calendar reminder the day you sign. - **No data-portability clause on exit** — no right to full claim history, worklists, and payer notes in a usable format within a fixed number of days. - **No named performance floor** on days in A/R, first-pass clean claim rate, or denial overturn time. "Best efforts" is not a KPI. - **Charging on gross charges rather than net collections** without a clear, audited definition. Gross is a larger base; it is not always wrong, but it must be explicit. - **Unilateral fee increases** mid-term without a material-change clause you can exit on. If a vendor will not put floors and exit rights in writing, treat that as information. ### Questions to ask an RCM vendor (printable) - What is the exact denominator for your fee — net collections, gross charges, or something else? — Write the definition down. Ask for a sample invoice with real line labels. - Which patient payments are excluded from your percentage? — Point-of-service cash, portal payments, payment plans the practice administers. - What is your first-pass clean claim rate on accounts like ours, and how is it defined? — Numerator, denominator, and whether secondary claims count. - What is the contracted days-in-A/R target, and what happens if you miss it? — Remedy: fee credit, termination right, or only a meeting. - Who owns denial workflow — and at what dollar threshold do you stop appealing? — Ask for the written threshold. A $25 floor may be rational; a silent floor is not. - On exit, what data do we get, in what format, within how many days? — Claims, remits, worklists, payer notes, patient AR aging. - Which software and clearinghouse costs remain on our books? — PM licence, e-statements, card processing, eligibility pings. - Show me three anonymised monthly scorecards for practices our size. — If they cannot, you are buying a pitch deck. Print this list and take it into the sales call. Fill the blanks with numbers, not adjectives. ### How the calculator works (open method) The model is shared with clinicpay.ai and lives in open constants — every band has a source, publisher, and as-of date. **balanceCount** = monthly patient-responsibility billed ÷ average patient balance **statementsSent** ≈ balanceCount × statement cycles per year **statementSpend** = statementsSent × per-statement cost for your channel **staffSpend** = balanceCount × staff minutes per balance × fully loaded hourly cost **feeSpend** = amount collected × effective card fee rate **cost to collect** = (statementSpend + staffSpend + feeSpend) ÷ amount collected Dollar outputs round **outward** to the nearest $100; rates to 0.5 percentage points. If the high is less than 1.35× the low, the range widens. If the result hits a 0.5%–25% clamp, or inputs look like total charges rather than patient responsibility, the tool **suppresses** the number. Statement bands are anchored to [USPS postage](https://pe.usps.com/text/dmm300/Notice123.htm) for the paper share. Card fees use a 1.5%–3.5% all-in band informed by [Federal Reserve debit interchange reporting](https://www.federalreserve.gov/paymentsystems/regii-average-interchange-fee.htm). Practice-size bands follow [HFMA cost-to-collect framing](https://www.hfma.org/wp-content/uploads/2025/09/Cost-to-Collect-Better-Practices.pdf). **Out of scope for this calculator:** geographic wage adjustment, named vendor pricing, full insurance adjudication cost, and any figure presented as what AdvancedCare would charge you. ### Get a second read on these numbers We are **AdvancedCare**. We sell revenue cycle services. If you want us to sanity-check what you just calculated, [send it over](#contact) — and if the honest answer is that your billing is fine, we will say that. Paste the calculator’s “Copy this estimate” output into the message so we see the same inputs you used. Nothing is attached silently. ### Questions Q: Is this calculator free? Do I need to sign up? A: Yes, free. No signup. Results update as you move the controls. Use “Copy this estimate” for plain text. Q: Why is the answer a range instead of one number? A: Because the constants are ranges, collection share is a band, and a single precise figure would read like a quote. This is an estimate. Q: Does this include insurance claim costs? A: No. It models patient-responsibility collection. Insurance claim adjudication is a separate stack — see Premier’s per-claim figures and the /denials page. Q: Is this the same as “cost to collect” on a hospital MAP scorecard? A: Related definition (expense ÷ collections), different inclusion set. Align your numerator with HFMA MAP Keys before you compare to a peer hospital number. Q: Will outsourcing always lower this number? A: No. Outsourcing moves cost from payroll into a fee and changes who does the work. Whether the total drops depends on your fully loaded in-house cost and what the fee includes. Q: Do you use this calculator to set AdvancedCare pricing? A: No. Vendor pricing is contracted. The tool is for your arithmetic, not a quote engine for our services. Sources: - HFMA Guide to Better Practices in Measuring Cost-to-Collect (HFMA): https://www.hfma.org/wp-content/uploads/2025/09/Cost-to-Collect-Better-Practices.pdf - HFMA MAP Keys — industry-standard revenue cycle KPIs (HFMA): https://www.hfma.org/data-and-insights/map-initiative/map-keys/ - USPS Domestic Mail Manual — Notice 123 postage prices (United States Postal Service): https://pe.usps.com/text/dmm300/Notice123.htm - Federal Reserve — average debit card interchange fee (Regulation II) (Board of Governors of the Federal Reserve System): https://www.federalreserve.gov/paymentsystems/regii-average-interchange-fee.htm - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense - MGMA Stat: medical practice operating costs still rising in 2025 (MGMA): https://www.mgma.com/mgma-stat/medical-practice-operating-costs-are-still-rising-in-2025-heres-how-to-control-them --- ## RCM benchmarks, and the definitions that make them comparable URL: https://rcm.today/benchmarks Last reviewed: 2026-07-18 A KPI without a denominator is a slogan. This page states formulas, exclusions, and sources so a vendor dashboard cannot quietly redefine the metric mid-pitch. ### How to use this page Prefer **named definitions** (HFMA MAP Keys where possible) over peer brag sheets. Prefer **your own year-over-year trend** when public percentile tables are paywalled or thin. Every band below is a reference frame, not a promise that your specialty must hit it. ### KPI definitions (formulas first) ### Days in A/R **Common formula:** total accounts receivable ÷ average daily charges, often on a rolling period, with credit balances handled explicitly. **Why it drifts:** including or excluding credits, using gross vs net, and mixing patient A/R with insurance A/R all move the number without changing operations. MGMA has reported periods where many practices saw days in A/R **increase** ([MGMA Stat context](https://www.mgma.com/mgma-stats/not-so-graceful-aging-half-of-practices-saw-days-in-a-r-increase-in-2021)). Practice literature often discusses a **30–40 day** overall band as a management target — treat that as a commonly cited target, not a single DataDive percentile reproduced here ([KPI materials](https://www.mgma.com/getkaiasset/64027d0a-cff9-43c6-8b43-17d6588d2413/PRCM-KPIWhitePaper-Final-19April23.pdf)). ### Cost to collect **HFMA-aware formula:** RCM expense ÷ cash collections, with inclusions listed ([HFMA guide](https://www.hfma.org/wp-content/uploads/2025/09/Cost-to-Collect-Better-Practices.pdf), [MAP Keys](https://www.hfma.org/data-and-insights/map-initiative/map-keys/)). **Why it drifts:** leaving out statement vendors, agency fees, or front-desk time makes the rate look better. Hospital discussion often centres near **~2–3% of net collections** under disciplined inclusion; independent clinics with heavy patient-responsibility work commonly sit **higher** once that stack is counted. Run [your own estimate](/cost-to-collect). ### First-pass clean claim rate **Formula:** claims accepted on first submission ÷ claims submitted (define whether secondary claims and voids count). **Why it drifts:** “accepted” can mean clearinghouse accepted, payer accepted, or paid without edit — three different bars. Better performers are widely discussed in the **mid-to-high 90%s**; many practices discover they sit lower once they measure. Publish the definition next to the number. ### Initial vs final denial rate **Initial:** denials on first adjudication ÷ claims. **Final:** claims never paid after appeals ÷ claims (or as % of net patient revenue — state which). Kodiak Solutions data reported via Fierce Healthcare put **median final denial rate** for hospitals at **2.5% in 2024 → 2.7% in 2025**, with rising revenue leakage ([report](https://www.fiercehealthcare.com/finance/despite-better-cash-flow-providers-missed-out-more-revenue-2025-due-increased-payer-denials)). Coding-related denials have been cited as up **126% over three years** in MDaudit data discussed in an [HFMA roundtable](https://www.hfma.org/technology/reshaping-revenue-cycle-strategy/). ### Net collection rate **Formula:** payments ÷ (charges − contractual adjustments), or a close variant — **name the contractual-adjustment source**. **Why it drifts:** using gross charges in the denominator turns a healthy collection rate into a horror story, and the reverse hides underpayments. ### Reference bands (not trophies) | KPI | Better-performer discussion | Common / median discussion | Needs attention | Source framing | | --- | --- | --- | --- | --- | | Days in A/R (overall) | Often discussed near ~30 days | Often discussed ~30–40 days | Sustained >50 without a definition change | MGMA-oriented practice KPI literature; verify definition | | Cost to collect | Low single-digit % of collections (hospital-style MAP) | Mid single-digit % when patient AR is heavy | Double-digit % of collections | HFMA cost-to-collect method; model on /cost-to-collect | | First-pass clean claim | Mid–high 90%s (definition-dependent) | Upper 80%s to low 90%s common when unmeasured | Persistently <~85% with a clear definition | Industry KPI practice literature; measure before ranking | | Final denial rate (hospital median example) | Below peer median with stable coding/auth | 2.5–2.7% final denial (Kodiak 2024–2025 hospital sample) | Rising final denials + rising adjudication cost | Kodiak via Fierce Healthcare; Premier adjudication $ | Bands are discussion ranges with sources, not a sold MGMA DataDive table. If your specialty association publishes a tighter table, prefer that — and keep the same definition year over year. ### Why definitions drift on purpose Two worked patterns show up in vendor demos: **1. The shrinking denominator.** A dashboard shows “denial rate” on *adjudicated clean claims only*, excluding claims rejected at the clearinghouse. The rate looks excellent; the worklist is still full. Ask: “What is excluded from the denominator?” **2. The missing numerator.** “Cost to collect is under 3%” while statement vendor fees, patient-statement postage, and half the front desk live in other cost centres. Ask: “List every GL account in the numerator.” [HFMA MAP Keys](https://www.hfma.org/data-and-insights/map-initiative/map-keys/) exist to make those games harder. You do not need to buy a peer survey to insist on a written definition. ### How to measure yours this month From your practice management system, pull: 1. **Total A/R** and **average daily charges** for the same rolling window (often 90 days) — compute days in A/R yourself. 2. **Patient-responsibility charges** last 90 days (not gross charges) and open self-pay balances. 3. **Claims submitted vs accepted on first submission** for one calendar month — write the acceptance rule you used. 4. **Initial denials** and **final write-offs to bad debt / denial** — separately. 5. **RCM expense** for the quarter: billing wages (loaded), clearinghouse, statements, collection agency, eligibility tools. Then run the [cost-to-collect calculator](/cost-to-collect) on the patient slice. If a vendor’s dashboard cannot reproduce these five pulls, it is not your system of record for the argument. ### Questions Q: Are these official MGMA percentiles? A: No. Where MGMA or HFMA publish methods or survey context we cite them. We do not reproduce paywalled DataDive percentile tables we cannot show you. Q: Should I use hospital MAP Keys for a five-provider clinic? A: Use the definitions; be careful with the peer set. Hospital inclusion sets and volumes differ. Year-over-year self-comparison is often more honest than a hospital percentile. Q: Where do I get the calculator constants? A: On /cost-to-collect — every constant is listed with source, publisher, and as-of date in the model notes and assumptions. Sources: - HFMA Guide to Better Practices in Measuring Cost-to-Collect (HFMA): https://www.hfma.org/wp-content/uploads/2025/09/Cost-to-Collect-Better-Practices.pdf - HFMA MAP Keys — industry-standard revenue cycle KPIs (HFMA): https://www.hfma.org/data-and-insights/map-initiative/map-keys/ - The KPIs that define revenue cycle excellence (HFMA): https://www.hfma.org/revenue-cycle/the-kpis-that-define-revenue-cycle-excellence/ - Reshaping revenue cycle strategy (HFMA roundtable; MDaudit-sponsored) (HFMA / MDaudit-cited data): https://www.hfma.org/technology/reshaping-revenue-cycle-strategy/ - Despite better cash flow, providers missed out on more revenue in 2025 due to increased payer denials (Fierce Healthcare (reporting Kodiak Solutions data)): https://www.fiercehealthcare.com/finance/despite-better-cash-flow-providers-missed-out-more-revenue-2025-due-increased-payer-denials - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense - MGMA Stat: half of practices saw days in A/R increase (2021 poll context) (MGMA): https://www.mgma.com/mgma-stats/not-so-graceful-aging-half-of-practices-saw-days-in-a-r-increase-in-2021 - Practice RCM KPI white paper (MGMA-oriented materials) (MGMA / practice RCM KPI white paper): https://www.mgma.com/getkaiasset/64027d0a-cff9-43c6-8b43-17d6588d2413/PRCM-KPIWhitePaper-Final-19April23.pdf --- ## How to evaluate revenue cycle software without buying a pitch deck URL: https://rcm.today/rcm-software Last reviewed: 2026-07-18 Feature grids are easy to fake. Criteria, integration constraints, and live demos on your data are not. This page is a buyer’s guide — including an open note that we sell in this category. ### Direct answer Buy RCM software on **workflow depth, clearinghouse economics, export-on-exit, and whether reporting exposes real denominators** — not on a vendor-authored scorecard. AdvancedCare sells RCM software and services (including RCMBoost for behavioural health). This page names that fact and **does not** rank our products against named competitors. ### Operator disclosure **AdvancedCare USA Inc.** operates rcm.today and sells EHR, RCM services, ClinicPay.ai, and **RCMBoost** (behavioural-health-focused RCM). If you want a product conversation, say so on the contact form. What we will not do on this domain: publish a comparison table that scores AdvancedCare or RCMBoost against named competitors and declares a winner. A vendor-authored scorecard that its own product wins is worthless to you. Use the criteria below and score the demos yourself. ### Evaluation criteria (score these yourself) 1. **Clearinghouse coverage and per-claim economics** — which payers, what rejects at the gateway, unit price at your volume. 2. **Denial-workflow depth** — worklists, appeal templates, reason-code analytics, not only a dashboard tile. 3. **Eligibility timing** — at scheduling vs only at check-in; batch vs interactive. 4. **ERA/EOB auto-posting rates** — on *your* payer mix, not a lab demo. 5. **Reporting denominators** — can it export days in A/R, first-pass, and cost inputs using [definitions on /benchmarks](/benchmarks)? 6. **Data export on exit** — full history in documented formats within a contractual window. 7. **Implementation timeline honesty** — calendar days to first clean claim file, not “go-live” marketing. 8. **Support model** — ticket SLAs, named CSM, after-hours for claim deadlines. 9. **Patient-responsibility tooling** — statements, plans, card fees visibility (see also [cost-to-collect](/cost-to-collect)). 10. **Security and BAAs** — not slogans; ask for the BAA and subprocessors list. ### Integration reality (what actually breaks) Most outpatient stacks still move claims and remits as **X12 837/835** through a clearinghouse. Eligibility is often **270/271**. Clinical and scheduling data may travel as **HL7 v2** ADT/SIU, with **FHIR** showing up at the edges for newer apps. What breaks in practice: - **Charge capture lag** between EHR sign-off and billing file generation - **Identity mismatches** (NPI, taxonomy, location) that look like “payer denials” - **ERA mapping** when payer-specific CARC/RARC usage is ugly - **Dual-write** when a new RCM tool and the PM both think they own the patient balance A demo that only shows happy-path clicks inside one product has not tested your integration surface. ### Demo questions (printable) — on your data - Import last month’s claim file (or a redacted extract) and show first-pass failures live. — Refusal usually means the happy path is the whole product. - Show an ERA auto-post with a partial payment and a denial on the same claim. — Watch how the worklist and patient balance update. - Produce days in A/R and first-pass using the definitions we state in writing. — If they substitute a different definition, stop and document it. - Export a full claim + remit history to a non-proprietary format in the session. — Exit rights are not theoretical. - Walk through a prior-auth failure that becomes a clinical denial. — Who owns the loop — billing, front desk, or clinician? - Show per-claim or monthly clearinghouse cost at our volume. — Get the number in writing after the call. Print and use on the demo. Adjectives are not answers. ### Questions Q: Will you recommend RCMBoost here? A: We will not rank it against named competitors on this site. If you want a product conversation, contact us and we will be explicit that we are selling. Q: Is rcm.today the same as RCMBoost? A: No. rcm.today is the decision and benchmarking resource. RCMBoost is a product surface for AI-assisted RCM services and software (especially behavioural health). Q: Do you cover clearinghouse shopping? A: Only as a criterion (coverage + unit economics). We do not publish a ranked clearinghouse directory. Sources: - HFMA MAP Keys — industry-standard revenue cycle KPIs (HFMA): https://www.hfma.org/data-and-insights/map-initiative/map-keys/ - HFMA Guide to Better Practices in Measuring Cost-to-Collect (HFMA): https://www.hfma.org/wp-content/uploads/2025/09/Cost-to-Collect-Better-Practices.pdf - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense --- ## Denial management that starts with the data, not the slogan URL: https://rcm.today/denials Last reviewed: 2026-07-19 Denial rates and the cost of fighting them are both rising in published industry samples. Prevention still beats heroics — but only if you measure first-pass and final denials separately. ### Direct answer Industry samples in 2025–2026 show **higher final denial rates**, **sharply higher coding-related denials over a multi-year window**, and **higher cost per claim to adjudicate**. Fix front-end eligibility, auth, and coding quality before you hire more appeal staff — then appeal what the data says is winnable. Utilities for letter drafting live on [rcm.tools](https://rcm.tools), not here. ### What the recent numbers say **Final denials.** Kodiak Solutions data reported by Fierce Healthcare put hospitals’ **median final denial rate at 2.5% in 2024 and 2.7% in 2025**, with combined “revenue leakage” figures rising year over year ([coverage](https://www.fiercehealthcare.com/finance/despite-better-cash-flow-providers-missed-out-more-revenue-2025-due-increased-payer-denials)). The same reporting emphasises growth in **clinical** denials (auth, medical necessity) relative to purely clerical edits. **Coding-related denials.** An HFMA roundtable article citing **MDaudit** data states that **coding-related denials increased 126% over three years**, outpacing authorization-related denials ([HFMA](https://www.hfma.org/technology/reshaping-revenue-cycle-strategy/)). That is a hospital/health-system network signal, not a guarantee for your specialty — but it is directionally consistent with what outpatient billing managers describe. **Cost to fight.** Premier’s hospital survey put **average cost to adjudicate a single claim at $57.23**, with total adjudication spend in the sample at **$25.7 billion** ([Premier](https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense)). Premier also reported that a large share of appealed denials are eventually overturned — which reframes appeal ROI as a **capacity** problem as much as a legal one. **Operating cost pressure.** MGMA’s mid-2025 poll found **90%** of medical group leaders reporting higher year-to-date operating costs than 2024 ([MGMA](https://www.mgma.com/mgma-stat/medical-practice-operating-costs-are-still-rising-in-2025-heres-how-to-control-them)). Denial labour competes with every other rising line item. ### Common denial cause groups (operational framing) | Cause group | Usually owned by | Prevention lever | Appeal notes | | --- | --- | --- | --- | | Eligibility / registration | Front desk + scheduling | Eligibility at scheduling; card-on-file discipline | Often not worth complex appeal — fix the feed | | Prior authorization | Clinical ops + billing | Auth required list by payer; lead time | Medical policy citations; deadlines are hard | | Coding / CDI | Coding + clinicians | Documentation specificity; modifier hygiene | Coding denials rising in multi-year samples | | Timely filing | Billing ops | Worklist aging; secondary claim clocks | Usually lost if the clock is real — prevent only | | Medical necessity | Clinician + UM | Payer policy check before service when possible | Highest effort appeals; track overturn rate | This table is operational framing, not a ranked national cause-code study. Pull your top CARC/RARC codes from your own 90-day denial file. ### Denial codes, one page each - [CO-16 — missing or invalid information](/denials/co-16) — The claim lacks required data or has a submission error. Read the RARC first; correct and resubmit before you appeal. - [CO-97 — bundled / inclusive procedure](/denials/co-97) — Payment for this service is included in another already-adjudicated service. Check NCCI PTP edits before you unbundle. - [CO-45 — charge exceeds fee schedule](/denials/co-45) — Billed charge is above the allowed amount. Usually a contractual write-off, not a recoverable denial. - [CO-22 — may be covered by another payer](/denials/co-22) — Coordination of benefits: this payer thinks another plan is primary. Fix the COB order before resubmitting. - [CO-96 — non-covered charge](/denials/co-96) — The service is not a covered benefit under this plan. Confirm benefit status before treating as a coding error. - [OA-23 — impact of prior payer adjudication](/denials/oa-23) — An other-adjustment code showing how a prior payer’s payment or adjustment affected this remittance — common on secondary claims. - [CO-109 — wrong payer / contractor](/denials/co-109) — This payer is not the correct one for the claim. Route to the right plan or Medicare contractor. - [PR-204 — not covered under current benefit plan](/denials/pr-204) — Patient-responsibility group: the plan does not cover this service/equipment/drug. Bill the patient only after confirming benefit language. ### Prevention vs appeal **Prevention** moves first-pass clean claim rate and shrinks the denial pile. **Appeal** recovers a fraction of what already failed, at [non-trivial labour cost](https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense). A practical split: 1. Measure **initial** vs **final** denials separately ([definitions](/benchmarks)). 2. Rank reason codes by **dollars**, not count. 3. Assign each top code to prevention owner vs appeal owner. 4. Set a **written dollar floor** for appeals and revisit it quarterly. 5. Re-check cost-to-collect when denial labour spikes — [calculator](/cost-to-collect). For the prior-auth failure modes specifically — the auth-to-denial chain, the CO-197-class code surface, and the prevention checklist — see the [prior authorization walkthrough](/prior-auth). ### Appeal basics — use rcm.tools for the letter We do not rebuild an appeal-letter generator here. **[rcm.tools](https://rcm.tools)** already offers an appeal letter utility alongside BCBS prefix lookup, NPI lookup, and related biller tools. Use those when you need drafting help; use this page for the management arithmetic and the decision to appeal at all. ### Questions Q: Are the +126% and 2.7% figures about my specialty? A: Not necessarily. They are published multi-facility samples (MDaudit via HFMA; Kodiak via trade press). Use them as pressure signals, then pull your own reason-code dollars. Q: Should we appeal every denial? A: No. Use a dollar floor, track overturn rates, and spend scarce labour where recovery exceeds cost. Premier’s high overturn share is an argument for selective capacity — not for appealing everything. Q: Where do I get appeal letter help? A: rcm.tools — not this domain. Sources: - Reshaping revenue cycle strategy (HFMA roundtable; MDaudit-sponsored) (HFMA / MDaudit-cited data): https://www.hfma.org/technology/reshaping-revenue-cycle-strategy/ - Despite better cash flow, providers missed out on more revenue in 2025 due to increased payer denials (Fierce Healthcare (reporting Kodiak Solutions data)): https://www.fiercehealthcare.com/finance/despite-better-cash-flow-providers-missed-out-more-revenue-2025-due-increased-payer-denials - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense - MGMA Stat: medical practice operating costs still rising in 2025 (MGMA): https://www.mgma.com/mgma-stat/medical-practice-operating-costs-are-still-rising-in-2025-heres-how-to-control-them - HFMA MAP Keys — industry-standard revenue cycle KPIs (HFMA): https://www.hfma.org/data-and-insights/map-initiative/map-keys/ - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes --- ## Denial code CO-16 — claim lacks information or has a submission error URL: https://rcm.today/denials/co-16 Last reviewed: 2026-07-19 CO-16 is a contractual-obligation code: the payer is saying the claim is incomplete or incorrect as submitted. Most recoveries come from fixing the missing field and resubmitting — not from a formal appeal. ### What CO-16 means **CO-16** (group code **CO** = contractual obligation) means the payer adjudicated the line as lacking required information or containing a submission/billing error. The short description alone rarely names the field — that detail almost always sits in a companion **RARC** (MA/N remark code) on the same remittance. First action: read every remark code on the line, then correct and resubmit within the timely-filing window rather than opening a formal appeal. ### What the code actually says X12 publishes Claim Adjustment Reason Code **16** with the short description: *“Claim/service lacks information or has submission/billing error(s).”* ([X12 CARC list](https://x12.org/codes/claim-adjustment-reason-codes), as of this page’s last review). The group code **CO** on the remittance indicates the adjustment is a contractual write-off against the provider under the payer’s rules for that transaction — not automatically a patient balance ([X12 CARC](https://x12.org/codes/claim-adjustment-reason-codes)). What it means in practice is narrower and messier. CO-16 is a **bucket**: the claim failed a completeness or format check, but the specific missing item — diagnosis pointer, NPI taxonomy, prior-auth number, attachment control number, place of service, subscriber ID digit — lives on the **RARC**, not the CARC. X12 maintains those remark codes separately ([X12 RARC list](https://x12.org/codes/remittance-advice-remark-codes)). Billing teams that work CO-16 without opening the remark codes are guessing. Medicare claim submission and remittance conventions are described in the [Medicare Claims Processing Manual (Pub. 100-04)](https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912). Commercial payers use the same CARC/RARC vocabulary under HIPAA claim-status standards, but their required fields and companion-guide edits differ by plan. ### Most common causes and where they originate | Cause | Where it originates | How to confirm on the remit | Prevention owner | | --- | --- | --- | --- | | Missing or invalid diagnosis pointer | Charge entry / coding | RARC naming diagnosis, ICD, or pointer | Coding + charge capture | | Subscriber/member ID mismatch | Registration / eligibility | RARC on member ID, policy, or group number | Front desk + eligibility | | Rendering or billing NPI / taxonomy incomplete | Provider enrollment + claim build | RARC on NPI, taxonomy, or provider data | Credentialing + billing ops | | Prior-auth number not on claim | Auth desk + charge entry | RARC on authorization or referral number | Clinical ops + billing | | Missing attachment or medical records control number | Billing ops | RARC on attachment, PWK, or documentation | Billing ops | | Place of service / facility type mismatch | Scheduling + coding | RARC on POS or facility | Coding + scheduling | | Incomplete other-payer or COB loop | Registration + secondary billing | RARC on other insurance or coordination | Registration + billing | Operational framing from common outpatient claim edits — not a ranked national study. Pull your own top CO-16 RARC pairs from a 90-day denial file. ### Working the denial, in order 1. **Step 1: Read every RARC / remark code on the line** — Open the 835 or payer portal remit for the claim line. List every MA/N remark beside CO-16 before touching the claim ([X12 RARC](https://x12.org/codes/remittance-advice-remark-codes)). If the portal only shows CO-16, pull the electronic remittance — portals sometimes hide remark detail. 2. **Step 2: Map the remark to a field, not a narrative** — Translate each RARC into a concrete claim field (diagnosis pointer, auth number, NPI, attachment). If you cannot name the field, you are not ready to resubmit. 3. **Step 3: Pull source-of-truth documentation** — Eligibility response, auth letter, enrollment file, operative note, or face sheet — whichever owns the missing data. Do not invent a value to clear an edit. 4. **Step 4: Correct and resubmit vs formal appeal** — Most CO-16 recoveries are corrected claims or replacements, not appeals. Use a formal appeal only when the payer has the correct data and still denies, or when the remark is wrong on the facts. Medicare’s appeal ladder and deadlines are summarised in [MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf) (as of that MLN publication). 5. **Step 5: Check the timely-filing clock** — Note original submission date, remit date, and payer timely-filing limit. Corrected claims still fail if the clock has run. Secondary claims often have shorter residual windows. 6. **Step 6: Log the root cause for prevention** — Tag the workqueue item with the RARC family and owning department. A CO-16 cleared without a process fix is a repeat denial pre-ordered. Labour cost of repeated adjudication is non-trivial — see [cost to collect](/cost-to-collect) and Premier’s published adjudication-cost work ([source](https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense)). ### Before you resubmit - Every RARC on the line is written down next to CO-16 — If the 835 and the portal disagree, trust the 835 and archive both. - Diagnosis codes and pointers match the service line — Primary diagnosis supports medical necessity language for that procedure; pointers are not blank or out of range. - Member ID, group, and subscriber relationship match the eligibility response — Copy from the current eligibility transaction, not last year’s card image. - Billing and rendering NPI, taxonomy, and taxonomy qualifier are present where required — Compare to the payer’s enrollment file for that TIN/NPI combination. - Prior-auth or referral number is on the claim in the field the payer expects — Auth is active for the date of service and the billed codes. - Required attachments have a control number and were accepted — PWK segment / portal upload confirmation stored with the claim. - Place of service and facility NPI (if any) match the encounter — Telehealth, POS, and modifier rules checked against the payer’s current policy for the date of service. - Timely-filing and corrected-claim frequency codes are still valid — Replacement claim uses the correct claim frequency code and original reference number when required. ### Preventing it upstream CO-16 is overwhelmingly a **front-end completeness** problem. Ownership sits with registration (member data), clinical ops (auth numbers), coding (pointers and POS), and charge entry (NPI, attachments) — not with appeals specialists. Controls that cut recurrence: 1. **Eligibility at scheduling and again at check-in**, with automated comparison of member ID digits to the card on file. 2. **Auth number as a hard stop** in charge entry when the payer/code combination requires authorization. 3. **Claim scrub rules** that reject outbound 837s missing diagnosis pointers, taxonomy, or attachment flags the payer has historically returned as CO-16. 4. **Weekly RARC Pareto** on CO-16 only — prevent the top two remark families before hiring more denial staff. When denial labour dominates staff time, re-run the arithmetic on [cost to collect](/cost-to-collect). For the management frame (prevention vs appeal capacity), see the [denials hub](/denials). ### How this code differs from ones it gets confused with **CO-16 vs [CO-109](/denials/co-109).** CO-16 says *this payer* needs more or better data on a claim it is processing. CO-109 says *this is the wrong payer or contractor* — stop fixing fields and re-route the claim. **CO-16 vs [CO-96](/denials/co-96) / [PR-204](/denials/pr-204).** Missing information is not the same as non-covered. If the plan excludes the benefit entirely, correcting fields will not create coverage. PR-204 is a patient-responsibility non-coverage signal; CO-96 is a contractual non-covered charge framing. Read the RARC and the EOB benefit language before treating either as a scrub error. **CO-16 vs [CO-22](/denials/co-22).** CO-22 is coordination of benefits — another plan may be primary. You may also see information edits on COB loops that travel with CO-16 remarks; still, the *reason* is COB order, not a missing CPT modifier. When you are unsure, the remark codes and the group code (CO vs PR vs OA) decide who is billed next — not the biller’s narrative summary. ### Questions Q: What does the CO-16 denial code description actually mean? A: X12’s short description is that the claim or service lacks information or has submission/billing error(s). In operations it means the payer could not fully adjudicate the line as submitted; the specific missing or invalid field is almost always on the companion RARC, not in the CO-16 text itself. Q: Is CO-16 a patient balance? A: The CO group code marks a contractual obligation adjustment under the remittance standards — it is not itself a PR (patient responsibility) code. Do not automatically statement the patient for a CO-16. Fix the claim or appeal; only transfer balance when a PR group code or a verified patient liability applies. Q: Should I appeal CO-16 or just correct the claim? A: Correct and resubmit when the RARC names data you can supply. Appeal when the payer already has complete, accurate data and still denies, or when the remark is factually wrong. Track labour cost — see the denials hub and cost-to-collect calculator. Q: Why does CO-16 keep coming back on the same payer? A: Usually a systemic scrub or enrollment gap (taxonomy, auth workflow, diagnosis pointer rules), not bad luck on one claim. Rank CO-16 by RARC family and fix the top sources upstream. Sources: - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes - X12 Remittance Advice Remark Codes (RARC) (X12): https://x12.org/codes/remittance-advice-remark-codes - CMS Medicare Claims Processing Manual (Pub. 100-04) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912 - CMS MLN006562 — Medicare Parts A & B Appeals Process (Centers for Medicare & Medicaid Services): https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense --- ## Denial code CO-97 — benefit included in another service already paid URL: https://rcm.today/denials/co-97 Last reviewed: 2026-07-19 CO-97 is a contractual bundling signal: the payer treated this line as included in another service already adjudicated. Start with NCCI and payer PTP edits, not with a blanket unbundle appeal. ### What CO-97 means **CO-97** (group code **CO** = contractual obligation) means the payer included the benefit for this service in the payment or allowance for another service or procedure already adjudicated. The single most common real cause in outpatient physician billing is a **procedure-to-procedure (PTP) bundling edit** — often an NCCI-style pair or a payer clone of one. First action: identify the “parent” paid line on the same claim or recent claim, then check whether a modifier or separate documentation path is actually allowed before you appeal. ### What the code actually says X12’s short description for reason code **97** is: *“The benefit for this service is included in the payment/allowance for another service/procedure that has already been adjudicated.”* ([X12 CARC](https://x12.org/codes/claim-adjustment-reason-codes), as of this page’s last review). In practice, CO-97 is the remittance language for **bundling**. Medicare’s National Correct Coding Initiative publishes PTP edits and a policy manual that explain when codes are not separately payable ([CMS NCCI](https://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits)). Many commercial payers apply NCCI, a licensed edit set, or proprietary “always bundled” lists. The CARC does not name which other code absorbed the payment — that comes from the claim’s paid lines, remark codes, and the payer’s edit rationale. Do not confuse “bundled” with “not medically necessary” or “not a covered benefit.” Those routes use different reason codes (for example non-covered paths discussed under [CO-96](/denials/co-96) and [PR-204](/denials/pr-204)). ### Most common causes and where they originate | Cause | Where it originates | How to confirm on the remit | Prevention owner | | --- | --- | --- | --- | | NCCI PTP column 1 / column 2 pair billed same day | Coding | Sibling line paid; CO-97 on the component | Coding + CDI | | Payer “always bundled” status indicator / fee schedule flag | Charge master + contracting | Zero pay with CO-97; fee schedule status B/bundled | Revenue integrity | | E/M with procedure when payer expects modifier or global package | Clinician documentation + coding | Procedure paid; E/M or add-on denied CO-97 | Coding + clinical education | | Add-on code without parent code | Charge entry | Add-on denied; parent missing or unpaid | Charge capture | | Bilateral / multi-unit coding that payer packages | Coding | Units reduced; package language in RARC | Coding | | Same service paid under a prior claim (duplicate component) | Billing ops | Prior claim reference on remit | Billing ops | Operational framing for outpatient physician/hospital outpatient denials — not a ranked national study. Validate against your NCCI version and each payer’s edit set for the date of service. ### Working the denial, in order 1. **Step 1: Read RARCs and identify the absorbing service** — List remark codes, then find which line or prior claim was paid for the related service. Without the parent code, you cannot evaluate unbundling. 2. **Step 2: Check NCCI PTP and the payer’s edit for the date of service** — Use the CMS NCCI materials and edit files for Medicare logic ([CMS NCCI](https://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits)). For commercial plans, check the payer’s code-edit policy or provider manual effective on the date of service — edits change. 3. **Step 3: Decide: correct coding vs true separate procedure** — If the pair is not separately payable, accept the contractual adjustment and fix upstream coding. If documentation supports a distinct procedural service and an allowed modifier, correct and resubmit only when the edit and payer policy allow it. 4. **Step 4: Appeal only with policy + documentation** — Appeals without the edit citation and the procedure note usually fail. Medicare appeal levels and time limits are in [MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf). Weigh labour against dollars — [cost to collect](/cost-to-collect). 5. **Step 5: Watch timely filing on corrected claims** — Replacement claims still need a live filing window. If the component was never payable, stop the appeal clock waste and retrain coding instead. ### Before you resubmit - Parent (absorbing) code and claim number are identified — Same-day lines and recent related claims both checked. - NCCI PTP or payer edit result is documented for the DOS — Include modifier indicator (0/1/9) where NCCI applies. - Operative or procedure note supports a distinct service if you are unbundling — Anatomically distinct, separate session, or other payer-accepted criterion — not just “we always bill both.” - Modifier use matches payer policy, not habit — Do not append a distinct-procedure modifier by default to clear CO-97. - Add-on codes still have a payable parent on the claim — Parent denial can cascade into component denials. - Charge master / status indicators reviewed for “bundled” flags — Especially for codes that never pay separately on this payer’s fee schedule. - Appeal vs write-off decision recorded with dollar amount — Align with the floor on the [denials](/denials) hub. ### Preventing it upstream CO-97 prevention is a **coding and charge-capture** control problem. 1. Run **PTP edit scrubbers** (NCCI and major commercial edit sets) before 837 generation. 2. Teach clinicians which services are typically packaged so documentation either supports a true separate procedure or stops prompting a second code. 3. Keep the **charge master** aligned with payer status indicators — billing a never-payable component burns denial labour for zero upside. 4. Track CO-97 dollars by parent/component pair monthly; fix the top pairs in CDI meetings. Prevention ROI shows up in first-pass yield and in lower adjudication spend ([Premier adjudication cost analysis](https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense)). See [denials](/denials) for prevention-vs-appeal arithmetic and [cost to collect](/cost-to-collect) for labour modelling. ### How this code differs from ones it gets confused with **CO-97 vs [CO-45](/denials/co-45).** CO-45 is “charge exceeds fee schedule / maximum allowable.” You may still receive a partial allowed amount. CO-97 typically pays **nothing** on the component because it was absorbed into another service’s allowance. **CO-97 vs [CO-16](/denials/co-16).** Missing information can *look* like bundling when a modifier or pointer is absent, but the fix paths differ: CO-16 is complete-the-data; CO-97 is edit logic about separately payable services. **CO-97 vs medical-necessity denials.** A medical-necessity denial challenges whether the service should be covered at all. CO-97 assumes the *component* is not separately payable even if the encounter was appropriate. Do not mass-appeal CO-97 lines without edit evidence — that pattern is how denial teams burn capacity documented as expensive in multi-facility adjudication studies ([Premier](https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense)). ### Questions Q: What does the CO-97 denial code description actually mean? A: X12 describes reason 97 as the benefit for this service being included in the payment or allowance for another service or procedure that has already been adjudicated. Operationally it is a bundling / inclusive-procedure decision, not a statement that the chart is incomplete. Q: Is CO-97 the same as an NCCI denial? A: Often related, not identical. Medicare uses NCCI PTP edits that commonly surface as CO-97 (or payer-specific equivalents). Commercial payers may use NCCI, licensed edits, or proprietary lists. Always check the edit source for that payer and date of service via CMS NCCI materials and the payer manual. Q: Can a modifier overturn CO-97? A: Only when the edit’s modifier indicator and the payer’s policy allow a distinct procedural service and the documentation supports it. Appending a modifier without meeting those tests creates compliance risk and repeat denials. Q: Should the patient be billed for a CO-97? A: CO is contractual obligation. If the component is contractually bundled, it is generally a provider write-off under the contract — not an automatic patient balance. Confirm the remittance group codes and contract terms before statementing. Sources: - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes - CMS National Correct Coding Initiative (NCCI) Policy Manual and edits (Centers for Medicare & Medicaid Services): https://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits - CMS MLN006562 — Medicare Parts A & B Appeals Process (Centers for Medicare & Medicaid Services): https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense - CMS Medicare Claims Processing Manual (Pub. 100-04) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912 --- ## Denial code CO-45 — charge exceeds fee schedule or contracted maximum URL: https://rcm.today/denials/co-45 Last reviewed: 2026-07-19 CO-45 is usually the contractual difference between billed charges and the allowed amount — not a “lost” claim. Verify the fee schedule before treating it as a recoverable denial. ### What CO-45 means **CO-45** (group code **CO** = contractual obligation) means the billed charge is higher than the fee schedule, maximum allowable, or contracted/legislated fee arrangement the payer applied. The most common real cause is simply **billing full charges against a contracted allowed amount**. First action: confirm the allowed amount against the contract or Medicare fee schedule for the date of service — most CO-45 dollars are expected write-offs, not appeal targets. ### What the code actually says X12’s short description for reason code **45** is: *“Charge exceeds fee schedule/maximum allowable or contracted/legislated fee arrangement.”* ([X12 CARC](https://x12.org/codes/claim-adjustment-reason-codes), as of this page’s last review). On a typical paid claim you will see: billed charge → allowed amount → CO-45 contractual adjustment → patient responsibility (copay/coinsurance/deductible under PR codes) → payer payment. The CO-45 piece is the **provider write-down to the allowed amount**, not proof the claim was denied in full. For Medicare Part B physician services, allowed amounts are driven by the Physician Fee Schedule; CMS publishes a [look-up tool](https://www.cms.gov/medicare/physician-fee-schedule/search) and annual rulemaking such as the [CY2026 MPFS final rule fact sheet](https://www.cms.gov/newsroom/fact-sheets/calendar-year-cy-2026-medicare-physician-fee-schedule-final-rule-cms-1832-f) (conversion factor and policy changes as of that rule). Commercial allowed amounts are **contract-specific** — this site does not publish commercial rate tables. ### Most common causes and where they originate | Cause | Where it originates | How to confirm on the remit | Prevention owner | | --- | --- | --- | --- | | Normal charge-to-allowed contractual write-off | Contract + chargemaster | Partial pay; CO-45 equals billed minus allowed (before PR) | Revenue integrity (monitor only) | | Wrong fee schedule / wrong payer product loaded | Contract management | Allowed amount differs from contract grid for that product | Managed care / contracting | | Multiple procedure / bilateral reduction applied | Payer adjudication | Reduction pattern on secondary procedures; RARC on reduction | Coding + contracting | | Out-of-network vs in-network schedule applied | Registration + enrollment | Allowed uses OON schedule; patient PR higher | Registration + enrollment | | Stale chargemaster vs updated fee schedule | Chargemaster | Systematic variance across codes after schedule update | Revenue integrity | | Legislated fee cap (e.g. certain state or federal schedules) | Payer policy | Remark citing maximum allowable or statute | Compliance + billing | Operational framing. CO-45 volume is not the same as denial rate — separate contractual adjustments from true zero-pay denials when you report KPIs ([HFMA MAP Keys](https://www.hfma.org/data-and-insights/map-initiative/map-keys/)). ### Working the denial, in order 1. **Step 1: Read RARCs and confirm it is not a zero-pay denial in disguise** — If allowed amount is greater than zero and payment plus PR plus CO-45 reconciles to billed, you are looking at a contractual adjustment, not a missing-info denial. 2. **Step 2: Verify the allowed amount against the right schedule** — Medicare: use the [PFS look-up](https://www.cms.gov/medicare/physician-fee-schedule/search) for the DOS, locality, and modifier. Commercial: pull the contract exhibit for that product. Note the fee-schedule year or contract effective date inline in your work notes. 3. **Step 3: Fork: expected write-off vs underpayment** — If allowed matches contract, post the contractual adjustment and stop. If allowed is below contract, open an underpayment dispute with contract exhibits — that is not a “coding appeal.” 4. **Step 4: Appeal only for true underpayment or misapplied schedule** — Attach the fee schedule page or contract rate. Medicare appeals process overview: [MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf). Do not appeal routine CO-45 write-offs — it destroys denial capacity ([denials hub](/denials)). 5. **Step 5: Reconcile to net collection metrics** — Contractual adjustments belong in net collection rate analysis, not in “denial rate” vanity metrics. See [benchmarks](/benchmarks). ### Before you resubmit - Billed, allowed, CO-45, PR, and payment reconciling math is checked — If the math balances to the contract, do not resubmit. - Fee schedule or contract exhibit for that DOS is attached to the ticket — Include product, locality, and modifiers. - Multiple-procedure reductions match contract language — Secondary procedures often reduce by rule, not by error. - Provider network status on DOS is confirmed — OON schedules explain many “low allow” surprises. - Chargemaster not systematically below or wildly above market without reason — Charges should still exceed allowables; that is normal. - Underpayment threshold met before dispute labour is spent — Compare recovery to labour via [cost to collect](/cost-to-collect). ### Preventing it upstream You do not “prevent” legitimate CO-45 write-offs — you **predict and post** them. What you prevent is *false* CO-45 work: 1. Keep **contract rate tables** loaded correctly by product and effective date. 2. Separate **contractual adjustment** queues from **true denial** queues so staff do not appeal noise. 3. After each major Medicare PFS update (see [CY2026 MPFS fact sheet](https://www.cms.gov/newsroom/fact-sheets/calendar-year-cy-2026-medicare-physician-fee-schedule-final-rule-cms-1832-f) for that rule’s as-of context), refresh expected allowables and variance reports. 4. Report net collection and denial rate as distinct KPIs ([HFMA MAP Keys](https://www.hfma.org/data-and-insights/map-initiative/map-keys/); [benchmarks](/benchmarks)). Labour spent appealing expected write-offs is pure cost-to-collect waste ([calculator](/cost-to-collect); [denials](/denials)). ### How this code differs from ones it gets confused with **CO-45 vs [CO-97](/denials/co-97).** CO-97 zeros a component because it is bundled into another service. CO-45 reduces a line to an allowed amount that may still pay. **CO-45 vs [CO-16](/denials/co-16).** Missing information is a stop-the-claim problem. CO-45 usually appears on adjudicated, often paid claims. **CO-45 vs patient responsibility codes.** Deductible, coinsurance, and copay are PR group codes. Do not reclass CO-45 to the patient simply because the charge was reduced — the contract, not the patient, owns that delta unless a PR code says otherwise. For collection-rate context when contractual adjustments dominate the remittance, use [benchmarks](/benchmarks). ### Questions Q: What does the CO-45 denial code description actually mean? A: X12 describes reason 45 as the charge exceeding the fee schedule, maximum allowable, or contracted/legislated fee arrangement. On most remits it is the contractual write-off from billed charges down to the allowed amount. Q: Is CO-45 a denial I should appeal? A: Usually no. Appeal or dispute only when the allowed amount is lower than your contract or the correct Medicare fee schedule for that date of service. Routine billed-to-allowed differences are expected under fee-for-service contracts. Q: Where do I verify a Medicare allowed amount? A: CMS Physician Fee Schedule Look-Up Tool for the date of service, and the applicable PFS rulemaking for conversion-factor and policy context (for example the CY2026 MPFS final rule fact sheet). Always record the as-of date of the schedule you used. Q: Does CO-45 mean the patient owes the difference between billed and allowed? A: Not by itself. In-network contracted care typically forbids balance-billing that contractual difference. Patient liability appears under PR group codes when applicable. Confirm contract and state rules before statementing. Sources: - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes - CMS Physician Fee Schedule Look-Up Tool (Centers for Medicare & Medicaid Services): https://www.cms.gov/medicare/physician-fee-schedule/search - Calendar Year (CY) 2026 Medicare Physician Fee Schedule Final Rule (CMS-1832-F) fact sheet (Centers for Medicare & Medicaid Services): https://www.cms.gov/newsroom/fact-sheets/calendar-year-cy-2026-medicare-physician-fee-schedule-final-rule-cms-1832-f - CMS MLN006562 — Medicare Parts A & B Appeals Process (Centers for Medicare & Medicaid Services): https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf - HFMA MAP Keys — industry-standard revenue cycle KPIs (HFMA): https://www.hfma.org/data-and-insights/map-initiative/map-keys/ - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense --- ## Denial code CO-22 — this care may be covered by another payer (COB) URL: https://rcm.today/denials/co-22 Last reviewed: 2026-07-19 CO-22 is a coordination-of-benefits signal: the payer believes another plan should pay first. Fix the primary/secondary order before resubmitting the same claim to the same payer. ### What CO-22 means **CO-22** (group code **CO** = contractual obligation) means the payer is adjusting the claim because **another payer may be responsible under coordination of benefits**. The most common real cause is outdated or incomplete other-insurance information at registration. First action: verify active coverages and primary-payer order for the date of service, then bill the correct primary — do not simply rebill the same payer with no COB change. ### What the code actually says X12’s short description for reason code **22** is: *“This care may be covered by another payer per coordination of benefits.”* ([X12 CARC](https://x12.org/codes/claim-adjustment-reason-codes), as of this page’s last review). COB is the set of rules that decide which plan pays first when a patient has more than one. For Medicare beneficiaries with other coverage, CMS’s Medicare Secondary Payer rules describe common situations (working aged, GHP, liability, no-fault, workers’ compensation, and others) in the [MSP manual chapter on MSP situations](https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf) (as of that manual publication). Commercial plans apply their own COB provisions and often require an other-payer paid amount on secondary claims. CO-22 is **not** a final statement that this payer will never pay — it is a stop until primary liability is resolved. Remark codes may name the other payer type or the missing COB data ([X12 RARC](https://x12.org/codes/remittance-advice-remark-codes)). ### Most common causes and where they originate | Cause | Where it originates | How to confirm on the remit | Prevention owner | | --- | --- | --- | --- | | Patient has active commercial primary; Medicare billed first incorrectly | Registration / MSP questionnaire | CO-22 with MSP or other-insurance RARC | Registration + MSP process | | Dual commercial plans; birthday rule or subscriber order wrong | Registration | CO-22; portal shows other carrier | Front desk | | Workers’ comp / auto / liability should be primary | Intake + case type | Remark on accident, WC, or liability | Intake + billing specialty desk | | Other coverage terminated but payer file still shows it | Eligibility | Patient insists single coverage; payer COB file stale | Billing + patient COB update | | Secondary billed without primary EOB / payment info | Secondary billing | CO-22 or COB information RARC on secondary | Billing ops | | Divorce / dependent coverage order incorrect | Registration | Dependent on two plans; order disputed | Registration | Operational framing for ambulatory billing. Always confirm COB against payer responses for the date of service — not against last year’s registration screenshot. ### Working the denial, in order 1. **Step 1: Read RARCs and payer COB messages** — Capture which other payer the remittance implies. Portal messages and eligibility COB segments often name the primary carrier. 2. **Step 2: Re-run eligibility and MSP / other-insurance questions for the DOS** — For Medicare, walk the MSP questionnaire scenarios in light of [CMS MSP guidance](https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf). For commercial, pull both carriers’ eligibility COB. 3. **Step 3: Establish primary and bill primary to conclusion** — Do not appeal CO-22 as if it were a medical-necessity denial. Obtain the primary determination (pay, deny, or patient liability) first. 4. **Step 4: Bill secondary with primary adjudication data** — Include payer paid amount, adjustments, and patient liability as the secondary requires. Missing primary data often produces another COB rejection. 5. **Step 5: If both payers refuse primary, escalate with evidence** — Use written COB determinations. Formal Medicare appeals, when applicable, follow [MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf). Track timely-filing on each plan separately. 6. **Step 6: Update the permanent coverage record** — A worked CO-22 that leaves registration data wrong will recur on the next visit. Measure labour via [cost to collect](/cost-to-collect). ### Before you resubmit - All active coverages for the DOS are listed with subscriber IDs — Including Medicare, Medicaid, commercial, and accident riders when relevant. - Primary payer decision is documented (EOB or denial) — Secondary claims need primary adjudication data. - MSP questionnaire answers match the billing order for Medicare patients — Working aged, disability GHP, ESRD, liability, no-fault, WC checked as applicable. - Accident-related claims have the correct casualty carrier billed first when required — Do not force medical primary when liability/no-fault is primary under the plan rules. - Timely-filing deadlines for each payer are calendarised — Primary delays can burn secondary clocks — escalate early. - Patient is not balance-billed while COB is unresolved unless policy allows — Confirm financial policy and state rules. - Registration system updated so the next claim inherits the fix — Workqueue closed only after master data change. ### Preventing it upstream CO-22 prevention is almost entirely **registration and eligibility**. 1. Require **full other-insurance capture** at scheduling and check-in, not only the card the patient hands over first. 2. For Medicare, complete **MSP screening** whenever coverage or employment status changes ([CMS MSP](https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf)). 3. Automate **eligibility COB segment** review before first claim. 4. Create a **COB workqueue SLA** measured in days, not in appeal letters — delay is what kills secondary timely filing. Management frame: [denials hub](/denials). Labour model: [cost to collect](/cost-to-collect). ### How this code differs from ones it gets confused with **CO-22 vs [CO-109](/denials/co-109).** CO-22 says another payer may be primary under COB rules while this payer might still have secondary liability. CO-109 says this payer/contractor is **not the correct entity** for the claim at all — re-route, do not just reorder COB fields on the same plan. **CO-22 vs [OA-23](/denials/oa-23).** OA-23 reports the **impact of a prior payer’s adjudication** on this remittance (common on secondary claims). It is an adjustment explanation, not the same as “we refuse primary because of COB.” **CO-22 vs [CO-16](/denials/co-16).** You may see information-style remarks when COB loops are incomplete. If the root issue is other-payer order, treat it as COB work, not as a generic missing-modifier fix. These two pages should be cross-trained: [CO-109](/denials/co-109) and CO-22 are the usual wrong-payer / COB pair. ### Questions Q: What does the CO-22 denial code description actually mean? A: X12 describes reason 22 as care that may be covered by another payer per coordination of benefits. The payer is pointing at COB order or other-insurance responsibility, not at medical necessity or a bundled procedure. Q: Does CO-22 mean this insurance will never pay? A: Not necessarily. Many CO-22s resolve by billing the true primary first and then this plan as secondary. Some resolve when outdated other-coverage is removed from the payer’s COB file. Q: How do Medicare Secondary Payer rules relate to CO-22? A: When Medicare is billed but another payer is primary under MSP, remittances often surface COB-related adjustments. CMS MSP manual materials describe the situations in which Medicare is secondary. Always match the questionnaire and evidence to the date of service. Q: Should I appeal CO-22 immediately? A: Usually no. Investigate coverage order and bill the correct primary first. Appeal when you have written proof this payer is primary and it still refuses after correct billing. Sources: - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes - X12 Remittance Advice Remark Codes (RARC) (X12): https://x12.org/codes/remittance-advice-remark-codes - CMS Medicare Secondary Payer Manual, Chapter 3 (MSP situations) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf - CMS MLN006562 — Medicare Parts A & B Appeals Process (Centers for Medicare & Medicaid Services): https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf - CMS Medicare Claims Processing Manual (Pub. 100-04) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912 - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense --- ## Denial code CO-96 — non-covered charge(s) URL: https://rcm.today/denials/co-96 Last reviewed: 2026-07-19 CO-96 means the payer treated the charge as not covered under the plan’s benefit design or coverage rules. Confirm the exclusion in writing before you treat it as a fixable coding error. ### What CO-96 means **CO-96** (group code **CO** = contractual obligation) means the payer adjudicated the charge as **non-covered**. The most common real cause is a plan exclusion or benefit limitation for that service on that date — not a missing digit on the claim. First action: pull the remittance remark codes and the plan’s coverage language for the service; only then decide among patient liability, appeal on coverage policy, or write-off. ### What the code actually says X12’s short description for reason code **96** is: *“Non-covered charge(s).”* ([X12 CARC](https://x12.org/codes/claim-adjustment-reason-codes), as of this page’s last review). That sentence is intentionally broad. It does not tell you *why* the charge is non-covered — statutory exclusion, plan rider, frequency limit, investigational status, or wrong benefit category all can surface as 96 depending on the payer’s mapping. Companion **RARCs** usually carry the actionable detail ([X12 RARC](https://x12.org/codes/remittance-advice-remark-codes)). Medicare coverage determinations and claims processing context live in CMS manuals such as the [Medicare Claims Processing Manual](https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912); commercial plans rely on the member’s certificate of coverage and medical policy library. Always record the **as-of** date of the policy you cite — coverage changes by plan year. ### Most common causes and where they originate | Cause | Where it originates | How to confirm on the remit | Prevention owner | | --- | --- | --- | --- | | Service excluded in plan certificate | Benefit design | RARC on non-covered / exclusion; EOB benefit note | Financial counselling + eligibility | | Frequency or unit limit exhausted | Utilization / prior visits | Remark on maximum allowed / frequency | Auth + scheduling | | Experimental / investigational per medical policy | Payer medical policy | Policy ID on denial letter or portal | Clinical + UM | | Wrong place of service or benefit category for coverage | Coding + scheduling | Covered in facility but not office (or reverse) | Coding | | Diagnosis does not meet coverage criteria (mapped to non-covered) | Coding + documentation | Medical policy diagnosis list vs coded ICD | CDI + coding | | Carve-out benefit billed to medical instead of carve-out vendor | Registration | Portal points to behavioral or dental vendor | Registration | Operational framing. Pull your top CO-96 procedure codes against plan policies — national averages are not a substitute for your mix. ### Working the denial, in order 1. **Step 1: Read RARCs and the EOB narrative** — Non-covered is a category; the remark and EOB sentence name the theory (exclusion, frequency, investigational, etc.). 2. **Step 2: Pull plan coverage language for the DOS** — Certificate of coverage, medical policy, or Medicare coverage document effective on the date of service. Snapshot the version date in the ticket. 3. **Step 3: Fork: true exclusion vs correctable coding/coverage criteria** — If documentation or diagnosis can meet published criteria, correct and resubmit or re-open. If the benefit is excluded, stop coding gymnastics. 4. **Step 4: Patient liability vs provider write-off vs appeal** — Check whether a PR group code also appears and whether an ABN/waiver or estimate process applied. Policy appeals need the coverage citation; Medicare levels are in [MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf). 5. **Step 5: Timely filing and advance notice process fix** — If staff should have known the exclusion before service, fix eligibility counselling. Track labour on [cost to collect](/cost-to-collect). ### Before you resubmit - RARC and EOB non-covered reason copied into the ticket — Not just “CO-96.” - Plan policy or certificate section cited with effective date — As-of date recorded for the coverage rule used. - Diagnosis and documentation compared to coverage criteria — Only resubmit when criteria can actually be met. - Frequency limits and prior utilization checked — Including other providers in the same plan year when visible. - Carve-out / correct payer already ruled out — Compare to [CO-109](/denials/co-109) wrong-payer patterns. - Patient communication path decided (estimate, appeal, self-pay) — Do not silent-statement without benefit confirmation. - Appeal package includes policy text + clinical rationale if appealing — Skip appeal when exclusion is explicit and undisputed. ### Preventing it upstream CO-96 prevention is **eligibility + financial counselling + medical policy checks before service**. 1. Maintain a **non-covered services list** for top payers (cosmetic carve-outs, specific POS rules, common investigational flags). 2. Run **benefit verification** that answers “is this code covered for this diagnosis?” — not only “is the plan active?” 3. For high-dollar elective services, require **written coverage confirmation** or a signed self-pay estimate. 4. Feed repeated CO-96 codes into scheduling alerts. See [denials](/denials) for prevention-vs-appeal capacity and [cost to collect](/cost-to-collect) for labour cost when non-covered work is discovered after the visit. ### How this code differs from ones it gets confused with **CO-96 vs [PR-204](/denials/pr-204).** Both can involve non-covered services. **PR-204** is a patient-responsibility group code: the remittance is assigning liability to the patient under the benefit plan. **CO-96** is contractual-obligation framing of a non-covered charge. Read the **group code** before you statement the patient. **CO-96 vs [CO-45](/denials/co-45).** CO-45 reduces a covered charge to an allowed amount. CO-96 says the charge is not covered (typically no allowed amount for that benefit). **CO-96 vs [CO-97](/denials/co-97).** Bundling assumes the service is packaged into another payable service. Non-covered means the plan is not buying that benefit as billed. When remarks are ambiguous, pull the EOB sentence and the plan policy before choosing an appeal template. ### Questions Q: What does the CO-96 denial code description actually mean? A: X12’s short description is simply “Non-covered charge(s).” It means the payer treated the billed charge as not covered. The specific exclusion, limit, or policy theory is usually in the RARC and EOB text, not in the three-character reason code alone. Q: Can I fix CO-96 by changing the CPT code? A: Only if the original code was factually wrong and the correct code is covered. Recoding solely to obtain payment for a non-covered service is a compliance problem. Fix documentation and coding accuracy first; do not “code to coverage.” Q: Is CO-96 always billable to the patient? A: No. Group code CO is not PR. Some non-covered services are patient responsibility under plan rules; some are provider liability depending on notice, network, and state law. Confirm PR codes, estimates, and waivers before statementing. Q: When is a CO-96 appeal worth it? A: When you have plan language or medical policy showing the service should be covered for this diagnosis and setting, plus clinical documentation. Pure benefit exclusions rarely overturn on appeal; spend labour using a dollar floor ([denials hub](/denials)). Sources: - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes - X12 Remittance Advice Remark Codes (RARC) (X12): https://x12.org/codes/remittance-advice-remark-codes - CMS Medicare Claims Processing Manual (Pub. 100-04) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912 - CMS MLN006562 — Medicare Parts A & B Appeals Process (Centers for Medicare & Medicaid Services): https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense --- ## Denial code OA-23 — impact of prior payer(s) adjudication URL: https://rcm.today/denials/oa-23 Last reviewed: 2026-07-19 OA-23 is an other-adjustment code that explains how a prior payer’s payment or adjustments affected this remittance. It is common on secondary claims and is often informational rather than a standalone “denial.” ### What OA-23 means **OA-23** uses group code **OA** (other adjustment) with reason **23**: the line reflects the **impact of prior payer(s) adjudication**, including payments and/or adjustments. The most common setting is a **secondary claim** where this payer is coordinating after a primary remittance. First action: reconcile the primary EOB amounts to the secondary remit before changing coding or appealing. ### What the code actually says X12’s short description for reason code **23** is: *“The impact of prior payer(s) adjudication including payments and/or adjustments.”* ([X12 CARC](https://x12.org/codes/claim-adjustment-reason-codes), as of this page’s last review). Paired with **OA**, it is not the same financial story as a **CO** contractual denial or a **PR** patient-balance code. In secondary billing, the secondary payer must know what the primary allowed, paid, and adjusted. OA-23 often appears as the adjustment that accounts for primary activity so the secondary payment math works. It can sit beside patient responsibility or small secondary payments without meaning “appeal me.” HIPAA remittance standards use these reason codes across Medicare and commercial payers; claims processing context for Medicare is in the [Claims Processing Manual](https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912). COB / MSP background when Medicare is involved is in the [MSP manual materials](https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf). ### Most common causes and where they originate | Cause | Where it originates | How to confirm on the remit | Prevention owner | | --- | --- | --- | --- | | Normal secondary adjudication after primary payment | Secondary billing | OA-23 with secondary pay or PR; primary claim cited | Billing ops (reconcile, don’t rework) | | Primary allowed/paid amounts sent incorrectly to secondary | Secondary claim build | Secondary under/over pays vs contract; mismatch to primary EOB | Billing ops | | Primary denial not attached; secondary treats as prior adjudication | COB workflow | OA-23 with zero secondary pay; primary was denied | Denial + COB desk | | Multiple prior payers (tertiary) stacked incorrectly | Billing ops | More than one prior payer loop; residual patient liability odd | Billing ops | | Duplicate primary payment reported | Payment posting | Secondary adjusts as if primary paid twice | Cash posting | | COB order wrong — “secondary” was actually primary | Registration | Compare to [CO-22](/denials/co-22) history on the account | Registration | Operational framing for professional and facility secondary claims. Always tie OA-23 back to the primary 835/EOB line by line. ### Working the denial, in order 1. **Step 1: Read RARCs and pull the primary remittance** — OA-23 without the primary EOB is unworkable. Match procedure lines, modifiers, and dates. 2. **Step 2: Reconcile primary paid + primary adjustments + patient liability** — Secondary payment should make sense against remaining liability under the secondary contract. If the math works, post and close. 3. **Step 3: If residual looks wrong, check claim build — not the CPT first** — Wrong CAS segments, missing primary paid amount, or wrong claim frequency create secondary noise that looks like a clinical denial. 4. **Step 4: Correct secondary submission or reopen COB order** — If primary was never billed correctly, fix primary first ([CO-22](/denials/co-22), [CO-109](/denials/co-109)). Use appeals only when secondary underpaid vs its own policy despite correct primary data ([MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf) for Medicare ladder overview). 5. **Step 5: Watch each payer’s timely-filing clock** — Secondary clocks often run from primary adjudication or from DOS depending on plan — read the manual for that payer. ### Before you resubmit - Primary EOB/835 line matched to the secondary line — Same DOS, codes, and modifiers. - Primary paid, allowed, and adjustment amounts entered as the secondary requires — Portal vs 837 requirements can differ. - Patient liability not double-stated across primary and secondary — Posting rules checked before patient statement. - COB order still correct after primary outcome — A primary denial can change next steps. - Tertiary coverage considered if residual remains — Do not age secondary AR while a tertiary exists. - Appeal threshold met for true secondary underpayment — Compare to labour on [cost to collect](/cost-to-collect). ### Preventing it upstream OA-23 “prevention” is mostly **clean secondary claim construction** and **COB master data**: 1. Standardise primary-EOB capture fields in the billing system. 2. Train posters not to reclassify OA-23 as a coding denial. 3. SLA the handoff from primary finalisation to secondary drop. 4. Fix registration COB so secondaries are not surprises ([CO-22](/denials/co-22)). Management context: [denials](/denials). Labour: [cost to collect](/cost-to-collect). ### How this code differs from ones it gets confused with **OA-23 vs [CO-22](/denials/co-22).** CO-22 refuses or adjusts because another payer may be primary. OA-23 explains the monetary impact of a prior payer that already adjudicated. **OA-23 vs [CO-45](/denials/co-45).** CO-45 is this payer’s contractual write-off to its allowed amount. OA-23 points at prior payer math. Both can appear on one secondary remit — read each CAS segment separately. **OA-23 vs [CO-109](/denials/co-109).** Wrong payer/contractor is a routing problem. OA-23 assumes this payer is adjudicating in a coordination context. If staff treat every OA-23 as an appeal, secondary AR will drown in false work. ### Questions Q: What does the OA-23 denial code description actually mean? A: X12 describes reason 23 as the impact of prior payer(s) adjudication, including payments and/or adjustments. With group code OA, it usually explains secondary (or subsequent) coordination math rather than a primary medical-necessity denial. Q: Is OA-23 always a denial? A: No. It often appears on paid secondary remittances as an adjustment explanation. Evaluate the whole line: payment, PR, and other CARCs before opening a denial work item. Q: Why do I see OA-23 next to patient responsibility? A: After primary payment and contractual adjustments, residual deductible or coinsurance may remain. Secondary may pay part, assign PR, and still show OA-23 for the prior payer impact. Reconcile before billing the patient. Q: Should coding change a claim that only has OA-23? A: Not first. Reconcile primary data and COB order. Change coding only if the primary or secondary outcome shows a true coding defect independent of coordination math. Sources: - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes - CMS Medicare Claims Processing Manual (Pub. 100-04) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912 - CMS Medicare Secondary Payer Manual, Chapter 3 (MSP situations) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf - CMS MLN006562 — Medicare Parts A & B Appeals Process (Centers for Medicare & Medicaid Services): https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense --- ## Denial code CO-109 — claim not covered by this payer/contractor URL: https://rcm.today/denials/co-109 Last reviewed: 2026-07-19 CO-109 means you billed the wrong payer or the wrong contractor. Stop polishing claim fields for this plan and re-route the claim to the entity that actually owns adjudication. ### What CO-109 means **CO-109** (group code **CO** = contractual obligation) means this payer or contractor is stating the claim/service is **not covered by them** and must be sent to the **correct** payer or contractor. The most common real cause is wrong plan selection at registration or wrong Medicare Administrative Contractor / plan footprint. First action: identify the correct payer ID and rebill there — do not treat this as a missing-modifier CO-16 fix. ### What the code actually says X12’s short description for reason code **109** is: *“Claim/service not covered by this payer/contractor. You must send the claim/service to the correct payer/contractor.”* ([X12 CARC](https://x12.org/codes/claim-adjustment-reason-codes), as of this page’s last review). That is a **routing** instruction. It differs from “non-covered benefit under this plan” ([CO-96](/denials/co-96)) and from “another plan may be primary under COB” ([CO-22](/denials/co-22)), though real accounts sometimes hit more than one of these in sequence. Medicare Fee-for-Service claims must go to the correct MAC and claim type; processing rules are in the [Medicare Claims Processing Manual](https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912). When Medicare vs other coverage is the issue, use [MSP guidance](https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf) to decide order — but if the remit says CO-109, this entity is saying it is not the right destination at all. ### Most common causes and where they originate | Cause | Where it originates | How to confirm on the remit | Prevention owner | | --- | --- | --- | --- | | Wrong commercial payer ID / plan selected | Registration | CO-109; eligibility shows different carrier | Front desk + eligibility | | Medicare billed to wrong MAC or wrong claim type | Billing ops | Contractor rejection language; MAC footprint | Billing ops | | Medicaid vs managed Medicaid plan mix-up | Registration | Fee-for-service vs MCO payer IDs | Registration | | Workers’ comp or liability carrier should receive the claim | Intake | Accident indicators; different carrier on file | Intake | | Payer ID for national plan vs local Blue plan incorrect | Clearinghouse setup | BlueCard / home plan routing remarks | Billing ops + enrollment | | Vendor carve-out (behavioral, dental, vision) owns the benefit | Registration + eligibility | Portal directs to carve-out administrator | Registration | Operational framing. Clearinghouse rejection reports often show the same root cause before a formal 835 CO-109 appears. ### Working the denial, in order 1. **Step 1: Read RARCs and capture the directed payer if named** — Some remits name the correct contractor or plan. Copy it exactly. 2. **Step 2: Re-verify eligibility and payer ID for the DOS** — Do not trust the superbill’s payer default. Pull a fresh eligibility response. 3. **Step 3: Rebill the correct payer; do not “correct” the wrong one endlessly** — Field-level fixes on the wrong payer waste timely filing. Open a new claim to the right destination with original DOS documentation. 4. **Step 4: If two entities bounce the claim, escalate with both responses** — Document each CO-109/CO-22. Medicare appeal overview when Medicare is in the dispute: [MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf). MSP situations: [CMS MSP chapter](https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf). 5. **Step 5: Fix the registration master and clearinghouse map** — Permanent payer ID tables prevent recurrence. Measure wasted labour on [cost to collect](/cost-to-collect). ### Before you resubmit - Correct payer name, payer ID, and product verified on eligibility — Screenshot or transaction ID stored. - Medicare MAC / contractor footprint confirmed for the provider address of service — Especially after practice relocation or enrollment changes. - Carve-out administrators checked for BH / dental / vision codes — Medical payer CO-109 is common when carve-out applies. - Accident / WC / liability carriers ruled in or out — Wrong medical primary creates multi-month AR. - Timely-filing clock calculated for the correct payer — Original wrong submission may not protect you — know each plan’s rule. - Clearinghouse enrollment for the destination payer is active — Avoid a second rejection for enrollment. - Patient not billed as if the service were non-covered without confirming — Wrong payer ≠ non-covered benefit. ### Preventing it upstream CO-109 is a **registration, eligibility, and payer-master** failure mode. 1. Prefer **eligibility-driven payer selection** over staff memory of payer IDs. 2. Maintain a **validated payer ID table** (national vs local Blue plans especially). 3. Train intake to capture **accident and carve-out** signals before the first claim. 4. Audit the top CO-109 destinations monthly — one wrong default can produce hundreds of claims. See [denials](/denials) and [cost to collect](/cost-to-collect). Cross-train with [CO-22](/denials/co-22). ### How this code differs from ones it gets confused with **CO-109 vs [CO-22](/denials/co-22).** CO-22 is coordination of benefits — another plan may be primary, but this plan might still be secondary. CO-109 says this entity is the **wrong destination**. The operational next step differs: COB investigation vs re-route. **CO-109 vs [CO-96](/denials/co-96).** Non-covered benefit assumes the correct plan adjudicated coverage and said no. Wrong payer means the correct plan has not yet adjudicated. **CO-109 vs [CO-16](/denials/co-16).** Do not sink days into missing fields on a claim the payer will never own. Route first, scrub second. These pages link to each other because wrong-payer and COB queues are adjacent in real AR: [CO-22](/denials/co-22). ### Questions Q: What does the CO-109 denial code description actually mean? A: X12 states that the claim or service is not covered by this payer or contractor and must be sent to the correct payer or contractor. It is a routing message: you billed the wrong entity for adjudication. Q: Is CO-109 the same as a non-covered service? A: No. Non-covered (for example CO-96 or PR-204) is a coverage decision by the plan that owns the claim. CO-109 means this plan is not the right plan or contractor to make that decision. Q: Can I appeal CO-109 to force this payer to process? A: Only if you have evidence this really is the correct payer and the CO-109 is wrong. Otherwise rebill the correct entity. Appeals without routing evidence waste timely filing elsewhere. Q: How does Medicare contractor routing relate to CO-109? A: Medicare FFS claims must go to the appropriate contractor and claim pathway. Billing the wrong MAC or program can return contractor-level rejections consistent with “send to the correct contractor.” Confirm enrollment and service-area routing in CMS claims processing materials. Sources: - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes - CMS Medicare Claims Processing Manual (Pub. 100-04) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912 - CMS Medicare Secondary Payer Manual, Chapter 3 (MSP situations) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/msp105c03.pdf - CMS MLN006562 — Medicare Parts A & B Appeals Process (Centers for Medicare & Medicaid Services): https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf - X12 Remittance Advice Remark Codes (RARC) (X12): https://x12.org/codes/remittance-advice-remark-codes - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense --- ## Denial code PR-204 — not covered under the patient’s current benefit plan URL: https://rcm.today/denials/pr-204 Last reviewed: 2026-07-19 PR-204 is a patient-responsibility code: the plan says this service, equipment, or drug is not covered under the member’s current benefits. Confirm the exclusion and notice rules before you statement the patient. ### What PR-204 means **PR-204** uses group code **PR** (patient responsibility) with reason **204**: the service, equipment, or drug is **not covered under the patient’s current benefit plan**. Unlike CO contractual write-offs, the remittance is assigning this amount to the **patient** side of the ledger. First action: verify the benefit language and any estimate/waiver requirements, then decide among patient billing, coverage appeal, or provider courtesy adjustment — do not silently absorb or blindly statement without that check. ### What the code actually says X12’s short description for reason code **204** is: *“This service/equipment/drug is not covered under the patient’s current benefit plan.”* ([X12 CARC](https://x12.org/codes/claim-adjustment-reason-codes), as of this page’s last review). The **PR** group code is the load-bearing part for patient accounting: HIPAA remittances use PR when the payer reports patient liability. Companion RARCs and the EOB narrative usually specify whether the issue is an exclusion, a missing rider, a pharmacy vs medical benefit mismatch, or a plan-year limitation ([X12 RARC](https://x12.org/codes/remittance-advice-remark-codes)). Medicare and commercial plans document coverage differently; CMS claims processing and appeals materials ([Claims Processing Manual](https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912); [MLN006562 appeals overview](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf)) apply when Medicare is the payer. Always store the **plan year / policy as-of date** you relied on. ### Most common causes and where they originate | Cause | Where it originates | How to confirm on the remit | Prevention owner | | --- | --- | --- | --- | | Plan exclusion (service never covered) | Benefit design | PR-204 + exclusion RARC; certificate cites exclusion | Financial counselling | | Covered only with rider patient did not buy | Eligibility | Remark on rider / optional benefit | Eligibility + counselling | | Drug or DME under pharmacy / DME benefit, not medical claim | Billing pathway | Reject points to pharmacy benefit manager or DME MAC | Billing ops | | Frequency or annual maximum already met | Utilization | Maximum reached language on EOB | Scheduling + auth | | Cosmetic or convenience service coded as covered E/M or procedure | Coding + clinical intent | Policy exclusion for cosmetic | Coding + clinicians | | Out-of-network service treated as non-covered under plan rules | Network status | OON non-covered vs higher PR cost-share — read carefully | Registration + counselling | Operational framing. Network cost-share (higher coinsurance) is not the same as non-covered — do not map every high PR balance to 204. ### Working the denial, in order 1. **Step 1: Read RARCs and confirm group code PR** — If the same reason appears under CO, patient-statement rules differ. Trust the 835 group code. 2. **Step 2: Verify benefit language for the DOS and plan year** — Certificate of coverage, formulary, or medical policy. Snapshot the version date. 3. **Step 3: Check notice / estimate / ABN-style requirements** — Some settings require advance notice before holding the patient financially responsible. Follow payer and state rules applicable to your setting — do not invent a universal form. 4. **Step 4: Fork: patient bill vs coverage appeal vs rebill correct benefit** — Pharmacy/DME pathway mistakes are rebills, not patient fights. True exclusions with valid notice are patient bills. Disputed coverage uses the appeal ladder ([MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf) for Medicare). 5. **Step 5: Timely filing if rebill or corrected claim is the path** — Patient statement aging is separate from payer appeal deadlines — track both. 6. **Step 6: Close the loop with financial counselling scripts** — Repeated PR-204 on the same code is an estimate-process failure. Labour cost: [cost to collect](/cost-to-collect). ### Before you resubmit - Group code is PR and amount matches the EOB patient liability — No silent transfer from CO without remit support. - Benefit exclusion or limitation cited with as-of date — Plan year boundaries matter. - Pharmacy / DME / carve-out pathway ruled out — Wrong benefit channel is not the patient’s coding error. - Advance estimate or notice requirements checked for your setting — Document what was given to the patient pre-service. - Appeal only with policy contradiction + clinical support — Use a dollar floor from the [denials](/denials) hub. - Patient statement language matches the actual reason — “Insurance denied” is not enough — name non-covered benefit when true. - Charity / hardship policy considered when appropriate — Operational compassion is still a policy, not ad hoc AR deletion without rules. ### Preventing it upstream PR-204 prevention is **benefit verification and honest estimates**: 1. Verify **coverage of the service**, not only active insurance. 2. For self-pay-likely services, give **written estimates** before care when your setting requires or benefits from them. 3. Route drugs and DME to the **correct benefit channel** at order entry. 4. Track PR-204 by procedure code monthly and add scheduling alerts for chronic offenders. Hub arithmetic: [denials](/denials). Labour: [cost to collect](/cost-to-collect). ### How this code differs from ones it gets confused with **PR-204 vs [CO-96](/denials/co-96).** Both involve non-covered charges. **PR** assigns patient responsibility on the remittance; **CO** is contractual obligation framing. Never statement from the reason number alone — read the group code. **PR-204 vs [CO-45](/denials/co-45).** CO-45 is the contractual write-off to an allowed amount on a covered service. PR-204 is non-coverage under the benefit plan, not a fee-schedule reduction. **PR-204 vs ordinary PR deductible/coinsurance codes.** Deductible and coinsurance assume a covered service with patient cost-share. PR-204 says the plan is not covering the service under current benefits. If you are also seeing wrong-payer patterns, compare [CO-109](/denials/co-109) before you tell the patient the benefit does not exist. ### Questions Q: What does the PR-204 denial code description actually mean? A: X12 describes reason 204 as a service, equipment, or drug not covered under the patient’s current benefit plan. With group code PR, the remittance is reporting that amount as patient responsibility rather than a provider contractual write-off. Q: Can I bill the patient the full charged amount on PR-204? A: Often the patient may be billed for non-covered services when plan rules and applicable notice requirements allow it — but charge, allowed, and patient-responsibility amounts on the remit still need reconciliation, and state/federal balance-billing and notice rules may apply. Confirm before statementing. Q: Is PR-204 the same as CO-96? A: Related concept (non-covered), different liability path. CO-96 is contractual-obligation non-covered charge framing; PR-204 is patient-responsibility non-coverage. Workflow for AR posters differs. Q: Should every PR-204 be appealed? A: No. Appeal when plan language or medical policy contradicts the denial for this patient and service. Pure exclusions with clear certificate language are poor appeal candidates; invest labour using a dollar floor. Sources: - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes - X12 Remittance Advice Remark Codes (RARC) (X12): https://x12.org/codes/remittance-advice-remark-codes - CMS Medicare Claims Processing Manual (Pub. 100-04) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912 - CMS MLN006562 — Medicare Parts A & B Appeals Process (Centers for Medicare & Medicaid Services): https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf - Premier: claims adjudication costs providers $25.7 billion (Premier Inc.): https://premierinc.com/newsroom/policy/claims-adjudication-costs-providers-257-billion-18-billion-is-potentially-unnecessary-expense --- ## Prior authorization: where auths actually fail URL: https://rcm.today/prior-auth Last reviewed: 2026-07-28 Most auth-related denials are not clinical disagreements — they are calendar, counter, and claim-field failures that were visible before the visit. This page walks the eligibility-to-claim flow, the failure modes that turn into CO-197-class denials, and the checklist that prevents them. ### Direct answer **Prior authorization** is a payer’s advance approval, before a service is rendered, that the service meets its coverage criteria. It is a condition of payment, not a guarantee of payment. The failure modes that cost practices money are overwhelmingly operational: no auth obtained for a service that required one (surfaces as reason code **197** — precertification/authorization absent), an **authorization number missing or invalid on the claim** (reason code **15**, often riding with [CO-16](/denials/co-16)), an **expired auth** or a date of service outside the validity window, and **units or visits beyond what was authorized** (reason code **198**). Prevention is a front-end discipline: verify before the visit, track validity windows, attach the auth number to the claim, and document medical necessity for the authorized service. ### What prior authorization is (and is not) Prior authorization — also called precertification or pre-approval depending on the payer — is a requirement that the provider obtain the payer’s agreement **before** certain services are rendered that the service will be covered. It sits on top of eligibility: a patient can be fully eligible, with active coverage, and the claim can still deny in full because the specific service needed an auth that was never obtained. Three things it is **not**: - **Not a referral.** A referral routes the patient from one clinician to another (common in HMO designs). An auth is the payer’s coverage review. Some plans require both; confusing them produces unpaid claims even when the clinical routing was perfect. - **Not a guarantee of payment.** An approved auth establishes that the service met coverage criteria as presented. The claim can still deny for coding errors, duplicate submission, eligibility retro-termination, or timely filing. Treat an approval letter as one requirement cleared, not as money in the bank. - **Not universal.** Original (fee-for-service) Medicare requires prior authorization for only a short, published list of items and services — CMS maintains those programmes publicly ([CMS prior authorization initiatives](https://www.cms.gov/research-statistics-data-systems/medicare-fee-service-compliance-programs/prior-authorization-and-pre-claim-review-initiatives)). Medicare Advantage, Medicaid managed care, and commercial plans use auth far more aggressively, each on its own list. ### Where it sits in the eligibility-to-claim flow Auth work is a chain, and the failure modes map one-to-one onto the links: 1. **Scheduling / pre-registration.** The appointment type and planned service are known. This is the cheapest point to catch an auth requirement. 2. **Eligibility verification.** Coverage and benefit status are confirmed — over the HIPAA-adopted **270/271** eligibility transaction in most shops. The eligibility response plus the payer’s policy together answer “does this plan require auth for this service?” 3. **Auth request.** Clinical and administrative documentation goes to the payer. The HIPAA-adopted standard transaction for this exchange is the **X12 278** (health care services review — request and response), one of the adopted standards CMS maintains in its administrative-simplification materials ([CMS adopted standards](https://www.cms.gov/Regulations-and-Guidance/Administrative-Simplification/HIPAA-ACA/AdoptedStandardsandOperatingRules)). In practice, much of the industry still submits via payer portals and fax alongside the 278. 4. **Decision.** Approval, denial, or pend for more information — with an authorization number, a validity window (start and end dates), and an authorized unit or visit count. 5. **Care delivery against the auth.** Dates of service must fall inside the window; units consumed must stay inside the count; the rendering provider, place of service, and procedure must match what was authorized. 6. **Claim submission.** The auth number travels on the claim — box 23 on the paper CMS-1500 per the [NUCC instruction manual](https://www.nucc.org/index.php/1500-claim-form-mainmenu-35), the prior-authorization REF segment on the 837. 7. **Adjudication and remittance.** When any link above failed, this is where you find out — as a denial with a reason code, weeks after the fixable moment passed. The point of drawing the chain: **links 1–4 are prevention; links 5–6 are hygiene; link 7 is the autopsy.** Staffing the autopsy instead of the prevention is the most common structural mistake in auth management. ### Why auths fail — the failure modes that become denials | Failure mode | How it happens | How it surfaces on the remit | Prevention owner | | --- | --- | --- | --- | | No auth obtained at all | Payer’s auth-required list not checked for this plan + service at scheduling | Reason code 197 (precertification/authorization absent) on a zero-pay line | Scheduling + clinical ops | | Auth number missing or invalid on the claim | Auth exists; charge entry never attached the number, or it landed in the wrong field | Reason code 15 (authorization number missing/invalid/not applicable), often with CO-16 | Billing / charge entry | | Expired auth or DOS outside the validity window | Long episodes of care; the clinical calendar drifts past the auth’s end date | Code 197-class denial with remarks on dates, or a policy denial letter | Clinical ops (auth calendar) | | Units or visits exceed the authorized count | No live counter against the authorized block; re-auth triggered too late | Reason code 198 (precertification/authorization exceeded) or 151 (info does not support this many services) | Clinical ops (session counters) | | Wrong procedure, provider, or place of service vs. the auth | Authorized for one CPT/setting; rendered and billed differently (e.g. telehealth instead of office) | Auth-mismatch remarks with 197-class or diagnosis/procedure (11) edits | Coding + scheduling | | Retroactive denial after payment | Payer re-reviews medical necessity or eligibility post-payment and recoups | Takeback / recoupment on a later remittance | UM + billing (appeal capacity) | Reason code descriptions are paraphrased from the X12 Claim Adjustment Reason Code list (source below) as of this page’s review date. Group codes on your remit (CO vs PR vs OA) still decide who can be billed next — see the /denials library. ### Working an auth-related denial, in order 1. **Step 1: Establish whether an auth ever existed** — Pull the auth letter, portal record, or 278 response for the date of service. If it exists, the fight is usually about the claim field or the match — not about coverage. If it never existed, decide between retro-auth (below) and write-off before spending appeal labour. 2. **Step 2: Match the auth to the claim line by line** — Dates inside the window? Units inside the count? Rendering provider, place of service, and procedure code matching what was authorized? A mismatch here explains most 15/197/198 combinations without any payer bad faith. 3. **Step 3: Corrected claim vs. appeal** — Missing or misplaced auth number with an otherwise valid auth: corrected claim (or payer portal re-key) with the number in the expected field — this is the [CO-16](/denials/co-16) pattern, not a formal appeal. Auth valid and payer still denies: formal appeal with the auth letter and clinical documentation; Medicare’s appeal ladder is summarised in [MLN006562](https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf). 4. **Step 4: Retro-authorization where the plan allows it** — Some plans permit retroactive auth within a defined window; many do not. Check the payer’s provider manual for the specific policy rather than assuming. Where it exists, it is usually cheaper than a full appeal. 5. **Step 5: Watch the timely-filing clock** — Corrected claims and retro-auths do not stop filing deadlines. Note the original submission date and the payer’s limit before choosing a slow path. 6. **Step 6: Close the loop at the owning link** — Tag the denial to the chain link that failed (requirement check, request, calendar, counter, claim field) and fix that step. Auth denials reworked without a process fix are repeat denials pre-ordered — and denial labour is real money ([cost to collect](/cost-to-collect)). ### The prevention checklist - Verify before the visit — At scheduling and again before the appointment: is this plan + service on the payer’s auth-required list? Check the payer’s current list for the date of service — auth lists change, and memory is not a control. - Track auth validity windows in one shared register — Auth number, start/end dates, authorized units/visits, authorized procedure and place of service, rendering provider. The schedule and the claim system should both read from it — not from a letter in a chart tab. - Count units against the authorized block — Every rendered visit decrements the counter. Trigger re-auth before the block runs out — the trigger point is your policy (a few visits before exhaustion), not the denial. - Attach the auth number to the claim in the field the payer expects — Box 23 on the CMS-1500 per the NUCC manual; the prior-authorization REF segment on the 837. “We had an auth” is not the same as “the auth was on the claim” — see /denials/co-16 and reason code 15. - Document medical necessity for the authorized service — An auth approves coverage as presented; the note must still support the service billed. For ongoing care, notes that show goals, progress, and continued need are what survive a retroactive review. - Reconcile remittances back to the auth register weekly — A zero-pay line with a 15/197/198 code is a signal about a specific link in the chain. Weekly reconciliation catches drift while corrected-claim windows are still open. - Escalate repeated payer behaviour with data — A payer whose auth requirements, decision times, or denial patterns look inconsistent with its own published policy is an escalation case — with the auth letters and remits as evidence, not a vibe. Print this for the auth desk. Every item maps to a failure mode in the table above — none of them require new software to start. ### The regulatory direction, as of this page’s review date Prior auth is an active regulatory target, and the direction of travel is shorter decision times and more transparency — for the payers the rules reach. CMS’s Interoperability and Prior Authorization Final Rule (CMS-0057-F) requires **impacted payers** — Medicare Advantage organisations, state Medicaid and CHIP fee-for-service programmes, Medicaid and CHIP managed care entities, and qualified health plan issuers on the federally facilitated exchanges — to send prior-authorization decisions within **72 hours for urgent requests and seven calendar days for standard requests beginning in 2026**, to give a **specific reason** when a request is denied, and to stand up patient-, provider-, and payer-facing APIs on published timelines (prior-authorization APIs by 2027 under the rule’s schedule). The rule’s scope and dates are in the [CMS fact sheet](https://www.cms.gov/newsroom/fact-sheets/cms-interoperability-and-prior-authorization-final-rule-cms-0057-f) — note that the prior-authorization provisions do not apply to drugs, and the rule does not reach every commercial plan on its own. Industry pressure has been building for longer. The AMA’s recurring physician surveys document prior auth as a top administrative burden — their research hub publishes each wave ([AMA prior authorization research](https://www.ama-assn.org/practice-management/prior-authorization/prior-authorization-research-reports)). HFMA maintains a prior-authorization topic hub for revenue-cycle operators ([HFMA](https://www.hfma.org/revenue-cycle/prior-authorization/)). What this means operationally: keep your own auth register regardless of payer-side reform. A 72-hour decision clock helps only if your side submitted a complete request with the right documentation in the first place. ### What AdvancedCare does in this space (disclosed) The operator bar at the top of this page already tells you we sell revenue-cycle software and services, so here is the specific, honest version for auth work. The cheapest auth failure to fix is the one caught at eligibility — before the visit, when the plan and service are known but nothing has been rendered. AdvancedCare operates **[TurboVOB](https://turbovob.com)**, a batch eligibility-checking product that returns coverage and authorization flags for a full appointment roster — exactly the front-end step where “does this plan require auth for this service?” should be answered. AdvancedCare also sells revenue-cycle services that include auth tracking as part of denial prevention. If your front end cannot answer that question at scheduling, that is the first fix — with or without us. The checklist above works with a spreadsheet and a shared calendar; tooling makes it faster, not possible. ### Questions Q: Is prior authorization the same as a referral? A: No. A referral routes the patient between clinicians (common in HMO designs); prior authorization is the payer’s advance coverage review of a specific service. Some plans require both. A perfect referral with no auth on an auth-required service still denies. Q: Does an approved authorization guarantee payment? A: No. It establishes that the service met coverage criteria as presented at the time. The claim can still deny for coding errors, untimely filing, eligibility retro-termination, or a mismatch between what was authorized and what was billed. Treat the approval as one requirement cleared. Q: What denial codes appear when the auth is missing or wrong? A: Per the X12 Claim Adjustment Reason Code list (as of this page’s review date): reason 197 when precertification/authorization is absent, reason 15 when the authorization number is missing, invalid, or does not apply to the billed services or provider, and reason 198 when the authorized amount is exceeded. A missing auth number on the claim often arrives as reason 15 riding alongside CO-16 — see /denials/co-16. Q: Does Medicare require prior authorization? A: Original fee-for-service Medicare requires it only for a short, published list of items and services — CMS maintains those programmes publicly (see the CMS prior authorization initiatives page in the sources). Medicare Advantage plans use prior authorization much more broadly, and CMS-0057-F now sets decision-time and denial-reason rules for those plans beginning in 2026. Q: Can a payer deny payment retroactively after approving an auth? A: In some circumstances, yes — payers conduct post-payment medical-necessity reviews and recoup via takebacks, and eligibility retro-termination can unwind coverage entirely. Documentation that supported the auth request (and the notes for the rendered service) is what an appeal stands on. See the working order above for the appeal path. Q: Where does the authorization number go on the claim? A: In the prior authorization number field — box 23 on the paper CMS-1500 per the NUCC instruction manual, and the corresponding REF segment on the electronic 837. An auth that exists but never reaches the claim field is the single most common self-inflicted auth denial. Sources: - CMS Medicare fee-for-service prior authorization and pre-claim review initiatives (Centers for Medicare & Medicaid Services): https://www.cms.gov/research-statistics-data-systems/medicare-fee-service-compliance-programs/prior-authorization-and-pre-claim-review-initiatives - CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) fact sheet (Centers for Medicare & Medicaid Services): https://www.cms.gov/newsroom/fact-sheets/cms-interoperability-and-prior-authorization-final-rule-cms-0057-f - CMS HIPAA administrative simplification — adopted standards and operating rules (Centers for Medicare & Medicaid Services): https://www.cms.gov/Regulations-and-Guidance/Administrative-Simplification/HIPAA-ACA/AdoptedStandardsandOperatingRules - AMA prior authorization physician survey research reports (American Medical Association): https://www.ama-assn.org/practice-management/prior-authorization/prior-authorization-research-reports - HFMA prior authorization topic hub (revenue cycle resources) (HFMA): https://www.hfma.org/revenue-cycle/prior-authorization/ - X12 Claim Adjustment Reason Codes (CARC) (X12): https://x12.org/codes/claim-adjustment-reason-codes - NUCC 1500 Health Insurance Claim Form Reference Instruction Manual (National Uniform Claim Committee): https://www.nucc.org/index.php/1500-claim-form-mainmenu-35 - CMS Medicare Claims Processing Manual (Pub. 100-04) (Centers for Medicare & Medicaid Services): https://www.cms.gov/regulations-and-guidance/guidance/manuals/internet-only-manuals-ioms-items/cms018912 - CMS MLN006562 — Medicare Parts A & B Appeals Process (Centers for Medicare & Medicaid Services): https://www.cms.gov/files/document/mln006562-medicare-parts-b-appeals-process.pdf --- ## About rcm.today URL: https://rcm.today/about Last reviewed: 2026-07-18 Who runs this site, how it makes money, how figures are sourced, and how to report an error — including an explicit retraction of the old “daily news” framing. ### Who operates this **rcm.today** is operated by **AdvancedCare USA Inc.** AdvancedCare sells EHR, revenue cycle services, ClinicPay.ai, and RCMBoost (among other healthcare tools) to outpatient practices. We are not a newsroom, not a hospital, and not an independent consumer advocacy organisation. ### How this site makes money This site is a **lead-generation and trust property** for AdvancedCare’s revenue-cycle products and services. Free tools and reference pages attract practice decision-makers; some of them contact us; some of those conversations become customers. We state that in plain language because the alternative — sounding like neutral editorial while functioning as a funnel — is how this domain previously failed. Disclosure is not optional here; it is the commercial model done honestly. ### What changed (the old news framing) Earlier versions of this site claimed daily or continuous publication, a morning newsletter digest, and tracking of state Medicaid bulletins. **Those claims were false.** There was no daily desk and no newsletter. The site now positions as a decision and benchmarking resource with a free calculator. Occasional sourced articles may appear under [/news](/news); that is not a cadence promise. ### Methodology and sourcing policy Every factual, regulatory, or benchmark claim must carry a real source URL, a publisher, and a visible as-of date. Preferred sources: CMS, HFMA, MGMA, Premier, KFF, Federal Reserve, USPS, and primary trade reporting that names the underlying dataset. If a figure cannot be sourced, we omit it or say it varies. Calculator constants live in a versioned JSON model validated at build time for freshness. Every benchmark and formula on this page is sourced and dated above. Where a figure is a range, the range is the honest answer, not a hedge. If you think something here is wrong or out of date, tell us — corrections are logged and dated. ### Corrections Email **news@rcm.today** or use the form below. We log material corrections with a date. Disagreeing with a range is welcome; we will not invent precision to win the argument. Sources: - HFMA Guide to Better Practices in Measuring Cost-to-Collect (HFMA): https://www.hfma.org/wp-content/uploads/2025/09/Cost-to-Collect-Better-Practices.pdf - Calendar Year (CY) 2026 Medicare Physician Fee Schedule Final Rule (CMS-1832-F) fact sheet (Centers for Medicare & Medicaid Services): https://www.cms.gov/newsroom/fact-sheets/calendar-year-cy-2026-medicare-physician-fee-schedule-final-rule-cms-1832-f --- ## Contact rcm.today URL: https://rcm.today/contact Last reviewed: 2026-10-22 Questions about a benchmark, a correction to a figure, or a conversation about your practice's revenue cycle. rcm.today is operated by AdvancedCare USA Inc., which sells RCM software and services. ## Contact Email: news@rcm.today Disagree with an assumption in the calculator, or spotted something out of date? Tell us. If you want us to look at your numbers, say so — we sell RCM services and will tell you when you do not need them. ## Site Homepage: https://rcm.today/ Sitemap: https://rcm.today/sitemap.xml ## Software Plans — RCM Today Benchmark & 835 Variance Monitor RCM Today Benchmark Monitor lets outpatient billing leads compare their clinic days-in-A/R, clean-claim rate, and cost-to-collect against sourced national benchmarks while flagging CARC/RARC denial spikes. - **Clinic Benchmark Workspace** ($49/month): Save monthly KPI snapshots and track CARC/RARC denial trends over time. — Persist monthly cost-to-collect & net-collection snapshots; Custom CARC/RARC denial playbook bookmarks for billing staff; Exportable quarterly board & partner RCM packets Workspace Signup Endpoint (JSON POST): https://rcm.today/api/saas-signup