Asset Control
Not a better calculator — a register that holds its own history. Financial years that lock, a year-end position fixed as a snapshot, every change attributed, and depreciation that reaches your books once.
A capability of ProcureTrail, configured by Kiren & Co as part of your professional engagement. It can be configured as part of an engagement on its own or alongside other ProcureTrail controls, depending on your organisation’s requirements. How the system fits together →
The register does not tie to the books, and reconciling it is an annual argument.
The depreciation schedule gets rebuilt from scratch every year in a spreadsheet.
Someone changed an asset’s life or cost last year. Nobody can say who, when, or from what.
Depreciation is table stakes. What follows is what makes the number defensible.
Close a year behind a readiness check, and it stays closed. Unlocking is possible and is itself recorded.
Each asset’s gross block, accumulated depreciation, net book value, life, rate and class fixed for that year — one snapshot row per asset, per year.
The snapshot carries a watermark of what has already reached your books, so re-opening or refreshing a year does not post the journal twice.
Straight line and written down value from cost, residual and either useful life or rate, with a configurable financial year start month, and componentisation where an asset has parts with different lives.
The fixed asset schedule for the notes to accounts, a movement roll-forward with export, and a portfolio health view.
Load your existing register from a workbook and get row-by-row validation against a published catalogue of rules — plus a control-totals check on opening balances.
The interesting part is not the depreciation figure. It is what happens at year end.
The note table and the movement schedule, exported.
The readiness check, the snapshot, the lock — and what happens when the year is re-opened.
A real register loaded, with the rule-by-rule findings the validator returns.
Every change to an asset is recorded with what it was before and after, and who made it.
Once a year is closed the position is a snapshot, not a re-computation that can quietly move.
The posted-to-date watermark means a re-opened year cannot send the same depreciation to your books again.
Where physical verification is also in use, each asset carries its own verification history in the same place.
Turned on per organisation. Same register, same audit trail, same login — no second system, no migration.
A calculator gives you a number. This holds the record behind it — the financial year locks, the year-end position is fixed as a snapshot, and every change to an asset is attributed with what it was before and after. The arithmetic is the easy part; the defensible history is the point.
Straight line and written down value, computed from cost, residual value and either useful life or an annual rate, with the financial year start month configurable.
It closes the year to further change. There is a readiness check before the close, a snapshot that fixes each asset’s gross block, accumulated depreciation and net book value for that year, and an unlock path that is itself recorded.
No. The snapshot records how much has already been posted, so re-opening and refreshing a year does not double-post the depreciation journal.
Yes. Registers are loaded from a workbook and validated row by row against a published catalogue of validation rules, so you see exactly what is wrong with the file rather than a single failure message. Opening balances additionally pass a control-totals check.
Depreciation classes and rates are set up for your organisation as part of onboarding, against your own asset categories. This is something we do with you rather than something you receive pre-filled.
The fixed asset schedule for the notes to accounts, a movement roll-forward with export, a portfolio health view, and per-asset schedules.
We will look at your existing file, tell you what the validator finds in it, and show you what the closed year looks like afterwards.