Utility Depreciation Reviews: Checking the Inputs
A depreciation review is more useful when it starts with the inputs that drive the calculation. Focus on the approved dates, classifications and valuation assumptions rather than treating a familiar total as proof of correctness.
Utility Depreciation Reviews
Separate a change in the asset population from a change in assumptions for existing assets. Both can move the expense, but they need different explanations.
Keep opening values, movements and closing values connected in the review. A closing balance alone can conceal offsetting errors or a transaction assigned to the wrong asset. Reconcile selected movements to their source documents and retain the attributes needed to explain them. Where several valuation views are used, specify which view each comparison covers.
A practical first pass
- Compare additions and retirements for the period.
- Review changed master-data fields.
- Reconcile a selected calculation to the approved policy.
Use examples to make policy questions visible, not to invent a universal accounting treatment. A replacement, repair, retirement or addition may require judgment under the utility's applicable accounting framework. Capture the physical facts and ask the responsible specialist to approve the treatment. Configuration should implement that approved conclusion rather than substitute for it.
A hypothetical example
A monthly movement may reflect new assets entering the calculation rather than a changed rate. Show those effects separately so the reviewer can identify which records need attention.
Distinguish operational completion from financial readiness. Work can be finished while invoices, material returns or supporting documents remain outstanding. Use separate status checks for those conditions rather than treating one completion flag as proof that every process is finished. The organization should define who can approve each stage and what evidence that approval requires.
Avoid the common shortcut
Do not select useful lives or rates from a generic online example. Those decisions require the applicable policy and responsible accounting review.
Connect the accounting record to the physical work without assuming that the two records answer the same question. Engineering may describe an installed component, while finance needs ownership, valuation and reporting information. Agree the handoff fields before the project reaches completion. Missing identifiers are much easier to resolve while the people who performed the work still have the relevant records.
Keep the wider process connected
Describe the work in terms that both the field team and the finance team can recognize. An order number is a useful reference, but it is not a complete explanation of what happened. Include the asset or location, the purpose of the task and the relevant work stage. This makes it easier to investigate a charge without repeatedly returning to the person who entered it.
Plan the human handoff alongside the data movement. Support teams need access, procedures, known issues and escalation contacts before the transition. Operational users need to understand what changes in their daily tasks and where to obtain help. A technically successful go-live can still be difficult if those responsibilities remain with the implementation team alone.
Distinguish creation, change and retirement of a record. The checks required for a new object may not be sufficient when an existing object changes ownership or becomes inactive. Preserve effective dates and historical relationships where the process needs them. Cleaning the current view should not make earlier transactions impossible to explain.
What to take away
Keep an input-change report and a movement explanation supported by selected asset-level checks.
Related reading
Engineering and Finance Asset Registers: A Reconciliation Plan; Partial Capital Project Completion: A Practical Handoff; Utility Asset Master Data: A Capital Project Checklist.