Income verification and the file behind it
Doing it right and proving it are two obligations
Most EIV findings are not about failing to check income. They are about being unable to demonstrate the check happened, on the date it should have, with the discrepancy resolved and recorded.
A reviewer cannot assess the left column. They can only read the right one, which is why competent teams still receive findings.
Try it
What a reviewer expects to find
Pick a situation. Each one leaves a different evidence trail, and each has a step teams most often skip because it feels like paperwork about paperwork.
Six situations on the left. Between them they cover where most EIV findings come from.
Choose a situation to see the step that gets skipped.
General guidance on the shape of the evidence, not a substitute for HUD's own requirements. Specific reports, retention periods and timeframes differ by programme and change; verify against current HUD guidance for your programme.
What EIV is
A system you must use, and use in a documented way
HUD's Enterprise Income Verification system holds employment and income data drawn from federal sources. Using it is mandatory for programmes that fall under the requirement, and it exists to catch differences between what a household reports and what the record shows.
The obligation is more than access. Reports have to be run at the right points in the cycle, reviewed, discrepancies pursued, outcomes recorded, and the whole trail retained. That last part is where most findings live.
It is also a security obligation. EIV contains protected personal information, so who has access, whether it is still appropriate, and what happens when a member of staff leaves are all part of what gets examined.
None of this is difficult in principle. It goes wrong because it is a recurring administrative task delegated to whoever has capacity, with no written procedure behind it, so it drifts quietly until somebody external looks.
EIV sits alongside the rest of programme compliance. Voucher administration is covered under HCV compliance, project-based submissions under TRACS compliance, and where an audit is already in play, the HUD audit page covers records and condition together.
What we do
Four steps, starting with a sample
File sample review
We test a sample the way a reviewer would, looking for the trail rather than the intention. Ten files usually reveal whether this is one person, one period, or the process itself.
Discrepancy resolution
Where differences are open or resolved without a record, we work through them properly and document the outcome so it stands up to later review.
Access and security review
Who has access, whether they still need it, what happens when someone leaves, and whether that is evidenced. A frequent finding and a quick one to close.
Written procedure and training
Correcting files is temporary. A written procedure and a trained team is what stops the same finding returning next cycle.
Where findings come from
The same handful, almost every time
EIV findings cluster tightly. It is rarely a team that ignored the system; it is almost always a team that used it and left a thinner record than a reviewer needs.
That is worth saying because it changes the fix. If the problem were competence, training alone would solve it. Because the problem is documentation, the answer is a written procedure that makes the record a by-product of the work rather than an extra task afterwards.
It also explains why this recurs after being corrected once. Cleaning up a set of files resolves the finding without touching the process that produced it, so the next cycle looks the same as the last one.
Not sure whether your files would hold up? Ten of them will tell you.
Who needs this
Authorities and owners, for different reasons
Housing authorities carry EIV obligations across public housing and voucher programmes at volume, which makes consistency the challenge rather than knowledge.
Owners and management agents of assisted multifamily carry them per property, which makes coverage the challenge: one person who understands it, and no procedure if they are away.
Either way, the trigger is usually the same. A review is coming, a submission was questioned, or the person who used to handle it has left. If an audit notice has already arrived, start with HUD audit compliance, which covers records and physical condition together.
- Public housing authorities and voucher administrators
- Owners and agents of assisted multifamily
- Organisations with staff turnover in the compliance function
- Anyone with an upcoming review or a questioned submission
Review coming, or nobody left who knows the process?
Questions
EIV compliance FAQs
What is EIV and who has to use it?
HUD's Enterprise Income Verification system holds employment and income data from federal sources, used to check what households report against what the record shows.
Use is mandatory for programmes that fall under the requirement, and the obligation reaches housing authorities and owners or agents alike.
We use EIV properly. Why would we still get a finding?
Because a reviewer cannot assess what you did, only what the file shows. Running a report, spotting a discrepancy and speaking to a tenant are all correct actions that leave no trace unless they are recorded.
That is the single most common source of EIV findings, and it is why competent teams receive them.
What does an EIV finding cost?
Typically repayment of subsidy paid on an incorrect certification, plus penalties where the failure is systemic rather than isolated.
Because errors repeat monthly until corrected, the amount is usually a function of how long the gap went unnoticed rather than how serious any single case was.
Is system access really part of compliance?
Yes, and it is one of the more commonly cited items. EIV holds protected personal information, so who has access, whether it remains appropriate, and whether leavers were removed are all examinable.
It is also among the quickest things to put right, which makes it worth checking first.
Can you fix this without disrupting our team?
Usually. File review is often better done remotely on a sample, and the remediation is mostly procedure rather than personnel.
Where the gap is knowledge, training your own staff is a better purchase than us running the task indefinitely.
How long does a review take?
A file sample and a written summary of where you stand is usually a matter of days. Full remediation depends on how many files are affected and how far back the pattern goes.
We tell you the scale before committing you to the work rather than after.