What Makes Affordable Housing Software Actually Useful?

One reported raise can need three different answers in a layered affordable housing file. HUD, USDA Rural Development, and LIHTC each measure the change their own way, on their own clock. Keeping those answers straight is what makes affordable housing software useful, and it is the same job a spreadsheet has when there is no software at all.

What Features Should Affordable Housing Software Have?

The basics are certification tracking, income and asset math, program forms, waitlists, document storage, and compliance reporting. They have to work across every program a portfolio touches: LIHTC (the Low-Income Housing Tax Credit program), HUD, USDA Rural Development (RD), HOME (the HOME Investment Partnerships Program), and layered funding. For the full picture, see what the category has to cover.

The harder part is what happens after a fact changes. A certification moves through intake, review, corrections, and approval, and every handoff is a chance for a number to get lost or typed in twice. For that path, see how certification work moves from intake to approval.

How Does One Income Change Ripple Through a Layered File?

Each program a household sits inside tests the change separately, using its own measure. So a single fact can require action on one layer and nothing on another.

Picture one household in a property layered with HUD Project-Based Rental Assistance, 100% LIHTC, and USDA Rural Development. One family member gets a raise and reports it. Here is what that single fact has to trigger, layer by layer:

1. HUD PBRA: does the change cross 10% or more of annual adjusted income? Under 24 CFR 5.657, that test runs on adjusted income, not gross pay. An earned-income increase only counts toward the 10% if the household already had an interim reduction earlier in that certification period. An owner can also skip the interim in the final three months of the certification period. If action is required, the regulation says the time taken generally should not exceed 30 days from the date the family reports the change.
2. USDA Rural Development: the same raise gets measured a different way. Under 7 CFR 3560.152, recertification is automatic at a flat $100 or more per month change, and a tenant can request one at $50 or more per month. RD counts dollars where HUD counts a percentage, so the same raise can land on the other side of the line.
3. LIHTC: there is no federal interim requirement at all. If the building is 100% low-income, the annual income recertification can be waived under 26 U.S.C. 42(g)(8)(B). That statute tests the entire building, so the waiver is a building-level rule. Two buildings in the same portfolio can sit on different rules in the same month.

When Is a Small Income Error Not a Compliance Problem?

HUD does not call it non-compliance when a monthly adjusted income error stays at $30 or less. Under 24 CFR 5.609, that is $360 in annual adjusted income, per family. The family still has to be credited or repaid if the error overcharged them.

That band changes how a reviewer sorts mistakes. A $12 rounding slip needs a correction. A $600 miscalculation can spill into other certifications on the same file, so it gets a closer look.

The same section gives operators a shortcut. An owner can rely on an income determination another federal means-tested program made in the previous 12 months. That includes TANF, Medicaid, SNAP, EITC, and SSI. Appropriate third-party verification still has to happen. To check the math on a specific file, run the tenant rent math yourself.

Why Do Workarounds Make Household Data Drift?

Workarounds make data drift because each one records the same household a little differently. When the right field is three menus deep, someone builds a side process to get around it. That side process rarely looks the same from one property to the next. Every portfolio has a few of them, and they usually live in a spreadsheet nobody will admit to owning.

The cost shows up later. The same household gets recorded one way at one property and another way at the next. Nobody notices until a file review or an audit pulls both records side by side.

Which Compliance Clocks Need Someone Watching?

The hardship clock is the easiest one to miss. Under 24 CFR 5.611, hardship relief ends when the circumstances that made the family eligible no longer apply, or after 90 days, whichever comes first. An entity can extend it in additional 90-day periods while the hardship continues, and only at its own discretion.

Somebody has to remember to make that call. A hardship case caught at day 75 still has time for a decision. At day 95 it is a finding with a date already attached. A monthly summary will not catch it in time. A list of what is past due, what is in review, and which files a recent change touched will.

Why Do HOTMA Dates Differ by Program?

Each agency set its own. HOTMA is the Housing Opportunity Through Modernization Act. HUD Multifamily and HUD PIH, the Office of Public and Indian Housing, both reach full HOTMA compliance on January 1, 2027. USDA Rural Development has required HOTMA-compliant certifications for anything effective on or after July 1, 2025, a deadline that has already passed. Each state housing finance agency also sets its own LIHTC HOTMA adoption date. A portfolio with properties on more than one program runs on more than one date. For the dates side by side, see HOTMA readiness by program and deadline.

Who Should Make the Call on a Layered File?

A trained person should. Tools can surface the facts fast, but when HUD, LIHTC, and RD disagree on the same household, someone who understands the file has to decide.

What Parts of Compliance Does No Software Own?

The agencies own their own systems. EIV, the Enterprise Income Verification system, belongs to HUD. Under 24 CFR 5.233, processing entities across nine HUD programs must use it to verify tenant employment and income during annual and streamlined reexaminations. Skipping it can mean sanctions or disallowed costs.

The state agency owns its own Tenant Income Certification format and its own monitoring portal. Any tool can format the data and send it. The agency still owns the receiving system and the rule's effective date.

How Do Teams Keep a Layered File Straight?

Tracking this by hand is hard, and plenty of teams still do it well with good spreadsheets and sharp reviewers. Whatever the setup, the check is the same. After a household reports a raise, someone on the team should be able to see every certification it touched.