How does HUD vouchering work in Fortress Compliance?

HUD vouchering can happen in a different system from the tenant data. HUD Vouchering & TRACS Integration, part of Fortress Compliance, puts the voucher in the same system as the certifications behind it. Fortress Compliance is our affordable housing compliance software, and this feature is in beta.

The voucher goes to TRACS, which HUD describes as a computer system developed to improve program management and financial control (HUD's TRACS page).

Where does Fortress build the HUD voucher?

Fortress sets up each voucher in the property system.

Each voucher is managed by property, subsidy type, contract number, and voucher month. Fortress fills Regular Assistance and Adjustments from eligible certifications, unit data, and resident data.

How does a certification change reach the HUD voucher?

A change in a certification updates the voucher in the same system. Fortress captures new tenant events from the HUD certification lifecycle, and tenant events are certifications. Each one is applied to a voucher by its Anticipated Voucher Date.

If a supported change is made to a Submitted voucher, Fortress returns that voucher to Draft. Every submission carries a timestamp.

How does Fortress check a HUD voucher before it goes to TRACS?

Fortress blocks empty vouchers and out-of-order submissions before anything goes to TRACS, and says what is missing. Eligible tenant events must be submitted to TRACS before the voucher can be submitted.

Fortress also applies TRACS-specific export and validation rules when it builds the MAT30 output. MAT stands for Monthly Activity Transmission, and MAT30 is the HAP voucher record.

How do regular assistance and adjustments stay separate on a HUD voucher?

Regular assistance and adjustments stay separate on a HUD voucher when each has its own section. Part III, line 8, of form HUD-52670 lists regular tenant assistance payments, adjustments, Section 8 special claims, miscellaneous accounting requests, and repayment agreements as separate lines.

HUD's form instructions, 05/2014 edition, call for a separate form for each subsidy contract. See form HUD-52670. Section 8 is defined in our glossary.

The Fortress voucher has six sections: New Tenant Events, Regular Assistance, Adjustments, Repayment Agreements, Miscellaneous Accounting, and Special Claims.

New Tenant Events is a Fortress working section with no line 8 match.

Repayment agreements can be created, modified, validated, and deleted. They carry over between vouchers until the balance is zero. Special claims and miscellaneous accounting entries can be added and removed.

How do you see the state of a HUD voucher in Fortress?

A Fortress HUD voucher carries a status and a timestamp. The four states are Draft, Submitted, Approved, and Paid. Approved and Paid vouchers are locked against changes.

Six permissions control vouchering: viewing, read-only, setup, submitting, approving payment, and posting payments.

How does HUD vouchering work in Fortress, step by step?

HUD vouchering in Fortress works in four steps, in this order.

1. Set up by property, subsidy type, and contract. Subsidy types, contract numbers, the Eligibility Universe Code, and unit coverage are configured during normal onboarding. Fortress then manages each voucher the same way.
2. Let the Drafts generate in order. Fortress creates rolling Draft vouchers in chronological order for each subsidy type and contract combination. It keeps two sequential Drafts for each.
3. Review tenant events and sections. Check New Tenant Events and the five other sections. Eligible tenant events go to TRACS first.
4. Move the voucher through Submitted, Approved, and Paid. Each voucher carries one of those states, with a submission timestamp.

Past voucher months can be created up to four months back, before the first voucher is submitted.

Which TRACS version does Fortress HUD vouchering support?

Fortress HUD vouchering is built to the TRACS 202D spec and does not support TRACS 203A. HUD issued a stakeholder notice dated September 2, 2026 about a draft TRACS Release 203A MAT Guide. Comments were due October 2, 2026. The notice says the draft incorporates changes needed to implement HOTMA within TRACS (HUD stakeholder notice).

HUD has published no 203A release date. For the full comparison, read TRACS 203A: what changes from 202D.

Where does HUD vouchering in Fortress stand today?

HUD vouchering in Fortress is in beta. The beta started September 28, 2026, and no general availability date is set. If you want to see how a beta fits your portfolio, talk to our team about Fortress Compliance.

When would you skip HUD vouchering in Fortress?

You may skip it if someone else already handles your vouchering and that arrangement works for you. AllTRACS is a partner that can manage vouchering for a client. AllTRACS is a Fortress OS integration partner, and the AllTRACS and Fortress OS page covers how the two fit together.

If you are comparing tools, what to look for in HUD voucher software lists the questions to ask. For the wider category, see affordable housing property management software.