Compliance, Year 15, and Minnesota's 30-year extended-use floor — not 55 — Minnesota

The real number: 30 years, not 55 — with an elective, uncapped-mechanism path to 50

The federal floor is the same everywhere: a 10-year Credit Period under IRC Section 42(f)(1), inside a 15-year Compliance Period under Section 42(i)(1), followed by an Extended Use Period of at least 15 more years under Section 42(h)(6)(D) — 30 years minimum, nationwide. Minnesota Housing's QAP states this floor in its own words, in the section titled "Declaration of Land Use Restrictive Covenants": "a project will be subject to a Declaration of Land Use Restrictive Covenants (LURA) between the owner and Minnesota Housing through which the owner commits the building(s) to low-income use for an extended use period of at least 15 years after the conclusion of the 15-year compliance period (a total of 30 years). The owner can elect to extend the term of the LURA and Section 42 income and rent restrictions up to 50 years." Minnesota's Housing Tax Credit Compliance Guide states the same floor independently: "Properties that received an HTC Allocation in 1990 and later are subject to a minimum 15-year extended use period, which begins after the close of the 15-year compliance period," and separately, in its Qualified Contract section, that "All properties will be subject to a LURA with a term of 30 years or longer."

What this research could not confirm is the mechanism or consequence of the elective extension beyond 50 years' cap and the 30-year floor — specifically, whether electing a longer term (35, 40, 45, or 50 years) earns Self-Scoring Worksheet points the way Texas's explicit 2/3/4-point Extended Affordability tiers do, or whether it is offered purely as a standalone election with no scoring benefit. Neither the QAP's Chapter 2.O (Declaration of Land Use Restrictive Covenants) nor its Chapter 5 selection-criteria sections, as reviewed in this research, tie the extension election to a named scoring category. Confirm directly with Minnesota Housing, or against the current Self-Scoring Worksheet, before assuming either way on a specific application.

Eventual Tenant Ownership (ETO) interacts with this term in one specific way: a project electing ETO receives a tie-breaker preference in Selection (Chapter 5.D), and "[u]ntil the time the HTC units are purchased by qualified tenants or in the event that not all HTC units are acquired by qualified tenants, the owner will extend the duration of low-income use for the full term of the LURA" — meaning an ETO election can functionally lock in the longer term regardless of whether the owner would otherwise have elected it.

The Qualified Contract door: a blanket waiver for every current award, but a fee schedule that still prices one

