Compliance, Year 15, and the 55-year tail — Iowa

Iowa's real extended-use math, and a qualified-contract waiver that's a threshold requirement, not a scoring choice

That 30-year figure is a floor, not a ceiling IFA has committed to holding at. Section 12.4's own language — the Extended Use Period ends 15 years after the Compliance Period closes "or the date specified by IFA in the LURA" — leaves room for IFA to record a longer term on a specific deal, the same way New York's regulatory agreement can run past its own QAP floor. Nothing in either QAP states a routine longer default the way California's 55-year term or New York's current 50-year Term Sheet minimum do; confirm the actual affordability end date on the deal's own recorded LURA rather than assuming either the 30-year floor or a 55-year round number.

What genuinely forecloses a Year-15 exit for any current-round Iowa award sits earlier in the QAP than the Extended Use Period definition — in Eligibility, not Terms and Conditions. Section 3.1 of both the 9% and 4% QAPs states, in identical language: "The Ownership Entity shall waive the right to a qualified contract in accordance with Section 42(h)(6)(F)." This is a mandatory condition of forming the Ownership Entity that applies, not an elected scoring trade-off. IFA's own Compliance Manual describes how this used to work: "many developers in Iowa waived their right to an early opt-out in exchange for additional points in the scoring and allocation process" — a voluntary, incentivized election on older awards. The current QAP text has converted that choice into a blanket requirement: every current-vintage Iowa award carries the waiver by default, full stop, before scoring ever begins.

IFA also builds a live incentive to stay in the program rather than exit at all. Both QAPs let an existing Tax Credit Project apply for a new allocation once it's past the close of its initial 15-year Compliance Period (9% QAP Section 3.5.G.2; 4% QAP Section 3.5.H.2), and both score the timing of that resyndication: the 9% QAP awards 1 point for a resyndication application "at the end of year 20 of the Compliance Period/Extended Use Period" (Section 6.5.B), while the 4% QAP awards up to 10 points — 10 points at year 25, 5 points for years 20 through 24 (Section 5.1.C.2). Combined with the mandatory QC waiver, the structural message of the current QAP is that Year 15 is a resyndication planning point, not an exit ramp.

The legacy Qualified Contract process — real, but only for pre-waiver deals

IFA still maintains a live Qualified Contract (QC) process, documented in its own standalone "Qualified Contract (QC) Process" policy (updated 06/2026) and restated in the Compliance Manual's Post-Year-15 chapter. Both sources are explicit about scope: the process "will apply to those properties that are eligible for opt-out at some point after year 15" — meaning an older allocation that either predates the current Section 3.1 waiver or elected to retain the right rather than take the scoring incentive to waive it. IFA tells owners to check two documents to find out which category they're in: the original submitted Application and the property's own recorded LURA. Nothing in the current QAP text or the QC policy states a specific award-year cutoff after which every Iowa deal is presumed to have waived — it has to be confirmed deal by deal.

The QC policy is candid about IFA's role: it is "not, and is not acting in the capacity of, a real estate agent or real estate broker" and undertakes no independent investigation of the accuracy of anything an owner submits. IFA posts the listing on its own site, sends it to a standing distribution list of investors, nonprofits and other agencies, and forwards buyer inquiries back to the owner — a marketing conduit, not a guaranteed sale. An owner who doesn't cooperate with that marketing effort — failing to respond to information requests, blocking property access, misstating material facts — forfeits the process outright and stays bound to the full LURA term. IFA separately maintains a public listing of properties actually in the QC process at welcomehomeia.com/section-42/, though this research did not review that live listing for its current contents.

Compliance monitoring runs through IFA itself, and the inspection cadence halves at Year 15

IFA is the compliance-monitoring agency of record under Iowa Code Section 16.35, and its own Compliance Manual names an assigned "Compliance Officer" for each audit rather than a contracted outside firm. The manual is explicit, though, that it has not foreclosed delegation: the Physical Inspection Protocol section opens with "IFA may use a contractor to conduct physical inspections and any references to IFA below may mean IFA and/or our contractors," while a separate closing chapter frames delegation as a live option rather than a current practice — "IFA may in the future decide to retain an agent or private contractor to perform some of the responsibilities listed above," adding that if it does, "IFA will always retain responsibility for notifying the IRS of any noncompliance of which it becomes aware via Form 8823." Read together, the honest summary is that IFA performs monitoring in-house today and has reserved, but this research did not confirm it has exercised, the option to hand physical inspections to a named third-party firm the way Florida contracts that function out.

