Restricted rents and the operating pro forma — Indiana

What happens, and in what order

The structural risk is the same one every LIHTC state shares: nothing in this sequence has a natural human checkpoint. A utility allowance error, a mis-applied rent chart, or a scoring election made without its matching sub-election propagates silently into net rent, NOI, supportable debt and the credit request.

Step one: which limits apply, and IHCDA's 45-day clock

HERA hold-harmless applies the same way it does everywhere: income and rent limits for a project (as defined by the Line 8b election on Form 8609) never decrease after 2008, and a subset of Indiana counties may carry HUD-published "HERA special" limits in a given year, usable only by projects placed in service on or before December 31, 2008. This guide did not independently verify which Indiana counties currently carry HERA special limits — check the current-year HUD MTSP release, not a prior year's list.

Indiana has no equivalent to California's separate state-agency income-limit methodology. IHCDA's tax credit, HOME and HTF charts are all drawn from HUD's own published data — there is no independent Indiana AMI regime layered on top of the federal one.

The formula, and the imputed-household-size mechanic

Maximum gross rent = 30% of the applicable income limit for the imputed household size, divided by 12 — regardless of how many people actually live in the unit (IHCDA Compliance Manual Part 4.2B). HUD publishes the resulting dollar rent limits directly; a tool that rebuilds rent limits from raw income-limit figures rather than reading HUD's own MTSP rent table risks the same rounding-direction error other states' developers make.

One national-methodology point worth carrying into Indiana underwriting even though this guide did not independently re-verify it against Indiana's own 2026 table: every MTSP AMI tier (30/40/50/60/70/80%) is HUD-derived from the Very Low-Income Limit rather than a literal percentage of the county median, because the VLIL itself carries high-housing-cost adjustments and a national cap. Never compute a tier by multiplying a median — read the published tier off IHCDA's own chart.

Utility allowances — five sources, three that need IHCDA's sign-off

Gross rent includes an allowance for tenant-paid utilities other than telephone, cable and internet (26 CFR Section 1.42-10; IRS Notice 89-6). Utility allowances are a building rule, applied under a strict, order-dependent hierarchy (IHCDA Compliance Manual Part 4.4D).

Sub-metered actual-consumption billing counts as tenant-paid utility cost and is eligible for a utility allowance (IRS Notice 2009-44). Ratio utility billing system (RUBS) charges do not qualify as a utility allowance at all — they must instead be counted as a non-optional fee directly in the gross rent calculation, a different and usually smaller allowable deduction.

Utility allowances must be updated at least annually, and reviewed within 90 days of any update by IHCDA, HUD, Rural Development or the local PHA (Compliance Manual Part 4.4E). Noncompliance is a two-pronged test: an error in applying the correct allowance type, that also caused rent charged to exceed the applicable limit. Both prongs must be true before an 8823 issues (Part 4.4F).

A genuinely Indiana-specific wrinkle: IHCDA publishes its own annual internet utility allowance, and an applicant claiming the QAP's internet-access scoring points (Part 6.2(I), up to 4 points) by including internet in the utility allowance calculation must use IHCDA's published internet figure or calculate one annually under the same Part 4.4 options — tying a scoring election directly to a utility-allowance choice.

Which revenue counts, and Indiana's narrower cash-flow ceiling

Gross rent excludes any rental assistance payment made to the owner to subsidize a tenant's rent — tenant-based or project-based Section 8, PBV, PBRA, or comparable federal/state/local rental assistance (IRC Section 42(g)(2)(B)(i); IHCDA Compliance Manual Part 4.2H). A PBRA or PBV unit can collect contract rent above the LIHTC limit because only the tenant-paid portion is tested against the cap.

Indiana's underwriting guidelines apply a cash-flow ceiling only to Project Based Voucher deals, not to every deal the way some states do: for PBV Developments, cash flow (net of acceptable reserve amounts, after ensuring all debt is satisfied) may not exceed 10% of total operating expenses (QAP Part 5.2(A)). A non-PBV Indiana deal has no comparable stated cash-flow ceiling — only the DCR band's upper bound functions as an implicit cap.

Unlike some states' underwriting regulations, this research did not locate an IHCDA rule explicitly barring the underwriting of tenant-based voucher income as project revenue. Because tenant-based assistance is excluded from the gross rent test but is not contractually tied to the unit the way project-based assistance is, treat it as a conservative, non-guaranteed revenue source rather than assuming an IHCDA prohibition that this guide could not confirm.

The pro forma is a parameter set: IHCDA's Part 5.2 underwriting guidelines

Management fee is capped by unit count against effective gross income: 7% for 1–50 units, 6% for 51–100, 5% for 101 or more (QAP Part 5.2(B)). Total operating expenses must underwrite to at least $5,000/unit/year, inclusive of replacement reserve contributions and exclusive of debt service — a single flat statewide floor, not a regional or building-type table (Part 5.2(A)). "Developments that depend on commercial income to meet the minimum underwriting guidelines will not be considered financially feasible" (Part 5.2, preamble).

