How to Automate Income Certification: A Step-by-Step Guide for LIHTC and HUD-Assisted Properties

‍Most affordable housing operators are still running recertifications the same way they did fifteen years ago. Here’s what changes when you stop.

ExactEstate — Industry Insider Series

If you walked into ten affordable housing leasing offices today and asked the compliance staff how they handle income certifications, eight of them would walk you through some version of the same workflow. A printed checklist. A folder of pay stubs and bank statements. A spreadsheet for asset calculations. A blank state TIC form pulled up in Acrobat. A desk calendar with sticky notes for upcoming recerts. Maybe a shared inbox where third-party verifications from employers come back two weeks late.

This is not a software problem. It is a workflow that grew up before the software existed, and the software — when it eventually arrived — was bolted onto it rather than replacing it.

The result is a recertification process that takes thirty to forty-five minutes per household when nothing goes wrong, and considerably longer when something does. For a property with two hundred LIHTC units running annual recerts plus interims, that is hundreds of staff hours every year spent on a workflow that an auditor will spend 90 seconds reviewing per file.

This guide walks through what income certification automation actually looks like — step by step, from the recert trigger to state HFA or TRACS submission — and where the manual process can be replaced with an automated workflow that runs without staff intervention. The framework is the same for LIHTC and HUD-assisted properties. Where they diverge, the differences are called out at the steps that matter.

Why the manual process breaks

Three things have changed in the last few years, and together they have made the manual recertification workflow harder to defend than it was even five years ago.

Manual workflows survive because they feel safe. The compliance manager knows where every file is. The Excel sheet has the right formulas. The state forms are saved in the right folder. Until the compliance manager leaves, or HUD changes the form, or the state HFA shows up for an audit and asks for the third-party verification on a unit certified two years ago.

The shared framework

Income certification — whether for an LIHTC initial, a Section 8 annual recert, an interim for a household composition change, or a USDA Rural Development recertification — follows the same nine-step arc. The work inside each step varies by program. The arc itself does not.

What follows is each step — what the manual version actually involves, where automation lives, and what changes when it does.

Step 1. Trigger and scheduling

What manual looks like

A compliance manager keeps a master calendar of recertification due dates. Annual recerts are scheduled twelve months from the previous certification. Interim recerts are triggered ad hoc when a resident reports an income change, household composition change, or unit transfer. The calendar is usually a spreadsheet or, in smaller operations, a printed wall calendar with notations.

The failure mode is straightforward: a recert gets missed. Either it falls off the calendar entirely, staff turnover causes the calendar to be lost, or the staff member responsible takes leave during the wrong week. A missed annual recert on a LIHTC unit is an 8823 finding. On a Section 8 unit, it is a TRACS error and a HAP payment risk.

Where automation lives

The system holds every household’s last certification date and the program-specific recert window. From that, it generates a forward-looking schedule and surfaces it as a queue. Annual recerts populate at twelve months out. Interims are created on demand by staff or triggered by household-reported changes through a resident portal. The queue is the calendar — it does not depend on a person remembering to check it.

Step 2. Notice generation and resident communication

What manual looks like

Staff drafts notices in Word or pulls a template from a shared folder. The notice goes out at 120, 90, 60, and 30 days before the recert deadline, with a document checklist attached. Each notice is addressed individually. For a property running fifteen recerts a month, this is a half-day of clerical work, repeated across every property in the portfolio.

Where automation lives

Notice templates merge resident, lease, and property data automatically. The 120, 90, 60, and 30-day notices are generated on schedule and deliver through email, the resident portal, and printed mail as configured. The documents checklist is program-specific — LIHTC, HUD, USDA RD, or HOME — and pulled from the household’s certification history. The compliance team’s involvement drops to reviewing the queue, not drafting the letters.

Step 3. Income and asset data collection

What manual looks like

The resident comes to the leasing office. Staff walks them through the income questionnaire by hand, transcribing wages, benefits, asset balances, and expense deductions onto paper. Verification documents — pay stubs, benefit letters, bank statements — are photocopied and clipped to the file. If the resident forgets a document, they leave and come back. If they cannot come in, the process stretches across multiple phone calls and mail exchanges.

The failure mode here is data entry. Numbers get transcribed wrong. Asset categories get misclassified. A household member is missing. The error compounds at every downstream step.

Where automation lives

Residents and applicants enter their own income and asset data through a self-service portal. They upload supporting documents directly. The system structures the data into the categories the TIC and 50059 forms require — wages, benefits, asset income with imputed income calculations, rental assistance, expense deductions — and stores the source documents alongside. Staff review and verify rather than transcribe.

