Capital asset registers: capitalization thresholds, depreciation, and reconciliation

Reference article · 7 min read

Every agency keeps more than one list of the things it owns. Finance keeps the capital asset register that feeds the financial statements and the depreciation expense. Public works keeps an asset inventory inside the work order or enterprise asset management system, because crews need to know what is in the ground and when it was last serviced. IT keeps a hardware inventory. The warehouse keeps stock. Those lists were built for different purposes, they use different identifiers, and in most agencies they are never reconciled to each other on a fixed schedule.

Auditors test the first list. When the other lists disagree with it, the finding lands on the capital asset register even though the error usually happened somewhere else: a pump was installed and no one told finance, a vehicle went to auction and no one retired it, a project sat in construction in progress for years after the road opened. The fixes are mostly policy and process. Systems help only after someone decides what belongs where and who is obligated to tell whom.

What belongs in the register, and what belongs elsewhere

• Capital asset register. Items that meet the written capitalization policy, carried at historical cost, with class, in-service date, useful life, accumulated depreciation, funding source, location, and custodian. This record exists to support the financial statements.
• Work order or EAM system. Everything crews maintain, regardless of cost. It will legitimately contain assets below the capitalization threshold and assets that are fully depreciated but still in service. That is not an error.
• Inventory and stores. Consumables, spares, and stock. These are expensed when issued, unless a part is installed as a component of a capital project, in which case the cost follows the project.
• Controlled or sensitive property. Laptops, radios, weapons, tablets. These are tracked for stewardship, not for the balance sheet. Keep a separate controlled property list rather than lowering the capitalization threshold just to get visibility.
• Leases and subscription arrangements. Right-of-use assets and subscription-based IT arrangement assets are recognized and amortized under their own GASB standards. Keep them in distinct classes so they are not confused with owned capital.

Thresholds, useful lives, and what counts as an addition

The capitalization threshold is a policy decision, usually adopted by the governing body and applied per unit rather than per invoice. Many agencies set different thresholds by class, with a higher threshold for buildings and infrastructure than for equipment. Write down whether like items bought together are aggregated, because that single sentence resolves most disputes about bulk purchases of meters, radios, or computers.

Federally funded property is a separate question. The Uniform Guidance defines equipment using the lesser of the agency's own capitalization level or a dollar figure stated in the regulation, and that figure has been revised, so confirm the current text rather than relying on an old policy manual. Federal property standards, including a periodic physical inventory of federally funded equipment that must be reconciled to the property records, apply based on how the item was funded, not on whether the agency chose to capitalize it.

Useful lives should be set by class, documented, and revisited when experience clearly contradicts them. Distinguish repairs, which are expensed, from additions and betterments that extend life or increase capacity, which are capitalized. Consider componentizing major buildings so that a roof or an HVAC replacement can be capitalized and the old component retired instead of layering new cost on an asset that was never reduced.

Construction in progress and multi-year projects

Construction in progress accumulates cost and is not depreciated. The event that moves it out is placement in service, meaning the asset is substantially complete and available for its intended use. It is not final invoice, not retainage release, and not grant closeout. Agencies that wait for the paperwork end up with roads carrying no depreciation for years, which is exactly the pattern auditors look for.

Practical controls: reconcile construction in progress to the project ledger at least quarterly, run an aging report on balances that have not moved, and require the project manager to certify the in-service date and the split between capitalizable and expensed costs. Long linear projects can be placed in service by phase or segment. When a project replaces existing plant, retire what it replaced in the same entry; a replacement that only adds cost inflates the register permanently. Treatment of interest cost has changed under more recent GASB guidance, so confirm current requirements before capitalizing it.

Infrastructure and the unit of account

Infrastructure is reported as networks or subsystems: a street network, a water distribution system, a collection system. The choice that matters most is the unit of account. If pavement is recorded as one citywide asset, no individual resurfacing can be retired and the register drifts away from reality. Block-to-block segments, pipe runs by material and diameter, or similar units make retirements and partial replacements possible.

Agencies that use the modified approach instead of depreciating eligible infrastructure take on real obligations: an asset management system, condition assessments performed and documented at the required interval, and an estimate of the annual amount needed to preserve assets at the disclosed condition level. If the documentation lapses, the agency must revert to depreciation, which is a difficult conversion. Donated and developer-contributed infrastructure is another common gap. Tie recognition to the formal acceptance action, not to a later discovery.

The reconciliation problem

Three findings recur, and each has a structural cause.

1. Assets installed but never capitalized. No trigger exists between the operational system and finance. Cure: make project closeout and work order completion produce a capitalization notice, with a named accountable owner.
2. Disposed equipment still on the books. Surplus, auction, salvage, and totaled vehicles move through fleet or procurement without a retirement entry. Cure: one disposal form that no department can bypass, and an annual match of auction and salvage records to the register.
3. No shared identifier. Finance calls it asset 10432; the crew calls it Pump Station 4, Unit B. Cure: carry the operational asset ID as a field in the financial record and the financial asset ID as a field in the EAM record, then test the crosswalk for orphans in both directions.

A useful starting exercise is a one-time crosswalk: export the register, export the EAM and fleet lists, and sort into matched, in finance only, and in operations only. The exceptions are the work plan, and an annual physical inventory with a documented variance report is what keeps the list from drifting again.

What to require when you buy or integrate systems

• Ask how the placed-in-service event is captured, not just whether the module has a field for it.
• Require a persistent cross-system identifier and an interface that carries it in both directions, with an exception report for unmatched records.
• Ask for partial retirement and componentization support, including retiring a component when a replacement is capitalized.
• Require auditable history: who changed a cost, life, or status, and when, retained for the full audit period.
• Ask for the disposal workflow end to end, from surplus request through the retirement entry and the gain or loss.
• Specify data conversion and reconciliation as acceptance criteria, with the vendor demonstrating a tie-out of converted balances.

Standards and federal requirements change. Confirm current thresholds, deadlines, and reporting requirements with the official source, your external auditor, or counsel before setting policy.

HQT works with state and local agencies on systems engineering and integration between financial, asset management, and operational systems.

Frequently asked questions