Property taxes and insurance get no fixed percentage-of-cost minimum the way some states set one; instead the applicant must submit a narrative explaining how the estimates were derived, and if a PILOT, tax abatement or exemption has not yet been approved by application, the project must be underwritten with full property taxes included (QAP Part 5.2(J)).

This research did not find a codified post-debt-service cash-flow distribution waterfall in the QAP the way some states write one directly into regulation — Indiana appears to handle distribution mechanics through IHCDA's own loan documents and the recorded Extended Use Agreement rather than in the QAP text itself. Confirm the actual waterfall against the specific IHCDA loan terms for the deal rather than assuming a QAP-level default.

The rent-restriction scoring trap

A separate 3-point election (QAP Part 6.1(B)) matches income restrictions to the rent restrictions selected. Skip it, and if the deal is on the 20/50 set-aside all units are income-restricted at 50% AMI regardless of the deeper rent tiers committed to under 6.1(A); on 40/60, all units are income-restricted at 60% AMI. The rents still lock into the deeper tiers in the recorded Extended Use Agreement — only the income eligibility ceiling stays at the higher pool-wide number. That mismatch is easy to build into a pro forma without noticing.

Extended Use Period length is also scored (QAP Part 6.1(C)): 2 points for committing to 35 years (15-year Compliance Period plus 20) or 4 points for 40 years (plus 25), on top of the 30-year default (15 plus 15) every award carries. The commitment is recorded in the Extended Use Agreement and will not be waived later.

The QAP's 3rd tie-breaker, used when scores are equal and credits are short, awards priority to the application with the lowest average rent restriction across all units — a direct incentive, on the margin, to underprice the rent roll to win a competitive round, independent of whether the deal can actually carry debt at that rent level.

The two pressures connect: committing to the maximum 16 points under Part 6.1(A) is also one of the paths to a discretionary basis boost of up to 30% on 9% applications (QAP Part 5.2(L)), alongside disaster-area designation and several set-asides. Chasing the deepest rent tier can lower the achievable rent roll and simultaneously raise the credit basis available to offset it — model both effects together, not the rent cut alone.

What's different from other states, and what's still open

Indiana runs a two-year QAP cycle rather than re-adopting annually — the current plan is the "Indiana 2026-2027 Qualified Allocation Plan," governing both the 2026 and 2027 LIHTC credit years, tax-exempt bond volume, and layered state Development Fund / HOME / HTF awards together.

Indiana does layer a state credit on top of the federal 4% credit: the Affordable and Workforce Housing Tax Credit (AWHTC), effective July 1, 2023, and available only to tax-exempt-bond-financed 4% LIHTC deals. It runs over a 5-year credit period beginning the year a building is placed in service, rather than the federal credit's 10-year period. IHCDA may allocate up to $6 million in new AWHTC each year (a $30 million aggregate cap once the 5-year rollout is fully layered), with 20% of each year's amount — $1.2 million — set aside for projects in each of Indiana's five regions. The program is administered through QAP Schedule D-1 rather than a separately codified allocation process, which is why this guide's own scoring tables already reference "4%/bond/AWHTC applications" (Ind. Code Article 6-3.1-35; QAP Schedule D-1).

Nothing in IHCDA's QAP, its compliance manual, or the general landlord-tenant code (Indiana Code Article 32-31) surfaced a statewide cap on how much an owner may raise in-place tenant rent between periods — no equivalent to California's percentage-based rent-increase cap. The one confirmed statutory constraint located is procedural, not a price cap: Indiana Code Section 32-31-5-4 requires at least 30 days' written notice before modifying any lease term, including rent, mid-lease. Treat the absence of a rent-cap statute as this guide's honest research finding, not as a legal opinion — verify against the current Indiana Code before relying on it, since a change could have been enacted this guide's research did not surface.

The Qualified Contract exit is unavailable on Indiana LIHTC deals, but by a different legal mechanism than California's outright statutory bar: IHCDA requires every applicant to sign an irrevocable contractual waiver of the QC right as a threshold requirement, recorded in the Extended Use Agreement (QAP Part 5.1(U)) — no waiver of this particular threshold requirement is even permitted at application. Any residual-value assumption premised on a year-15 QC conversion to market rate should be checked against the specific recorded EUA and Form 8609 elections, not against a state statute.

IHCDA backs its scoring and underwriting assumptions with real dollar consequences through Final Application: failing to maintain the initial application's score can draw a $5,000-per-point fine, a $10,000-per-unit fine if the unit count drops, and up to a one-year suspension of the applicant, owner, developer and other team members from IHCDA funding (QAP Part 7.6). A $1,000 modification fee (plus $1,500 if legal documents must be amended) and a separate $1,000 re-underwriting fee apply to changes that touch the pro forma or sources and uses before loan closing (Part 7.2).