Legal requirements vary by affordable housing funding source

Regulation & Ethics tracker note

Last verified: Aug. 2, 2026, UTC. This record maps the legal requirements that attach to affordable housing development funding sources. It is a current-law reference for issue spotting and file review, not legal advice, and it does not substitute for deal counsel’s review of the current statute, regulation, state qualified allocation plan, subsidy documents, and recorded regulatory agreement.

The useful starting point is not whether a project is “affordable housing.” It is which dollar created which promise. A LIHTC allocation, a HOME loan, a HUD-assisted operating layer, and a CDBG-funded local subsidy can sit in the same capital stack while giving different public bodies different remedies.

Funding-source obligations map

That table is deliberately source-driven. It is too easy, especially after syndication or a refinancing, to inherit a closing binder and treat “affordability” as one umbrella covenant. The safer read is to trace each restriction back to the authority that can enforce it: the Internal Revenue Code for credits, the participating jurisdiction for HOME, HUD for HUD-assisted project operations, the local grantee for CDBG-funded terms, and the state allocation documents for deal-specific promises.

LIHTC: the federal regime has its own vocabulary

LIHTC is usually the load-bearing compliance layer because Section 42 is unusually specific. The project’s minimum set-aside election is not a loose affordability description. Section 42(g) recognizes the 20-50 test, the 40-60 test, and the average income test, with average-income designations in 10% AMI increments and an average not exceeding 60% of area median gross income. Gross rent for a low-income unit is capped by reference to 30% of the applicable imputed income limitation [1].

The common shorthand that “LIHTC requires 30 years” hides two different legal periods. The federal compliance period is 15 taxable years. Separately, Section 42(h)(6) requires an extended low-income housing commitment, recorded as a restrictive covenant, with an extended use period that runs at least 15 years beyond the compliance period [1]. A state agency may require a longer affordability term through its QAP, application scoring, or recorded agreement, but that is a state or deal-specific obligation layered on top of the federal minimum rather than a reason to blur the two periods.

Monitoring also has a defined channel. State agencies monitor LIHTC projects and report noncompliance to the IRS on Form 8823. Nebraska’s NIFA materials, for example, describe a 60-day period for the owner or manager to respond to notices of noncompliance [2]. That is useful as an example of agency practice, not a universal cure period for every state or every fact pattern.

Secondary enforcement commentary should be labeled as such. PRRAC and Shelterforce reported in 2023 that state correction periods typically provide at least 30 days and may be extended up to six months; the same article also discussed TIGTA findings involving approximately 67,000 claims and about $15.6 billion, and referenced a 20%-of-units inspection standard. Those figures are enforcement context from secondary reporting, not a substitute for Section 42, Treasury rules, the state monitoring policy, or the project’s recorded documents [6].

For counsel, the practical LIHTC question is therefore not just whether the project is tax-credit financed. It is which set-aside was elected, which income and rent limits attach to each unit, where the qualified-basis risk sits, how the state agency documents noncompliance, what the state will report to the IRS, and whether the recorded extended-use agreement imposes a longer or narrower promise than the federal baseline.

HOME adds a separate affordability clock and repayment consequence

HOME money should not be treated as a soft layer that merely helps a LIHTC deal pencil. HUD Exchange’s HOME rental housing requirements describe affordability periods that, under the baseline summarized there, run from 5 to 20 years depending on the activity and the amount of HOME funds invested per unit. The same HUD Exchange page states that if the housing does not meet affordability requirements for the specified period, the participating jurisdiction must repay the HOME investment [3].

That repayment duty falls on the participating jurisdiction as a federal-program matter, but the owner should expect the HOME written agreement, loan documents, and recorded affordability covenant to push practical risk back into the deal. A tenant-file failure, a rent-limit error, or an early loss of affordability can therefore matter under both the public funder’s HOME exposure and the owner’s contractual obligations.

The HOME analysis also needs a current-law warning. The 2025 HOME final rule affected current Part 92 statements, including affordability-period treatment for certain assistance levels and other program requirements. For a 2026 closing or refinancing, do not rely on a legacy HOME period chart without checking the current regulation, HUD guidance, and the participating jurisdiction’s written agreement.

