The HOTMA compliance date is 1 January 2027. TRACS 202D is still HUD's current production version. TRACS 203A is the version designed to carry the HOTMA changes. And on 2 September 2026, HUD posted draft 203A MAT Guide materials for stakeholder review.

So 1 January 2027 is a compliance deadline, not a promise that the production system will be ready on the same date. The gap between the two is where the operational work lands.

This post is about what that gap actually requires on Form HUD-50059, how the rent override works while 202D remains in production, and what operators can reconcile now rather than during the transition.

The Version That Kept Moving

Worth laying out the sequence, because it explains why guidance on this subject contradicts itself depending on when it was written.

HUD's TRACS materials include 203A final industry specification documents dated 20 December 2019, followed years later by the September 2026 draft MAT Guide materials now under review.

In between, the expected timing moved. Earlier HUD guidance had anticipated 203A operationalisation by early 2025, when the compliance timeline was different. Later guidance and industry materials reflected further movement as the compliance date moved to 1 January 2026 and then to 1 January 2027.

So 203A is no longer an unknown document. It is a moving implementation target.

Which means any guidance you find on this is dated, and the date matters more than the content. HUD itself warns that documents showing prior compliance dates have been superseded. Check when something was written before acting on it.

What The Rent Override Actually Involves

HUD permits owners who implement HOTMA before 203A to calculate incomes and rents manually and enter the results into 202D using the rent override function. That sounds like a workaround. It is more specific than that.

Under HUD's guidance on the override, an owner using it must:

Submit accurate information in Sections B and C of the 50059. Section B is the summary and Section C is household information. Section C in particular must accurately reflect the circumstances of the household, so that HUD can continue income data-matching with other agencies.

Enter the data in Sections D, E and F from the family's most recent reexamination, whether annual or interim. Income information, asset information, and allowances and rent calculations.

Submit applicable non-interim transactions as interim reexaminations.

Read the first two together and the consequence is unusual. The rent on the form is your HOTMA figure. The income, asset and allowance detail behind it is not. The 202D form and transmission path cannot fully represent the HOTMA calculation that produced the overridden rent.

And it may generate discrepancy codes you are told to disregard. HUD's guidance notes that use of the override may produce specific, limited discrepancy codes which owners may disregard, and that contract administrators have been instructed to process vouchers despite those codes once other information is confirmed correct.

That is a deliberate, HUD-authorised workaround for a system limitation: the record can generate specific discrepancy codes even though the underlying HOTMA calculation has been performed correctly.

HUD also strongly encourages owners to give their contract administrator notice that they intend to use the override. Worth doing before the first one rather than after a query.

Which Makes File Annotation The Control

The 50059 does not show the full HOTMA calculation when the rent override is used. The tenant file therefore has to carry the explanation.

HUD's guidance requires owners implementing HOTMA before 203A to annotate tenant files with three things.

Which provisions were implemented, regardless of whether they produced a different tenant rent than the pre-HOTMA rules would have. HUD cautions that many aspects of HOTMA are interrelated, and that implementing some without others may be infeasible or may itself affect tenant rents.

How the family's income, assets and mandatory deductions were determined under the implemented provisions.

And where applicable, both numbers: what the tenant rent would have been under pre-HOTMA rules, and the HOTMA tenant rent actually entered using the override.

That third item is particularly important because it preserves both rent calculations side by side when the override is used. The form itself shows one of them.

The Figures That Do Not Move Yet

Here is where the gap has a directly practical consequence, and it catches people who have read about HOTMA and want to apply it.

HOTMA's inflation-adjusted values are published annually. But whether you use them depends on your implementation status and the system you are transmitting through.

Contract administrator guidance has also addressed the transition. Published guidance has reported that 202D certifications should continue using specified pre-HOTMA deduction amounts until 203A, rather than applying newer inflation-adjusted figures prematurely, with similar guidance on the passbook savings rate. That is operational guidance tied to the transition, not a general rule that every HOTMA calculation must use the old figures.

So a certification can be wrong in two opposite directions. Using newer adjusted figures in a 202D certification may create a submission that does not align with the applicable 202D processing requirements. Using pre-HOTMA figures after implementing a HOTMA provision that changes the applicable amount may produce a rent that does not match your HOTMA calculation.

The resolution is not a rule you can read off a page. It depends on your implementation status, your transmitting system version, and what your contract administrator will accept. Establish all three before changing what you submit.

What Actually Moves Through TRACS

Worth being concrete about the plumbing, because the discussion above is meaningless without it.

