How a Payer Policy Change Triggers a Denial Spike

A denial spike after a payer policy change is a sudden run of denials from one payer on the same codes, with the same reason code. The run starts with services on the policy's effective date. It is the visible end of a chain reaction. The payer changes a coverage policy, a bundling edit or a prior authorization requirement. It announces the change in a monthly bulletin, a newsroom post or a message in your EHR. If nobody on your team sees the notice, claims keep going out built the old way, each with the same defect.

None of this is a billing error in the usual sense. The claim goes out the way it always has, against a policy that is new. The fix is a process that sorts the first denials by payer, code and reason code, then ties them to the policy before the next batch goes out.

How payers announce policy changes

Payers such as UnitedHealthcare and Cigna announce policy changes, but in channels your practice has to watch. UnitedHealthcare's 2026 administrative guide says it posts policy, product and reimbursement changes to Network News, at UHCprovider.com/news, at the beginning of each month. Consistent with your agreement and applicable law, UnitedHealthcare may use that page to give electronic notice of policy, protocol and payment policy changes. You can sign up for email notice of those updates at UHCprovider.com/subscribe. UnitedHealthcare's medical policy update bulletins go up on the first calendar day of every month.

If your EHR supports direct messaging, the guide says UnitedHealthcare may send changes to prior authorization requirements and other policies there. Unless your agreement or the law requires otherwise, that message can be the only notice you get. The same guide says payment will be denied, in whole or in part, for failure to comply with a protocol. Check what notice your agreement promises.

UnitedHealthcare's new allergen testing policy for its commercial and Individual Exchange plans shows how one change moves through those channels. Its history shows UnitedHealthcare's Reimbursement Policy Oversight Committee approved it on April 28, 2026. The June 2026 bulletin announced it on June 1 for dates of service on or after September 1, 2026, in every state but seven. The September bulletin set October 1 for those seven: Arkansas, Colorado, Kentucky, Nebraska, North Carolina, Ohio and Rhode Island. The policy limited reimbursement for specific IgE allergy testing to 20 allergen specific antibodies per year for patients 20 and older.

On October 1, a month into the policy in most states, the October bulletin raised the limit to 29 for dates of service on or after September 1. The limit applies to each procedure code on its own. If UnitedHealthcare denied a patient's units of a code past the 20th in September, units up to the 29th now fall inside the limit. The bulletin does not say whether UnitedHealthcare will reprocess them, so pull your September claims for the codes the current policy lists, 86003 and 86008, and check which units paid.

Cigna posts changes on its provider newsroom. A post dated April 14, 2026, announced additions to the drug list for its Specialty Care Options programs. At prior authorization, those programs check whether a specialty drug given in a higher-intensity setting, such as a hospital outpatient department, could be given somewhere less intensive. Three of the additions took effect March 9, March 23 and April 1, before the post went up. The post says the drug list is subject to change and asks you to review it often. The list itself sits behind a login at CignaforHCP.com.

For traditional Medicare, each Medicare Administrative Contractor issues its own coverage policies, called local coverage determinations. They go up in CMS's Medicare Coverage Database. The Medicare Program Integrity Manual requires at least 45 calendar days' notice before a final determination takes effect. Corrections and some other revisions are exempt.

Prior authorization lists move in both directions. UnitedHealthcare announced on December 1, 2025, that it would stop requiring prior authorization for certain nuclear imaging, obstetrical ultrasound and echocardiogram procedures. The change took effect January 1, 2026, across its commercial, Community Plan, Individual Exchange and Medicare Advantage plans, but the code list differs by plan. For Medicare Advantage, the list holds only nuclear medicine codes, and the obstetrical ultrasound codes appear only under Oxford Health plans. A practice that assumes its list stays put either requests authorizations it no longer needs or misses new requirements the payer added.

Why claims keep getting denied after a payer policy change

Claims keep getting denied after a payer policy change because your claim scrubber still checks them against the old policy. A claim scrubber is the software that reviews claims before they go out. The billing operation keeps doing what it was built to do, which is the problem. CMS posts changes to its NCCI procedure-to-procedure edit files every quarter. If you bill both codes of an edit pair for one patient on one day, the payer denies one of them unless an appropriate modifier applies. For the edits effective October 1, 2026, CMS posted the practitioner additions, deletions and revisions on September 1. A scrubber still running the July table passes code pairs the October table now flags, and those claims deny at the payer instead of stopping in your office. Those denials can carry CARC 236, the claim adjustment reason code for a procedure not compatible with another on the same day under NCCI.

