PIC vs. TRACS: Which HUD Submission System Do You Actually Need — and Why RAD Changes the Answer

‍If you're a PHA undergoing a RAD conversion, the most expensive software decision you'll make this year starts with one question that most operators get wrong. Here's how to ask it right.

The most expensive question in HUD compliance

Talk to enough housing authorities, and you'll hear the same sentence in different accents: "We need software that submits 50058s through TRACS."

That sentence is wrong. Not slightly wrong. Wrong in a way that, if you act on it, gets you a vendor that can't do the work you actually need.

HUD itself flags this in the first paragraph of its guidance for properties undergoing RAD conversion. The exact language: "PIH Information Center (PIC) is not TRACS! Do not assume an established Public and Indian Housing (PIH) vendor knows TRACS." That's HUD warning operators about the conflation, not us.

If you're a public housing agency, an owner taking on a RAD-converted portfolio, or a multifamily operator with mixed program types, this distinction is load-bearing. It determines which forms you file, which system you file them in, which software you need, and — for RAD conversions specifically — what you have to get done in the first 90 days after closing or your subsidy stops moving.

Here's how the two systems actually work, where operators get tripped up, and the questions to ask any software vendor before you sign anything.

Two forms, two systems, two different jobs

HUD runs a separate submission infrastructure for two different sides of the assisted housing world. The forms look similar at a glance — both capture household composition, income, and rent — but the systems behind them are not interchangeable.

HUD-50058 → PIC (transitioning to HIP)

The Family Report, or HUD-50058, is the form that Public Housing Agencies file. It goes to the PIH Information Center (PIC), which HUD is in the process of replacing with the Housing Information Portal (HIP). PHAs use 50058s to report on:

If you administer any of those programs, your monthly compliance work runs through PIC. Your software needs to generate, validate, and transmit 50058s in the format PIC accepts — and increasingly, in the format HIP will accept once the transition completes.

HUD-50059 → TRACS

The Owner's Certification of Compliance, or HUD-50059, is the form that owners and management agents file for project-based Section 8 multifamily properties. It goes to the Tenant Rental Assistance Certification System (TRACS), run by HUD's Office of Multifamily Housing. 

TRACS handles:

If you own or manage any of those properties, your monthly compliance work runs through TRACS — 50059 certifications and HAP voucher transmissions — with deadlines.

Why this matters: they don't talk to each other

PIC and TRACS are separate systems with distinct logins, submission cadences, edit checks, data formats, and vendor ecosystems. A software platform that knows one of them well is not, by default, equipped to handle the other. HUD's guidance on this is unusually direct: "an established PIH vendor that is knowledgeable about PIC is not guaranteed to be knowledgeable about TRACS."

That single sentence has been the source of expensive software decisions for years. Operators sign with vendors who handle one side and assume the other side will work — only to find it doesn't.

