What Retro Authorization Means When a Claim Is Already Out the Door

Missing authorization deadlines costs more revenue than clinical review denials.

Altair Health 20 September 2026

Retro authorization is the request a practice files after the care has been delivered, asking the payer to approve a service it would have reviewed beforehand. The claim is often already out the door when someone notices the authorization is missing. From that moment two deadlines run at once, and most of the revenue lost on these cases goes to the calendar rather than to the clinical review.

Prior authorization is the standard sequence: the payer approves before the service happens, which covers most elective procedures, advanced imaging and specialty drugs. Concurrent authorization runs alongside an active episode such as an inpatient stay, with the payer checking at intervals that the treatment still meets its medical necessity criteria. Retro authorization arrives after both of those windows have closed. The practice submits the clinical record, the procedure and diagnosis codes, and an explanation of why the normal sequence did not happen, and the payer applies the same criteria it would have applied before the service.

A retro request is a request. The payer can deny it for every reason it could deny a prior authorization, plus one that belongs to the retro pathway alone: the practice missed the payer's filing window. Practices that treat retro authorization as a formality lose most of those claims before a reviewer ever reads the chart.

The situations that qualify

Emergency care sits at the top of the list and is the easiest case to defend. A patient who arrives unconscious, in active labor or in respiratory distress leaves nobody time to call a payer. Federal prudent layperson standards back the practice here. For commercial plans, 45 CFR 147.138 requires plans to cover emergency services without prior authorization, and parallel provisions apply to Medicare Advantage under 42 CFR 422.113 and to Medicaid managed care under 42 CFR 438.114. Billing staff file the retro request once the patient is stable, which is the sequence the regulations anticipate.

Retroactive eligibility is the second and less obvious category. Coverage shows as inactive on the date of service, and weeks later an employer finalizes a renewal that backdates the policy. Medicaid works this way by design. Under 42 CFR 435.915, a state must make eligibility effective at least as far back as the third month before the month of application when the patient received covered services and would have qualified at the time. Several states have obtained federal waivers that shorten or remove that period, so check the state program. Newborns fall into this bucket as well, since a baby is not on a policy until after birth and care starts in the delivery room.

Administrative oversights make up a third group. A scheduler misreads a payer policy and books a service believing no authorization was needed. Paperwork starts but never finishes before the service date. A patient moves between plans and nobody is sure which policy covered the gap. None of these are clinical emergencies, and payers know it, but they still generate retro cases that someone has to work.

Two more categories deserve a line. Involuntary psychiatric holds override administrative process for the same reason trauma care does. Surgical surprises, where the surgeon finds a condition nobody anticipated and treats it in the same session, produce services outside whatever the original authorization covered.

The cases that do not qualify matter as much. A service that was elective, schedulable and unauthorized because someone forgot to make the call is a weak candidate, and payers deny these with little discussion. Triage the queue in that order. Defensible emergency and eligibility cases first, forgotten calls last, and the same staff hours recover more revenue.

How payers review a retro request

The payer reviews the request as if it were prospective, against the same medical necessity criteria. The difference is that the record you submit is the only version of the story the reviewer will see. A chart that would have passed with a phone call to fill the gaps has to stand on its own.

Payers publish more of the mechanics than most billing teams realize. UnitedHealthcare's 2026 Care Provider Administrative Guide spells out its process for urgent cardiac procedures and advanced outpatient imaging performed outside business hours. The ordering provider must request a retrospective authorization within 2 business days of the date of service for stress echocardiograms and for advanced imaging, and within 15 calendar days for diagnostic catheterizations and electrophysiology implants. The documentation has to explain two things: why the procedure had to happen on an urgent basis, and why nobody could request an authorization number during business hours. If the reviewer finds the service medically necessary, the plan issues an authorization number. If not, it issues a denial with no number and a notice of the appeal process.

That is the template for every payer, whether or not it publishes one. Someone pulls the full record for the encounter: notes, orders, labs, imaging, discharge summary. Someone checks the payer's retro filing window before anything else, because that window decides whether the rest of the work is worth doing. Then the team checks each documentation element the payer's own criteria call for, and the request goes in through whatever channel the payer requires, with a justification letter attached.

The letter carries the case. It has to explain why the practice did not obtain prior authorization and tie that explanation to the payer's criteria rather than describe the situation in general terms. "Patient presented emergently" convinces nobody on its own. A reviewer wants a direct line from the clinical facts at presentation to the reason authorization was impossible, documented at the time of service rather than reconstructed later. Call logs, portal timestamps and fax confirmations showing that staff tried to reach the payer before the service carry weight too.

Two clocks, then a third

Filing windows vary by payer, and some payers do not accept retro requests at all. Check the window before pulling a single record. Traditional Medicare is the exception in the other direction: it requires prior authorization for a limited set of items and services, such as certain durable medical equipment and specific hospital outpatient procedures, so retro cases there cluster around those programs.

The retro request and the claim are two separate clocks. The retro authorization has to resolve before the payer will pay the claim, and the claim's own timely filing deadline keeps running the whole time the request sits in the payer's queue. Practices do everything right on the retro request and still lose the claim because nobody tracked the second deadline.

