FET vs. Fresh Transfer Billing: What's the Same, What's Different
FET and fresh transfer cycles share some billing codes and diverge sharply in others. Understanding the differences prevents authorization mismatches and coding errors.
A fresh embryo transfer and a frozen embryo transfer both result in an embryo being placed in the uterus β but the billing for each diverges at nearly every step. The procedure codes change, the monitoring codes differ in clinical context, the authorization pathway is often separate, and the ICD-10 code set may differ depending on the clinical scenario. Understanding where they align and where they split prevents authorization mismatches and claim denials.
Procedure Code Differences
- Fresh transfer: CPT 58974 β Embryo transfer, intrauterine (fresh cycle)
- FET β Thaw component: CPT 89352 β Thawing of cryopreserved embryo(s)
- FET β Transfer component: CPT 58976 β Frozen-thawed embryo transfer
- Some payers bundle 89352 and 58976 and pay a single combined rate; others pay them separately. Verify per payer before billing.
Monitoring Code Differences
Fresh transfer monitoring occurs during the stimulation phase β follicle tracking with 76830 and an E&M code (99213) at each visit. FET monitoring focuses on endometrial preparation β typically estradiol and progesterone levels with endometrial stripe measurement. The ultrasound code (76830) is the same, but the clinical context and frequency differ. Hormone assay codes (82670 for estradiol, 84144 for progesterone) are billed separately from the ultrasound for FET monitoring visits.
Authorization Distinction
Many payers authorize fresh IVF cycles and FET cycles through separate authorization pathways. An FET cycle requires a new prior authorization even if the patient used the same clinic for the fresh cycle and the original IVF retrieval was authorized. Never assume prior cycle coverage carries forward to the FET.
ICD-10 Code Differences by Scenario
- Fresh IVF transfer: N97.x (female infertility by etiology) + Z31.83 (encounter for ART)
- Donor egg FET: Z31.7 (encounter for procreative management, using donor oocyte)
- Own-egg FET after freeze-all: N97.x + Z31.83 for both the freeze encounter and the FET encounter
- Fertility preservation then FET: Z31.84 for the original preservation + N97.x + Z31.83 for the FET encounter
Cryostorage and Annual Storage Fees
If embryos were cryopreserved at the same clinic, the FET cycle may also intersect with annual cryostorage billing. CPT 89258 covers the cryopreservation procedure itself. Annual storage fees are typically patient-pay β insurance-billable storage is uncommon, and attempting to bill it to a payer without verifying coverage results in a denial that is difficult to appeal.
Why FET Requires a Separate Authorization
Most commercial payers treat the fresh IVF cycle (retrieval and fresh transfer) and any downstream FET as distinct benefit-consumption events, each requiring its own prior authorization. The fresh-cycle auth typically covers stimulation, retrieval, fertilization, embryology, and the fresh transfer. It does not extend forward to a subsequent FET even when the embryos originated from that same authorized retrieval. The FET auth request is a separate submission with its own medical-necessity documentation, its own approval-to-service window, and its own expiration date. Practices that assume authorization carryover discover the gap only when the FET claim posts as CO-197 (precert or authorization absent) β after the transfer has already occurred and the patient balance is difficult to unwind.
Timing matters too. FET authorization windows are typically shorter than fresh-cycle windows because the payer expects the FET to be scheduled within a defined preparation cycle rather than delayed indefinitely. Verify the auth-to-service window on each FET approval, and re-submit for extension if endometrial preparation runs long or the transfer must be postponed. An expired FET auth is a common source of last-minute rework that a proactive schedule review would prevent.
Documentation Physicians Must Provide for Each Cycle Type
The clinical documentation that supports a fresh-cycle claim is not identical to what supports an FET claim, and coders working from the operative note alone will miss elements the appeal packet later requires.
- Fresh cycle β stimulation start date, medication protocol, retrieval date and oocyte count, fertilization method (conventional vs. ICSI), fertilization result, day of transfer, embryo count and quality grade, transfer technique.
- FET cycle β preparation protocol (programmed / natural / modified natural), endometrial thickness at trigger or transfer, medications used for lining preparation, thaw date, embryo count and post-thaw survival, transfer date and technique.
- Freeze-all conversion β the medical reason documented in the operative note (OHSS risk, endometrial receptivity concern, PGT hold pending results, elective medical decision) is the documentation that unblocks a CO-236 appeal when the retrieval claim lacks the expected fresh-transfer companion line.
- PGT interaction β which embryos are known-euploid at time of FET, whether the transferred embryo(s) were biopsied and tested at the fresh cycle or the thaw cycle, and which biopsy CPT (89290 or 89291) was billed to which encounter.
Fresh vs. FET Denials: The Patterns Worth Watching
The denials practices see on fresh-cycle claims and FET claims are not the same, and the appeal path is not the same either.
- CO-197 (authorization absent) on FET claims β most often caused by the "fresh auth extends to FET" assumption. Cleanest remedy is preventive: verify a distinct FET auth exists before scheduling the transfer.
- CO-236 (procedure inconsistent with another procedure) on fresh cycles that were converted to freeze-all β the retrieval was authorized as a fresh-transfer path, but no fresh transfer occurred and the claim posts against a cycle template the payer did not expect. Documentation of the medical reason for the freeze-all needs to accompany any appeal.
- CO-11 (diagnosis inconsistent with procedure) on FET when the ICD-10 code set was carried forward from the fresh cycle without adjustment β a donor-egg FET encounter is Z31.7, not Z31.83; carrying the fresh-cycle encounter code forward causes a payer-side inconsistency at the very next scrub.
- PR-96 (non-covered) on FET monitoring when the payer covers the transfer procedure but not the endometrial-preparation monitoring visits β a benefit-language distinction that eligibility calls asking about "coverage for FET" as a single question routinely miss. Ask about monitoring separately.
- PR-119 (benefit maximum exceeded) on the FET side of a mandate-state plan when the fresh cycle already consumed the cycle-count or dollar allowance β this is patient-financial-responsibility, not appealable, and should be caught in the pre-FET benefit re-verification rather than after the claim posts.
Freeze-All Cycles Reshape the Billing Timeline
A growing share of IVF cycles are planned or converted to freeze-all β the fresh retrieval is done, all viable embryos are cryopreserved, and no fresh transfer occurs. The billing implications separate the fresh-cycle claim from any subsequent FET claim by weeks or months, and each side of the split needs its own auth, its own encounter documentation, and its own claim submission.
On the fresh-retrieval side of a freeze-all, the claim excludes CPT 58974 (fresh transfer) because no fresh transfer occurred. It includes retrieval, fertilization, embryology, and the cryopreservation code (89258 for the embryo-freezing procedure). On the downstream FET side, the claim is a standalone FET encounter with 89352 (thaw) and 58976 (frozen transfer), monitoring, and its own auth. When the freeze-all was elective, the fresh-cycle auth typically reflects the elective decision β but if it was a medical conversion during the cycle, the operative note must document why or the retrieval-side claim may be denied for the missing transfer.
Why the Same Payer Pays Fresh and FET Differently
It is common for a single payer to reimburse the fresh cycle and the FET at different rates, apply different member cost-sharing, and count each against a different benefit accumulator. A mandate-state plan with a lifetime cycle-count limit (Massachusetts, Colorado, Maryland, Arkansas) may count the fresh retrieval as one cycle and the FET as either its own cycle or as part of the original retrieval cycle β the statutory definition varies by state and by how the payer implemented it in benefit language. Read the plan-language definition of "one cycle" during eligibility and re-verify before each FET; the answer changes materially between plans that count "one retrieval plus all resulting transfers" as one cycle versus plans that count each transfer as a distinct cycle event.
On non-mandate commercial plans, the FET is often billed against a lifetime dollar cap, an annual dollar cap, or a per-cycle sub-limit that treats the FET separately from the fresh cycle. When a fresh cycle has consumed most of the benefit, an otherwise-approved FET may post PR-119 (benefit maximum exceeded) as patient responsibility. Communicate the split to the patient before the FET is scheduled, ideally in the same signed cost estimate the practice uses at fresh-cycle intake β the pre-cycle written estimate converts an after-the-fact billing dispute into a pre-cycle agreement.
Fresh vs. FET Billing Checklist
- Confirm authorization type β fresh cycle vs. FET. These are separate authorizations at most payers.
- Verify procedure codes: 58970 and 58974 for fresh; 89352 and 58976 for FET.
- Check payer bundling: does the payer pay 89352 and 58976 separately or as a combined payment?
- Match ICD-10 codes to the clinical scenario β donor egg, own eggs, fertility preservation, or freeze-all.
- If FET monitoring is a separately authorized benefit, obtain the monitoring auth before billing any monitoring claims.
Related Reading
Have a billing question?
Our team can answer questions specific to your practice's payer mix and procedures.
Book a Free Audit β