EIV explained: what the system does and what HUD expects from you

Enterprise Income Verification, almost always called EIV, is HUD's system for comparing what a household reported to what federal wage, unemployment and benefit records show. For owners and agents of HUD assisted multifamily properties, using it is not optional and neither is documenting that you used it.

Most findings tied to EIV are not about the data. They are about process: reports that were never run, discrepancies that were never resolved, and a file that cannot prove either way. Here is what the system contains, what HUD expects you to do with it, and how a reviewer tests that.

What EIV actually contains

EIV draws on federal data sources rather than on anything the property collects. In practice the useful pieces are wage data, unemployment compensation, Social Security and Supplemental Security Income benefit information, and new hire records. The system matches that data to the certifications a property has transmitted, which is why EIV is only as current as your own transmissions.

Two consequences follow from that. First, a household that was never transmitted correctly will not match, and the mismatch looks like a data problem when it is really a certification problem. Second, EIV data lags real life. It is a verification and monitoring tool, not a substitute for third party verification at certification.

The reports you are expected to work

The EIV reports that generate findings are the ones with a required cadence and a required resolution trail.

Income Discrepancy Report. Compares reported annual income against EIV sources and flags variances above HUD's threshold. Each flagged household needs a documented review, a conclusion, and where warranted a corrected certification or a repayment agreement.

New Hires Report. Surfaces employment that started between certifications. This is the report that catches unreported income early enough to correct it cheaply.

Existing Tenant Search. Run at application and move in to confirm the household is not receiving assistance at another property. Skipping it is one of the easiest findings for a reviewer to prove.

Multiple Subsidy and Deceased Tenants reports. Low volume, high consequence. Both identify households that should not be receiving assistance in their current form.

Identity verification failures. Households whose identifiers do not verify will not return income data at all, so the failure has to be worked or every other report is quietly incomplete for that household.

No Income Reported and Zero Income households. HUD expects periodic scrutiny of households reporting no income, and EIV is where that scrutiny starts.

Reviewers do not ask whether you have EIV. They ask you to produce the report, the date you ran it, and what you did about what it said.

Documentation, retention and disclosure

EIV data is federal privacy protected information. Three practical rules follow.

Keep it separate and secure. EIV printouts belong in a controlled location with limited access, not loose in the general tenant file, and the property needs a written policy describing where they live and who can see them.

Retain it for the period HUD requires, then destroy it. Holding EIV documents longer than the retention period is its own exposure, and disposal has to be the kind that actually destroys the data.

Disclose to the household when required. When EIV data drives a change to a certification, the household has the right to see the information and to dispute it, and the file should show that this happened.

How a reviewer tests EIV use

During a Management and Occupancy Review the contract administrator will ask for the EIV policy, then ask for evidence that the policy was followed. Expect a request for report copies covering a lookback period, with run dates visible, and for a walk through of two or three flagged households from report to resolution.

The properties that come through this cleanly treat EIV as a monthly operating routine with a named owner, not as something to assemble before a review. If you want the routine tested against the way a reviewer reads it, that is exactly what an independent HUD compliance review does.

Where teams get tripped up

Running reports and filing them without resolution notes. A printed report with no annotation proves you generated a PDF, not that you reviewed anything.

Treating a discrepancy as closed because the household explained it verbally. The explanation needs to be documented and, where it changes income, reflected in a corrected certification.

Letting access lapse so the reports stop being run at all. That is a system access problem with a compliance consequence, and it is covered in our companion piece on EIV access and login.

EIV rewards boring consistency. A named person, a monthly calendar entry, a resolution log, and a secure file location will prevent most of what monitors cite.