Owners and agents transmit MAT records monthly through third-party software. The records map to the forms:

MAT10 corresponds to Form HUD-50059, the tenant certification.

MAT30 is used for voucher-related data associated with Forms HUD-52670 and HUD-52670-A.

Other MAT records cover specific tenant and voucher-related transactions, including move-outs, terminations, unit transfers and gross rent changes.

TRACS applies electronic edits to transmitted records before acceptance. Which means the constraint is not what you believe the rent should be. It is what the record format permits you to say and what the edits will pass.

And your software vendor sits in the middle of it. Vendors have to calculate rent and subsidy correctly, print current versions of the forms, and submit MAT records meeting the TRACS specifications. A vendor that cannot support the applicable 203A data and transmission requirements cannot provide a 203A submission path, regardless of what your compliance team has calculated. That is separate from the 202D override route, which remains available in the meantime.

The Reconciliation Worth Doing Now

Here is the part worth acting on independent of when 203A lands.

A version transition is also a good point to surface existing data errors. Differences between TRACS and your property management system that have remained unresolved can become more difficult to reconcile during a system transition.

Three things worth doing before it rather than during it.

Run a TRACS certification query and compare it against your property management system. The two should agree. Where they do not, the difference is a correction you would rather make now.

Check your current compliance percentage, so you know your starting position rather than discovering it mid-transition.

Reconcile the voucher to the certifications behind it. A voucher that reconciles in total can still be wrong at the line level, and how the underlying subsidy and tenant portions are recorded determines whether that reconciliation is possible at all.

None of that requires knowing the 203A production date. All of it is easier to reconcile before the transition than during it.

What To Do Between Now And January

• Establish your actual implementation status. Have you implemented HOTMA, in part, in full, or not at all. This determines which figures apply and which route you are on.

• Confirm your software vendor's 203A position and timing. This is one of the practical constraints on what you can submit, and it is outside your control.

• Ask your contract administrator what they will accept, and tell them if you intend to use the rent override. HUD strongly encourages that notice.

• If you are using the override, check the annotation against HUD's three requirements. Provisions implemented, how income and assets and deductions were determined, and both rent figures where applicable.

• And keep the dated guidance. In an area where HUD, contract administrators and vendors have all issued positions that later moved, the record of what you were told and when gives you a dated record of the basis for your implementation decision. Holding that against the property rather than in an inbox is what makes it retrievable later.

Why This Matters More Than It Reads

Three consequences, and none of them is theoretical.

Subsidy depends on the voucher, and the voucher depends on the certification. A certification that cannot be transmitted can delay voucher processing and subsidy payment. That is a cash-flow consequence, not just a compliance one.

Corrections can be retroactive, and they compound. A calculation applied on the wrong basis for six months can mean six months of certifications and related voucher records to review and potentially correct.

And the calculation and the system are now separate problems. Getting the income determination right is necessary and it is not sufficient. The figure still has to move through a form and a record format, and while 202D is in production, that path has a specific shape with specific documentation attached to it.

FAQ

1. What is Form HUD-50059?
The tenant certification form used in HUD Multifamily programs. It corresponds to the MAT10 record transmitted through TRACS.

2. What is TRACS 203A?
The updated version of HUD's Tenant Rental Assistance Certification System, designed to carry the HOTMA changes. Version 202D remains the current production version.

3. When will TRACS 203A be released?
The current HUD materials do not provide a final production date. On 2 September 2026, HUD posted draft 203A MAT Guide materials for stakeholder review. Confirm the production timeline with HUD, your contract administrator and your software vendor rather than relying on an earlier estimate.

4. What is the rent override function?
A method permitting owners implementing HOTMA before 203A to enter manually calculated incomes and rents into 202D. It requires accurate information in Sections B and C of the 50059, entry of Sections D, E and F from the family's most recent reexamination, submission of applicable non-interim transactions as interim reexaminations, and annotation of the tenant file.

5. What has to go in the tenant file annotation?
Which provisions were implemented, how income, assets and mandatory deductions were determined, and where applicable both the pre-HOTMA tenant rent and the HOTMA rent entered using the override.

Statements about historical 203A timing, contract administrator processing positions and transition treatment of current-year figures reflect published HUD, industry and contract administrator guidance at the dates indicated and may have changed. Current as at September 2026. Confirm the position with HUD, your contract administrator and your software vendor before changing any certification or transmission practice. This article describes general concepts and is not accounting, tax or legal advice.