Spending that is not an expense yet
A capital project accumulates cost until what it builds goes live. Then the pile becomes an asset and the run starts charging it. Three piles hold 776,800.00 in flight, and the May go-live moved 640,000.00 onto the register.
◆ In flight, 31 Maythree piles, one balance.
| Project | Started | Cost in flight |
|---|---|---|
| Warehouse mezzanine | January 2026 | 412,000.00 |
| Office build-out, floor two | March 2026 | 268,500.00 |
| Fleet telematics retrofit | April 2026 | 96,300.00 |
| Construction in progress | 776,800.00 |
Each pile is invoices and internal labor coded to its project worktag, accumulating in a construction account that depreciates nothing. The mezzanine has been in flight since January, which is exactly the kind of fact this page exists to keep visible: old piles are where abandoned spending hides. Sample values are illustrative, never client data.
◆ The May go-liveone pile changed nature.
| Capitalized in May | Amount |
|---|---|
| Laptop refresh, went live 26 May | 640,000.00 |
The 640,000.00 is the roll-forward’s additions line, to the cent: the pile left this page and became the eighteen computer assets the register carries at full cost. The run starts charging them in June, a month after go-live, per the stated convention.
◆ The owned answerpiles as facts, go-live as a date.
Project cost lines land with their worktags on the same keys as everything else in this wave, so a pile is a grouping and capitalization is a dated transfer. A project still accumulating after its go-live date fails the nightly check instead of inflating an asset quietly.
- capital project
- Spending that builds an asset instead of buying an expense.
- construction in progress
- The account where project cost accumulates before go-live.
- capitalize
- Move the accumulated pile onto the register as an asset.
- go-live date
- The signed date a project becomes a depreciating asset.