Most asset registers live in a spreadsheet. Someone adds this year’s purchases, recalculates depreciation, copies the total into a journal and hopes the formulas still point at the right rows. Disposals get missed, or removed without a gain or loss. The register stops agreeing with the general ledger, and the audit begins with a reconciliation nobody budgeted for.
It gets harder with several entities, a tax depreciation method that differs from the books, or assets bought through dozens of bank and card payments.
When custom beats a module or a package
The fixed asset modules in accounting and ERP systems, and standalone fixed asset packages, handle standard registers well. Use one if it covers your methods and entities.
Custom software makes sense when:
- You keep book and tax depreciation under different rules, across entities or countries.
- Assets need to link to the purchase transactions, invoices and documents behind them.
- Your tax rules pool assets by class instead of depreciating them one by one.
- The register has to tie to the ledger at every close, and you want a failed tie to block the close, not appear as a footnote.
How we would build it
The data model
- Assets: entity, class, description, cost, acquisition date, in-service date, location and the source transaction or document
- Books: for each asset, a book and a tax book (or more), each with its method, life or rate and start date
- Rate and life tables, stored by the date each rule took effect
- Events: additions, transfers between entities or locations, impairments and disposals
- Schedule lines: the depreciation computed for each asset, book and period
Depreciation as a computation
Depreciation is never typed in. It is computed from the register and the rule tables, and the journal posted to the ledger comes from that computation. Change an asset, and every later period recomputes.
Disposals
A disposal records the date and the proceeds. The system works out the carrying value at that date, the gain or loss and the entry to post. Under pooled tax regimes, proceeds come off the pool, and a pool that goes below zero is flagged to your accountant.
Checks that keep the register honest
- Dates in order: in service on or after acquisition, disposal on or after both.
- A disposal needs both a date and proceeds.
- Land carries no depreciation.
- One payment backs one asset, so an asset can’t be capitalized twice.
- Money in integer cents, never floating point.
- Closed periods are locked. A change that would move a closed period’s figures is refused.
- At close, depreciation posted in the ledger must equal the register’s computation, or the close check fails.
Proof from our own code
Lekhavo, our bookkeeping product for Indian accounting practices, runs a fixed-asset register and depreciation schedule in production. It follows Indian income-tax rules, where assets are pooled by rate class, a shape similar to pooled regimes elsewhere. The code shows how we approach the problem:
- Rates by year. Each class’s rate is stored with the financial year it took effect, from the official rate table, so a past year recomputes at its own rates.
- Part-year rules. An asset in use for less than 180 days in the year gets half the rate, as the law requires.
- Disposals surfaced. When sale proceeds exceed the pool’s value, the pool closes at zero and the excess is shown as a short-term capital gain for the accountant to treat. It is not absorbed.
- Exact arithmetic. Money is held in paise. Where an amount times a rate could overflow ordinary number precision, the calculation uses arbitrary-precision integers.
- Validation twice. Each row is checked on entry: an opening value with its year, or a cost with an acquisition date; dates in order; disposal date and amount together; no depreciation class on land. The database enforces the core rules again as constraints. A bank transaction can back only one asset, and not also an investment.
- Locked years. A register change is refused if a locked year falls at or after the earliest year it touches, since every later year moves with it.
- A close check. “Depreciation posted equals the register” is one of the checks run before a year is locked.
- An audit trail. Every register change is recorded with its actor.
Lekhavo serves CA practices, and its tax rules are Indian. For accounting firms and companies elsewhere, we would build on the same approach with your own rules.
What the first version includes
- An asset register with import from your current spreadsheet, checked row by row
- Book and tax depreciation schedules for your methods
- Disposals with gain or loss, and transfers between entities
- Journals exported or posted to your ledger
- A register-to-ledger tie-out at close, along the lines of our reconciliation software
- An audit trail and period locks
- Source code, a written spec and runbooks
How the work is run
Tembrant builds with an AI software factory: many agents work in parallel, held to fixed gates. Every change starts from a written spec. Depreciation rules are written down with your accountant first, then tested against schedules you already trust. Each change gets independent reviews, and a person signs off before it ships.
If your asset register is a spreadsheet that only one person understands, tell us what it tracks.
