Construction, the 10% test, and getting to 8609 — Indiana

The clocks you are now running against

Indiana Housing and Community Development Authority (IHCDA) is Indiana's sole LIHTC allocating agency, and — unlike California's split between CTCAC and CDLAC, or Texas's split between TDHCA and the Bond Review Board — it is also the bond issuer on 4% deals. There is no second agency's calendar to track. That consolidation simplifies the org chart but does not touch the deadlines that matter most, because those come from the Internal Revenue Code, not from IHCDA's own Qualified Allocation Plan (QAP).

Notice what is missing from that list: a standalone, QAP-stated deadline to start construction. California's regulations set a hard 12-month construction-start clock tied to reservation, with rescission as the consequence. Nothing in Indiana's 2026-2027 QAP does the same. IHCDA's only construction-start mechanism is a scoring incentive — up to 5 points under Readiness to Proceed for committing to close financing within six months of Board approval — not a threshold requirement with a stated penalty for missing it. The forcing function that actually exists is the federal one: the 10% test at 12 months and placed-in-service at the close of the second calendar year.

That 90-business-day figure is the one genuinely verified processing-time data point this research turned up — IHCDA publishes it directly in the QAP. No published distribution of actual Indiana construction or lease-up durations exists, and this guide will not invent one.

The 10% test: Indiana runs it by contract, tied to a signature date, not the reservation date

The federal rule is unchanged by geography: basis in the project one year after the allocation must exceed 10 percent of reasonably expected total basis as of the close of the second calendar year following the allocation year (IRC Section 42(h)(1)(E)(ii)). IHCDA operationalizes that rule through the Carryover Agreement itself (Form D) rather than through a separate regulation the way California's 4 CCR Section 10328(d) does. The Agreement's own text sets the deadline as 12 months from the date the Owner and IHCDA execute that Agreement — a contract-signing date, which typically follows the November reservation date by weeks.

That gap matters for scheduling. A developer who counts 12 months from the reservation notice, rather than from the date the Carryover Agreement was actually signed, is working off the wrong anchor date — usually in the deal's favor by a few weeks, but it is the executed Agreement's date, not the Conditional Commitment's date, that controls.

The same unresolved federal question that complicates this test everywhere applies in Indiana too: 26 CFR Section 1.42-6(a)(2)(i)-(ii) still carries pre-2008 language tying the test's timing and consequence to a July 1 allocation-date split (close-of-calendar-year for allocations before July 1, six months for allocations after June 30) that the HERA-era statute's uniform 12-month rule superseded. No IRS notice reconciling the two was located. IHCDA's Form D implements the statute's 12-month rule, but neither the Agreement nor the QAP addresses the regulation's still-published consequence language.

If the test is missed, IHCDA's own escape valve is stated in the Carryover Agreement's own terms: at IHCDA's sole discretion, it may deem the allocation canceled, and Owner is separately obligated to return the credits by written notice once it determines the Development cannot be completed within the required timeframe.

IHCDA is the bond issuer too — there is no separate volume-cap agency's clock to track

On a 4% deal, applicants must agree to use IHCDA itself as bond issuer — there is no equivalent of California's CDLAC or Texas's Bond Review Board running a parallel process. That means one Determination Letter, one closing deadline, and one agency handling both the credit allocation and the bond issuance. It also means Indiana's bond-track deadlines live inside the QAP's own schedules rather than in a separate regulatory code.

A development entity's track record on this exact process is itself a scoring category: up to 4 points if the applicant's developer has been issued an 8609 on an Indiana 4% bond deal placed in service within the last 5 years, 2 points if 5–10 years.

Two federal traps set earlier in the process still detonate here, and they are identical to every other state because they come from the same regulations. Predevelopment spending before the issuer's official intent resolution cannot be reimbursed from bond proceeds, and a stale TEFRA approval forces a re-hearing at the worst point in the schedule.

Placing in service is a filing event, not a construction event

