Construction through placed-in-service — Minnesota

Design and accessibility: the Fair Housing Act and Minnesota's own Type A Unit standard — but only for state-financed deals

Minnesota Housing's Multifamily Rental Housing Design/Construction Standards (Last Updated: May 2025, covering the 2025-2026 Consolidated RFP and 2026-2027 HTC funding rounds) states plainly that its new-construction accessibility requirements "only apply to multifamily projects containing four or more units...that are financed by Minnesota Housing, including projects receiving only HTCs allocated by Minnesota Housing. Developments receiving only HTCs from a local sub allocator are exempt from this standard and need only comply with the Minnesota State Building Code provisions and the sub allocator's requirements." That is a real scope limit worth tracking on any Minneapolis or Saint Paul deal, since both cities are Housing Tax Credit Suballocators under Minnesota Housing's own QAP — a project relying solely on a Suballocator's HTC allocation is not automatically bound by Minnesota Housing's own design standards, and has to be checked against whatever the Suballocator itself requires.

For a project that is bound by the standards, the design chapter requires compliance with the Fair Housing Act of 1968, as amended, on top of applicable state and local codes, and sets Minnesota-specific unit-count minimums: "A minimum of 5% of the total housing units (with its fraction rounded up) in the project must be designed and constructed to meet accessibility requirements for a Type A Unit as promulgated by the Minnesota Accessibility Code," applying to townhouses as well as every other multifamily unit type. Separately and additionally, "at least 2% (but not less than one unit) of the total housing units must be adaptable for persons with vision/hearing impairments," with rough-in wiring for audible and visual alarm devices under ICC/ANSI A117.1. Accessible parking must be provided to match the Type A Unit count, and if grab bars are not installed at initial occupancy in a Type A Unit, the owner remains responsible for installing code-compliant grab bars immediately upon a resident's request.

Section 504 of the Rehabilitation Act of 1973 and the Architectural Barriers Act appear in the Design/Construction Standards only in two places, and both are narrower than a blanket LIHTC requirement: (1) as part of the Accessibility Analysis and Survey required for rehabilitation projects that also carry federal financial assistance (in addition to what a no-federal-assistance rehab project must already show under the Fair Housing Act and Titles II/III of the ADA), and (2) inside Chapter 7, "Design, Construction, and Property Standards for Federally Funded Projects," which applies specifically when a project is awarded HOME or National Housing Trust Fund (NHTF) proceeds from Minnesota Housing — both of which cite 24 CFR Part 8 (implementing Section 504) and Titles II/III of the ADA. A Housing Tax Credit allocation on its own, without a HOME or NHTF layer, does not appear from this research to trigger Section 504 or UFAS as an independent, universally-applicable Minnesota Housing standard — confirm against the specific federal funding sources layered into a given deal rather than assuming Section 504 attaches to every Minnesota HTC award.

Senior Housing Projects (100% of units restricted to age 55-plus) must meet Minnesota Housing's Universal Design requirements regardless of funding source, and must submit a Universal Design Worksheet both at application and again before 100% Construction Document approval. Any project separately awarded Universal Design scoring points in the Self-Scoring Worksheet carries the same Worksheet-compliance obligation. The Design/Construction Standards also require an Accessibility Analysis and Survey for every rehabilitation project — conducted by an architect, qualified needs assessor, or qualified rehabilitation specialist — before the work scope is finalized, whether or not federal assistance is present, with the survey's required contents (unit counts by accessibility type, identified deficiencies, feasibility determination, cost estimates) spelled out in the standards themselves.

Prevailing wage arrives at Minnesota LIHTC: Minn. Stat. Section 116J.871, DLI enforcement, and certified payroll gating Form 8609

