How to Prepare for an 8823 Audit: A LIHTC Compliance Playbook

Every LIHTC owner knows the feeling. Your state housing finance agency schedules a monitoring visit. The compliance team disappears into a conference room for a week. Files are pulled, source documents are chased, calculations are redone. Sometimes everything checks out. Sometimes a Form 8823 gets filed with the IRS and the deal partners get a phone call.

Form 8823 is the IRS's record of non-compliance at a LIHTC property. State HFAs are required to file it within 45 days of identifying an issue, and the IRS uses it to decide whether credits should be recaptured. There are 17 categories of non-compliance on the form. Most owners have seen at least one of them in person.

The 8823 categories that matter most

The five categories that drive the majority of 8823s we see are:

• Household income above the income limit at move-in
• Owner failed to correctly complete or document the annual income certification
• Violation of the Available Unit Rule (AUR)
• Project failed to meet minimum set-aside requirements
• Owner failed to maintain or provide tenant income certifications

Notice how four of the five are documentation and process issues, not physical or eligibility issues. That is the good news. Process problems are fixable. The bad news is that they fail the same way every year for the same operators, because the process depends on humans remembering rules and finding files.

The playbook

1. Score every file the day it is certified

The right time to find an 8823 issue is the moment the file is certified, not eighteen months later when the state monitor walks in. Every certification should run through a rule check that mirrors what the HFA monitor will look at: income limit, asset treatment, set-aside, AUR posture, source document completeness, and signature requirements.

2. Treat the Available Unit Rule like a clock, not a memory

AUR violations are some of the most common 8823 categories, and they happen because the clock starts on a household that crossed 140% of the income limit and nobody noticed until a comparable unit was rented at market. The trigger needs to be automatic, and the next available comparable unit needs to be tagged the moment it turns over.

3. Build an evidence pack you can produce on demand

For every unit, you should be able to produce the executed Tenant Income Certification, the source documents (paystubs, asset statements, third-party verifications), the calculation worksheet, the set-aside math, and the AUR tracking, in under five minutes. Not in a binder. Not on a shared drive your senior reviewer is the only one who can navigate. As a single export.

4. Pre-audit on a 5% sample every quarter

Sample like a monitor would. Pull 5% of your files at random across the portfolio every quarter, run them through your own rule check, and remediate whatever fails. The cost of fixing an issue on a file you found yourself is a tenth of fixing one a state HFA found.

5. Make HOTMA part of the playbook

HOTMA changes how income and assets are calculated for LIHTC files on dates determined by each state HFA. An 8823 will be filed against a calculation done under the wrong rule set just as readily as a calculation done with the wrong inputs. Track your effective date by state and confirm every file uses the right engine.

What changes when this is software, not a binder

Every step above is achievable manually if you have unlimited senior compliance staff and a small portfolio. For most operators, neither is true. HousingIntellect runs the rule check, AUR clock, evidence pack export, quarterly sample, and HOTMA effective date tracking automatically. Files arrive at the state monitor's review already scored, already documented, already audit-ready.