Platform · financial core

A subledger, not a spreadsheet that happens to agree

Most companies below $100M keep their fixed-asset register outside the accounting system, because QuickBooks and Xero have no real subledger for it. The register usually agrees with the trial balance, and it agrees by convention rather than by construction — which is a distinction an auditor cares about and nobody else notices until they do.

Permitted

  • Adjusting entries
  • Reclassifications

Blocked

  • New subledger activity
State is enforced by the posting engine, not by convention. An agent cannot post into a closed period at any authority level.
Ties to the GL by constructionTax and book methods in parallelDisposals handled properly

What it does

Six things, specifically.

The register itself

Cost, in-service date, method, useful life, salvage, accumulated depreciation, and net book value per asset — with the class and location it belongs to.

Depreciation runs

Monthly, staged for review before posting, across straight line, declining balance, units of production, and the MACRS conventions where tax basis differs.

Book and tax in parallel

Two sets of depreciation on one asset with the deferred tax difference visible, rather than a book register and a separate spreadsheet your CPA maintains.

Disposals and transfers

Gain or loss computed and posted correctly, partial disposals handled, and transfers between locations or entities recorded rather than re-keyed as new assets.

Construction in progress

Costs accumulated against a project and capitalised on a stated in-service date, which is where the interaction with job costing usually matters.

Ties to the control account

The subledger reconciles to the GL continuously. A break surfaces the day it happens rather than during the audit.

Why the spreadsheet is a problem even when it is right

The register outside the ledger is usually accurate. Someone competent maintains it, the depreciation journal is posted monthly from it, and the numbers reconcile.

What it lacks is construction. There is no mechanism preventing the journal from being posted for a different amount than the schedule computed, no version history explaining why an asset’s life changed in 2023, and no way for anybody but its author to demonstrate that it is correct. In an audit that is a control deficiency regardless of whether the figures are right, and it typically appears in a management letter before it appears in a finding.

The register is usually correct. What it cannot do is demonstrate that it is correct to somebody who did not build it.

Book and tax is where the spreadsheet really strains

One asset with two depreciation bases — book for your statements and tax for the return — means two schedules that have to stay aligned on cost, disposals, and additions while diverging on method. Most companies maintain the book register and let their CPA keep the tax one, which works and means the deferred tax difference is only visible annually.

Holding both on one asset makes the difference continuously visible, which matters for interim reporting and for anyone modelling cash taxes. It also removes an annual reconciliation nobody enjoys.

The migration is usually easy

Bringing an asset register in is one of the more straightforward conversions, because the data is structured and low-volume — a few hundred assets rather than a few hundred thousand transactions. What takes the time is agreeing the classes, confirming the in-service dates, and reconciling accumulated depreciation to the control account, which frequently surfaces a small historical difference nobody had noticed.

We would rather find that during conversion than have your auditor find it, and we label it rather than quietly absorbing it into the opening balance.

Limits

Where this does not help.

Not an asset-tracking system

This is the accounting subledger. Barcode tagging, physical inventory counts, and maintenance scheduling belong in a maintenance or EAM system, and we integrate rather than replace.

Lease accounting is separate

ASC 842 right-of-use assets are related and different. We handle the resulting asset and liability; the lease determination and classification is a judgement we support rather than automate.

Not a tax return

We hold the tax basis and compute tax depreciation. Preparing and filing the return is your CPA’s work and we produce the schedules they need.

Questions

What people ask.

Does it handle MACRS?
Yes, including the half-year and mid-quarter conventions and bonus depreciation, held as a parallel tax basis alongside the book basis on the same asset.
What about ASC 842 leases?
We hold the right-of-use asset and lease liability and the resulting amortisation. The classification judgement is yours and your auditors’ — we support it rather than deciding it.
How hard is it to bring our register in?
Usually straightforward, because it is structured low-volume data. The time goes into agreeing classes and reconciling accumulated depreciation, which often surfaces a small historical difference.
Can we depreciate by location or department?
Yes — assets carry dimensions, so depreciation posts to the department or location that uses the asset rather than to one central account.
Does it track physical assets?
No. This is the accounting subledger. Barcoding, physical counts, and maintenance scheduling belong in an EAM system and we integrate with one.

Bring the register into the ledger.

Tell us how many assets and where the schedule lives, and we will scope what it takes.