If financial reporting is the operational early warning system for affordable housing portfolios, compliance reporting is the regulatory safeguard that ensure institutional integrity.
Within the LIHTC program (as well as Affordable Housing regulated programs), compliance failures do not usually occur suddenly. Instead, they accumulate gradually over time through small administrative oversights.
A missed recertification. An improperly assigned unit. An income calculation error.
Left unaddressed, these small issues could eventually result in state monitoring findings or tax credit recapture risk.
For this reason, experienced asset managers rely on a Monthly Compliance Status Report.
Core Components of the Compliance Report
The monthly compliance dashboard should include:
- Unit designation schedule
- Tenant income qualification summary
- Recertification or annual tenant income certification tracking
- Student rule monitoring
- Vacancy and Next Available Unit Rule (NAUR) compliance
These reports allow compliance teams to monitor regulatory risk continuously rather than waiting for annual reviews.
Recertification Pipeline Management
Annual tenant income certifications and recertifications are among the most common compliance failure points in affordable housing.
A well-structured compliance dashboard tracks recertifications across multiple time horizons:
- Tenant Income Certifications (TICs) due in 120 days
- TICs due in 90 days
- TICs due in 60 days
- Overdue recertifications
This pipeline approach allows teams to prioritize files and prevent last-minute compliance issues.
Next Available Unit Rule (NAUR)
The Next Available Unit Rule governs how units must be reassigned when tenants exceed income thresholds.
If a household’s income rises above program limits, the property must rent the next available comparable unit to an eligible low-income tenant.
Failure to monitor NAUR status can lead to compliance violations affecting multiple units.
Monthly reporting should therefore track:
- Vacant LIHTC/affordable units
- Over-income households
- Next available unit assignments
This ensures that unit turnover decisions remain compliant with regulatory requirements.
Average AMI and AIT Monitoring for Income Averaging Deals
Income averaging developments introduce additional complexity.
Instead of requiring every unit to meet a single income threshold, income averaging deals allow units to be designated across multiple AMI levels.
In addition, some LIHTC properties can also qualify with Average Income Test (AIT) calculations. The Consolidated Appropriations Act of 2018 allows developers more flexibility in how they designate affordable units, instead of requiring every low-income unit to be capped at a fixed income level (like 60% of Area Median Income), AIT allows a blend of income levels across units—as long as the average does not exceed 60% of Area Median Income (AMI).
Monthly reporting should therefore track:
- Overall Average Income Test calculations
- AMI designation for each unit
- Weighted average AMI across the property
- Compliance with regulatory agreement thresholds
- Utility Allowances (UAs) and centralized tracking across portfolio
- Flag UA’s approaching 12-month expiration date as well as any missed updates
- Maintain audit-ready UA calculation documentation (source of UA, calculation methodology, effective date, proof of timely implementation)
Failure to monitor these metrics can place the entire development at risk.
Additional Compliance Risk Indicators
Additionally, be sure to track a LURA in real-time. A LURA (Land Use Restriction Agreement) is the core legal document that governs property under the Low-Income Housing Tax Credit (LIHTC) program. It defines what must be complied with and for how long.
For audits (HFA, investor, or internal), your ability to track, interpret, and prove compliance with the LURA is critical.
How to track:
- Convert the LURA into real-time structured data (instead of static PDFs)
- Break into % set-aside, AMI limits, compliance dates, special provisions
- This information should be connected to LURA requirements to enable real-time validation or flag if in violation
- Build compliance dates, alerts and flags into the real-time structure
- All information should roll up into a LURA compliance dashboard
- Keep Audit-Ready Documentation
- For every LURA provision, maintain source document (recorded LURA), Interpretation (how your team applied it), Supporting data (ex. Tenant files, utility allowances etc.)
These indicators provide early visibility into operational patterns that may lead to regulatory scrutiny.
Tracking Physical Inspections
The HFA and other bodies do physically inspect properties on a regular basis, not just when there is an issue of non-compliance. Inspections occur during the initial place-in-service/lead up, ongoing compliance inspections (federally every property is required to be audited every 3 years but HFA usually inspects ever 1-2 years). Over and above a property could receive an additional physical inspection that is triggered by tenant complaints, prior failed inspections, suspected non-compliance or a post-correction reinspection. Physical inspections should be tracked and logged just like all compliance calculations and reporting.
How to Track HFA or other physical inspections:
- Create a Property-Level Inspection Log that tracks last inspection date, next expected date, inspection type, inspecting agency
- Track findings at the line-item level (unit/building, deficiency type, severity type etc) in a structured data format (vs. PDF)
- Monitor and calendarize correction deadlines
- Maintain record and evidence of fixes/corrections (before/after photos, work orders, vendor invoices, internal sign-off etc.)
- Roll this up to a portfolio level dashboard across all assets to monitor inspection pass/fail rates, open deficiencies, repeat violations etc.
Why Compliance Must Be Monitored Monthly
Many organizations treat compliance reporting as a quarterly or annual task. This approach creates significant risk. By the time an issue appears in a state monitoring review or audit, it may already have existed for months.
Monthly compliance reporting allows organizations to shift from reactive problem-solving to proactive compliance management.
How a purpose-built affordable housing platform can help with compliance monitoring and reporting
A purpose-built affordable housing and LIHTC asset management platform can dramatically improve how monthly compliance reporting is managed by centralizing the data, structuring the data, workflows, and documentation required to monitor regulatory risk. Instead of compliance teams manually tracking recertification timelines, NAUR exposure, and AMI thresholds across spreadsheets and property manager reports, a specialized platform can automatically aggregate tenant compliance data across the portfolio and surface critical indicators through real-time dashboards. Automated alerts can flag recertifications approaching 120, 90, or 60 days, identify units where household income exceeds program limits, and continuously calculate weighted AMI for income averaging properties.
Purpose-built affordable housing platforms, like Fusion Asset Management, maintain a structured record of unit designations, tenant certifications, and compliance documentation, allow teams to gain a clear audit trail while reducing the administrative burden of monitoring multiple regulatory rules simultaneously. The result is that compliance teams spend less time gathering and reconciling information and more time proactively addressing potential violations before they become Housing Finance Agency (HFA) audit findings or receive an IRS form 8823 (report of non-compliance) putting tax credits at risk.
Leave a Reply