Methodology
Methodology
The Cloudapitools method for fixed asset register reviews: scoping, sampling, site walks, reconciliation, and exception reporting.
A register-first sequence
Every engagement follows the same backbone so your finance team knows what evidence we will ask for and when site time is required.
1. Scope against the close
We lock the cut-off date, map asset classes to ledger controls, and list locations. High-risk classes — recently relocated offices, ageing plant, projects with mixed capital and expense spend — receive heavier sampling.
2. Evidence request
A short list covers register exports, addition and disposal reports, selected invoices and POs, site maps, and access contacts. Incomplete tagging is treated as a finding, not a reason to skip the floor.
3. Desk testing
Cost samples are vouched to invoices and contracts. Capitalisation judgements are challenged where repairs, reimbursements, or software licences sit on the border. Useful lives are compared with replacement patterns where data exists.
4. Site walks
Existence testing matches tags and serials to the register. Ghost assets, unrecorded floor assets, and location mismatches are logged with enough detail for your controller to approve write-offs or transfers.
5. Reconcile and report
We bridge the adjusted register to control accounts, deliver an exception schedule, and walk the draft with your finance lead before the pack is marked final.
What “done” looks like
You leave with a register your auditors can sample from, a clear list of book adjustments, and notes on process gaps — tagging discipline, disposal notifications, capex coding — that caused the drift.
Engage us
Browse engagements or request a scoping call with your asset count and deadline.