Unlike several states this library has already covered where state prevailing wage law simply does not reach a privately-owned LIHTC deal, Minnesota's does — and it does so through a statute written specifically to reach Housing Tax Credit projects. Minnesota Housing's own "State Prevailing Wage Frequently Asked Questions" document (an external guidance document, most recently revised 4/10/2026 per its own version history) states that new construction projects, including adaptive reuse, are subject to state prevailing wage requirements under Minnesota Statute Section 116J.871 if selected for an award or allocation of federal Housing Tax Credits on or after January 1, 2025, and the project consists of more than ten units. Separately and independently, new construction or rehabilitation financed with a Minnesota Housing loan of $500,000 or more or a grant of $200,000 or more triggers the same statute regardless of HTC involvement — a threshold that reaches essentially every Minnesota Housing first-mortgage or gap-financing tool (LMIR, Bridge Loans, FFCC, state-appropriated funds, state bond proceeds, State Housing Tax Credit funds, and federally-appropriated funds passed through Minnesota Housing, including HOME and NHTF). A separate, older statute — Minn. Stat. Sections 177.41 through 177.44, sometimes called the Minnesota Prevailing Wage Act — applies independently to publicly-owned new construction or rehabilitation projects with an estimated cost of $25,000 or more; the FAQ states the two statutes "are not mutually exclusive" on a publicly-owned project.

The Department of Labor and Industry, not Minnesota Housing, is the agency that actually sets and administers Minnesota's state prevailing wage rates and answers substantive compliance questions — the FAQ is explicit that it is "secondary to guidance provided by the Department of Labor and Industry (DLI)" and that "questions about applicability regarding prevailing wage should be directed to DLI." Minnesota Housing's own role is narrower: collecting the Prevailing Wage Certification Form (which the developer submits directly to DLI and then provides an executed copy of to Minnesota Housing before closing) and running the ongoing payroll-reporting pipeline through construction.

The underlying codified statute confirms this mechanism precisely. Minn. Stat. Section 116J.871, subdivision 1(c)(4) defines "financial assistance" to include "allocations or awards of low-income housing credits by all allocating agencies...for which tax credits are used for multifamily housing projects consisting of more than ten units" -- the exact statutory hook for the HTC-specific trigger described above. Subdivision 2(a) requires the person receiving that assistance to certify directly "to the commissioner of labor and industry" (DLI's statutory title) that laborers and mechanics will be paid the prevailing wage rate, and subdivision 2(b) contains an unusual deeming clause: for purposes of the certified-payroll recordkeeping requirements in Section 177.30, "the state agency or allocating agency awarding the financial assistance is considered the contracting authority and the project is considered a public works project" -- a legal fiction that pulls a privately-owned HTC deal inside the public-works recordkeeping framework for this purpose alone. The penalty has real teeth: subdivision 3 makes it a misdemeanor for a person who certified that prevailing wages would be paid to subsequently fail to pay them, with each day of continued violation charged as a separate offense.

That reporting pipeline is where Minnesota Housing's verification during construction monitoring actually happens, and it is tied directly to money and to the path to Form 8609. Once a project is subject to state prevailing wage, the employer must furnish a Certified Payroll Report at least every two weeks throughout construction, uploaded into LCPtracker (an online payroll-tracking system Minnesota Housing began requiring, per the FAQ's own revision history, as of the April 2026 update). Each report requires an oath and signature from an owner or officer of the employer and states, per employee, name, identifying number, prevailing-wage job classification, hours worked each day, rate of pay, gross and net pay, deductions, and fringe-benefit contributions and administrator information — see Minn. Stat. Section 177.30(a)(6)-(7) for the full record-keeping list the FAQ cites.

That last consequence is the one worth building directly into any Minnesota construction schedule: Minnesota Housing's own FAQ states outright that Form 8609 issuance is contingent on being current with certified payroll reporting, not merely on completing construction and cost certification. A project that is otherwise ready for its 8609 application but has fallen behind on biweekly LCPtracker submissions — even for a portion of the job unrelated to any actual wage underpayment — has created its own closing delay.

Cost certification splits on identity of interest — and the QAP itself is thinner on audit standards than some other states' agencies

Minnesota Housing publishes a short, separate quick-reference document, "Cost Certification Requirements" (Updated March 2024), that sets a materially different standard depending on two variables: which entity is certifying costs, and whether an identity of interest exists between the owner and the general contractor. This structure is worth reading closely, because the QAP's own Appendix A table lists only a generic "Certified Public Accountant Certification" line item without describing an audit standard — the actual audit-versus-notarized-statement distinction lives in this separate document, not in the QAP itself.

Timing differs by financing structure as well. For a 4% or 9% Housing Tax Credit project carrying no Minnesota Housing loan, cost certification is required with the application for Form 8609 — folded into the same submission package discussed below. For a project with a Minnesota Housing deferred loan or LMIR first mortgage, cost certification is instead a Post-Construction Due Diligence checklist item, required after final contractor payment but before final draw close-out — a separate, earlier gate tied to Minnesota Housing's own lending function rather than to the tax credit allocation itself.