This step is where the greatest time savings appear, because it shifts data entry from staff to the resident, who only has to do it for their own household. Per-cert data entry that runs thirty to forty-five minutes manually drops to under ten.

Step 4. Third-party verification

What manual looks like

Staff prints verification request forms, mails them to employers, banks, and benefit sources, and waits. Two weeks is a reasonable response time. Four weeks is common. Some employers do not respond at all and require follow-up calls. For Section 8 households, the lack of third-party verification delays the entire recert until it arrives.

Where automation lives

Income and asset verification is handled through integrated services that electronically pull payroll data, bank account balances, and benefit records, often within hours rather than weeks. The household-level grouping means a multi-earner household is verified in a single request rather than parallel paper trails. Discrepancies between resident-declared income and verified income automatically flag for compliance review — which is the actual fraud-prevention point of third-party verification, not the paper trail.

This is also the step where the verification checklist becomes a hard control. The TIC cannot proceed to approval until all required verifications are uploaded and marked as verified. Staff sees the gap before the compliance officer does.

Step 5. Eligibility check against income and rent limits

What manual looks like

Staff opens the current MTSP income limits PDF or the state-specific HUD income limit table for the property’s county. Looks up the household size limit. Compares the household’s annual income against the set-aside designation’s income limit. Calculates the rent limit, subtracts the utility allowance, and confirms the contract rent is below the maximum. If the property is doing the Average Income Test, the staff member also checks the building-level average against the 60% cap.

This is arithmetic, but it is arithmetic done at high frequency under audit pressure, and the failure mode — approving a household that exceeds the income limit — is one of the most common 8823 findings in LIHTC monitoring.

Where automation lives

HUD income limits are imported directly from the HUD User API by the property’s ZIP code. Limits update annually when HUD publishes new figures, with effective dates preserved historically so prior certifications remain valid against the limits in effect at the time. The system runs the eligibility check during the certification process and blocks the approval if the household exceeds the income limit for the unit’s designation. The same enforcement applies to rent limits during designation pricing.

For LIHTC properties using the Average Income Test, the AIT calculation runs in real time. Pre-change validation prevents a designation update from pushing the building average above 60%.

For Section 8 properties, the eligibility check is structurally similar but tied to TTP calculations and HAP allocation rather than income limits at the unit level.

Step 6. Form generation

This is where LIHTC and HUD-assisted diverge.

LIHTC and HOME

State HFAs each publish their own TIC form. Some states use the older NCSHA model. Others have their own. Forms get revised when state policy changes — Texas published a HOTMA-aligned 2025 TIC, Florida updated its FHFC TIC-1 to v-24-04 in January 2025, Georgia DCA maintains both 2006 and 2024 versions. Manually filling a state TIC means typing the same household, income, and asset data into a hundred-plus PDF form fields, often after already entering it into the property’s system. Mismatches between what staff entered into the system and what they typed onto the form are a documentation finding waiting to happen.

Automation generates the state-specific TIC PDF from the data the resident and staff already entered — mapping household composition, income, assets, and rent fields directly into the form’s fillable cells. If the household has fewer than five members, the addendum page trims automatically. DocuSign anchor tags are embedded during generation, so the form is ready to route for signature without a second handling pass.

HUD-assisted (Section 8 PBRA, 202, 811)

The form is the 50059 (or 50059-A for partial certifications). The 50059 is generated by the property’s software and submitted electronically to TRACS, not filled out by hand on paper for most operations. The manual workflow here is more about TRACS submission readiness — verifying that the 50059 data string assembles cleanly, that voucher amounts reconcile against the contract, and that the submission window is met.

USDA Rural Development

Rural Development properties submit through MINC — schema-validated XML conforming to USDA RD standards. The income field categorization is different from LIHTC and HUD. Social Security income is broken out separately. Imputed income from assets uses a configurable passbook savings rate. Manual MINC preparation is rare; the form complexity makes it impractical without automation.

The shared point: in every program, the form generation step is where the error rate spikes manually and where automation produces the most defensive value at audit.

Step 7. Approval workflow

What manual looks like

The site manager reviews the file. Then it routes to the compliance officer or asset manager. Both review the supporting documentation, the income calculations, and the form. If anything is wrong, the file goes back to the site manager. The cycle continues until both approve.

In smaller operations, the same person performs both roles, and the segregation of duties an auditor expects is not present. This is a finding category that does not show up until an external audit reviews the approval trail.

Where automation lives

Dual-track approval routes the certification to the management and compliance approvers in parallel — they review independently, and final approval is conjunctive. Both must sign off. Each approval is logged with a timestamp and the user. Denials carry a reason and route the file back for correction. The audit trail is complete by construction.

Step 8. Signature collection

What manual looks like