Minnesota's QAP describes the federal Qualified Contract mechanism under Section 42(h)(6)(E)(i)(II) in standard terms — if Minnesota Housing is unable to find a buyer within one year of a valid request, the extended-use period terminates, subject to the standard three-year post-termination tenant-protection period. But the QAP closes the door on new awards categorically: "Owners of properties that receive 4% or 9% HTCs are required by Minnesota Housing to waive the right to request a Qualified Contract." This is a blanket, agency-imposed waiver requirement — closer in structure to the mandatory waivers this library has already documented in New Jersey and Iowa than to Colorado's approach (where the mechanism itself is scoped out of existence for post-2019 awards by the federal statute's own terms) or Georgia's (a waiver newly added to the current QAP cycle).

Despite that blanket waiver, the current Multifamily Loan Programs and Housing Tax Credit Program Fee Schedule (effective August 20, 2026) still lists a $5,000 Qualified Contract Processing Fee as an active line item. This research could not confirm the specific population that fee schedule entry is meant to serve — most plausibly, HTC awards that predate Minnesota Housing's mandatory-waiver policy, or an administrative retention of the fee line pending a future policy change — so treat any pre-existing Minnesota HTC asset's Qualified Contract eligibility as a question to confirm against that specific deal's own recorded LURA, not as settled either way by the current QAP's blanket-waiver language alone.

Whichever way an extended-use period actually ends — natural expiration, a legitimate foreclosure or deed-in-lieu, or (for the narrow population not bound by the mandatory waiver) a failed Qualified Contract search — the same federal three-year tenant protection applies: for three years, an owner may not evict or terminate tenancy other than for good cause, and may not raise rents above the Section 42 limit. Minnesota Housing's Compliance Guide operationalizes this with its own annual reporting: owners must certify no bad-cause evictions occurred, report a recertification event for every household occupying a unit at expiration/termination ("Protected Households"), and report move-out dates — due February 15 each year, with no monitoring fee charged and no Minnesota Housing inspection required during this three-year window.

Monitoring cadence and fees: every 3 years during compliance, every 5 years after — and Form 8823 stops mattering

During the 15-year Compliance Period, Minnesota Housing must inspect each development at least once every three years, with the first review due no later than the end of the second year of the credit period. The inspection samples at least 20% of low-income units in each project (or the applicable Revenue Procedure 2016-15 minimum-unit-sample-size table for larger projects, whichever is less), reviewing tenant income certifications, supporting documentation, rent records, and a physical inspection conducted pursuant to HUD's National Standards for the Physical Inspection of Real Estate (NSPIRE) — HTC properties are not subject to NSPIRE's scoring protocol, but any NSPIRE-standard deficiency is treated as HTC noncompliance and is reportable to the IRS on Form 8823, filed no later than 45 days after the end of the owner's correction period regardless of whether the violation was actually corrected.

The compliance framework itself changes shape at the Year 15/16 boundary, and Minnesota Housing's Compliance Guide is unusually candid about why: "After the 15-year compliance period has expired, there may be no tax impact in the event of noncompliance; therefore, filing IRS Form 8823 to report noncompliance is no longer an effective consequence." Because IRS officials have indicated that allocating agencies may not report noncompliance to the IRS once the compliance period ends — the tax benefit is exhausted, and the IRS can no longer recapture or disallow credits — Minnesota Housing built a separate, internally-enforced set of extended-use-period policies rather than continuing the Form 8823 pipeline into Year 16 and beyond. Several Section 42 mechanics are relaxed accordingly during the extended use period: the student-status rule no longer applies (student status is not one of the LURA's own defined requirements), unit transfers between buildings are allowed without triggering noncompliance, the Available Unit Rule is simplified to a one-for-one replacement triggered only above 140% of the applicable income limit, and mixed-income properties no longer have to verify income and assets at annual recertification (a Sworn Statement of Income and Assets suffices) unless other financing requires it.

Minnesota's own enforcement lever after Year 15: Not in Good Standing, and losing the 4d(1) property tax break

In place of Form 8823, Minnesota Housing's extended-use-period enforcement runs through its own public status lists and a defined correction process: a Notice of Noncompliance triggers a correction period of up to 90 days (extendable another 90 days for good cause), and a property making good-faith progress on an agreed correction plan remains "in good standing" at Minnesota Housing's sole discretion. Serious or flagrant noncompliance — repeated delay, failure to submit certifications or fees, or ignoring the process outright — results in the property and owner (and any affiliated management company) being designated Not in Good Standing, published on Minnesota Housing's website and in a Report of Development Not in Good Standing (HTC 31), and cuts the owner and its affiliates off from any further Minnesota Housing funds or tax credit allocations until the property returns to good standing.

The consequence that ties directly into this state's property-tax system is stated in the Compliance Guide's own noncompliance list: "The property may be ineligible for a lower property tax rate under the Low Income Rental Classification (LIRC)." That is a genuinely Minnesota-specific enforcement lever — a property's real, currently-effective property tax reduction is put at risk by the same extended-use-period compliance failures that no longer generate a federal Form 8823 filing, so the practical stakes of staying in good standing with Minnesota Housing do not actually disappear at Year 15 even though the federal recapture exposure does.

The distinctly Minnesota mechanism: Class 4d(1) and the Low Income Rental Classification (LIRC) program