IFA can accelerate either cadence at its sole discretion if a development shows numerous or severe violations, and continues giving 30 days' written notice before any post-Year-15 inspection so owners can prepare residents and files. What changes materially at Year 15 is the paperwork underneath the inspection, not just its frequency: full annual income recertification stops for most projects (it continues only for mixed-use and Deep Rent Skewed projects and units carrying a state covenant set-aside at a mixed-income 100% LIHTC property), LIHTC student-status rules stop applying outright (with the manual's own caution that a project planning resyndication should keep applying them anyway), and the Available Unit Rule narrows from a "comparable or smaller size" standard to a strict one-for-one unit replacement. Record retention runs the opposite direction — longer, not shorter: beginning in year 16, an owner must keep a resident's file for that family's entire term of residency plus one additional year after they vacate.

The enforcement mechanism itself changes at the same boundary. During the 15-year Compliance Period, IFA reports federal noncompliance to the IRS on Form 8823 after a correction period that runs 90 days, extendable to a total of six months at IFA's discretion for good cause; purely state-covenant violations instead draw a State Notice of Noncompliance, with no federal tax exposure. Once the Compliance Period ends, IFA stops filing Form 8823 altogether — "there is no tax impact in the event of noncompliance" once the Extended Use Period begins — and repurposes a modified version of that same form purely as a State Notice of Noncompliance for LURA violations, issued once the same 90-day correction window closes without a cure. For systemic or chronic post-Year-15 noncompliance, the manual adds that "temporary suspension and/or debarment procedures may be implemented," without further detail in the text reviewed this session.

The ongoing cost of staying in, and what property-tax relief actually exists

The $42-per-Unit annual compliance monitoring fee covered in Phase 10 isn't a closing-year line item — it's the one IFA charge that runs the entire 30-year tail. The QAP's own worked example states it plainly: "$42 per Unit x 24-Unit Project = $1,008 paid annually for 30 years," due each December 31 through both the Compliance Period and the Extended Use Period, with an option to prepay the whole term in advance — though IFA reserves the right to bill an owner who prepaid for any rate increase adopted during that same 30 years (IFA 9% QAP Section 2.2; 4% QAP Section 2.2). Scattered Site Projects of 5 or more sites carry an additional $10-per-Unit annual charge on the same schedule.

On property tax, Iowa Code Section 427.1(21) is a real, narrow exemption worth knowing rather than assuming applies broadly: it exempts property "owned and operated or controlled by a nonprofit organization ... providing low-rent housing for persons who are elderly and persons with physical and mental disabilities," and — unlike Ohio's genuinely unresolved question about a for-profit LP with a nonprofit GP — the statute explicitly allows "the controlling nonprofit entity [to] serve as a general partner or managing member of a limited liability company or limited liability partnership which owns the property," the standard LIHTC ownership structure. But the exemption's own clock is tied to financing, not affordability: it runs only "until the final payment due date of the borrower's original low-rent housing development mortgage or until [that] mortgage is paid in full or expires, whichever is sooner" — a window that can close well before the LURA's 30-year term does, and that has nothing to do with family (non-elderly, non-disability) LIHTC projects at all. This research did not locate any LIHTC-specific, statewide property-tax exemption comparable to New York's RPTL Section 420-c or Ohio's CRA program that reaches a typical family Iowa Tax Credit project; any abatement on a family deal would have to come from a locally negotiated, city-by-city arrangement that this session did not independently verify.

What the sources do not settle

Three things should be treated as open questions to confirm directly with IFA or the deal's own recorded documents, not as settled facts drawn from this guide.

No standalone, currently published Iowa LURA or Extended Use Agreement template was located on IFA's resources page. The Compliance Manual states that "IFA will prepare a Land Use Restrictive Agreement (LURA) prior to the issuance of the IRS Form 8609," which reads as a per-project document IFA drafts rather than a fillable template it publishes — so while Section 3.1's waiver obligation is confirmed QAP text, the exact language IFA actually records in a given LURA (and whether it reproduces the Section 42(h)(6)(F) waiver verbatim) could not be independently verified this session.

Whether IFA has ever actually delegated physical inspections to a named third-party contractor — as opposed to reserving the option — was not confirmed. The Compliance Manual's own two references to contracting (one describing it as already possible, one describing it as a future decision) sit in some tension with each other, and no contractor is named anywhere in the manual or the QAP.

The QAP's own naming is inconsistent in a way worth flagging rather than silently correcting: the 9% QAP calls the recorded instrument the "Land Use Restriction Agreement (LURA)" (Section 13.3), while the 4% QAP calls the same document the "Land Use Restrictive Covenants Agreement (LURA)" (Section 8.3). Both define the same acronym and the same underlying obligation; the difference appears to be a drafting inconsistency between the two QAPs rather than two different instruments.