Why operators conflate the two (and why it's understandable)

If you're a PHA that's run public housing for thirty years, your team has filed 50058s into PIC tens of thousands of times. Then your portfolio converts under RAD, and suddenly you need to file 50059s into TRACS. Same households. Same units. Same staff. New form. New system. New rules.

The conflation isn't ignorance — it's pattern recognition. The forms ask similar questions. The income calculations are cousins. The compliance officer's job feels superficially the same. Calling everything "the 58" or "the TRACS submission" is a reasonable shorthand among practitioners who've been doing this work for years.

The shorthand becomes a problem the moment you talk to a software vendor. If the vendor hears "50058 via TRACS" and nods politely, one of two things is happening: either they don't know either system well enough to correct you, or they're hoping the conversation moves on before they have to admit which side they actually serve. Both are bad signs.

The right move, when you're evaluating software, is to lead with the program type and let the form and the system follow. "We're a RAD-converting PHA. Within twelve months, we'll need to submit 50059s and HAP vouchers to TRACS for our converted units. Tell me how your software handles that." That sentence forces clarity in a way the shorthand can't.

The RAD trigger: when conversion forces the switch

Most PHAs hit the PIC-vs-TRACS question for the first time when they go through a Rental Assistance Demonstration (RAD) conversion. RAD moves a property from Section 9 (public housing, 50058, PIC) to Section 8 (project-based rental assistance, 50059, TRACS). The forms change. The system changes. The vendor probably has to change.

Over 200,000 public housing units have been converted through RAD since the program launched, and conversions continue. If you're inside that pipeline — or you're a multifamily operator buying a RAD-converted property — the software question stops being a planning conversation and becomes a deadline-driven scramble.

The 90-day clock

HUD's own guidance puts a number on it. From the date you select a TRACS-compliant software vendor, expect roughly 90 days before you're fully operational in TRACS. Inside that window, you have to:

If your software vendor can't move forward with those steps with you, your subsidy won't move. That's the failure mode. Properties don't typically miss RAD compliance for lack of effort — they miss it because the software they bought wasn't ready for the workflow they intended to use it for.

The first-year quirks nobody tells you about

Even after the 90-day setup, the first year of TRACS operations after a RAD conversion has a handful of behaviors that catch new operators flat-footed. Worth knowing before you talk to any vendor.

Zero vouchers in year one

During the first year of conversion (specifically, Component I conversions from public housing), HUD requires owners to submit "zero vouchers" to TRACS — voucher submissions that document tenant data and certifications without requesting subsidy payment. The actual subsidy in year one continues to flow through legacy public housing channels. The TRACS submissions are running in parallel until January of the year following conversion.

Software that doesn't understand zero-voucher submission will either reject the workflow outright or generate vouchers that ask for a subsidy HUD won't pay. Both outcomes are bad. Both are avoidable.

OARQ adjustments after year one

Starting in January, following the conversion year, owners begin submitting "actual" subsidy requests — but with a wrinkle. Adjustments from the prior year (when zero vouchers were active) must be zeroed out in the new voucher's adjustment section using OARQ (Owner Adjustment Request Query) entries. Forget this step, and your first "real" voucher gets kicked back.

The 21-business-day manual review

For several months after a property starts "real" voucher submissions, every voucher must be emailed to the property's HUD Account Executive before transmission and goes through a 21-business-day manual review process. This continues until HUD's Voucher Processing team takes the property off manual review. Plan your cash flow accordingly — and plan your software workflow around it.

None of this is hidden. It's all in HUD's RAD post-conversion guidance and the TRACS Tip Sheet for converted properties. But it's almost never in the software pitch deck, which is how operators end up surprised by it in month two of a conversion they've been planning for two years.

Questions to ask any vendor before you sign

If you take one thing from this piece into your next vendor conversation, take this list. These are the questions that surface real capability — and real gaps — fast.

That last question is the one most worth running. The PIC and TRACS sides of HUD compliance often don't live in the same software. Pretending otherwise is how operators end up paying for two systems that each do half the job badly.

Where ExactEstate fits — and where we don't

ExactEstate is purpose-built for the TRACS side of the equation. Our compliance module handles 50059 generation with state-specific TIC support, dual approval workflows, and DocuSign-integrated signing. Our TRACS integration runs through ShofCorp — including 50059 data string generation, HAP voucher payment processing, rent roll synchronization with discrepancy detection, and one-click access to the embedded HDS interface. For owners and management agents running PBRA, Section 202, Section 811, or RAD-converted portfolios under PBRA, this is the workflow our customers run on every month.

We're equally direct about scope. ExactEstate is not a PIC submission tool. If your compliance work is centered on Public Housing 50058s or HCV administration, we're not the platform you're looking for, and a vendor that pretends otherwise is signing you up for a problem. The right answer is honest scope from a vendor who can actually do the work — and we'd rather lose a fit conversation than win a wrong one.

For PHAs going through RAD conversion: the conversation worth having with us is the post-conversion TRACS workflow — the part that starts at closing and runs every month thereafter. The first-year zero-voucher quirks, the OARQ adjustments, the manual review window — these are workflows our team helps configure during onboarding alongside the standard TIC, recertification, and HAP reconciliation setup.

The platform is NSPIRE-ready and built for HOTMA. We support layered compliance for properties operating under multiple programs — RAD-PBRA + LIHTC, for instance — with per-property configurability so each property's rules engine matches its actual funding stack. Pricing is flat: $3 per unit per month, with all features included, unlimited users, unlimited support, and U.S.-based support. Implementation runs in days, not months.

If you're going through a RAD conversion right now

The 90-day clock is unforgiving, but it's also predictable. Operators who get TRACS right ahead of conversion — and who pick a vendor that can describe the workflow without flinching — don't have the scrambles that the operators who waited do.

If you want to walk through how the post-conversion workflow actually runs on our platform, our AE, Fernando Castaño, can schedule a demo. Bring your conversion timeline. We'll bring the workflow.

Frequently Asked Questions

What's the difference between PIC and TRACS?

PIC (PIH Information Center) is the HUD system where Public Housing Agencies submit HUD-50058 forms for public housing and HCV programs. TRACS (Tenant Rental Assistance Certification System) is a separate HUD system where owners and management agents submit HUD-50059 forms for project-based Section 8 multifamily properties. They have different logins, data formats, deadlines, and vendor ecosystems — they do not talk to each other.

When does a RAD conversion change which system I need?

At closing. RAD moves a property from Section 9 (public housing, 50058, PIC) to Section 8 (PBRA, 50059, TRACS). From that point forward, your monthly compliance work runs through TRACS — and if your software isn't ready to support that workflow, your subsidy stops moving. You should have a TRACS-compliant vendor selected before closing, not after.

What are "zero vouchers" and why do they matter?

During the first year after a RAD Component I conversion, HUD requires owners to submit vouchers to TRACS documenting tenant data and certifications without requesting subsidy payments — the actual subsidy still flows through legacy public housing channels during that period. Software that doesn't understand this workflow will either reject it or generate vouchers that request payment HUD won't make. It's one of the most common first-year surprises for newly converted properties.

Can one software platform handle both PIC and TRACS?

Some claim to. The right way to test that claim is to ask the vendor to describe the actual data flow for each system separately — forms, validation, transmission format, and submission cadence. Vendors who handle both well can describe both in detail. Vendors who handle one and paper over the other will struggle to get specific. An honest scope from a vendor is more valuable than claimed coverage of everything.

How long does it take to get fully operational in TRACS after a RAD conversion?

From the date you select a TRACS-compliant vendor, budget roughly 90 days. That window covers obtaining a UEI, registering in SAM, getting set up in LOCCS, obtaining Secure Systems access, building a baseline 50059 file for every household, and beginning monthly voucher transmissions. The clock is predictable — the operators who get into trouble are the ones who start the vendor search after closing rather than before.