How to Submit HUD-50059s via TRACS Without Triggering Errors(And what to do when they happen anyway)
Voucher week. You hit transmit. Then you wait. The discrepancy report comes back with a string of fatal errors, your HAP voucher is stuck in manual review, and your accounting team is asking when the deposit is going to land.
If you've worked on a HUD-assisted property for more than a few months, you know this rhythm. And you know the published guidance from HUD on how to actually fix the errors is sparse, technical, and assumes you already know what you're looking at.
This is the practical version. Written by people who've sat through the manual-review phone calls, watched a single bad effective date cascade into six months of cleanup, and figured out which errors are landmines versus which ones you can ignore.
First: Make sure you're filing the right form to the right system
Half the operators we talk to who say they have a "TRACS problem" actually have a PIC problem, or vice versa. The two systems are not interchangeable, and HUD itself warns RAD-converting properties not to assume their PIH-experienced vendor knows TRACS.
- HUD-50058 (Family Report) goes to IMS/PIC. Used by PHAs for Public Housing, Housing Choice Vouchers, and Section 8 Mod Rehab.
- HUD-50059 (Owner's Certification of Compliance) goes to TRACS. Used by owners and management agents for project-based Section 8, Section 202, Section 811, RAD-converted properties, and a handful of related multifamily contracts.
If you converted from public housing to PBRA via RAD, you're filing 50059 to TRACS now. The 50058 workflow that your team spent 10 years mastering no longer applies. That sentence alone explains a lot of the "why is everything broken" feeling people get six months post-conversion.
This guide covers TRACS and 50059. The PIC/50058 piece is its own animal — we'll cover that separately.
The pre-submission audit: catch errors before you transmit
TRACS errors fall into two buckets: fatal (the submission stops processing for that household) and warning (it processes but flags). Fatal errors are what cause your voucher to get stuck. Most fatals can be caught in your own data before TRACS ever sees them.
Run through this list before you build your monthly transmission file.
1. Effective date sequencing
This is the single most common fatal error category, and the easiest to prevent.
- Annual Recertifications must have an effective date no more than 12 months after the most recent AR, IC, or MI for that household.
- Effective dates of ARs are always the first of the month.
- If a later record already exists in TRACS for that household, you cannot submit an earlier-dated record without correcting the sequence first.
- For interim recerts and unit transfers, effective dates must logically follow the move-in or last AR.
Practical fix: pull a TRACS Certification Query before you build your transmission file. If your local data shows a December 1 AR for a household but TRACS already has a January 1 AR posted, you have a sequencing problem to resolve before you transmit anything else.
2. Relationship codes (Item 37)
HUD's edits will reject the submission if the relationship codes don't add up.
- Exactly one household member must be coded H (Head of Household).
- Only the HOH gets member number 01.
- Spouse (S), Co-Head (K), Adult Co-Tenant (A), Dependent (D), Child (C), Foster (F), Live-in Caretaker (L), and Unborn (U) all have specific income and household-size implications.
- F, L, and U don't count toward income-qualifying household size. Get this wrong, and your rent calculation will be off, which cascades into voucher mismatches.
3. SSN and Alien Registration validation
TRACS rejects submissions with malformed identifiers, and the error messages aren't always self-explanatory.
- SSNs must be nine digits with no dashes in the transmission file.
- Repeating-digit SSNs (e.g., 999-99-9999) trigger problem-SSN edits.
- If the household includes a non-citizen with a T-Alien Registration Number, the field has its own format requirements.
- Tenant ID Management corrections must be made through the Tenant ID Management process, not by editing and resubmitting the 50059.
4. Rent calculation and subsidy math
This is where errors stop being clerical and start costing real money.
- Tenant rent (TR) = Total Tenant Payment (TTP) minus utility allowance (UA). If utilities are included in rent, UA is zero.
- Gross rent = Contract Rent + Utility Allowance. If you're doing a unit transfer in this certification, both contract rent and UA need to reflect the new unit.
- HAP request on the voucher must reconcile to the sum of (Contract Rent − Tenant Rent) for every assisted household, plus or minus your adjustments.
If your 50059 shows the household pays $312 in tenant rent, but your voucher line item asks for HAP, which implies $298 in tenant rent, expect a discrepancy report.
5. Action codes
Section 2 of the 50059 captures the action type. The most-confused pairings:
- MI (Move-In) versus IC (Initial Certification). MI is for tenants moving into an assisted unit at the start of the lease. IC is for tenants who become assisted while already in place — the most common cause is a Section 236 or 221(d)(3) BMIR tenant who later begins receiving Section 8 assistance.
- AR (Annual Recert) versus IR (Interim Recert). AR effective dates are always the first of the month and constrained by the 12-month rule. IR is for in-between changes and has its own triggers.
- UT (Unit Transfer) requires that both the old unit data from the prior cert and the new unit data in this one line up.
- GR (Gross Rent Change) is a separate action with its own MAT record. Don't combine it with an AR unless the timing genuinely overlaps.
Run a TRACS Certification Query before every transmission
This is the single most underused defense against discrepancy reports. It takes about ten minutes and catches problems before they cost you days.
- Log in to HUD Secure Systems with your WASS ID.
- Open TRACS and pull a Certification Query for the active HAP contract.
- Compare the query results against your property management system: tenant names, unit numbers, effective dates, contract rent, tenant rent, utility allowance, HAP amount.
- Compare the same data points against the voucher you're about to transmit.
- Flag every mismatch. Resolve at the source data — don't paper over it in the file.
If the query, your PM software, and your voucher don't all tell the same story, transmitting will not fix it. Transmitting will create a discrepancy report and move the cleanup work to your inbox three days later.
Common error categories and how to fix them
"A record with a later Effective Date exists in the database."
Translation: someone — you, a prior agent, or a previous version of your own file — already submitted a cert dated after the one you're trying to send. You have two options: change this cert's effective date to be later than what's in TRACS, or void the later record and resubmit your sequence cleanly. Voiding existing records should be a last resort and documented in the tenant file.
"This tenant already exists at this PHA / property."
Usually, a duplicate move-in submission, often because the household was previously in another assisted unit on the same contract. The fix is action code 7 (Unit Transfer) instead of MI, or correction (Section 2c = Y) if the prior record was wrong.
"This SSN/AID appears in other households."
Someone is on two cert records simultaneously. Could be a legitimate dependent who moved between households, or a clerical duplicate. Pull the Possible Duplicate report, identify the current record, and clean up the other record through Tenant ID Management.
HAP request doesn't match the certified subsidy
Your voucher is requesting a different amount than your certs indicate. Causes, in order of likelihood:
- The voucher includes adjustments (OARQ, miscellaneous accounting requests) that you forgot to itemize.
- A move-out or termination wasn't reflected in the voucher line items.
- A utility allowance change was posted to the cert but not to the voucher.
- Gross rent change effective date doesn't align with the voucher month.
Discrepancy report after RAD conversion: zero out OARQ adjustments
This catches almost every operator in the first year post-conversion. For RAD-converted vouchers, you must zero out any adjustments in the adjustment section from the prior year with an OARQ. If you carry prior-period adjustments into the new contract's voucher without zeroing them, your voucher will trip a manual-review flag and sit for the full 21 business days while a Voucher Processing reviewer untangles it.
When you do trigger errors, the manual review reality
Voucher Processing runs a 21-business-day manual review process for RAD-converted properties during the first several months post-conversion, and for any voucher that fails automated edits. That's a month of cash flow you don't have access to. A few things to know:
- Email the voucher to your HUD Account Executive before you transmit during the manual review period. If you don't, your voucher waits in line. If you do, your AE can usually advance it.
- Don't keep retransmitting the same broken file, hoping for a different outcome. TRACS will keep rejecting it, and each rejection adds to your AE's review backlog.
- Fix the source data. Generate a fresh transmission file from corrected data. Re-run your pre-submission audit. Then transmit.
- Document what you changed in the tenant file. If your file shows a March correction with a clear note explaining the original December error, the next MOR reviewer has nothing to flag. If it's silent, you'll be answering questions.
HOTMA, TRACS 203A, and the 2027 deadline
As of late 2025, HUD extended the HOTMA compliance deadline for Multifamily Housing programs to January 1, 2027 (Notice H 2025-07). TRACS 203A — the version that will fully accommodate HOTMA's changes to income, asset, and rent calculations — is not yet operationally deployed. Until it is, here's the operating reality:
- TRACS 202D is still the current production version. Build for it.
- Owners who want to implement HOTMA early can do so by manually calculating HOTMA-compliant income and rent and using the rent override function in 202D. HUD wants an annotation in the tenant file explaining each override.
- HUD has explicitly told operators not to implement Sections 102 and 104 of HOTMA prematurely — the system can't process them yet, and you'll create error cleanup later.
- The updated 50059, 9887, 9887-A model leases and AR notice templates are still in the HUD release pipeline. Don't draft your own.
If your software vendor is telling you they're "HOTMA compliant" today, ask them which final HUD-published forms they're using and which version of the 203A spec they've built against. The honest answer right now is some version of HOTMA-ready, built for HOTMA, and ready for 203A — because no one can be fully HOTMA-compliant on a system HUD hasn't released specs for yet.
How to make this routine instead of monthly fire drills
Most properties that consistently transmit clean files have built three habits:
- Run the TRACS Certification Query against your PM software's rent roll on the same day every month, before any voucher work begins. Reconcile every line.
- Track voucher_date, run_date, and transmission_date for each property each month. If any of those three slip, you know which property to investigate.
- Centralize discrepancy detection. When you do find a mismatch — between TRACS, your PM software, and your voucher — fix it once, in the source data, and propagate the fix outward. Don't let three systems drift independently.
If you're doing this in spreadsheets, you'll catch most of it. Most of it isn't all of it, and the things you miss tend to be the expensive ones.
Where ExactEstate fits
Our compliance module was built around the workflows above because every person who designed it has filed 50059s. The TRACS workflow connects directly to ShofCorp through an embedded interface — your team doesn't bounce between systems. Specifically:
- 50059 data string generation pulls directly from your certification records, so what's on the cert is what gets transmitted.
- HAP voucher payment preview shows you the voucher math before you transmit, with a built-in discrepancy check against your rent roll.
- Rent roll CSV sync pulls from ShofCorp, matches against ExactEstate units and residents using fuzzy name matching, and automatically flags HAP and contract rent mismatches.
- Voucher status tracking captures voucher_date, run_date, and transmission_date per property per month — the three dates above — automatically.
- One-click ShofCorp portal login when you do need to drop into the HDS interface directly.
On the HOTMA side: NSPIRE-ready, built for HOTMA. When TRACS 203A is released and HUD publishes the final form set, our compliance module updates accordingly. You don't pay for the upgrade. You don't switch tiers. That's how everything in the platform works.
If your voucher week is consistently a fire drill
It usually isn't your team. It's the seams between three systems that don't talk to each other — your PM software, ShofCorp/TRACS, and your accounting ledger. ExactEstate closes those seams.
Walk through a 50059 transmission with us in a 30-minute demo: exactestate.com/demo.
FAQs
What's the difference between a HUD-50058 and a HUD-50059, and which system does each go to?
The HUD-50058 (Family Report) goes to IMS/PIC and is used by PHAs for Public Housing, Housing Choice Vouchers, and Section 8 Mod Rehab. The HUD-50059 (Owner's Certification of Compliance) goes to TRACS and is used by owners and management agents for project-based Section 8, Section 202, Section 811, and RAD-converted properties. Properties that converted from public housing to PBRA via RAD are now filing 50059s to TRACS — the 50058 workflow no longer applies.
What's the single most effective thing you can do to prevent TRACS errors before you transmit?
Run a TRACS Certification Query against your property management system's rent roll before you build your transmission file. Compare tenant names, unit numbers, effective dates, contract rent, tenant rent, utility allowance, and HAP amounts across your PM software, the query, and the voucher you're about to send. If all three don't tell the same story, transmitting won't fix it — it will just create a discrepancy report a few days later.
What are the most common causes of fatal TRACS errors?
Effective date sequencing is the most frequent culprit — specifically, trying to submit a record dated earlier than one already in TRACS for that household. Other common causes include incorrect relationship codes (missing or duplicate Head of Household designations), malformed SSNs, rent calculation mismatches between the 50059 and the voucher, and using the wrong action code — for example, submitting a Move-In when a Unit Transfer is actually required.
What happens when a voucher gets flagged for manual review, and how do you speed it up?
Manual review runs a 21-business-day process, which can mean a month of delayed cash flow. The most important step is emailing the voucher to your HUD Account Executive before transmitting during the manual review period — without that heads-up, your voucher waits in line. Avoid retransmitting the same broken file repeatedly, as each rejection adds to the review backlog. Fix the source data first, generate a fresh file, run the pre-submission audit again, then transmit.
What's the RAD-specific error that catches almost every operator in the first year post-conversion?
Failing to zero out prior-period adjustments in the voucher using an OARQ. RAD-converted vouchers require that any adjustments carried over from the prior year be zeroed out. Operators who carry those adjustments forward without clearing them will trigger a manual-review flag and wait the full 21 business days for a Voucher Processing reviewer to sort it out.
Can properties implement HOTMA changes in TRACS right now?
Not fully. As of late 2025, HUD extended the HOTMA compliance deadline to January 1, 2027, and TRACS 203A — the version that supports HOTMA's updated income, asset, and rent calculations — hadn't been deployed yet. Properties can manually calculate HOTMA-compliant figures and use the rent override function in TRACS 202D, with a file annotation explaining each override, but HUD has explicitly told operators not to implement Sections 102 and 104 prematurely. Any vendor claiming full HOTMA compliance before 203A is released is overselling.
ExactEstate — Property management software built by property managers, for property managers. One platform, any situation.