A denial starts the third clock. Appeal windows are payer specific and often short, and a practice that reviews denials on a weekly or biweekly cycle can be outside one before anyone opens the queue. Medicare Advantage is the one place federal rules set the pace on the payer's side: under 42 CFR 422.590, a plan must decide an expedited reconsideration within 72 hours unless it invokes a permitted extension of up to 14 calendar days. Everywhere else, the contract and the provider manual govern.

What changed in 2025 and 2026

Payers now run much of their review through automated systems, and a denial can come back in hours rather than days. The AMA's 2025 prior authorization survey found 60% of physicians concerned that payers' use of AI is increasing or will increase denial rates, and 79% reporting that prior authorization at least sometimes leads patients to abandon treatment. Faster turnaround on more contested denials means more retro and appeal cases reaching the billing queue at once.

The first mandatory public reporting under CMS-0057-F landed in March 2026, and KFF's analysis of the largest insurers put standard denial rates at 12% in Medicare Advantage, 14% in Medicaid managed care and 18% in the marketplace, with 67%, 47% and 43% of appealed denials overturned. We covered those figures and what they say about approval versus payment in a separate post. For retro work the overturn rates are the point. Payers reverse a large share of their own denials when someone appeals, so a first denial is a step in the process, and a write-off skips that step.

Hospitals got one specific protection. Under the contract year 2026 Medicare Advantage final rule, from January 1, 2026, a plan may not reopen an approved inpatient admission and deny it on information gathered after the approval, except for obvious error or fraud. That closes one of the more damaging retroactive denial patterns for hospitals. The 2026 change targets inpatient admission decisions. The underlying rule at 42 CFR 422.138 already bars a Medicare Advantage plan from reopening an approved authorization, inpatient or outpatient, except for good cause or reliable evidence of fraud.

What CMS-0057-F did and did not do

CMS-0057-F, the Interoperability and Prior Authorization Final Rule, does not address retro authorization. It shortens the prospective process for the payers it covers: Medicare Advantage plans, state Medicaid and CHIP programs and their managed care plans, and marketplace plans on the federal exchange. From January 1, 2026, Medicare Advantage, Medicaid and CHIP plans have to decide expedited requests within 72 hours and standard requests within 7 calendar days. Every covered payer has to give a specific reason for each denial and post its approval, denial and turnaround metrics each year, with the first postings due March 31, 2026. The API requirements that let practice systems query authorization status and documentation requirements follow on January 1, 2027.

The specific denial reason changes retro work more than the deadlines do. A retro request or an appeal has to hit a target, and a vague code left practices guessing at what the payer objected to. For the covered payers, the guessing is supposed to be over. The public metrics add something too: a practice arguing that a payer's denial pattern looks aberrant now has numbers to point to.

More is proposed. CMS-0062-P, released April 10, 2026, would extend the same standardized approach to prior authorization for drugs, including denial explanations and clinical documentation through the same kind of interface. If CMS finalizes it as proposed, most of it takes effect October 1, 2027. None of this makes retro authorization go away. It gives practices a sharper target to aim at.

Where the revenue goes

An MGMA Stat poll in January 2026 asked practices where their revenue cycle leaks most and drew 288 responses. Denials and appeals came first at 48%, ahead of front-end problems at 23%, billing and collections at 14% and coding at 13%. Retro authorization sits inside that 48%, and given the overturn rates in the KFF data, a real share of the retro denials practices write off would have paid on appeal.

The failure sequence is predictable. A claim comes back denied for lack of authorization. It goes into a weekly review queue. The retro filing window closes before anyone reaches it. The claim ages past timely filing and the revenue is gone. Nobody made a mistake in the usual sense. Retro authorization sat low enough on the list that the clock ran out.

Front-end eligibility feeds this pipeline. Coverage that changes after the date of service is a routine retro trigger, and a gap at check-in becomes a documentation project weeks later, for care the practice has already delivered.

A workflow that catches the case early

Treat retro authorization as its own tracked workflow. Flag the situation the moment it happens, an ER admission, a newborn without a policy, a retroactive Medicaid reinstatement, rather than waiting for the denial. Log the filing window before anyone pulls a record.

Build the documentation against the payer's specific criteria. A justification letter for a UnitedHealthcare cardiac case should answer the two questions its guide asks, in that order, instead of describing urgent circumstances in general terms. That takes knowledge of how each payer reads these letters, which is a different skill from routine prior authorization submission.

Schedule the follow-up. Retro requests sit in payer queues while the claim's timely filing clock keeps moving. And when a retro denial lands, appeal before writing anything off. The overturn rates above are the argument.

Altair runs this exception work as a service. Software flags the retro situations and the deadlines attached to them, and billers who know each payer's criteria and denial history write the justification and work the appeal. Whatever workflow a practice uses, the discipline is the same. Catch the situation early, respect the filing window above everything else, and check whether a denial is worth appealing before treating it as final.

Which situations support a retro authorization request

Common questions