Section 263A Interest Capitalization

Architecture

Key specifications

What it does for you

A real-estate developer that builds designated property with borrowed money may not deduct all of the interest it pays. Under the avoided-cost method of IRC §263A(f), the interest production could have avoided -- the period rate applied to the accumulated production expenditures tied up in a project -- must be capitalized into that property's basis rather than deducted in the year paid, and the rest is deducted. The annual schedule lays every active project across a grid of calendar quarter-ends, pulls each project's interest expense by quarter, and computes that split. It is rebuilt every fiscal year, and it goes stale in ways nobody watches. Four failures hide inside it, none of which look wrong in a grid of quarters. A row stops footing: a quarter column is edited and the annual total beside it is not re-added, so the interest, capitalized and deducted columns no longer cross-foot while the schedule still looks complete. The split leaks: the interest a project incurred no longer equals its capitalized portion plus its deducted portion, so a slice of interest is neither capitalized into basis nor deducted -- it has left the schedule. A project is missing: a construction project carrying an interest balance on the entity trial balance never reaches the roster, so its interest is deducted in full and none is capitalized. And the capitalized figure is asserted rather than derived: it is typed in instead of recomputed as accumulated production expenditures times the period rate rolled by quarter, or one project is rolled at a rate the others were not, or the comparison never carries the prior year's capitalized balance forward. None of these are judgment calls. They are equalities -- a stated capitalized figure against the rate applied to the expenditures, capitalized plus deducted against the interest incurred, an annual against its quarters, an ending balance against prior plus current -- which a deterministic control settles better than a workbook inherited by whoever rebuilds the schedule this year, and the consequence of missing one stays in basis for the life of the asset.

The seeded demo runs every control over every capitalization file⁷. The CLI generates twenty-one fictional FY2029 capitalization files -- one clean baseline and one carrying each of the twenty planted defects -- then runs all nineteen controls over each. The clean file returns PASS with no flags; every defect file returns REVIEW or FAIL and names the control it tripped along with the reason that control exists.

The capitalized column is recomputed, not read back⁸. One defect file raises a project's fourth-quarter accumulated production expenditures without re-deriving the schedule beneath it. Every column still foots, the split still closes, and the annual totals still add -- but cap_rederives rebuilds that quarter's capitalized interest as the period rate applied to the new expenditure balance, finds it is not the figure stated, and fails, proving the capitalized column is derived from the expenditures rather than trusted as written.

Completeness is proved against the trial balance, not against the schedule⁹. Another defect file adds a project to the entity trial balance that was never added to the roster. Nothing inside the schedule is inconsistent -- every project on it foots, ties and re-derives -- and prj_tb_complete still fails, because the trial balance is the authoritative population and a construction project absent from the schedule has all of its interest deducted and none capitalized.

Functional block diagram

Instruction set

Benchmarks

Control characteristics

• Read-only: capitalization files are parsed and never written back, so the engine cannot introduce the break it reports.
• Integer cents throughout, compared with exact ==; there is no tolerance band on a capitalized, deducted or annual figure, and a cent off the re-derivation is reported as a break.
• An amount that should be integer cents but is not produces an AMOUNT_INVALID finding contained to the one row it was read on, rather than being coerced into the number the engine is meant to audit.
• One capitalization kernel: the controls and the generator share the arithmetic in capitalize_engine.capitalize, so a re-derived figure cannot disagree with the data that produced it.
• The rate is applied with truncating division exactly once, in the kernel, so a derived capitalized figure compares to the reported figure with exact == rather than through two rounding conventions.
• Completeness is proved in the authoritative direction: the trial balance is the population, and the roster is tested against it rather than against itself.
• Deterministic and byte-stable: same inputs produce the same findings in the same order, with no timestamps or absolute paths in any output.
• Absent evidence is never a passing control; a missing tab or quarter fails completeness rather than letting the controls that read it pass unread.

Operating limits

• The engine never posts an entry, files a return, adjusts basis, or writes to a source artifact. It reads the capitalization file and stops.¹⁴
• It reads the five tabs the annual schedule emits. It does not connect to a general ledger, a job-cost system, loan documents or a fixed-asset register.¹⁵
• It re-derives the capitalized interest at the basis-point rate the file carries and proves one rate is applied across the period; it does not decide whether that rate is the correct avoided-cost rate for the entity, whether the debt is properly traced, or whether the property is designated property at all.¹⁶
• It flags a project placed in service that is still capitalizing interest as a matter for review; it does not determine the in-service date or decide when the capitalization period ended.¹⁷
• It takes the accumulated production expenditures and the quarterly interest expense at face value: it confirms they are well-formed and that everything derived from them ties, not that the underlying cost or interest is correct. All shipped data is fictional -- the developers, the projects, the company and job numbers, the expenditures, the interest and the rate are invented, and the fiscal year is set in a fictional future.¹⁸

See it run

Integration

Distribution: public repository, MIT license.