The Best Affordable Housing Software for HOTMA Compliance in 2026

HUD Multifamily and public housing agencies both hit full HOTMA compliance on January 1, 2027. They run under two separate notices with two separate histories. Notice H-2025-07 covers Multifamily, and Notice PIH 2026-15 covers public housing and vouchers. HUD has already published the 2027 factor tables that take effect that day. Every deduction, asset limit, and passbook rate a system uses has to flip on that date, per property, without breaking files certified the day before.

What is HOTMA and why does it change how you should buy compliance software?

HOTMA is the Housing Opportunity Through Modernization Act. It rewrites how you calculate income, assets, and deductions for housing that takes federal money. It does not roll out on one date for the whole industry. It also does not touch the 30% and 10% income tests, the $25 minimum rent, or the HAP and tenant-rent formulas. Those stay the same. Want the rule change itself, including the medical phase-in math and the layered timelines? the HOTMA rule changes themselves cover that ground in full.

This post asks a narrower question. Once you know the rule, what should your software do about it? Every major HUD program now lands on the same date, January 1, 2027. That is true whether the property answers to Multifamily Housing or to PIH, HUD's Office of Public and Indian Housing. HUD already published the numbers that take effect that day. That makes this a software problem, not just a training problem. A platform has to hold two rule sets and apply the right one per property. Then it has to prove which one it used on a file certified last month.

Most vendor pages answer a different question. They say "we support HOTMA." That is true of almost every platform in this post. What they rarely say is whether the platform can run pre-HOTMA and HOTMA math on two properties in the same portfolio, on the same day. It should do that without a manual switch someone has to remember.

What should HOTMA-ready compliance software actually do?

A features page that names HOTMA proves nothing. Six jobs come straight out of the rule. A platform either does them, or someone on your team does them by hand.

Teams miss the second row most often, so here it is in full. These are HUD's published annual factors. Every line moves on January 1, 2027.

Source: HUD's annual inflationary adjustments and passbook rate, published through HUD USER. The CY2027 set went out on August 5, 2026. Seven values changed on one effective date. The passbook rate went down while the rest went up. A system that stores one set of numbers gets all seven wrong at once.

AppFolio publishes the clearest example of the first item on that list. It offers a property-by-property toggle that "lets property managers switch between current and HOTMA-compliant calculations, allowing teams to train and test new processes without making the full switch until the deadline." That is the shape the job should take. Ask to see it built that way, per property, not per portfolio, whether the vendor names it or not.

How do the leading platforms compare on HOTMA readiness?

Every value below reports what a vendor publishes on its own site, checked August 29, 2026, including ours. Where a page carries its own date, that date is the one shown. "Not stated" means the claim was not found on that vendor's pages during the check. It does not mean the product lacks it.

Platform	Where its HOTMA claim lives	Per-property calculation switch	TRACS or 50059 submission	Most recent compliance date its page cites
	"HOTMA-ready" on the LIHTC and HUD program pages, plus a dated rule summary on the reporting page	Not stated	TRACS workflows and 50059 recertifications named	January 1, 2027
Yardi	Breeze affordable features page, undated, plus a blog post dated August 29, 2023	Not stated	TRACS and MINC named	None cited
MRI Software	Compliance news page, current	Not stated	TRACS submissions named	January 1, 2027
RealPage	Dedicated HOTMA page, updated July 10, 2025	Not stated	TRACS 2.0.3.A named	January 1, 2026
ResMan	A blog post dated November 14, 2023, not the product page	Not stated	Not stated	None cited
AppFolio	Affordable housing articles, updated November 18, 2024	Yes, a property-by-property toggle, named and described	TRACS submission and error surfacing named	July 1, 2025

