Affordable housing

Affordable is a different document set, not a stricter one.

A conventional screening flow assumes wage income and pay stubs. An affordable household frequently has none of that, and gets handled as a manual exception. Exceptions are where consistency and compliance both break.

Request a demoHow verification works

24% fewer evictions across the ResProp portfolio.

What it handles

Four things a conventional flow cannot process.

Not because it is stricter, but because it never expected these documents.

Non-wage income sources

Social Security, SSI, pensions, child support, and benefits. A conventional screening flow that only understands pay stubs cannot process an affordable applicant at all.

Multiple income types per applicant

An affordable household commonly combines part-time wages, a benefit, and support payments. Each needs its own treatment rather than a single number.

Asset documentation

Asset docs are part of the certification, not an afterthought. LIHTC asset certification form auto-fill is in progress rather than shipped.

A consistent audit trail

Every verification attempt, method, and document recorded per applicant. Affordable compliance is an audit exercise, and the file has to assemble itself.

Shipped, in progress, planned

Where the line actually is.

Affordable compliance is the area where overclaiming causes real harm, so here is the state of it without softening.

  • Shipped: affordable document engine for Social Security, W-2, child support, benefits, and assets

  • Shipped: multiple income types per applicant for HUD

  • Shipped: net income thresholds configurable per property

  • In progress: LIHTC asset certification form auto-fill

  • In progress: employer confirmation of offer letters

  • Planned: broader income certification form auto-fill

Why consistency is the compliance argument

Screening decisions that are not documented create fair housing exposure.

Affordable applicants are the population most likely to be processed by hand, which makes them the population most likely to receive an undocumented decision. That is a compliance problem before it is an efficiency one.

Every verification attempt, method, and document is recorded per applicant, and an override is logged as an override.

FAQ

Affordable questions

How is affordable screening different from conventional?
It is a different document set rather than a stricter threshold. A conventional flow assumes wage income evidenced by pay stubs. An affordable household commonly has Social Security, a pension, child support, a housing voucher, and part-time wages, in combination. A tool that only reads stubs cannot process that applicant at all.
What is actually shipped versus planned?
Shipped: the affordable document engine covering Social Security, W-2, child support, benefits, and asset documents, plus multiple income types per applicant for HUD. In progress: LIHTC asset certification form auto-fill and employer confirmation of offer letters. Planned: broader income certification form auto-fill. We would rather draw that line than blur it.
Does it handle Tenant Income Certification forms?
Auto-filling income certification forms is planned rather than available today. What exists now is the document collection and verification underneath a TIC, which is the part that consumes the time.
What about grading applicants differently by property class?
Requested rather than shipped. Class A and workforce properties reasonably grade applicants on different bars, and treating them identically is its own problem. Today the income rules are configurable per property, including net income thresholds.
How does this affect fair housing exposure?
Favorably, if the process is uniform. The exposure comes from undocumented, inconsistently applied standards, which is exactly what happens when affordable applicants get handled as manual exceptions. A consistent flow with a logged audit trail is the defensible position.

Bring an affordable application that took an hour.

The combination of a benefit letter, a part-time stub, and a support order. That is the case worth testing.

Book a demosales@proofuphq.com
Schedule a Demo