Asset Control
Some parts of an asset wear out long before the asset does. Deciding which of them are significant enough to depreciate separately is a judgement, and it has to be documented. We make that judgement with you and carry it through to the schedule, the entries and the file.
Componentisation separates significant parts of a fixed asset that have different useful lives, such as a lift within a building or a lining within a furnace. The work involves deciding which parts are significant, documenting that judgement, and carrying the resulting structure through the fixed-asset schedule.
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 carries one line reading “Factory Building”, and nobody can say what is inside it.
Someone asked which parts are significant, and there was no threshold to point to and no note explaining one.
Useful lives were revised last year. Nobody can now say on what basis, or who agreed it.
Componentisation is rarely something a finance team goes looking for. It usually arrives with one of these.
A query about significant parts, or about how the depreciation charge on a large composite asset was arrived at. The question is usually specific, and it usually has a date on it.
The schedule has to show opening balances, additions, disposals and the charge for the year, and it has to agree with the ledger. A register built from composite lines makes that hard to produce and harder to defend.
A new plant, building or wing is commissioned and lands in the register as a single figure. Establishing the component structure at this point is straightforward. Reconstructing it from invoices years later is not.
A technical assessment or a change in use means an asset will not last as long as assumed. The revision is applied going forward, and the reason for it belongs on the record rather than in an email.
A unit is loss-making, a line is idle, a branch has closed. Where an impairment review follows, the recoverable amount is yours and ours to determine; the allocation across the assets and the resulting entries are what the system carries.
The judgement in this work is the work. It is not something a system can be asked to supply.
We agree a significance threshold with you, record the basis for it, and apply it consistently across the classes in scope. The threshold is a position your organisation has taken, and it should read that way when someone asks about it a year later.
Which parts are separated, how the carrying amount is apportioned between them, and where a part stops being a component and becomes maintenance. We do this class by class, against how your assets are actually used.
Where a technical assessment of remaining life is needed it comes from your engineer or a valuer. We review it, decide what it supports, and set out the effect of the change and the disclosure that goes with it.
Every split and every valuation event is reviewed on a preview that shows the full allocation before anything is posted. Nothing reaches the register because it was computed. It reaches the register because it was reviewed and approved.
The note disclosure, the supporting schedules, and a file that answers the question a reviewer will actually ask, which is not what the number is but how it was arrived at and by whom.
ProcureTrail is the system this firm works in. It carries the record and the mechanics. It does not form a view.
A component split is created, submitted, approved and posted through the same approval routing as the rest of the organisation’s documents, and it can be reversed. It is a transaction with a history, not an overwrite of the register.
A monthly charge per asset, written once and immutably, with a movement roll-forward that reconciles to the general ledger accounts the entries were posted to. Both are exportable.
The original basis of an asset is frozen before any revision touches it, so the position before and after a change are both recoverable, together with who approved the change and when.
The significance threshold, the useful lives, the residual values, the boundaries of a cash-generating unit and any recoverable amount are inputs the firm and the organisation supply. The system applies them, shows its working, and flags what falls below the threshold you set. It never overrides that judgement and never substitutes for it.
Four working outputs. Each is produced by the system and reviewed by the firm before it goes anywhere.
Each parent asset with its components, the apportioned carrying amounts, the life applied to each, and the note where a component sits below the threshold you set.
Opening, movements and closing per class, with the totals reconciled against the ledger accounts the entries were actually posted to.
For a revaluation or an impairment, the full allocation across the assets shown before approval, so the effect on each asset is visible while it can still be changed.
The accounting entries the work produces, including the ones that belong in your own legacy ledgers rather than in the register.
Your existing register as a workbook, the cost documentation behind the classes in scope, and access to the people who know how the assets are used.
Set the threshold, design the component structure, determine the lives, review the allocation, and prepare the disclosure and the file.
The judgements remain the organisation’s. We form them with you and record them; you adopt them.
The subledger cannot be switched on until every completed financial year is closed and locked. For most organisations that means bringing the register in and closing the prior years is the first phase, and we scope it as one.
A common and reasonable objection to any system that touches accounting is that it should not be writing to the ledgers. It does not have to.
ProcureTrail can be configured so that it raises no entry in your books at all. In that mode every posting is suppressed and the system instead renders the exact entries it would otherwise have raised, together with a reconciliation against your general ledger. Your finance team passes them. The engagement is delivered either way; what changes is who makes the entry.
Where an organisation does run on TallyPrime, the entries can be posted through a governed queue instead. That is a configuration decision taken at the start of the engagement, and it can be changed. See how the system fits together.
Configured per organisation. Same register, same trail, same login — no second system.
It is the separate recognition and depreciation of the significant parts of an asset that have different useful lives. A building whose lift, air-conditioning plant and electrical fit-out will each be replaced on their own cycle is one asset in the register and several components in substance. Componentisation makes that structure explicit so each part runs on its own life.
That is a judgement about materiality, and it is the reason this is an engagement rather than a data-entry exercise. We set a threshold with you, record the basis for it, and apply it consistently across the classes in scope. The system holds the threshold you set and flags a component that falls below it, but it never blocks a split and never decides the question for you.
No. The register and the component structure are held in ProcureTrail, the system this firm works in. Your books stay where they are. Where an organisation runs on TallyPrime the entries can be posted through a governed queue, and where it does not, the entries are produced for your own finance team to pass.
Yes. The system can be set so that it never writes to your ledgers at all. In that mode it suppresses every posting and instead renders the exact entries it would otherwise have raised, alongside a reconciliation against your general ledger. Your finance team passes them. Nothing reaches your books except through a person who chose to put it there.
Your existing fixed asset register as a workbook, the supporting cost documentation for the classes in scope, and access to whoever can speak to how the assets are actually used and maintained. Where a technical assessment of remaining life is needed, that comes from your engineer or a valuer, and we review it rather than produce it.
Every completed financial year has to be closed and locked first. That is deliberate: a subledger that can be run over a year somebody may still reopen is not a record anybody can rely on. For most organisations this means the engagement begins with bringing the existing register in and closing the prior years, and we scope that as its own phase rather than discovering it later.
Send us the file. We will tell you which classes are worth componentising, what the threshold conversation looks like for your assets, and what the first phase would involve.