A clean clearinghouse report does not close the gap. UnitedHealthcare's administrative guide says the clearinghouse applies HIPAA edits to help ensure each claim contains specific information, and returns claims that fail as rejections. The payer's own edits come after that. For Medicare Advantage claims, UnitedHealthcare bases its edits on sources that include coverage determinations, NCCI, other CMS guidance and its own medical policies. For commercial claims, its NDC policy says UnitedHealthcare applies its reimbursement policies through iCES Clearinghouse, a customized version of the Optum Claims Editing System. Despite the name, it runs on the payer's side. A claim can pass your clearinghouse and still deny, because clean and payable are two different tests.

How a denial spike shows up in your remittances

A denial spike looks like a cluster: one payer, one code or code pair, one reason code, one starting date of service. The first denials look like routine noise, a handful of claims in the work queue. Whoever works them does not yet know about the policy change, so new claims keep going out on the old logic. A second wave, identical to the first, is already in transit before anyone has worked the first one.

One CMS correction shows the pattern. Effective July 1, 2025, CMS added NCCI edits that paired COVID-19 vaccine administration code 90480 with G0008, G0009 and G0010, the flu, pneumococcal and hepatitis B vaccine administration codes. On October 14, 2025, CMS said it would withdraw those edits retroactive to July 1. Medicare Administrative Contractors would reprocess affected claims with dates of service from July 1 through October 15, 2025, within 30 business days. CMS issues replacement files like this one when a change cannot wait for the next quarter.

Every claim those edits touched billed 90480 with one of three codes, for a date of service on or after July 1, 2025. A shared code and a start date that match a published change are the signature of a policy change, not of worse documentation.

Reason codes such as CARC 50, 96 and 97 name the outcome, not the policy behind it. CARC 50 says the payer does not deem the service a medical necessity. CARC 96 marks a non-covered charge, and CARC 97 says the payment for another, already processed service covers this one. X12, which publishes the code list, attaches the same usage note to all three: refer to the 835 Healthcare Policy Identification Segment, loop 2110 REF, if present. The 835 is the payer's electronic remittance file. Its policy segment, when the payer fills it in, identifies the policy behind the adjustment. If the payer leaves it empty, someone has to match the denials to the change by date.

The size of a spike depends on how many more claims go out before someone finds the cause of the first denials. That count is the part of the chain your practice can change.

2026 coverage and payment changes: Medicare Advantage plan exits and the fee schedule

KFF found that about 2.6 million people in individual Medicare Advantage drug plans, 13% of enrollees, were in a plan terminated for 2026. That is up from 6% in 2025, and the count leaves out special needs plans, plans without drug coverage and employer coverage. A KFF follow-up tied the terminations to insurers discontinuing plans or shrinking the areas they served. Those patients could join another Medicare Advantage plan, if one was available, or choose traditional Medicare. Either way, the card on file may still show the old plan. Claims sent to the old plan for 2026 visits will not pay.

A federal regulation protects patients already in treatment. Under 42 CFR 422.112(b)(8), a Medicare Advantage plan must not disrupt or require reauthorization for an active course of treatment for new enrollees for at least 90 days. The protection applies to basic benefits. A service the patient starts after the switch falls under the new plan's prior authorization requirements.

Beginning in 2026, CMS-0057-F, the Interoperability and Prior Authorization final rule, requires covered payers to give a specific reason when they deny a prior authorization request. That reason can point you to the policy behind the denial. The requirement does not apply to drugs. Covered payers are Medicare Advantage plans and federal marketplace plans, plus Medicaid and CHIP in both fee-for-service and managed care. Our post on why prior authorization approval does not guarantee payment covers the prior authorization data these payers had to publish.

