LIHTC COMPLIANCE SOFTWARE · SECTION 42 · TIC
No more rebuilding the household from a spreadsheet to finish the certification. Bring income, assets, project elections, state HFA requirements and layered funding together, find what’s missing and move the Tenant Income Certification (TIC) toward review.
A signed form isn't useful if the numbers and documentation behind it don't hold up.
A project’s set-aside election is too important to live in someone’s email. Keep elections, income limits, household documentation, certification history and state requirements in view when it’s time to prepare the TIC.
ExactEstate reads the applicable income limit and the state TIC form from that configuration, so the specialist does not have to remember them.
A project’s set-aside election and unit designations change which LIHTC income limits apply. For an Average Income Test project, units have designated limits and the qualifying group must meet the statutory average. ExactEstate shows the project configuration next to the TIC, so staff review any redesignation against the agency’s guidance instead of rebuilding those decisions from a spreadsheet.
The TIC should start from information your team already collected. Bring the verification, lease and program record together, check what is missing and make the approval trail easy to follow.
Anything the software asks for twice is something it failed to carry, and a place two versions of the file can start to disagree.
When household income rises above the applicable 140% threshold, the LIHTC Next Available Unit Rule matters to subsequent leasing of comparable-or-smaller units in that building. ExactEstate flags the building and lists its over-income households, so the specialist can apply the rule to the next comparable unit. For an Average Income Test project, the threshold calculation differs from a conventional set-aside election, and layered HUD Multifamily requirements run in their own workflow.
Prepare the TIC from the household record at move-in and at each recertification required for that project. Keep the effective date, approval, next due date where applicable, and over-income review in the same workflow.
State TIC forms are live for Alaska, Florida, Georgia, Maryland, New York and Texas. Other states receive NAHMA-format XML where the HFA accepts it.
The reviewer signs off inside the workflow. That approval stays on the record with the TIC.
Once approved, the TIC's PDF is stored with a frozen summary of what it was built from. A correction withdraws the approval with a recorded reason and generates a new TIC, and the withdrawn copy stays on the record.
Work the LIHTC TIC with the property's HOME, bond or NHTF designations in view. Each layer keeps its own requirements, and ExactEstate keeps them apart on one shared record so your specialist reviews each against its own rules and limits. That is how ExactEstate runs affordable housing compliance across every program.
The unit carries its High or Low HOME rent. With HOME checks on, HOME income and rent limits apply alongside the LIHTC limits.
When the property also has tax-exempt bond financing, the bond designation stays on the certification record, so your team checks the bond’s own income, occupancy and reporting rules alongside the TIC.
A National Housing Trust Fund (NHTF/HTF) designation sits alongside the TIC in the property record, so the HTF documentation and reporting the project owes stay in view.
HOTMA changed how income and assets are calculated, and each program set its own start date: January 1, 2027 for HUD Multifamily and for public housing and vouchers, and July 1, 2025 for USDA Rural Development.
For a LIHTC project, the requirement is whatever its state or HFA has set. ExactEstate applies HOTMA per property from that adoption date. That covers the indexed asset threshold, the updated deductions and the 10% medical expense phase-in. Program-specific review does not go away because the calculation changed.
The risk score on each resident record sets the review order, not the verdict, so reviewers open the riskiest file first instead of alphabetically.
Your reviewers make every call; the score just puts the right file on top.
EEva reads the project's configuration, names what blocks the certification and cites the authority where one exists, not a specialist's memory.
The example below uses a sample LIHTC project, not yours.