The resident comes back to the leasing office to sign the TIC. The head of household signs first, then any co-head or spouse, then any adult co-tenants. Then the property owner or authorized agent signs. If anyone is unavailable, the file waits. For a recert, this often means scheduling a second appointment, which compounds the delay if the recert is already running tight against its deadline.

Where automation lives

Embedded electronic signature — routed through the resident portal — lets household members sign from their phones in the required order, then routes the form to the property owner. Real-time signing status tracks per recipient. Reminders go out automatically if a signer is delayed. The compliance team does not have to chase signatures by phone.

Step 9. Submission and filing

LIHTC

Approved TICs get filed electronically with the state HFA according to that state’s reporting cadence. Some states require quarterly tenant data submissions. Others run annual reports. Demographics and household composition data flow into the same submission.

HUD-assisted

The 50059 data string transmits to TRACS. HAP voucher payments process through the housing authority. Rent roll syncs reconcile HAP amounts against contract rents and flag discrepancies.

ExactEstate handles TRACS submission through a bundled ShofCorp integration — not as a separate vendor relationship that the operator has to source, manage, or pay for separately.

USDA Rural Development

MINC XML exports validate against the USDA schema and submit through the agency’s payment processing system.

The shared point at this final step: submission is the place where errors made earlier in the process become external. A bad income calculation on a TIC is a private mistake until it is filed with a state HFA. An incorrect 50059 is an internal error until it is transmitted to TRACS. Automation’s value here is not the submission itself — it is the cumulative effect of every prior step having been correct.

A note on HOTMA-readiness

Every operator running compliance certifications is asking the same question right now: how much of this should I change today to be ready for the full HOTMA implementation in January 2027?

The honest answer is that no software vendor can claim full HOTMA compliance today, because HUD has not finalized the TRACS 203A specifications. The interim guidance is partial. The form revisions are partial. The state HFAs that key off HUD’s framework are waiting on HUD.

What operators can do — and what their software should support — is HOTMA-readiness. That means asset exclusion logic that aligns with the new $50,000 de minimis threshold. Imputed income calculations that use the updated passbook savings rate. Relationship code enforcement that matches the HOTMA-compliant household composition rules. Per-program configuration that lets a property turn HOTMA logic on as soon as HUD publishes the final specifications, without rebuilding the certification workflow.

The transition window before TRACS 203A drops is the rare period when migrating off a manual workflow does not stack risk on top of HUD’s ongoing changes. Operators that move now will spend their transition period running recertifications. Operators who wait will spend their time reconciling spreadsheets against form revisions they did not anticipate.

Where this lands

Income certification automation is not a feature — it is the compliance team’s working environment. The right system makes the difference between a compliance staff that processes recerts as a background activity and one that drops every other priority during recert season.

ExactEstate was built for affordable housing from day one, which is why every step in the workflow above is native to the platform rather than bolted on as a module. Self-service applicant and resident portals. State-specific TIC generation. Verification checklist as a hard control. Dual-track approval. Embedded DocuSign. HUD income limit auto-import. ShofCorp-bundled TRACS submission. AIT validation. The 140% rule runs automatically at every recert approval.

It is also priced to make the math obvious for portfolios under serious cost pressure. Every feature is included. Flat per-unit pricing. U.S.-based support that answers when called.

The case for moving off a manual recertification process is not the time savings, although those are real. It is that the manual process is the part of the operation most likely to fail an audit, most likely to break when staff turns over, and most likely to absorb the cost of HOTMA implementation when the final rules drop. Automation cuts all three. Significantly.

If the recert calendar lives in a spreadsheet today, the next audit window is the right time to change that. Book a demo today!

Frequently Asked Questions

How much time does automation save?

Manual recerts take 30-45 minutes per household; automation drops this to under 10 minutes by shifting data entry to resident portals and speeding verifications.

Is it HOTMA-ready for 2027?

No full compliance yet (HUD specs pending), but automation supports HOTMA features like $50,000 asset exclusions—toggle on when finalized.

Why avoid manual recerts?

Risks missed deadlines, errors, and turnover; automation enforces queues, validations, and audit trails.

Does automation work for both LIHTC and HUD-assisted properties?

Yes. The nine-step certification workflow applies to both programs. Where they differ — primarily in form generation (state TIC vs. 50059) and submission (state HFA vs. TRACS) — the system handles each path automatically based on the property's program type.

What happens to our recertification process if a compliance staff member leaves?

With a manual workflow, turnover often means losing the recert calendar and institutional knowledge along with the person. An automated system holds all due dates, household history, and approval trails in the platform itself, so a new staff member can pick up an active queue without rebuilding anything from paper files.

BOOK A DEMO