What the company owns, on one page

A register is four columns that must agree. This one carries 379 assets across four classes: 11,530,000.00 of cost, 4,741,500.00 charged so far, 6,788,500.00 remaining, and every row is one honest subtraction.

RuleKeep one register: every asset with its cost, accumulated depreciation, and net book value, each row subtracting exactly, reconciled to the ledger monthly.

Neverlet the register live in a spreadsheet beside the asset module. Two asset lists diverge the month someone edits one of them.

The register is a subtraction done 379 times. Its bottom line is the balance the auditor tests first.

◆ The register, 31 Mayfour classes, every row subtracting.

Class	Assets	Cost	Depreciation to date	Net book value
Computers	230	3,340,000.00	1,950,000.00	1,390,000.00
Office equipment	96	1,440,000.00	504,000.00	936,000.00
Leasehold improvements	12	5,040,000.00	1,860,000.00	3,180,000.00
Vehicles	41	1,710,000.00	427,500.00	1,282,500.00
The register	379	11,530,000.00	4,741,500.00	6,788,500.00

The cost column is the roll-forward’s closing; the depreciation column grew by the run’s 187,500.00 this month; the eighteen computers added in May sit at full cost with nothing charged yet. Every row is cost minus depreciation to date, no exceptions. Sample values are illustrative, never client data.

◆ Why registers driftthe spreadsheet copy ages badly.

Most registers start in the asset module and end in a spreadsheet, because reporting wanted a column the module would not show. The copy then ages: a disposal missed here, an addition typed twice there. An owned register is the module’s own rows landed, with the extra columns computed instead of maintained.

◆ The owned answerone row per asset per month.

Assets land monthly on the module star, one row per asset per month, so the register is the latest month filtered, any earlier month is kept, and the bottom line pins nightly to the as-of store.

Use case

Problem

The asset register lives in a spreadsheet that drifted from the module years ago, ghost assets keep depreciating, and the year-end fixed asset audit becomes archaeology.

What we build

The register as landed monthly asset rows: four columns that subtract exactly, totals tied to the roll-forward and the ledger, history kept.

What you get

An asset book the auditor reconciles at a glance, a register that cannot disagree with the module it came from, and every past month one filter away.

Does your register still match your asset module?

We build the landed register that cannot drift from it.

Talk to us

Terms on this page

fixed asset: A thing owned and used, not sold; charged to expense over a life.
depreciation to date: The cost already charged since the asset went into service.
net book value: Cost minus depreciation to date; what remains on the book.
class: Assets sharing a life and a rule: computers, vehicles, improvements.