HUD-assisted layers operate through project administration duties

A HUD-assisted layer brings its own operating file. In a practitioner summary of HUD funding compliance must-dos, BerryDunn identifies tenant eligibility files, monthly replacement-reserve deposits through Form HUD-9250, and residual-receipts calculations through HUD-93486, including remittance to HUD when residual receipts exceed $250 per eligible unit [4]. Those are not LIHTC set-aside questions, even if the same tenant file is used to support several programs.

This is where stacked deals become easy to misread. A rent that is acceptable under one layer may still create a problem under another. A reserve withdrawal that makes business sense may still require HUD approval. A tenant certification package that satisfies an investor’s annual review may still be incomplete for a HUD-assisted contract administrator. The legal risk turns on the document that created the duty, not on the staff label attached to the checklist.

CDBG and local layers belong in the stack review, but not in a generic checklist

CDBG-funded housing layers often appear as local subsidy, infrastructure support, acquisition assistance, or subordinate debt. This tracker does not attempt a detailed CDBG compliance taxonomy, so the safer treatment is document-specific: pull the grant agreement, local funding agreement, loan documents, eligible-use conditions, and recorded covenant before assuming the layer is merely economic.

The same habit applies to state-level funding records. A state housing measure, local bond program, or public loan can create a separate obligation even when it is politically described as one housing initiative; for an example of that source-by-source reading, see the related Regulation & Ethics record on California’s Housing Bond Act.

Layering changes the default analysis

A four-layer deal can have four different default paths. The state HFA may care about the LIHTC election and the recorded extended-use agreement. The participating jurisdiction may care about the HOME affordability period and repayment exposure. HUD may care about tenant eligibility, replacement reserves, and residual receipts. A local CDBG grantee may care whether its funded use and local covenant remain satisfied.

The state QAP deserves particular attention because it often converts application promises into enforceable deal terms. The National Housing Conference describes QAPs in the context of competitive 9% LIHTC allocations, where states use scoring and allocation criteria to direct tax credits [5]. Once those commitments are incorporated into allocation documents or the recorded regulatory agreement, they are no longer just application strategy.

That is why a closing checklist organized only by “LIHTC deal,” “HUD deal,” or “mixed-finance deal” is too crude. The file should identify the authority for each restriction, the document where the promise was recorded, the party that receives reports, the party that can declare default, and whether cure is governed by statute, agency practice, contract, or all three.

Before closing, refinancing, or inheriting the file

• Identify every funding source in the capital stack, including grants, subordinate public loans, rental assistance, tax credits, bond financing, and local soft debt.
• For each source, pull the governing statute or regulation, the award or allocation document, the written agreement, and any recorded covenant.
• For LIHTC, confirm the Section 42 set-aside election, rent and income limits, compliance-period status, extended-use term, state monitoring policy, and Form 8823 reporting path.
• For HOME, confirm the current Part 92 requirements, the applicable affordability period, the participating jurisdiction’s repayment exposure, and the owner’s pass-through obligations in the written agreement.
• For HUD-assisted layers, confirm tenant-file requirements, reserve deposits, residual-receipts treatment, withdrawal approvals, and the project-specific HUD forms in force.
• For CDBG or local funding, do not infer the compliance burden from the program name; read the award conditions and recorded restrictions.
• Separate federal minimums from stricter state QAP terms, application commitments, and deal-specific regulatory-agreement promises.

No affordable housing deal carries one uniform compliance burden. The legal exposure follows the money, and counsel’s job is to trace each dollar to the enforceable condition it bought.

References

1. 26 U.S. Code § 42 - Low-income housing credit, Legal Information Institute, Cornell Law School.
2. LIHTC Compliance, Nebraska Investment Finance Authority.
3. Key HOME Rental Housing Requirements, HUD Exchange.
4. HUD funding: Three compliance must-dos for affordable housing owners, BerryDunn.
5. Elements of Effective State Qualified Allocation Plans, National Housing Conference.
6. How Are LIHTC Rules Enforced, and How Well?, PRRAC and Shelterforce.