The 2026 Medicare physician fee schedule created two conversion factors for the first time. A conversion factor is the dollar amount that turns a service's relative value units, or RVUs, into a payment rate. Qualifying participants in advanced alternative payment models get $33.57, up 3.77% from $32.35. Everyone else gets $33.40, up 3.26%. Both include a 2.50% increase that Public Law 119-21 applies only to services furnished in 2026. CMS also cut the work RVUs, the part that values the clinician's work, for non-time-based services with a 2.5% efficiency adjustment. It exempted E/M visits, care management, behavioral health and telehealth list services, among others. It lowered the indirect practice expense, the overhead share of payment, for services furnished in a facility such as a hospital.

Those are payment changes, not denials, but they land in the same remittances. A billing system still using the old conversion factor, or the wrong one of the two, computes expected payments that do not match what arrives. If an allowed amount does not move with the new schedule, the payer may never have loaded the rate.

What a denial spike costs a practice

A denial spike costs more for every week it goes unnoticed, because each week adds more claims built on the old policy. Reworking a denied claim takes staff time, and more of it for anything that needs a peer-to-peer review or a written appeal. That labor recovers money the practice already earned and produces no new revenue.

The window to recover that money comes from each payer's manual, your contract and the law. UnitedHealthcare's 2026 administrative guide gives you 12 months from the original EOB or PRA to file both the reconsideration and the appeal. The law or your agreement can change that. The guide also lets you submit 20 or more reconsiderations for the same administrative issue in bulk online, if they need no attachments. A spike that comes from one policy change can fit that description. Our UnitedHealthcare payer guide links our pages on its denials and appeals.

The revenue is not lost the day a claim denies. Getting it back depends on working every denial before its window closes. If one payer brings in most of your revenue, a policy change there reaches more of your claims than the same change at any other payer.

How to catch a denial spike early: by payer, code and reason code

You catch a denial spike early at four points: eligibility, prior authorization, claim scrubbing and denial review. The first three stop a claim built the old way before it goes out. The fourth spots a spike from its first denials. Each one needs a specific process, not a general reminder to be careful.

The earliest point is eligibility. Confirm active coverage, plan type and payer at scheduling and again at check-in, for every patient at every visit. A plan can change between visits without anyone telling the practice. Checking every time catches the Medicare Advantage plan change before the practice provides a service the new plan has not authorized.

The second point is prior authorization. Your authorization checklist has to reflect each payer's current published requirements, not the list from the last time someone looked. Read each payer's bulletins and newsroom posts as they come out, and update the checklist with each change's effective date.

The third point is claim scrubbing. The scrubber's NCCI tables have to match the current quarter. Your scrubber needs a second layer for each payer's own edits, like the iCES edits UnitedHealthcare applies on top of whatever your clearinghouse checks. Load each payer policy change into the scrubber with its effective date, so claims with earlier dates of service still follow the old policy.

The fourth point is denial review. Group each week's denials by payer, by CPT code or code pair and by reason code, then find the first date of service in each group. A cluster that starts on a policy's effective date points to that policy. Check the 835's loop 2110 REF segment for the policy the payer applied, and compare remark codes across the group. Remark codes add detail to the reason code. Our post on denial management workflow design covers how to read each remittance and route each denial.

Building a billing operation that catches payer policy changes

A billing operation that catches payer policy changes runs those four checks as standing processes, not occasional ones. A weekly denial review by payer, code and reason code turns a spike into a policy signal within days, instead of a surprise at month-end.

The payer knowledge behind those checks has to live somewhere durable. Knowing where each payer posts its changes, and which of its edits caught your claims last time, lets you catch the next change before it produces another spike. That knowledge leaves with the biller who holds it. Our post on billing staff turnover covers what else goes with them.

Altair is a done-for-you medical billing service, AI backed by expert in-house billers, that runs the whole revenue cycle from eligibility to payment posting. It reads every remittance as it arrives, groups the denials by payer and reason code, then works every one. It keeps what it learns about each payer in the system rather than in a person. The practice owner sees every claim and every dollar as it moves, not in a monthly report. The practice hires no one and manages no one, and it keeps the EMR and clearinghouse it already uses. Every claim is checked against the payer's current policy before it goes out, so it holds up if the payer reviews it later, and the money stays with the practice. See how Altair runs denial management.

A payer's policy change starts on its effective date, whether or not anyone on your team saw the notice. The first denials are the second notice, and every affected claim sent after them carries the same defect.

Common questions