Sign in to Fortress OSPart of Affordable Housing Compliance Guide: LIHTC, HUD, USDA and HOTMA
HUD Voucher Software: What to Look For Before You Buy
HUD voucher software should build a separate voucher for each contract and subsidy type and show which tenant events must reach TRACS first, produce the HUD-52670 and MAT30, and validate the voucher before submission. Ask which TRACS version it supports and what the vendor will put in writing about 203A.
Key takeaways
HUD voucher software should build one voucher per subsidy contract, because HUD's form instructions call for a separate HUD-52670 for each subsidy contract.
Ask whether the tool shows which tenant events must reach TRACS first, and whether it blocks a voucher that is empty or out of order.
Approved and Paid vouchers should be locked, and each submission should carry a status and a timestamp, so you can see what was submitted and when.
HUD has published no TRACS 203A release date, so ask any vendor which TRACS version it supports today and get its 203A answer in writing.
A service bureau such as AllTRACS can still be the right call when you want an outside group to manage the vouchering.
HUD voucher software should build a separate voucher for each contract and subsidy type, show which tenant events must reach TRACS first. It should produce the HUD-52670 and MAT30 content and check the voucher before anyone submits it. Vouchering is the monthly job of asking HUD to pay the subsidy you earned.
HUD Vouchering & TRACS Integration is part of Fortress Compliance, our affordable housing compliance software. You can hand this checklist to any vendor, including us.
What should HUD voucher software do?
HUD voucher software should take the certifications and unit data you already keep and turn them into a voucher ready for TRACS. It should do that for each subsidy type and contract you run, every month. If your team still copies numbers into a form or a spreadsheet, the software has not taken the job.
HUD's own form shows the shape of the work. The HUD-52670 has five parts: contract information, occupancy and income eligibility, the breakdown of assistance requested, distribution of subsidy earned, and the owner's certification. Line 8 of Part III lists regular tenant assistance payments, adjustments, Section 8 special claims, miscellaneous accounting requests, and repayment agreements. Good software has a place for each one.
The 52670 instructions call for a separate form for each subsidy contract. They also say Section 8, PAC, and PRAC billing is due by the 10th of the month before the month requested (per HUD's form instructions, 05/2014 edition).
What should you ask a HUD voucher software vendor?
Ask seven questions every time, and six more if you run many contracts or have several people touching vouchers. Ask each one out loud in the demo, then ask the vendor to show it on screen.
| What to check | Question to ask the vendor |
|---|---|
| Every HUD operator needs | |
| One voucher per subsidy contract | Does it build a separate voucher for each subsidy contract, month by month? |
| Tenant event order | Does it show which tenant events must reach TRACS before the voucher is submitted? |
| HUD-52670 and MAT30 output | Does it generate the HUD-52670 content and the MAT30, or do we rebuild either one by hand? |
| Validation before submission | What does it block, and does it say what is missing when it blocks? |
| Voucher states and locks | Does it track Draft, Submitted, Approved, and Paid, and are Approved and Paid vouchers locked? |
| The line 8 categories | Can we handle repayment agreements, special claims, and miscellaneous accounting requests in the voucher itself? |
| TRACS version | Which TRACS version do you support today, and what will you put in writing about 203A? |
| Multi-contract operators also need | |
| Many properties and contracts | Can we set up and manage vouchers by property, subsidy type, and contract number in one place? |
| Permission separation | Can viewing, setup, submitting, approving payment, and posting payments sit with different people? |
| Status and timestamp | Can we see each voucher's status and when it was submitted? |
| Repayment carry-over | Does a repayment agreement carry from one voucher to the next until the balance is zero? |
| Changes after submission | What happens when a certification changes after the voucher is already Submitted? |
| Switching mid-stream | How many past voucher months can we create when we move over? |
Why does voucher order matter in TRACS?
Voucher order matters because eligible tenant events must be submitted to TRACS before the voucher can be submitted. In Fortress HUD vouchering, tenant events are captured from the HUD certification lifecycle and applied to vouchers by Anticipated Voucher Date.
Fortress keeps two sequential Draft vouchers for each subsidy type and contract combination, created in chronological order. Validation blocks out-of-order submissions and says what is missing. For the full walkthrough of drafts, tenant events, and submission, read how HUD vouchering works in Fortress Compliance.
Which TRACS version does your software support?
Ask the vendor to name the TRACS version, then ask what it will say about 203A in writing. TRACS 202D is still in production.
HUD issued a stakeholder notice dated September 2, 2026 about a draft TRACS Release 203A MAT Guide. Comments were due October 2, 2026. HUD says the draft incorporates changes needed to implement HOTMA within TRACS.
HUD has published no 203A release date, so any date a vendor gives you for 203A is the vendor's own plan. Ask for it in writing, and who set it. HUD's stakeholder notice also says the HOTMA provisions tied to 203A cannot be implemented until HUD publishes the release and its related documents.
Until then, HUD's rent override guidance covers owners who adopt HOTMA early. They enter results through the rent override function in 202D and annotate the tenant file. Ask how the vendor's tool supports that annotation. For what the draft changes, see TRACS 203A: what changes from 202D.
Fortress HUD vouchering is built to the TRACS 202D spec and does not support TRACS 203A.
When does a service bureau like AllTRACS still make sense?
A service bureau still makes sense when you want an outside group to own the monthly vouchering. AllTRACS, for example, can manage vouchering for a client.
A bureau fits if your team is small and vouchering is a small share of the work. It also fits if no one on staff wants to learn the TRACS rules, or if you want an outside group to carry the submission step. AllTRACS is a Fortress OS integration partner, and the AllTRACS and Fortress OS page covers how the two fit.
How does Fortress measure against this checklist?
Fortress HUD vouchering covers the checklist rows below, but it does not support TRACS 203A.
| Checklist row | Fortress today |
|---|---|
| One voucher per subsidy type and contract | Vouchers are set up and managed by property, subsidy type, contract number, and voucher month. Rolling Drafts are created in chronological order for each subsidy type and contract combination. |
| HUD-52670 and MAT30 output | Generates HUD-52670 content, a summary plus supported schedules, and MAT30 output with TRACS-specific export and validation rules. |
| Voucher sections | New Tenant Events, Regular Assistance, Adjustments, Repayment Agreements, Miscellaneous Accounting, and Special Claims. |
| Validation before submission | Blocks empty vouchers and out-of-order submissions and says what is missing. |
| Voucher states and locks | Draft, Submitted, Approved, and Paid, with submission timestamps. Approved and Paid vouchers are locked against changes. Supported changes to a Submitted voucher return it to Draft. |
| Repayment carry-over | Repayment agreements can be created, modified, validated, and deleted, and they carry over between vouchers until the balance is zero. |
| Permission separation | Six permissions: viewing, read-only, setup, submitting, approving payment, and posting payments. |
HUD vouchering in Fortress has been in beta since September 28, 2026, and there is no general availability date. Ask to see the workflow on your own contracts in any beta tool before you decide, ours included.
Fortress is the wrong pick if you want a bureau to own the vouchering end to end, or if you need a tool that supports TRACS 203A. If you want the voucher built inside the same system as your certifications, see Fortress Compliance.
Built by operators, for operators. Posts under this byline are written and reviewed by the team.
Frequently asked questions
Quick answers to what people ask about this topic. Still curious? Talk to our team.
Contact UsWhat is the HUD-52670?
Form HUD-52670 is the Housing Owner's Certification and Application for Housing Assistance Payments. It has five parts, from contract information through the owner's certification. HUD's form instructions call for a separate form for each subsidy contract.
What is a MAT30?
A MAT30 is the HAP voucher record in the TRACS 202D MAT guide. MAT stands for Monthly Activity Transmission. The MAT30 carries assistance payment detail, adjustments, approved special claims, miscellaneous accounting requests, and repayment agreements.
Does Fortress HUD vouchering support TRACS 203A?
Fortress HUD vouchering does not support TRACS 203A. It is built to the TRACS 202D spec and has been in beta since September 28, 2026. HUD has published no 203A release date, so ask any vendor for its own date in writing, and who set it.
Where does Fortress HUD vouchering stand today?
HUD vouchering in Fortress is in beta, which began September 28, 2026. There is no general availability date. Book a demo to see the voucher workflow.
What can I change after a voucher is submitted?
In Fortress, supported changes to a Submitted voucher return it to Draft. Approved and Paid vouchers are locked against changes. Ask every vendor the same question, because the answer shows how the tool treats a voucher already marked Submitted.
How does HUD want owners to handle HOTMA before TRACS 203A is released?
HUD's rent override one-pager says an owner who implements HOTMA before 203A must use the rent override function in TRACS when the HOTMA-calculated tenant rent differs from the pre-HOTMA amount. Owners also annotate tenant files. HUD has not said when this workaround ends, and the page implies it ends when HUD publishes 203A.
Do I still need a service bureau if my software builds vouchers?
That depends on who you want to own the work. AllTRACS is a Fortress OS integration partner that can manage vouchering for a client. Teams that want to run vouchering in-house look for software, and teams that want an outside group to handle it keep the bureau.
Who can submit a voucher in Fortress?
Fortress splits vouchering into six permissions: viewing, read-only, setup, submitting, approving payment, and posting payments. Ask any vendor whether setup, submitting, and payment posting can sit with different people.
Related resources
Fortress Compliance
Certifications, recerts, and HUD vouchering (in beta).
How HUD vouchering works in Fortress Compliance
How voucher drafts, tenant events, and submissions work step by step.
TRACS 203A: what changes
What HUD has published about 203A, and what it has not.
AllTRACS and Fortress OS
How the AllTRACS integration partner and Fortress OS fit together.
