WalkthroughBy Khaled Hawari

Rebuilding a Fixed Asset Register From the Ledger

Plenty of companies this size have a depreciation entry and no register behind it, which works until somebody asks what the assets are.

The tell is a depreciation journal that has been the same amount every month for several years. Nobody chose that amount recently. It was calculated once, by someone who has left, from a schedule that either lives at the accountant’s office or does not live anywhere, and it has been posted ever since by a recurring entry that nobody reviews because it always agrees to itself.

That arrangement is stable and it is fine right up to the moment somebody asks a question it cannot answer. What are the assets. Which of them are still here. What did you dispose of last year. Which ones are financed and which are pledged. A lender asks the last one, an insurer asks a version of the second, and whoever reports on your statements asks all four.

The good news is the one that companies in this position never believe: the register is reconstructable, and the reconstruction is a project with an end date rather than a condition you live with. The ledger holds the additions. The purchase records hold the detail. The building holds the assets. All three exist; nobody has ever put them beside each other.

What follows is that rebuild. The figures used are illustrative and are not a client’s. All amounts are Canadian dollars.

Scope it before you start, or it will not finish

A rebuild without a boundary becomes an archaeology project. Three decisions, taken in an hour, before anybody opens a ledger.

Pick the earliest reliable point. Almost always the opening balance sheet of a year that has been reported on, because that balance was agreed by somebody outside the company. Everything before it is accepted as an opening block rather than reconstructed item by item. A company that insists on tracing back eleven years will still be tracing in the spring.

Agree what you are going to chase and what you are not. Not a dollar figure in this piece, because the level is a policy question and it belongs with the company and its accountant. What matters is that the line is set in advance and written down, so that the person doing the work is not deciding item by item whether a purchase is worth an hour of searching.

Write the exclusion list. Assets held under a financing or lease arrangement, assets belonging to a related entity but sitting in your building, tooling held at a supplier, anything fully written down but still in use. Each of those is a real case and each needs a decision about whether it belongs in this register, in a different one, or in a note. Deciding now is a paragraph. Deciding in week three is a rework.

The rebuild is also a natural companion to a chart of accounts rebuild, and if both are on the list, do the chart first. A register keyed to account codes you are about to replace has to be re-keyed on cutover.

Step one: take what already exists, because something usually does

The step everybody skips. Before reconstructing anything, ask your accountant for the capital asset working papers from the last engagement they performed.

In most cases those papers contain a continuity schedule: opening cost, additions, disposals, closing cost, and the same four lines for accumulated depreciation, by class. Frequently they also contain an additions listing for the year with descriptions. That is not a register, because it has no individual assets in it and no locations and no serial numbers, but it is a skeleton with agreed totals, and starting from agreed totals is worth several days.

Ask separately whether they maintain a depreciation schedule for tax purposes. If they do, that schedule is a useful cross-check on what was capitalised and when. It is not the register and it should never be adopted as one. It is prepared on a different basis for a different purpose, it groups assets in ways your operations would not recognise, and it will not tell you which machine is in which building.

Step two: pull the ledger, by year

For every year from your reliable point forward, extract the transaction detail in every capital asset account, plus the accumulated depreciation accounts.

Then remove the noise. The recurring depreciation entry, any year end reclassifications, and any journal that moved a balance between classes. What remains should be additions and disposals, and the additions are your starting list.

Three things routinely sit outside those accounts and have to be brought in.

Where a missing addition hides How to find it Why it happened
In repairs and maintenance, or a similar expense account Sort that account by amount, descending, for each year, and read the top of the list Whoever coded it did not know a purchase was part of a project, or there was no policy to apply
In a supplier’s invoice that was part goods and part installation, coded entirely one way Read the invoices for the largest suppliers in the period The split takes a decision and nobody made one
In a financing or lease arrangement that never touched the purchase accounts The debt register, the bank debits, and the lease register The asset arrived without an invoice attached to it

The third row is the one that produces the most surprise. A company can acquire a substantial piece of equipment without a single transaction ever passing through a capital asset account, because the only ledger entries are monthly payments.

