"We just got the Board's selection letter for a 2027 9 percent reservation — what actually has to happen, and by when, before Minnesota Housing can take the credit back?"
Reservation to carryover: fixed calendar dates, not a floating window
A 9% reservation is site-specific from the start — the QAP states that "changing a development's site could lead to the revocation of the HTC reservation/Allocation." Two elections lock in early and cannot be revisited: the applicable percentage (made at reservation or, by default, fixed to the month the building is placed in service) and the gross rent floor date (elected at any point from reservation forward, but the completed election form must reach Minnesota Housing no later than the placed-in-service date, or the gross rent floor defaults to the allocation date instead of whatever the owner might have preferred). Both elections are irrevocable once made.
A project that will not place in service within its allocation year must request a carryover allocation. Federal law (IRC §42(h)(1)(E)-(F); Treasury Regulation §1.42-6) lets Minnesota Housing grant one, and the QAP fixes the calendar around it precisely: a complete carryover application package is due to Minnesota Housing no later than October 1 of the allocation year for which the reservation was issued (or the next business day, if October 1 falls on a weekend or holiday), and the carryover allocation agreement itself "must be executed prior to December 31 of the allocation year for which the reservation was issued." The agreement must state the reasonably expected basis at the end of the second year after allocation and the amount of that basis that must be expended within one year.
| Requirement | Carryover (Ch. 6.B) | 42M application, bond deals (Ch. 7.C) | Placed-in-Service 8609, 9% (Ch. 6.C) | Placed-in-Service 8609, 4% (Ch. 7.H) |
|---|---|---|---|---|
| Market study | Yes | Yes | Not applicable | Not applicable |
| Owner Certification/Carryover Application | Yes | Not applicable | Not applicable | Not applicable |
| Election of Applicable Percentage | Not applicable (completed at reservation) | Yes | Not applicable (completed at reservation) | Yes |
| Building Information (HTC 5) | Yes | Yes | Not applicable | Not applicable |
| Attorney's Opinion Letter | Yes | Not applicable | Yes | Yes |
| CPA Certification | Yes | Yes (Minimum Percent Test Verification Letter) | Yes | Yes |
| Gross Rent Floor Election | Yes | Yes | Yes | Yes |
| Determination of Bond Issuer | Not applicable | Yes | Not applicable | Yes |
| Placed-in-Service Evidence | Not applicable | Not applicable | Yes | Yes |
| LURA | Not applicable | Not applicable | Yes | Yes |
| 8609 Certification by Owner | Not applicable | Not applicable | Yes | Yes |
Selected rows from the QAP's own Table 1; utility allowance, reserves/contingencies, partnership/operating agreement, identity-of-interest, and affirmative fair housing marketing plan are required at every stage and are omitted here for space.
The federal 10 percent test, run on an estimate-then-certify basis
Federal law requires more than 10% of the project's expected basis — including land — to be expended by the date one year after the allocation is made, verified by a CPA certification. Minnesota lets an owner submit that certification either with the carryover application itself or later, but if the final, CPA-certified basis and expenditure figures simply are not ready by October 1, the QAP requires "an estimate of the expenditure of greater than 10% of the expected basis" to be submitted in their place by that same October 1 deadline — the estimate holds the applicant's place, but it does not eliminate the requirement to eventually certify. The final CPA certification is still due by whichever comes first: the deadline set by Section 42 (as IRS relief may extend it) or Minnesota Housing's own Chapter 6.B deadline. Missing either one is treated as a late or incomplete carryover application and triggers Chapter 8.E's late fee plus an additional per-business-day penalty running from the missed due date through the date a substantially complete package finally arrives.
No carryover for bond deals — a 60-day, percentage-driven clock instead
A 4% credit financed with tax-exempt volume-limited bonds skips the carryover mechanism entirely; its controlling deadline is the 42(m) application, which "must be submitted to Minnesota Housing at least 60 days prior to the issuance of the tax-exempt volume limited bonds" sufficient — together with any bonds issued previously for the same project — to finance at least the Required Minimum Percentage of the project's aggregate basis. That percentage is itself a live, current federal-law question: the QAP sets it at 50% of aggregate basis for most projects, but at 25% for a project placed in service after December 31, 2025 where at least 5% of aggregate basis is financed with bonds issued after that date. A project that qualifies for the lower threshold needs materially less tax-exempt bond volume in its stack than the older 50% rule assumed — a genuinely different capital-stack math for a 2026-and-later deal than for one placed in service earlier.
Minnesota Housing's own processing estimate for the preliminary determination letter that follows a 42(m) application is "eight weeks or more from the time the full application package is submitted," and a preliminary determination fee is due before that letter is released. An applicant can get ahead of that clock with an optional (not required) pre-application track — a Predictive Cost Model determination and a Preliminary Scoring Determination, the latter filed at least 30 days before the 42(m) application itself — that flags a per-unit cost overrun or a scoring shortfall before the developer has committed to an actual bond issuance.
Reallocation is the only extension valve found in the QAP, and it is discretionary
This research pass did not find a formal, no-fault extension of the placed-in-service deadline anywhere in the QAP's body text. The closest thing to relief is Chapter 2.V's return-and-reallocation process: an owner who has received a carryover allocation but will not be able to place in service on time may ask Minnesota Housing to let them return the original Allocation and reallocate the same amount of credit in a future credit year, without a new application or a fresh scoring round. Minnesota Housing's own language is unambiguous about how discretionary this is: "Applicants should not assume that this reallocation will be automatically provided."
To even be considered, the owner must, at minimum: give Minnesota Housing timely written notice describing the circumstances, the remedial measures already attempted, and other relevant facts; show the delay stems from "extenuating circumstances beyond the reasonable control of the owner" — the QAP's own examples are fire, natural disaster, pandemic, or another large-scale industry disruption; demonstrate the project remains economically viable without additional HTCs or other Minnesota Housing deferred funding; and satisfy Minnesota Housing that the project still meets the selection criteria and minimum requirements of the QAP applicable to the new credit year, and still meets the community's affordable housing needs. A return-and-reallocation is capped at once per project, and a developer may only complete one such return-and-reallocation per year. The request carries a nonrefundable fee and requires Minnesota Housing board approval, and — separately from whether the request is granted — Minnesota Housing "may assess negative ranking points on subsequent applications from the applicant (or related entity)," a consequence that outlasts the single deal being rescued. A project that already carries a QCT or DDA designation at the time of its original allocation may retain it through a reallocation if doing so stays consistent with Section 42.
Miss every deadline, and the loss is total, not partial
Chapter 2.W is direct about the consequence of doing nothing: "a project that has neither received a carryover allocation nor has been placed in service and issued appropriate IRS Form 8609s before December 31 of the year of allocation will lose its entire Allocation of HTCs" — there is no prorated fallback for partial progress. An owner who never intends to use carryover at all, going straight from reservation to placed-in-service in the same allocation year, still faces a hard internal deadline: the 8609 application itself must reach Minnesota Housing by October 1 of that year for Minnesota Housing to be able to issue the 8609 before year-end. Separately, non-compliance with the terms of either a preliminary determination or an executed carryover agreement can itself cause a loss of HTCs, independent of whether the placed-in-service deadline is ultimately met — a project can be current on its calendar and still lose credit over a terms violation.
On the other side of placed-in-service, Minnesota Housing states it will make "reasonable efforts to issue an approved IRS Form 8609 within 60 days" once every required item has been received in satisfactory form and substance, and it recommends submitting the complete 8609 package within 30 days of project completion and at least 60 days ahead of any filing deadline the owner is working against — a package arriving later than that, or not received within 15 days of the close of the first year of the HTC period, is itself treated as late and can trigger a fee.
Where this goes wrong
- Treating the carryover deadline as flexible. The QAP fixes a complete carryover package's due date at October 1 of the allocation year and requires the carryover agreement itself to be executed by December 31 of that same year — both are calendar dates tied to the reservation year, not a window measured from the date the reservation letter happened to arrive.
- Assuming a missing CPA certification can simply be filed late. The QAP allows an estimate showing more than 10 percent basis expenditure to stand in at the October 1 deadline, but the final CPA certification is still due by the earlier of the federal deadline (as IRS relief may extend it) or Minnesota Housing's own Chapter 6.B deadline — missing either one triggers the Chapter 8.E late fee plus a per-business-day penalty.
- Applying the 9 percent carryover process to a bond-financed 4 percent deal. There is no carryover step for tax-exempt-bond deals at all; the controlling deadline is a 42(m) application due at least 60 days before bond issuance, evaluated against the Required Minimum Percentage test instead.
- Assuming 50 percent is still the Required Minimum Percentage for every bond deal. The current QAP drops that requirement to 25 percent of aggregate basis for a project placed in service after December 31, 2025 where at least 5 percent of aggregate basis is financed with bonds issued after that date — a materially smaller bond-volume requirement for a qualifying 2026-and-later deal than the older 50 percent rule.
- Assuming Minnesota offers a formal, no-fault extension of the placed-in-service deadline. No such provision appears in the QAP body text reviewed for this guide; the only relief mechanism found is the discretionary Chapter 2.V return-and-reallocation process, which requires proving extenuating circumstances beyond the owner's control, is capped at once per project, carries a nonrefundable fee, and is explicitly not guaranteed.
- Assuming a partial allocation survives a missed year-end deadline. A project that neither obtains a carryover allocation nor places in service and receives its 8609 by December 31 of the allocation year loses its entire Allocation under Chapter 2.W — there is no prorated outcome for a project that was most of the way there.
- Treating a reallocation request as cost-free beyond its own fee. Minnesota Housing may, at its sole discretion, assess negative ranking points against the requesting applicant or a related entity on that party's future applications — a consequence that follows the sponsor past the single deal being rescued.
- Assuming the applicable-percentage or gross-rent-floor elections can be revisited later. Both are irrevocable once made, and if the required election forms are not submitted by the placed-in-service date, the gross rent floor defaults to the allocation date rather than whatever date the owner might have preferred.
- Assuming staying current on the placed-in-service calendar is enough to keep the credit. Non-compliance with the terms of a preliminary determination or an executed carryover agreement can itself cause a loss of HTCs, independent of whether every calendar deadline is otherwise met.
- HUD
- LIHTC
- State QAPs
- IRS § 42
- Housing Finance Agencies