What this research could not confirm is whether the CPA's audit of HTC Form 9 or HUD Form 92330A is held to the same government-auditing-standards ("Yellow Book") bar that some other states' agencies write directly into their QAP text. Minnesota Housing's own published materials describe the certification as "audited," without further specifying GAAS-only versus GAAS-plus-Government-Auditing-Standards — that distinction may live in the HTC Form 9 template itself (available only through the Multifamily Customer Portal and Post-Selection Materials webpage, not independently reviewed in this research). Confirm the actual engagement-letter language required on HTC Form 9 directly with Minnesota Housing's Multifamily Division before assuming either standard applies.

The path to Form 8609: no agency-run construction inspections in the QAP, but a real document package and a real fee

A structural point worth stating plainly: this research did not find, in either the QAP or the Design/Construction Standards, an agency-assigned quarterly (or any fixed-cadence) physical inspection program running during construction itself, the way some other states' allocating agencies operate. Minnesota Housing's own compliance-monitoring inspection cycle — discussed in full in this guide's Phase 11 entry — begins after a building is placed in service, with the first review due "no later than the end of the second year of the credit period." The one construction-period inspection function this research did confirm, the "Loan Closing and Construction Oversight Fee," is a flat fee ($25,000 to $75,000 depending on the aggregate Minnesota Housing loan amount, per the current Multifamily Loan Programs and Housing Tax Credit Program Fee Schedule) tied to Minnesota Housing's own construction lending on projects that carry one of its direct loan products (LMIR, Bridge Loans, EDHC, ERA2 Capital, FFCC, Housing Infrastructure loans/bonds, or PARIF) — a lender's construction-draw oversight function, not a tax-credit-program-wide inspection requirement that reaches every HTC deal regardless of financing source.

The placed-in-service date itself is defined the standard federal way — the date the first unit in a building is certified as available for occupancy — and must occur for every building in a project by the Section 42 deadline (as it may be extended by IRS relief). Minnesota's QAP recommends, rather than strictly requires ahead of a hard cutoff, that owners submit the complete Form 8609 application package no later than 30 days after completion and at least 60 days ahead of any required filing deadline; a package not received within 15 days of the last day of the first year of the HTC period is treated as late and may draw a fee. Minnesota Housing states it will make "reasonable efforts" to issue an approved Form 8609 within 60 days of receiving a complete, satisfactory submission — a target, not a guarantee.

What the sources don't settle

Three things below should be confirmed directly with Minnesota Housing or a specific deal's own documents rather than treated as settled by this guide.

The QAP's own text does not describe a Minnesota-specific administrative process for the federal 10% expenditure test (IRC Section 42(h)(1)(E)) the way some other states' QAPs do — what this research found instead was the October 1 carryover-package deadline and a separate "return of allocation" provision for missed placed-in-service deadlines due to extenuating circumstances. The 10% test itself remains a live federal requirement on any deal holding a Carryover Allocation; Minnesota Housing simply may address its own verification of that test through a document (an application form, or the Multifamily Customer Portal's carryover checklist) not captured in the QAP's narrative text reviewed in this research.

Whether the CPA audit required on HTC Form 9 (owner cost certification) or HUD Form 92330A (GC cost certification, identity-of-interest deals) must meet Government Auditing Standards ("Yellow Book") in addition to ordinary GAAS was not confirmed — Minnesota Housing's public-facing documents describe the certification as "audited" without specifying which standard, and the underlying form templates live behind the Multifamily Customer Portal login.

Whether Minnesota Housing's design/accessibility standards, prevailing wage collection duties, or cost-certification requirements described above apply on identical terms to a project whose only HTC allocation comes through a Suballocator (Minneapolis or Saint Paul) was only partly confirmed: the Design/Construction Standards explicitly exempt Suballocator-only HTC deals from Minnesota Housing's own accessibility minimums, but this research did not separately confirm whether Minneapolis's and Saint Paul's own Suballocator procedures independently impose the state prevailing wage statute's certified-payroll requirement on the same terms Minnesota Housing does. Confirm directly with the applicable Suballocator on any city-allocated deal.