Step three: match each addition to a document

For every addition on the list, find the invoice. That is the standard, and where the invoice exists, this step is dull and fast.

Where it does not, work down this ladder and record which rung you used, because the person who reads the register later needs to know how good the evidence is.

  1. The supplier’s invoice.
  2. The purchase order or the signed quotation.
  3. A statement line from the bank or the corporate card, matched on amount and date.
  4. A copy requested from the supplier, which is often available for a surprisingly long time and is almost never asked for.
  5. The finance or lease agreement, where the asset was acquired that way.
  6. The asset itself: the serial plate, the model number, and a dated photograph of both.
  7. The insurance schedule, which frequently lists equipment by description and value and is the most overlooked document in this entire exercise.

Rung seven is worth a paragraph on its own. Your insurer holds a list of what you told them you own, updated at each renewal, and it is often more complete than anything in the accounting records because somebody had a financial incentive to keep it complete. It will also disagree with your register, and every disagreement is informative in one direction or the other.

Anything that reaches rung six or seven goes into the register with its evidence rung noted. An asset supported only by its own serial plate is still a real asset and belongs in the register. It just carries a weaker record, and pretending otherwise by writing “invoice” in the reference column is how a rebuild loses its credibility in one conversation.

Step four: go and look at them

The register now claims a set of assets exist. Walk the building and confirm it, then walk it in the other direction and see what is there that the register does not claim.

Both directions are necessary and most companies only do the first. Register to floor finds assets that are gone. Floor to register finds assets that were never recorded, which is the half that produces the more uncomfortable conversations, because an unrecorded asset usually arrived through a channel nobody was watching. The count method, the sheets and the evidence to keep are set out in counting the assets.

Two practical notes for a rebuild specifically. Tag as you go, because you are already standing in front of every asset and you will not be again this year. And take the serial number even when you think you have it, because the register’s version came from an invoice and the plate is the asset.

Step five: the disposals, which is where every register is wrong

Additions get recorded because they involve paying money and somebody wants the expense. Disposals involve no payment and nobody chases them, so an old register almost always carries assets that left the building years ago.

Search for them rather than waiting for the count to surface them.

Signal Where to look
A trade-in on a purchase invoice The invoices you have just gathered in step three. A trade-in line is a disposal that was never recorded as one.
An insurance claim The claims history. A written-off vehicle or a destroyed machine is a disposal.
Scrap or recycling receipts Accounts payable, usually under a waste or metals supplier
A sale of equipment Other income, or a credit sitting in an odd account, or a deposit in the bank with no invoice behind it
An asset at a closed location Property files and lease terminations. Assets at a site the company has left are frequently still on the books.
An employee departure Laptops, phones, tools and vehicles that went with someone and were never returned

Every disposal you find has two consequences: the cost comes out of the register, and something has to happen to the accumulated depreciation and any resulting gain or loss. The second of those is not yours to decide when the disposal happened in a period that has already been reported on. Assemble the facts, state the dates, and send it.

Step six: reconcile to the ledger, and expect a difference

The proof that ends the project. The rebuilt register’s total cost against the ledger control account, at a date.

Cost
Rebuilt register, assets traced and confirmed 1,284,600
Ledger control accounts 1,311,900
Difference 27,300

A rebuild that ties to the cent on the first attempt has usually been forced, and the forcing is normally a plug line called “assets per ledger not identified”. The difference is not a failure of the rebuild. It is the output of the rebuild, and the work is to explain it rather than to remove it.

Explanation of the difference Cost How it was found
Two items disposed of in a prior year and never removed 18,400 The floor to register pass, plus a trade-in line on an invoice
One addition capitalised twice, from a supplier statement and its invoice 6,200 A duplicate scan on supplier, amount and date across all years
Freight and installation charges posted to the control account with no asset named against them 2,700 Ledger detail, transactions with no matching addition
Total explained 27,300

Now the register and the ledger disagree by nothing that is unexplained, which is a completely different position from agreeing by accident.

The accumulated depreciation side is deliberately not reconstructed here. You cannot rebuild it independently without knowing the basis that was applied to each class in each year, and that basis is not a fact sitting in your ledger. It is the second half of this project and it belongs to somebody else.

