Compliance, Year 15, and Idaho's 30-year floor — with a Qualified Contract right that isn't blanket-waived — Idaho

The compliance/extended-use math: 30 years confirmed by IHFA's compliance manual, not restated in the QAP itself

The Compliance Manual states the definitions in federal terms: under IRC §42(j)(1), “the compliance period means, with respect to any building, the period of 15 taxable years beginning with the first taxable year of the credit period,” with the first year being either the year a building is placed in service or, at the owner's election, the following year. It then addresses the extended use period directly: “According to Section 42 of the IRS, all buildings that receive allocations of tax credit after December 31, 1989, must comply with additional eligibility requirements in effect beginning January 1, 1990. Such developments are committed to an extended use period, as stated in each development's individual regulatory agreement. After developments are placed in service, they must comply with eligibility requirements for at least an additional 15 years beyond the initial fifteen 15-year compliance period, for a total of at least thirty 30 years.” Elsewhere the manual defines the extended use period with IRC §42(h)(6)'s own mechanics: beginning on the last day of the compliance period and ending on the later of the date specified in the regulatory agreement or 15 years after the close of the compliance period.

The manual adds one more sentence worth carrying into underwriting: “Many developers have committed to longer extended use periods. Previous IHFA Qualified Allocation Plans (QAP) have granted preference points to those developers who were willing to expand the extended use period beyond the minimum fifteen 15-year requirement.” That confirms the 30-year figure is Idaho's floor, not its ceiling, and that the current QAP's 40-year Preference Point (below) continues a pattern IHFA has used across QAP cycles rather than introducing something new. Note the Compliance Manual itself is dated June 26, 2020 — six years old at the time of this research, and IHFA's compliance-resources page lists no newer version — so treat program mechanics that could plausibly have changed (fee amounts, specific procedural windows) as needing a cross-check against the current QAP, while the compliance-period/extended-use-period math itself is IRC-driven and not something a QAP or manual revision would likely change.

The 40-year Preference Point: an opt-in scoring choice, not a QAP-wide floor

Section 6.5's Preference Points category leads with its highest-value item: 15 points — more than any other single preference listed — for “Developments that are obligated to provide low-income use 25 years beyond the initial 15-year compliance period.” The QAP's own text spells out what that buys IHFA in return: “This 40-year obligation requires the waiver of the Qualified Contract provision for the purpose of converting to market-rate use until one (1) year before the final year of the 40-year obligation and thereafter shall be subject to the three (3) year provisions regarding eviction and rent increase.” Projects that claim these points must have that commitment written into their Low-Income Housing Regulatory Agreement.

Read carefully, this is an opt-in trade, not a universal rule: an Applicant that wants the 15 points accepts a QC waiver that runs almost the full 40-year term (QC becomes available only in the 40th year), while an Applicant that doesn't pursue those points keeps whatever QC rights its Regulatory Agreement otherwise provides at the 30-year floor. This is the opposite structure from states that waive QC unconditionally on every award and then offer no route back to it — in Idaho, waiving QC (partially or in exchange for extending it almost to Year 40) is the price of extra scoring points, not a blanket condition of every award.

Qualified Contract: a live process, gated by your specific Regulatory Agreement, a 14-year floor, and a $25,000 fee

Section 17.1 opens with the conditional that matters most: the statutory QC process under IRC §42(h)(6)(E)(i)(II) is available “if such rights have not been waived in the LIHTC Regulatory Agreement or said Agreement does not provide for such right.” IHFA also “reserves the right not to permit the Qualified Contract in future Regulatory Agreements” — meaning the QC landscape in Idaho is deal-vintage-specific: a development awarded under an older QAP cycle, or one that didn't chase the 40-year Preference Point, may have full QC rights at Year 15; a development that took the 40-year points has a QC waiver running to Year 39; and IHFA could choose to write QC out of Regulatory Agreements going forward. The Compliance Manual's own guidance to owners on this point is blunt: “Prior to contacting the manager, please review the language in your regulatory agreement to determine whether this is a viable option for your property.”