IHCDA's own Compliance Manual defines the placed-in-service date directly, citing IRS Notice 88-116: the date a building is ready and available for its assigned function, evidenced by the date the first unit is certified suitable for occupancy — for new construction, that is the certificate of occupancy date; for acquisition, the date of acquisition; for rehabilitation, the close of a 24-month period in which the rehabilitation expenditure test is met. A certificate of occupancy by itself does not produce a Form 8609.

Then the federal step every state's owners forget in the same way: the owner must certify first-year information to the IRS, and no credit is allowable for any taxable year ending before that certification is made (IRC Section 42(l)(1)). IHCDA's own process folds this in — the owner completes Part II of Form 8609 in the first taxable year the credit is claimed and sends IHCDA a copy with that year's Annual Owner Certification submission.

An error discovered later is not free to fix. A Form 8609 amendment triggered by an error in the Final Application documentation costs $1,500; an amended Carryover Agreement for a Building Identification Number or legal-description error costs the same.

Lease-up decides the credit, permanently

The three periods stack the same way they do everywhere, but Indiana's Compliance Manual states the total plainly: 10 years of credit, 15 years of compliance, and — for any allocation after 1989 — an Extended Use Period running an additional 15 years beyond that, for 30 years total unless the Extended Use Agreement specifies a later date.

IHCDA's Compliance Manual walks through the two mechanics that decide how much of the credit an execution slip actually costs, with its own worked numbers. In the initial year, occupancy is prorated monthly: a 40-unit building fully occupied only by December, after leasing 20 units in November, claims 12.5% of the year's credit — the disallowed 87.5% shifts to Year 11, the first year after the credit period ends. And under the Two-Thirds Rule, a unit not occupied by a qualified household by the end of the first credit year loses that year's credit permanently; if occupied later, it earns only two-thirds credit for the remaining years of the 15-year compliance period.

Missing a date, and the narrow ways out

Even within those two triggers, relief is capped: no more than one Exchange of Credits is available per development, ever. The request window runs from January 1 through November 1 of the year the Development was originally required to be placed in service, requires a new Form A, the application fee, and a non-refundable reservation fee of 4.0% of the annual LIHTC amount. The original carryover allocation is returned under 26 CFR Section 1.42-14 and a new one is completed — but the Development stays bound to the threshold and scoring requirements of the QAP year it was originally funded under, not the current one.

Outside those two triggers, a missed placed-in-service deadline has no QAP-provided path around it. The allocation simply fails under IRC Section 42(h)(1)(E).

A missed Form H window or a late Annual Owner Certification is not a paperwork footnote here — the certification miss doubles a live annual fee immediately and, past April 30, becomes a reportable Form 8823 event, the same instrument IHCDA uses for units that were never eligible for credit in the first place.

What the sources do not settle

Four things are genuinely open on the record reviewed, and a schedule built on this phase should treat them as inputs rather than knowns.

Indiana's QAP does not publish a standalone construction-start deadline. Where California ties construction start to a 12-month regulatory clock with rescission as the stated consequence, Indiana's only comparable mechanism is the points-based Readiness to Proceed category, which rewards (but does not require) a six-month closing commitment. Do not model a state-imposed construction-start deadline for Indiana deals — on the documents reviewed here, it does not exist.

No published distribution of actual Indiana LIHTC construction or lease-up durations was located. IHCDA's Construction Notification Form (Form P) collects anticipated and actual dates for financing closing, construction start, lease-up start, and placed in service for every development — the raw data to build a real empirical distribution likely already sits in IHCDA's own files, but nothing publicly assembled from it was found.

The 90-business-day anticipated 8609 turnaround is IHCDA's own published target, not a tracked or guaranteed performance metric. Whether IHCDA's actual average processing time meets that target is not published.

The same federal question left open nationally is left open here too: no IRS notice was located reconciling 26 CFR Section 1.42-6(a)(2)'s pre-HERA close-of-calendar-year and six-month consequence language with the statute's post-2008 uniform 12-month rule. IHCDA's Carryover Agreement implements the 12-month statutory rule but is silent on the regulation's still-published consequence text — and how a post-hoc IRS determination that the test was actually missed would interact with an already-recorded Extended Use Agreement is not addressed anywhere in the documents reviewed.