Minnesota Statutes Section 273.13, subdivision 25, and Section 273.128 together create a property-use classification commonly called "4d(1)" that carries a materially lower property tax class rate than a market-rate rental property. Since assessment year 2024, the 4d(1) class rate is a flat 0.25% (previously a tiered structure: 0.75% on the first $100,000 of each unit's estimated market value, 0.25% on the value above that). Minnesota Housing administers the qualification and annual certification process directly, under the name "Low Income Rental Classification" (LIRC) — a Program Guide (most recently dated November 16, 2023) governs the application mechanics.

To qualify, at least 20% of a property's units must meet one of several tests at the time the application is submitted: a project-based Section 8 HAP contract; rent- and income-restricted Section 42(g) LIHTC units (the category that puts nearly every Minnesota HTC deal automatically in scope); Rural Housing Service Section 521(a) rental-assistance units; or units subject to rent and income restrictions under other federal, state, or local financial assistance, where those restrictions independently cap initial-occupancy household income at 60% of the greater of area or state median income and cap rent at 30% of that same 60% figure. If only a portion of a building's units qualify, only that proportion of the building's value receives the 4d(1) rate.

The annual-reapplication requirement is written directly into the statute, not just Minnesota Housing's own Program Guide: Minn. Stat. Section 273.128, subdivision 1(b) states that "[t]o maintain the class 4d(1) classification, the property owner must annually reapply and certify to the Housing Finance Agency that the property tax savings were used for one or more eligible uses," and subdivision 1(c) separately requires a property that received 4d(1) in the prior year to "demonstrate compliance" with that same eligible-use requirement before it can qualify again. That reapply-and-certify language was added by the 2025 First Special Session (1Sp2025 c. 13, art. 2, section 7), effective beginning with assessment year 2026 -- which lines up with the LIRC Program Guide's own statement that the written-narrative compliance documentation applies "[b]eginning with Renewal Applications submitted in calendar year 2026." The statute also caps the application fee Minnesota Housing may charge at $10 per unit (subdivision 2(c)), and gives the agency limited flexibility on the March 31 filing deadline -- "or at a later date if the Housing Finance Agency deems practicable" (subdivision 2(a)) -- even though the LIRC Program Guide's own operational language currently treats March 31 as a hard, no-extensions cutoff. Confirm the agency's current practice before relying on that statutory discretion clause to excuse a late filing.

This is a real, ongoing compliance obligation layered on top of the federal Section 42 framework, not a one-time election made at placed-in-service — a Minnesota LIHTC pro forma that books the 4d(1) tax savings as a permanent, unconditional line item for the full 30-to-50-year LURA term is overstating certainty on two fronts: the annual March 31 renewal deadline (with no extensions, per the Program Guide's own language) and the eligible-use restriction on how the savings themselves may be spent.

What the sources don't settle

Three things below should be confirmed directly with Minnesota Housing, the Minnesota Department of Revenue, or a specific deal's own recorded LURA rather than treated as settled by this guide.

Whether electing to extend the LURA term beyond the 30-year floor (up to the stated 50-year maximum) earns Self-Scoring Worksheet points was not confirmed in the QAP sections reviewed in this research — unlike Texas's explicit, points-tiered Extended Affordability election, Minnesota's QAP describes the extension only as an owner election in its Declaration of Land Use Restrictive Covenants section, with no scoring cross-reference found. Confirm against the current Self-Scoring Worksheet before assuming either a scoring benefit or its absence.

What population the fee schedule's $5,000 Qualified Contract Processing Fee is actually meant to serve, given that Minnesota Housing's QAP requires a blanket Qualified Contract waiver from every current 4% and 9% HTC recipient, was not confirmed. The most plausible explanation — that it serves a legacy population of pre-waiver-era awards — is this guide's own inference, not something stated directly in either the QAP or the Compliance Guide.

Whether a property that loses 4d(1)/LIRC eligibility specifically because Minnesota Housing designated it Not in Good Standing (as opposed to failing the LIRC Program's own independent 20%-unit or eligible-use requirements) has any defined path to reinstate 4d(1) status once the property returns to HTC good standing was not addressed directly in either the Compliance Guide or the LIRC Program Guide as reviewed in this research — the two programs' guides describe their own processes independently rather than cross-referencing each other's reinstatement mechanics. Confirm directly with Minnesota Housing on any deal where this sequence is a live risk.