Where QC is available, the QAP sets four gating conditions before a request can even be submitted: the right to request must not have been waived in the Regulatory Agreement; at minimum 14 years of the compliance period must be completed for every building in the development (measured, for multi-building/multi-year placed-in-service developments, from the last building's placed-in-service year); the property must be in full §42 compliance, with all violations corrected; and the development must secure a complete, unconditional waiver of all purchase options, including any nonprofit general partner's right of first refusal. Once a complete request and the application fee are received, IHFA has one year to present a qualified contract at a price calculated under §42(h)(6)(E)(i)(II) using IHFA's own forms and directives; IHFA may treat a Sponsor's lack of cooperation in marketing or documentation as suspending that one-year clock, and can reject a future QC request from a Sponsor who previously abandoned or rejected a presented contract.

Compliance monitoring: Years 1–15 vs. the Extended Use Period

For a new project, IHFA's first monitoring inspection must occur “no later than the end of the second year of the credit period,” matching the federal floor under Treas. Reg. §1.42-5. After that, cadence during the initial 15-year compliance period is scored: properties rated superior or above-average are monitored every three years, satisfactory-rated properties every two years, and any property rated below-average or unsatisfactory (overall or in any single category) is monitored annually until it earns a satisfactory rating — with a below-average/unsatisfactory rating also triggering watch-list status, and a second consecutive poor rating changing status to not-in-good-standing. Sample size during the first 15 years is a minimum of 20% of household units (and the same percentage of tenant files); IHFA also inspects all common areas, grounds, building systems, exteriors, and maintenance facilities against HUD's Uniform Physical Condition Standards (UPCS). Form 8823 (“Report of Noncompliance or Building Disposition”) must be filed with the IRS no later than 45 days after the correction period ends, whether or not the noncompliance was actually corrected.

Once a development transitions into the Extended Use Period, the sample size drops — IHFA samples a minimum of 10% of household units in the extended use period (versus 20% during the first 15 years) and the same percentage of tenant files — while the three-year inspection cadence continues (“At least every three years, IHFA will perform a physical inspection”), with the first extended-use review occurring “no more than three years from the last inspection conducted during the compliance period.” The manual caps a single inspection at 10% of low-income units, not to exceed 15 units in any development, and notes that IHFA may choose different units for the physical inspection than for the file review. Because there's no federal tax consequence to noncompliance after Year 15, Form 8823 filing generally stops being an effective enforcement tool; IHFA instead relies on its own watch-list/not-in-good-standing status, correction periods of up to 90 days, and — for serious or flagrant noncompliance — withholding future IHFA funds and tax credits from the owner, its partners, and any management company involved, until good faith correction is demonstrated.

Property tax: Idaho Code §63-602GG excludes active LIHTC properties from its nonprofit housing exemption — no PILOT program was found

Idaho does have a targeted property-tax exemption statute for affordable rental housing — Idaho Code §63-602GG, “Property exempt from taxation — Low-income housing owned by nonprofit organizations” — but its structure works against a typical syndicated LIHTC deal rather than for one. To qualify at all, an organization must be a nonprofit corporation under Idaho Code Title 30, Chapter 30 (or an equivalent out-of-state law) with 501(c)(3) status, and no proceeds or tax benefits may inure to any individual or for-profit entity beyond normal employee compensation (§63-602GG(2)). The property itself must then meet its own conditions: “Both legal and equitable title to the property is solely owned by the nonprofit organization seeking the exemption” (§63-602GG(3)(a)) — a bar that a standard LIHTC ownership structure (a limited partnership with a for-profit investor limited partner, even where the general partner is a nonprofit) does not clear, because title sits with the partnership entity, not solely with the nonprofit. The property must also independently dedicate its units in specific tiers — 55% of units to households at or below 60% of county median income, 20% at or below 50%, and 25% at or below 30% (§63-602GG(3)(c)) — a different mix than the standard LIHTC 20/50 or 40/60 minimum set-aside elections, so even a qualifying nonprofit-owned property would need to check its unit mix against this statute's own tiers separately from its §42 set-aside.

The statute then closes the door explicitly on active tax credit deals: the exemption “shall not apply … to any property used by a taxpayer to qualify for tax credits under the provisions of 26 U.S.C. chapter 42 or any successor programs until such time as the property is solely owned by a nonprofit organization as defined in this section and is no longer utilized to receive federal tax credits” (§63-602GG(4)(c)). Read together with the sole-ownership requirement above, that means a typical Idaho LIHTC development — for-profit investor limited partner in place, credits still being claimed — is affirmatively excluded from this exemption for essentially the entire compliance and extended use period; the exemption becomes reachable only after the property both exits the tax credit program and converts to sole nonprofit ownership (for example, following a nonprofit GP's post-Year-15 acquisition via right of first refusal). The statute separately excludes properties receiving certain federal project-based assistance under 42 U.S.C. §1437f(d)(2), (f)(6), or (o)(13), and includes an undue-hardship carve-out only for properties financed before the statute's effective date whose financing depended on tax-exempt status. This research found no state-level PILOT (payment-in-lieu-of-taxes) program for LIHTC properties in IHFA's QAP, compliance manual, or program materials — that doesn't rule out a city- or county-specific PILOT arrangement, but none was confirmed, so treat property tax as fully assessable at the local jurisdiction's normal rate for a standard syndicated deal unless a specific local agreement says otherwise.

Prevailing wage: no state law since 1985, and the QAP is silent

Idaho repealed its own state prevailing-wage (“little Davis-Bacon”) statute in 1985 and has had no state-level prevailing wage law since, per the Congressional Research Service's survey of state prevailing wage statutes (CRS Report RS20940). A full-text search of the 2026 QAP found zero references to “prevailing wage” or “Davis-Bacon” anywhere in the document — IHFA does not layer a state wage requirement onto LIHTC construction, and the QAP doesn't flag the topic even as a pass-through disclosure. That does not mean federal Davis-Bacon requirements can never apply to an Idaho LIHTC deal: Davis-Bacon attaches through separately layered federal funding — HOME Investment Partnerships funds, USDA Rural Development financing, or HUD project-based Section 8, all of which the QAP itself discusses elsewhere as common LIHTC layering sources — not through a LIHTC allocation by itself. A development financed with 9% or 4% credits alone, with no other covered federal source in the capital stack, would not be subject to Davis-Bacon on IHFA's own program terms.