Step seven: hand the second half over, properly

Four things go to the company’s accountant, together, as a single package with a single covering question.

The rebuilt register with an evidence rung against every line. The explained difference from step six. The disposals found, with dates and any proceeds. And the assets found on the floor that were never capitalised, with their invoices where they exist.

The questions that come back to you are theirs to answer, and this piece is deliberately not going to answer any of them:

  • What rate or basis applies to each class, and has it changed over the period covered.
  • How to treat the two disposals that belong to a period already reported on.
  • Whether the duplicate capitalisation needs correcting in a prior period or currently.
  • What the capitalisation policy should be going forward, which then becomes the input to a capitalise or expense matrix.
  • Whether any class needs revisiting in light of what the count found still in use.

Depreciation rates, useful lives and the treatment of prior period corrections are determinations under the framework your statements are prepared on. A finance operations function that supplies them is guessing with a straight face, and the guess is invisible until an outside reader tests it. Supply the facts, in a form that makes the determination easy, and let the determination be made by the person whose name goes on the statements.

The register you end up with

Once the rates come back, the register becomes a live document. These are the columns that earn their place. Anything beyond them is usually a column somebody wanted once and nobody has updated since.

Field Why it is there
Asset number and tag The link between the ledger and the physical thing
Description, make, model, serial number Identification that survives the person who bought it
Class Drives the depreciation basis and the statement presentation
Location, and the department or cost centre Makes the count possible, and makes an insurance schedule producible
Acquisition date and in-service date Not the same date, and the second one is the one that matters
Cost, split between purchase, freight and installation So a later question about what was included has an answer
Supplier and invoice reference, plus the evidence rung Honesty about how good the record is
Funding: cash, financed, leased, or acquired with the business Lenders and insurers both ask, and covenant definitions frequently turn on it
Whether it is pledged as security, and to whom The question nobody can answer on the day it is asked
Disposal date, method and proceeds The field that stops the register drifting again
Accumulated depreciation and net book value Populated from the basis the accountant confirms, never invented locally

The pledge column is the one worth insisting on. When a lender asks what secures their facility, or a second lender asks what is already encumbered, the answer has to come from somewhere, and in most companies at this size it comes from an owner’s recollection of an agreement signed years ago.

Keeping it from happening again

The rebuild is worthless if the register goes stale, and it goes stale in one specific way: additions get added because finance sees the invoice, and disposals never get removed because finance sees nothing at all.

So the maintenance rule is a disposal rule, not an addition rule. Nothing leaves the building without a line. A one line form, or an email to a single address, naming the asset, the date, where it went and what was received for it. Attach it to whatever process already exists for equipment leaving, because there always is one, even if it is informal.

Where the register lives is worth deciding rather than defaulting. A spreadsheet is workable and a module inside the ledger is better, because it ties to the control account without anybody retyping anything, and choosing between them is a finance systems question rather than an accounting one.

Then three habits in the monthly close: the register ties to the control account every month rather than every year, additions are matched to their invoices in the month they are posted, and anything sitting in a purchase or repairs account above the agreed line gets a second look before the period is locked. None of the three takes long once the register exists. All three are impossible until it does.

What we do not do

We do not set depreciation rates or useful lives, and we do not adopt the ones on a tax schedule as though they were the company’s accounting policy. Those are determinations under the reporting framework and they go to the accountant who reports on the statements.

We do not force a rebuilt register to tie to the ledger with a plug line. An unexplained difference is documented as unexplained, in the file, with what was tried.

We do not decide the treatment of a disposal that happened in a period somebody has already reported on.

And we do not perform audits, reviews or compilations. The rebuild exists so the company holds a register it can stand behind, and so the questions above arrive at the accountant as a package rather than as a discovery.

The engagement behind this document: Taking Over a Close That Is Failing.

MoreOther working documents

If this keeps failing in the same place.

A document that has to be re-explained every period is a process problem rather than a documentation problem. That is the point at which handing the function over is cheaper than fixing it again.