Free tool
Check your fixed asset register for free, right now.
Drop in a CSV export. See duplicate asset codes, missing location or useful life, and assets with a negative or impossible net book value — the structural problems that actually cause CARO findings.
Drop your fixed asset register CSV here, or choose a file.
Needs an asset code column; location, useful life, cost and accumulated depreciation improve the check.
What this does and doesn't do
- Your file is read entirely in your browser and never uploaded anywhere.
- It checks the register's own internal consistency only — it doesn't physically verify that an asset exists, or test additions and disposals against source documents.
How to use this
Export your fixed asset register as CSV
Needs an asset code column; location, useful life, cost and accumulated depreciation make the check more thorough.
Drop it in above
The tool matches common header variations automatically.
Start with duplicate codes
These usually mean the same physical asset was entered twice — worth resolving before anything else.
Treat missing fields as a data-cleanup list
Not a finding by itself — a prompt to fill in what the register should have had from the start.
This free tool, and where it stops
This free tool checks
- Duplicate asset codes
- Missing location or useful life
- Negative or fully-depreciated net book values
A full engagement in Lekhya also checks
- Physical verification against a sample
- Testing additions and disposals against source documents
- Componentization checks where useful lives genuinely differ within one asset
- CARO clause 3(i)/(ii) response built directly from the evidence
One run, one file, four or five rules — versus every procedure a real engagement needs, run continuously against the full population, with every exception linked to its source document.