If you're running 33, 80, or 150 units, the property management software built for the largest HFAs wasn't designed for you. Here's what that actually means at month-end — and what an integrated workflow looks like instead.
Let's be honest about something the big vendors don't talk about.
Every enterprise property management platform on the market today was built for the top of the affordable housing pyramid. Yardi targets the largest HFAs. MRI/Bostonpost services the largest Section 8 contract administrators. RealPage has private-equity-scale affordable housing operators.
None of them were built for the small PHA with 33 units of Section 202 senior housing and one part-time bookkeeper.
But that's the PHA we keep hearing from on demo calls. Rural. Under 200 units. Running a mix of Public Housing, project-based Section 8, or maybe a Section 202 property the authorities took over from a dissolving non-profit years ago. And every month, someone at that PHA is downloading reports, reformatting them in Excel, opening TRACS in another window, and manually uploading the 50059s.
That workflow has a cost. Let's look at what it actually is.
The manual TRACS workflow, step by step
Start with what TRACS submission actually involves. Every month, you're generating MAT (Monthly Activity Transmission) records:
- MAT10 records for tenant certifications (HUD form 50059)
- MAT30 records for voucher requests (HUD 52670 and 52670-A)
- MAT40 and MAT70 records for move-outs, terminations, unit transfers, and gross rent changes
Each record has to pass HUD's electronic edits against Handbook 4350.3. Each one has to match the voucher you're submitting. Each one has to reconcile against the HAP payment you're expecting back.
Here's what that looks like in practice at a 33-unit property without integrated software:
- Pull your resident roster from whatever system holds it — often a spreadsheet or a legacy tool.
- Calculate rent portions by hand: tenant portion, subsidy portion, total contract rent.
- Reformat the data into a MAT-compliant structure, usually in Excel or a free interim tool.
- Upload to TRACS.
- Wait for the fatal and non-fatal error report.
- Correct the rejections. Re-upload. Repeat.
- When the HAP voucher hits, reconcile against what you expected.
- Post the subsidy receipt to each resident ledger, one at a time.
At 33 units, if nothing goes wrong, that's roughly a day of work per month. If something goes wrong — a miscalculated household income, a missed interim cert, a MAT10 that fails a HUD edit — it's a week.
It almost always goes wrong somewhere.
Where the hours actually go
The hour count matters less than what those hours displace. At a small PHA, the person doing TRACS is also the person:
- Answering the phone when a resident's garbage disposal breaks
- Processing the wait list for the three vacant units
- Reconciling petty cash and cutting vendor checks
- Signing the annual HUD audit package
Every hour spent reformatting a MAT file is an hour not spent on anything else. And when the executive director is the one doing it — which happens more often than the big vendors think — it's an hour not spent running the authority.
The error tax
Here's what the enterprise vendors genuinely don't price for: the cascade effect of a rejected submission at a small PHA. A large operator with dedicated compliance staff catches errors in pre-submission validation. Three people on TRACS. A rejection is an inconvenience.
A small PHA has one person doing it between other tasks. A rejected MAT10 can mean:
- The 50059 gets resubmitted late
- The HAP voucher for the following month is short
- The operating account runs thin
- Tenant rent portions don't post on schedule
- An uncomfortable board meeting follows
None of this is hypothetical. We hear versions of it every week.
The HOTMA squeeze
Now add the current regulatory timeline.
HOTMA's full compliance deadline was pushed to January 1, 2027, under HUD Notice H 2025-03. TRACS 203A — the version that actually supports HOTMA-updated income, asset, and rent calculations — has not been released as of early 2026. HUD's guidance has been explicit: owners and agents should not implement Sections 102 and 104 yet, because TRACS 202D can't accept the data correctly.
Where does your portfolio actually stand on HOTMA? Find out in 5 minutes. Get your free personalized compliance scorecard across the 8 domains that matter most.
Which means, between now and whenever 203A ships, every small PHA still has to:
- Keep running pre-HOTMA calculations in TRACS 202D
- Update Tenant Selection Plans and EIV policies to reflect HOTMA language — this requirement is separate from full-rule compliance and should already be done
- Track which tenant rent calculations will change under HOTMA, so you're ready to re-certify
- Prepare to recert a large share of your population after 203A drops, within whatever grace window HUD ultimately provides
If you're doing this manually at 33 units, the cutover is going to hurt. Every cert you have to correct post-203A is another MAT10 edit cycle. Every household where your pre-HOTMA rent calculation diverges from the post-HOTMA calculation is a rent override today and a re-cert tomorrow.
Big vendors have compliance teams preparing for this right now. Most small PHAs don't. That gap will show up on the first MOR after the transition.
What integrated actually looks like
"Integrated TRACS" gets thrown around a lot. Here's what it actually means at a small-portfolio scale:
- Resident data lives in one place. No re-entry, no exports, no reformatting.
- MAT10/MAT30/MAT40/MAT70 records are generated from your actual certification data, not from an Excel reshape of it.
- Pre-submission validation runs automatically. You catch HUD edit errors before HUD does.
- HAP vouchers come back in and post to resident ledgers without line-item data entry.
- When 203A drops, the software updates. You don't rebuild the spreadsheet.
That's it. The principle is simple. The execution is where small PHAs have been stuck.
Why nobody's built for this market
Enterprise PMS vendors don't build for 33-unit PHAs because the economics don't work for them. A 33-unit deal priced at enterprise seat rates doesn't cover the implementation project. So the big vendors price out of the market, and small PHAs get quoted five-figure implementation fees for a platform that's overkill for their portfolio.
That gap is the whole reason ExactEstate exists.
A flat $3 per unit per month, with a $300 monthly minimum for portfolios under 100 units. All features included. TRACS submission via our bundled ShofCorp integration — not a separate vendor you have to source. 50059 generation with state-specific TIC templates. HAP voucher import with auto-posting to resident ledgers. A recertification schedule that sends automatic notices at 120, 90, 60, and 30 days before the due date. Live in days. U.S.-based support that answers the phone. Implementation scoped to the actual portfolio — not to an enterprise deal template.
We can't promise full HOTMA compliance. No vendor can honestly say until TRACS 203A is out. What we can promise is that you won't have to rebuild your TRACS workflow from scratch when it drops.
What to do now
If you're a small PHA still running TRACS manually, four moves for the next 90 days:
- Document your current workflow. Actually, take time for each step. You'll be surprised.
- Pull your last six months of TRACS submissions. Count the rejections. That's your real error rate.
- Confirm your TSP and EIV policies have been updated to reflect HOTMA language. This requirement applies whether or not you've implemented the new income and rent rules.
- Start evaluating integrated platforms now. Don't wait for 203A. You want the migration done before the regulatory cutover, not during it.
The authorities that migrate before the 203A drops will spend their transition period running recertifications. The ones that don't will spend theirs rebuilding spreadsheets. Your call.
See what integrated TRACS looks like at 33 units
Book a 20-minute walkthrough with Fernando. We'll show you the actual MAT10/MAT30 generation, the HAP voucher posting flow, and what ShofCorp integration looks like inside the platform. No pitch deck.
Frequently Asked Questions
1. What is TRACS, and why does it matter for small PHAs?
TRACS (Tenant Rental Assistance Certification System) is HUD's system for processing tenant certifications, voucher requests, and other monthly activity records. For small PHAs, it's a required part of receiving HAP payments — and submitting it incorrectly or late can directly impact operating cash flow.
2. How much time does manual TRACS submission actually take?
At a 33-unit property with no integrated software, a clean month with no errors takes roughly a full day of staff time. When errors occur — a miscalculated income, a missed interim cert, a failed HUD edit — that can stretch to a week. At small PHAs, that's often the executive director's time.
3. What is HOTMA, and does it affect how I submit to TRACS today?
HOTMA updates HUD's rules around income calculations, assets, and rent. Full compliance has been pushed to January 1, 2027, and TRACS 203A — the version that will support HOTMA data — hasn't been released yet. For now, PHAs should continue submitting under TRACS 202D, but should already have updated their Tenant Selection Plans and EIV policies to reflect HOTMA language.
4. What does "integrated TRACS submission" actually mean?
It means your resident data, certifications, MAT file generation, and HAP voucher posting all happen inside one system — no exporting, reformatting in Excel, or manual re-entry. Pre-submission validation catches HUD edit errors before you upload, and when 203A drops, the software updates rather than requiring you to rebuild your workflow.
5. Why don't enterprise property management platforms work for small PHAs?
Enterprise platforms like Yardi and RealPage were built for large HFAs and private-equity-scale operators. Their pricing and implementation costs — often five figures — don't make sense for a 33- or 80-unit portfolio, leaving small PHAs either priced out or paying for far more than they need.
6. When should a small PHA start evaluating integrated software?
Now, before TRACS 203A is released. PHAs that complete their migration beforehand will spend the HOTMA transition period running recertifications. Those that wait will be simultaneously managing a platform migration and a major regulatory cutover — a much harder combination to absorb with limited staff.
As VP of GTM Strategy, Anja McKinley leverages over a decade of experience in demand generation and revenue operations to drive measurable growth. She excels at aligning marketing, sales, and product teams, using data-driven insights to accelerate pipeline velocity and deliver genuine business impact.
