How Prior Auth Expiration Causes IVF Claim Denials
Authorization expiration is one of the most preventable — and least recoverable — denial categories in IVF billing. Learn how payer auth windows interact with IVF cycle timelines, and build the workflows that stop mid-cycle expirations before they happen.
Prior authorization expiration is among the top five causes of IVF claim denials at most fertility practices, yet it is almost entirely preventable with the right tracking systems. Unlike denials caused by coverage exclusions or incorrect coding — which require appeals that often succeed only partially — an expired auth denial is almost always unwinnable. Once the authorization window has closed, the clinical service was performed outside the authorized period, and the payer has no contractual obligation to pay. The only resolution paths are retroactive authorization — which most payers deny outright — or a hard-fought appeal arguing that the expiration was caused by administrative circumstances beyond the practice's control. Prevention is not merely preferable; for expired auth, it is the only viable strategy.
What makes IVF authorization management uniquely difficult is the mismatch between how payers structure authorization windows and how IVF cycles actually work. Most payer auth windows are defined by calendar dates — typically 90 to 180 days — rather than by cycle stage or clinical progression. An IVF cycle is driven by patient physiology: stimulation lengths vary, retrievals are scheduled around follicular response, and embryo transfer timing shifts based on endometrial preparation and embryo quality. A clinic that authorizes an IVF cycle in October may find that the retrieval occurs in January if prior cycles cancelled, fresh transfer is deferred to March because of poor embryo quality, and by the time the frozen embryo transfer finally occurs, the original authorization has expired. This is not a failure of clinical planning — it is the clinical reality of ART. Billing systems that do not account for this reality produce preventable denials at scale.
What "Expired Authorization" Actually Means in a Claim Denial
An expired authorization denial occurs when a claim is submitted for a service that was performed after the end date of the authorization that was issued for that service. This is distinct from a "no authorization" denial, where no auth was ever obtained. The distinction matters because most payers treat expired auth identically to no auth — the fact that authorization was once in place does not create a coverage obligation for services rendered after the auth window closed. Some payers include a short grace period — typically 30 days — during which an extension request submitted before the expiration date can retroactively cover services rendered before the extension was formally granted. This grace period policy is payer-specific and must be confirmed in each payer's provider manual; it cannot be assumed.
When a payer denies a claim citing "authorization expired" or "services rendered outside authorized dates," the standard denial reason code is CO-57 (Prior authorization not received) or CO-197 (Precertification/authorization/notification absent) in the ANSI reason code system. Some payers use CO-15 (Payment adjusted because the submitted authorization number is missing, invalid, or does not apply to the billed services or dates of service). The specific denial code tells you which element failed: CO-57 and CO-197 indicate no valid auth existed on the date of service; CO-15 can indicate either that the auth number is wrong or that the auth existed but did not cover the service date. Pulling the denial code before working the account saves time and shapes the response correctly.
How IVF Cycle Biology Creates Authorization Expiration Risk
The fertility billing team must understand the clinical sequence of an IVF cycle to anticipate where authorization gaps occur. A single IVF cycle involves multiple discrete service categories, each of which may require separate authorization: the stimulation phase (monitoring ultrasounds under CPT 76830, estradiol and LH draws, and follicle counts), the oocyte retrieval procedure (CPT 58970), the embryology laboratory services (CPT 89250, 89254, 89268, 89272, and related codes), optional preimplantation genetic testing (CPT 89290 with associated PGT panel codes billed by the genetics lab), cryopreservation (CPT 89258 for embryo freezing), and ultimately the frozen embryo transfer cycle (CPT 58978). Some payers require a single bundled authorization that covers the entire cycle; others require separate authorizations for each phase, each with its own window.
The phases of an IVF cycle do not occur at fixed intervals. Stimulation typically spans 10–14 days, but cycle cancellations, poor response, or planned freeze-all protocols create gaps of weeks or months between retrieval and transfer. PGT results take 10–14 business days to return from the genetics laboratory, and cases involving complex chromosomal rearrangements (PGT-SR) or custom probe development (PGT-M) can extend to 4–6 weeks. Endometrial preparation for a frozen embryo transfer typically spans 3–6 weeks. When these time gaps compound — a cancelled fresh transfer, a waiting period for additional embryo accumulation, a PGT delay — the interval between authorization issuance and the date of service for the final procedure can easily exceed 180 days. This is not the outlier scenario; it is the common trajectory for any patient undergoing more than a single standard IVF cycle.
Payer Authorization Windows for IVF Services
The following table summarizes typical authorization window lengths for IVF-related services by payer. These windows represent general patterns based on current payer policies and are subject to change — verify current windows directly in each payer's provider portal or by contacting provider relations before each authorization request, as payers update clinical policy bulletins and auth requirements without direct notification to providers.
| Payer | Auth Window (Typical) | Phase-Specific Auth? | Extension Process | Key Risk Note |
|---|---|---|---|---|
| Aetna | 90–180 days from issue date | Yes — separate auth for retrieval vs. transfer | Submit extension via Availity or NaviMedix before expiration; 30-day retroactive window on extensions submitted prior to expiration | FET auth window starts from issue date, not from retrieval date — a common source of gap denials |
| Cigna | 90 days standard; some plans 180 days | No — single cycle auth often covers retrieval through transfer | Call fertility precertification line before expiration; extensions generally granted for documented clinical delays | Accounts on Progyny or WINFertility benefit managers operate under separate rules — confirm which plan governs before submitting |
| United Healthcare | 90 days from auth issue date | Yes — monitoring, retrieval, and lab services often require separate authorizations | Submit extension in UHC provider portal 30 days before expiration with medical reason for delay | UHC applies windows strictly; services performed after the auth end date deny with CO-197 regardless of clinical justification |
| BCBS (varies by state) | 90–180 days; varies by plan | Varies by state plan | Contact local plan's precertification line; document cycle timeline and reason for delay | BlueCard members' auth is governed by the home plan — confirm home plan window, not local plan window |
| Anthem | 90–120 days | Yes — typically separate auth for retrieval and transfer phases | Submit extension via Anthem provider portal; extensions approved for documented medical delays | Anthem HSA and HRA plans may have different auth workflows — verify plan type before initiating auth request |
| Humana | 90 days | No — usually single auth per cycle | Call provider relations line; limited retroactive window (approximately 30 days with documentation) | Humana fertility coverage varies widely by employer group — verify benefit exists before initiating auth |
| Progyny (via employer plan) | Smart cycle model — no fixed calendar expiration; cycle unit consumption rules apply | No — smart cycle covers full cycle phases | N/A — contact Progyny provider relations for paused cycle rules | Cycles paused across a benefit year boundary may require a new authorization request under the new plan year |
High-Risk Points in the IVF Cycle for Authorization Expiration
Not every point in an IVF cycle carries equal auth expiration risk. The following scenarios generate the highest volume of expired auth denials in fertility practices and require proactive management before services are rendered:
- Cycle cancellation followed by re-stimulation: when a stimulation cycle is cancelled due to poor ovarian response (ICD-10 N97.9) or medical contraindication, the original auth often remains active only for the anticipated duration of that single cycle attempt. If the patient restarts stimulation after a 4–8 week recovery period, that restart may fall outside the original auth window. Most billing teams incorrectly assume the original auth covers the re-attempt — payers treat each stimulation attempt as a separate service event requiring current authorization.
- Freeze-all cycles with deferred FET: when all embryos are cryopreserved and no fresh transfer occurs — due to OHSS risk (ICD-10 N98.1), endometrial lining concerns, PGT requirements, or poor embryo quality — the frozen embryo transfer (CPT 58978) occurs weeks or months after retrieval. If the original auth covered retrieval through anticipated fresh transfer, the FET may fall entirely outside that window, and a separate FET authorization is required before scheduling the transfer.
- PGT delays extending the transfer timeline: when embryos are sent for preimplantation genetic testing, the genetics laboratory typically returns results within 10–14 business days. Cases involving complex chromosomal rearrangements (PGT-SR) or custom probe development for monogenic disease (PGT-M) can extend to 4–6 weeks. Adding the endometrial prep cycle duration means the FET date may land 8–10 weeks after embryo biopsy — at which point a 90-day auth window initiated at the start of stimulation may have less than 2 weeks remaining.
- Failed endometrial preparation cycles requiring repeat attempts: when a patient's endometrial lining does not reach adequate thickness (typically ≥7mm) during the first preparation cycle, the transfer is cancelled and another preparation cycle is attempted. Each additional preparation cycle adds 3–6 weeks to the overall timeline before transfer. A patient requiring two failed preparation cycles before a successful endometrial lining may extend the auth window requirement by 6–12 weeks beyond the original anticipated timeline.
- Multiple retrieval cycles for embryo accumulation: patients with diminished ovarian reserve or those pursuing PGT often require multiple retrieval cycles to accumulate enough euploid embryos before proceeding to transfer. Each retrieval cycle — including stimulation, retrieval, and recovery — adds 4–6 weeks to the timeline. Three retrieval cycles before a transfer attempt adds 12–18 weeks to the overall window requirement, a timeline that routinely exceeds a single 90-day authorization.
- Administrative delays in payer processing of extension requests: occasionally extension requests are submitted before the auth expiration date but are not processed before the authorization end date due to payer administrative backlog. When the claim subsequently denies citing expired auth, the practice must produce date-stamped documentation of the extension submission to support the appeal. This is one of the few expired auth scenarios where an appeal has reasonable success probability — but only with proof of the timely submission.
The Retroactive Authorization Myth
Many billing teams assume they can obtain retroactive authorization after discovering that an auth expired during a cycle. This assumption is incorrect for most payers. Aetna, UHC, and Cigna formal policies each state that authorization cannot be granted retroactively for services already performed — the auth must be in place before the service is rendered. The narrow exception is when the service was urgent and prior auth was clinically impossible to obtain before the service — a standard that almost never applies to planned IVF cycles. Some payers allow a 30-day retroactive window when an extension request was submitted before the original auth expired but was not processed in time, but this requires documented proof that the extension was requested before expiration. Do not build retroactive auth into your contingency planning; build expiration prevention into your pre-cycle workflow instead.
Payer-Specific Authorization Extension Rules
Each major payer handles authorization extension requests differently. Understanding these rules before a cycle begins — not after a claim denies — is what separates billing teams that routinely prevent expired auth denials from those that routinely appeal them. The following guidance covers the key rules for high-frequency payers in fertility billing:
- Aetna: Submit extension requests through Availity or NaviMedix. Aetna requires a stated clinical reason for the extension — blanket requests citing "patient not ready" are insufficient. Acceptable reasons include documented ovarian response issues, cycle cancellation with physician attestation, failed PGT results, or endometrial preparation failure with supporting clinical notes. Include the original auth number, the new anticipated service date range, and the clinical documentation. Aetna typically processes extension requests within 3–5 business days; the fertility-specific precertification queue is faster than the general precertification line.
- United Healthcare: UHC processes extension requests through the provider portal under the existing auth number. The fertility precertification team requires documentation of the clinical reason for delay — an operative note from a cancelled cycle, a physician letter, or PGT lab results showing all aneuploid outcomes are all acceptable. UHC extension approvals typically extend the auth window 90 days from the approval date — not from the original expiration date. Services rendered during the gap between original expiration and extension approval may still deny and require separate appeal.
- Cigna: Cigna allows phone-based extension requests for documented clinical delays through its fertility precertification line, which is separate from the standard Cigna precertification number. For patients managed through fertility benefit administrators on Cigna plans — Progyny, WINFertility, or Carrot — the extension request must go to the benefit administrator, not to Cigna directly. Contacting Cigna for an auth extension on a Progyny-managed account results in a referral back to Progyny; skipping this step costs 2–3 business days.
- Blue Cross Blue Shield: BCBS plan extension processes vary by state. Plans in states with fertility mandates (Illinois, New York, New Jersey, California) typically have more defined extension processes tied to the mandate's requirements. For BlueCard claims — out-of-state BCBS members whose claims route to the home plan — the extension request must be submitted to the member's home plan. The local BCBS affiliate cannot grant an extension on behalf of the home plan, and submitting to the wrong entity resets the clock.
- Fertility benefit managers (Progyny, WINFertility, Carrot): these managers do not issue date-based authorizations in the traditional sense. Progyny uses smart cycle units; WINFertility issues case-level authorizations tied to cycle phase; Carrot tracks benefit dollar amounts. Each manager has a distinct process for paused or interrupted cycles. Contact provider relations for each manager individually before assuming that a paused cycle carries forward automatically — unit consumption rules and benefit year boundaries create their own category of coverage gap that does not map neatly to the traditional expired auth framework.
Building an Authorization Expiration Prevention Workflow
The most effective defense against expired auth denials is a proactive tracking and alert system built into the practice's revenue cycle workflow. The following steps represent a practical framework that fertility billing teams can implement without specialized software:
- Enter every authorization into a centralized tracker immediately upon receipt. The tracker must include: auth number, payer name, patient MRN, service category authorized (retrieval, transfer, monitoring, lab), authorization start date, authorization end date, the authorized CPT codes, and the anticipated service date based on the clinical treatment plan. A spreadsheet is sufficient for practices without a billing system with built-in auth tracking, but any system used must be updated every time a new auth is received or an extension is approved.
- Set a 30-day expiration alert for every active authorization. When an authorization is within 30 days of expiration and the anticipated service date extends beyond that window, a billing team member must proactively contact the payer to request an extension. Do not wait for the patient to schedule the service — if the clinical timeline indicates that a service is unlikely to occur within the auth window, request the extension before the 30-day threshold is crossed.
- Review the auth expiration tracker at least weekly as part of standard billing operations. Assign a single named owner to auth tracking. Practices that treat this as a shared responsibility with no designated owner consistently miss expirations. The auth tracking owner reviews all active authorizations every Monday, flags any expiring within 30 days, and initiates extension requests for any case where the anticipated service date extends past the current window.
- Cross-reference the auth tracker against the clinical scheduling calendar weekly. When the clinic schedules a monitoring appointment, retrieval, or transfer, the billing team must confirm that an active auth covers the service date before the appointment is confirmed. If the auth window does not extend to the appointment date, the extension must be requested before the appointment occurs — not after the claim denies.
- Document every extension request with a date-stamped confirmation. When a verbal extension approval is granted by phone, follow up through the payer's online portal within 24 hours. If the payer subsequently denies the claim citing expired auth after a verbal extension was granted, the date-stamped written submission record is the evidence base for the appeal. Verbal approvals that are not documented in writing are nearly impossible to defend in an appeal proceeding.
- For patients undergoing PGT, coordinate the auth extension request with the genetics laboratory's expected turnaround time at the moment of embryo biopsy. Obtain the expected report date from the lab, use that date to calculate the anticipated FET date including endometrial preparation, and confirm whether the current auth window covers that date. If not, initiate the extension request immediately — do not wait for PGT results to return before addressing the expiration risk.
Appealing an Expired Authorization Denial
When a claim denies citing expired authorization and the prevention measures above were not in place, the appeal process is narrow but not impossible. Success depends on the specific reason the auth expired and whether the practice can document circumstances that support the payer's discretionary retroactive review. The following steps provide a structured appeal pathway:
- Identify the precise denial reason code (CO-57, CO-197, or CO-15) on the EOB and confirm that the denial is truly an auth expiration issue — not a different auth problem such as incorrect auth number, wrong NPI on the authorization, or unauthorized CPT code — each of which requires a different appeal strategy.
- Request a copy of the original authorization from the payer's provider relations team if the practice does not have it on file. Confirm the exact start and end date of the auth and the date of service of the denied claim. Quantify the gap in days: smaller gaps of 1–14 days are more successfully appealed than gaps of 30 or more days.
- Document the clinical reason the service occurred outside the auth window. Acceptable clinical justifications for appeal include: cycle cancellation with physician attestation, PGT delays with lab turnaround documentation, failed endometrial preparation with clinical notes, or OHSS risk requiring deferral with provider documentation. Prepare a cover letter from the treating REI physician explaining the clinical sequence and why it was not possible to complete the service within the original auth window.
- For cases where an extension request was submitted before auth expiration but not processed in time, include the date-stamped extension submission record with the appeal. This is the strongest factual basis for an expired auth appeal — the practice fulfilled its authorization management obligation, and the denial resulted from payer administrative delay rather than practice failure.
- Invoke the payer's provider grievance process if the first-level appeal is denied. Some payers have a formal process for provider grievances related to administrative denials — expired auth denials caused by payer processing delays or system errors may resolve at the grievance level even when the standard appeal fails. Reference the specific dates of extension request submission and payer response in the grievance filing.
- For services covered by state fertility insurance mandates — including services in Illinois (215 ILCS 5/356m), New York (Insurance Law §3221(k)(6)), New Jersey (N.J.S.A. 17B:27-46.1x), and California (SB 729) — evaluate whether the expired auth denial can be contested under the mandate's external review provisions. Many state mandates include external review rights for mandate-required services denied on administrative grounds. An expired auth denial for a mandate-required IVF cycle may be eligible for external review even after internal appeals are exhausted.
Authorization expiration denials represent a category of revenue loss that is uniquely within the practice's control. Unlike coverage exclusions, which turn on the patient's plan design, or medical necessity denials, which involve clinical judgment disagreements with payer reviewers, expired auth denials result from an administrative failure that a well-designed tracking system prevents. Fertility practices that invest in dedicated auth tracking — a named owner, a centralized tracker, weekly reviews, and 30-day alert thresholds — eliminate the vast majority of these denials before they occur. For the small percentage that happen despite these systems, the structured appeal approach above provides a path to recovery. The practices with the strongest auth management disciplines also tend to have the shortest AR days and the highest net collection rates, because authorization accuracy at the front end of revenue cycle eliminates the downstream correction work that consumes staff time and delays payment at every phase of the IVF cycle.
Related Reading
Have a billing question?
Our team can answer questions specific to your practice's payer mix and procedures.
Book a Free Audit →