Read that last column as a fact about a webpage checked on one day. It is not a claim about anyone's software. Two of the six pages we checked, RealPage and AppFolio, cite a compliance date HUD has since replaced. A third, ResMan, cites no compliance date at all. This happens because HOTMA moved its own deadline twice in three years, and marketing pages do not get updated on the same cadence as HUD notices. It says something about documentation discipline. It does not say whether a vendor's product is behind.

These same platforms handle the rest of affordable housing compliance too, not just HOTMA. See which platforms publish LIHTC, HUD, and RD support.

"Ask your spreadsheet" is not a compliance strategy. Seven HOTMA factor values changed on a single date this August, all at once, and every one of them touches a live certification calendar somewhere.

How do you evaluate HOTMA readiness before you buy?

Marketing copy tells you what a vendor wants you to believe. A demo tells you what the system does. Ask to see these on real screens, not slides.

• "Show me a certification with a 2026-12-15 effective date and one with 2027-01-15, on the same property, in the same screen. Which factor table did each pull?"
• "Where do you store the CY2027 values? Is the dependent deduction $525 in your system today?"
• "Add a household member with no income change. Does an interim reexamination fire?"
• "Show me a resident who held the medical deduction on January 1, 2024, and one who did not. What threshold does each get?"
• "What is the date on your public HOTMA status page?" Ask it anyway. Two of the six pages we checked answer it with a date that HUD has since replaced. Ours carries no date at all.
• "Show me a layered Section 8 plus LIHTC plus RD file where two layers are on different rule sets."

Then ask for the boring screens too: document generation, a failed submission, a report export, an audit log. HOTMA readiness that only shows up in a curated demo is not readiness. You can run the tenant rent math yourself to check whatever a vendor shows you against the current numbers. For the fuller checklist beyond HOTMA alone, the full buying process walks through what else to ask.

Sit through enough of these demos and the pattern is obvious. The honest ones look boring. A vendor who shows you an error message, and how it gets fixed, is telling you more than one who only shows the happy path.

When should you not switch compliance software?

A few situations make switching the wrong call, at least right now.

Start with your own records. If your certification history is a mess, migrating it does not fix anything. Dirty data just becomes messy in a nicer font. Clean the records first. Or budget the cleanup as its own project with its own timeline.

Timing matters as much as data. Changing systems and changing rule sets in the same quarter doubles your failure surface. If you are mid-cycle heading into the January 1, 2027 cutover, land the HOTMA transition first. Evaluate a switch after that. And if nothing in your portfolio is income restricted, a general-purpose platform fits better and usually costs less.

The last one is the one software companies skip. Your current vendor may already hit its published dates. It may tell you what it has and has not shipped. That kind of trust is expensive to rebuild. HOTMA by itself is not a reason to walk away from it.

Fortress is built affordable-first. Corporate general ledger, tenant screening, and credit checks run through integration partners here, not native modules. If one set of corporate books is the actual pain point, that matters more than a HOTMA table. See what breaks mid-move before you commit to a timeline either way.

A Rural Development portfolio we work with, 7,600-plus units across multiple states, was building RD budgets across Yardi, Excel, MINC, Word, and Adobe before moving to one system. This is the same underlying problem showing up again: rule-driven calculations living in more places than one team can watch at once. That is exactly what a January 1, 2027 cutover will test on every property you run.

Where is compliance software headed next?

Compliance software is moving from storing one rule to tracking which version of the rule applied to which file, and when. Three things point that way. HOTMA has moved its own deadline three times in three years. HUD republishes the factor tables every year, and the numbers move in both directions. The passbook rate dropped from 0.40% to 0.38% for CY2027 while other figures rose. And the new interim-reexamination trigger fires on an event, a household member added or removed, not on a threshold you check once a year.

Put those together and the job of compliance software is shifting. It used to be enough to store the rule. Now the job is tracking which version of the rule applied to which file, on which date. A 2027 file review will look at 2026 certifications under 2026 rules, sitting next to 2027 certifications under 2027 rules, in the same portfolio. Software that treats a rule change as a one-time update will keep falling behind the next one.