Your Fixed Asset Register Only Gets Checked One Way

Floor to book means starting with the equipment a company actually has on the ground and checking whether it made it onto the books, the reverse of the annual count most companies run, which starts from the list and confirms each item on it is still there. One direction is common. The other almost never happens.

A fixed asset register is a company’s internal list of the equipment and property it owns, showing what should exist and where. Once a year, most companies check that list against reality by walking the floor with a printout and confirming what’s still there. That check has a name in the auditing world, existence testing, and it only covers half the job. It tells you whether what’s on the list is real. It cannot tell you what never made the list at all.

Somewhere between 10 and 30 percent of the average company’s fixed asset register no longer matches what’s actually on the floor, and up to 65 percent of the records in that register carry some kind of error, according to Kroll Advisory’s review of more than 8,000 engagements a year across 36 countries. Controllers and fixed asset managers live with a version of this gap constantly, and the usual response is to treat the annual count as the fix. It isn’t, not by itself. The annual count starts from the register and walks the floor to confirm it, the direction auditors call existence, and it’s the only direction almost anyone runs. Almost nobody starts on the floor and asks whether everything sitting there actually made it onto the register, the direction auditors call completeness. That direction is harder to run for a specific reason: there’s no list to walk from. You cannot find what was never written down by sampling what was.

What Is Floor to Book?

Floor to book is the practice of starting with the physical assets a company actually has, walking the floor first, and checking whether each one is properly reflected in the register. It’s the mirror image of book to floor, which starts with the register and confirms each listed item still physically exists, still sits where it says, and is still worth what it says. Auditing standards have kept these as two separate assertions for decades, not out of habit but because they catch opposite kinds of mistakes. PCAOB Auditing Standard 1105, paragraph 11, defines the existence assertion as confirming that what’s recorded actually exists, and the completeness assertion as confirming that everything that should be recorded is recorded. One tests for a list that overstates reality, the classic ghost asset. The other tests for a list that understates it, an asset the company has and doesn’t know it has on paper. A single procedure can’t do both, because each one has to start from a different place, one from the list, one from the floor.

Picture a warehouse that swaps out an aging forklift for a replacement. Book to floor asks a simple question: is the old forklift still on this list, still where it says, still worth what it says? That’s the check almost every annual count runs, and it’s a real check worth running. Floor to book asks a different question about the same event: does the new forklift, sitting right there on the floor doing the job, appear on the register at all? If nobody entered it, the answer is no, and a book-to-floor count would never have caught that, because a book-to-floor count never looks past what’s already written down. It walks the list, not the floor. The new forklift simply isn’t part of the walk.

Why Floor to Book Almost Never Happens

Four things combine to leave the completeness direction unrun almost everywhere:

1. An annual count starts from a list, so it can only check what’s already on the list. Walking the floor with a printout in hand tells you whether each printed line is still accurate. It has nothing to say about anything the printout never had, because the printout is where the walk begins and ends.
2. Adding something to the register has never been anyone’s single, assigned job the way removing something is. A retirement or a write-off flows through a defined process with a form behind it. Nothing forces the same discipline when equipment shows up new, gets swapped in as a replacement, or moves in from another site. There’s often no form for "this exists now and nobody entered it."
3. A physical inventory feature inside an ERP reconciles whatever evidence you feed it; it doesn’t go out and gather that evidence itself. Oracle’s own guidance for its Assets module says a company must first take physical inventory of its assets, manually confirming they exist as recorded and sit where recorded, before the system can reconcile that count against the ledger. SAP documents a similar process, ordered by a director and carried out by a commission that posts differences back into the record. In both cases the ERP is the second step. Somebody still has to walk the floor first.
4. Component swaps are routine and rarely trigger a paperwork event on their own. Under IAS 16, replacing a component of a larger asset is supposed to retire the old component and add the new one to the record as two separate entries. In practice, the retirement tends to get logged because someone is disposing of the old part, and the addition tends to get skipped because nobody treats installing the new part as a bookkeeping event.

Book to Floor vs. Floor to Book

The Real Cost of Only Checking One Direction

• A register only ever checked one way drifts wider every year, quietly. Every uncaught addition sits there unrecorded until some unrelated event, a move, an audit, a sale of the facility, forces someone to notice, if one ever does.
• Depreciation, insurance, and tax figures all inherit whatever the register says, including everything it’s missing. An asset that never made it onto the books can’t be depreciated correctly, can’t be insured at anything close to its right value, and can’t be defended in an audit, because on paper it doesn’t exist to defend.
• Two regulators that can’t tolerate a one-directional gap have already written the two-way check into law. A company holding equipment bought with federal grant funds must physically inventory that equipment and reconcile the results against the property records at least once every two years, under the federal Uniform Guidance. A government contractor holding federal property faces a standing obligation to periodically perform, record, and disclose physical inventory results, with a final inventory required when the contract ends, under the Federal Acquisition Regulation. Neither rule applies to a typical warehouse, distribution center, or cold storage operator. Both exist because a regulator concluded that checking only one direction wasn’t good enough for property it cared about.
• No credible benchmark puts a dollar figure on running one direction instead of both. The honest claim isn’t that floor to book is the cheaper option. It’s that book to floor, run alone, was never built to find what it’s structurally incapable of seeing.

"For years, there has been a misconception in the industry that traditional accounting systems like an ERP’s fixed asset register deliver an adequate basis from which to determine fixed asset valuations and depreciation schedules. This has unfortunately resulted in all sorts of downstream accounting, reporting, and budgeting issues for businesses, including the problematic existence of ghost assets. SoloTruth solves this problem."

Tim Harris, CEO and Co-Founder, SoloTruth

Who Is Most Affected?

• Controllers and fixed asset managers at manufacturers and logistics companies running equipment across multiple sites, where swaps, additions, and relocations happen constantly and a completeness gap compounds fastest.
• CFOs overseeing depreciation schedules and audit prep, who inherit whatever gap exists between the floor and the book at exactly the moment it’s most expensive to discover, during the audit itself.
• Internal and external auditors performing PP&E testing, who can run existence procedures thoroughly and still miss a completeness gap, because nothing about testing the list surfaces what the list never had.
• Companies running composite or group depreciation (an accounting method that tracks a whole group of similar assets at one blended rate rather than tracking each one individually), who are not exempt from this problem just because an unrecorded addition or retirement can net to something close to zero on the balance sheet. The asset itself is still missing from the register, and that gap follows insurance and tax independent of whatever the depreciation entry shows.

What to Look For in a Fixed Asset Verification Solution

Not every approach to asset verification runs in both directions. When evaluating options, look for six capabilities:

1. Verification that runs floor to book, not just book to floor. The solution should be built to start from what’s physically present and check it against the register, not only walk a pre-existing list.
2. Continuous evidence capture instead of a once-a-year event. A newly added or swapped asset should surface close to when it actually shows up, not at the next scheduled count.
3. Multi-source evidence, combining physical inspection, location data, photos, and document extraction, so a single missed data point doesn’t hide which direction an error runs in.
4. Direct reconciliation into the ERP and subledger, so a floor-to-book finding updates the systems that depend on it without a manual handoff that only happens annually.
5. Human-in-the-loop routing at the point a new or unrecorded asset is found, so it reaches the people who need to know, not just a log entry nobody reviews.
6. A documented evidence chain for additions, not only retirements, so a newly entered asset can be defended with the same rigor as one that’s been written off.

What Good Looks Like

1. The floor gets walked first, not just the list, on a standing basis rather than once a year.
2. Every new or swapped asset triggers an entry, the same discipline a retirement already gets today.
3. Depreciation, insurance, and tax processes treat floor-to-book findings as a routine input, not something discovered for the first time during an audit.
4. Composite or group depreciation is tracked as an accounting choice, separate from whether the physical asset is actually on the register, so a convention that nets out on the balance sheet doesn’t quietly stand in for verifying the asset itself exists on the books.
5. Both directions run on the same standing cadence, not concentrated into one count a year that only ever manages to run one of them.

Common Misconceptions About Floor to Book

Misconception: The annual physical count already checks completeness.

Reality: It checks existence, confirming that what’s listed is still there. It starts from the list, which means it structurally cannot find anything that was never on the list to begin with. Completeness requires starting from the floor instead, a different walk with a different starting point.

Misconception: The ERP’s physical inventory feature already handles this.

Reality: Oracle’s and SAP’s own documentation describes that feature as reconciling against physical evidence a person supplies, not generating that evidence on its own. Someone still has to walk the floor and gather what’s there before the ERP can do anything with it.

Misconception: Composite depreciation nets an unrecorded asset out, so it doesn’t really matter.

Reality: For a non-regulated company, the accounting convention can absorb much of the balance-sheet consequence of an unrecorded addition or retirement. That doesn’t put the asset back on the register. The gap still affects what’s disclosed to an auditor, what’s covered by insurance, and what a tax filing reports, independent of whatever the depreciation entry shows.

Frequently Asked Questions

What is floor to book?

Floor to book is the practice of starting with the assets a company physically has and checking whether each one is properly reflected in the fixed asset register, the reverse of starting with the register and confirming each listed item still exists.

What’s the difference between the existence and completeness assertions in an audit?

Existence tests whether what’s recorded actually exists, catching overstatement. Completeness tests whether everything that should be recorded is recorded, catching understatement. Auditing standards keep them separate because one procedure can’t test both directions at once.

Why doesn’t the annual physical count already find what’s missing from the register?

Because it starts from the register and walks the floor to confirm each listed item, the existence direction. It never asks whether something on the floor that isn’t on the list should be there, because it never looks past the list in the first place.

Does my ERP’s physical inventory feature already handle this?

Not on its own. Oracle and SAP both document a physical inventory process inside their asset modules, but both describe it as reconciling against evidence a person gathers first. The ERP reconciles what it’s given. It doesn’t go out and look.

Does composite or group depreciation protect a company from an unrecorded asset?

Not fully. It can absorb much of the balance-sheet consequence for a non-regulated company, but the underlying asset is still missing from the register, which still affects insurance, tax exposure, and audit defensibility on its own.

Are there regulations that require checking both directions?

Some do, for specific situations. Federal grant equipment must be physically inventoried and reconciled against the records at least once every two years. Government contractors holding federal property face a similar standing obligation. Neither applies to a typical commercial operation, but both illustrate what a regulator requires when one direction isn’t enough.

What is asset relationship management (ARM)?

Asset relationship management is a category of software that continuously verifies the existence, location, and condition of physical assets, in both directions, and reconciles that evidence with the systems, ERP, depreciation, tax, and insurance, that depend on it.

The Annual Count Was Only Ever Checking One Direction

A fixed asset register that’s only ever checked book to floor isn’t complete, no matter how carefully that one direction is run. It’s missing whatever showed up, got swapped in, or moved in from somewhere else and never made it onto the list, because nothing about walking the list was ever going to find that.

This is the gap SoloTruth Asset Relationship Management (ARM) was built to close. ARM verifies physical assets continuously in both directions, floor to book and book to floor, and reconciles that evidence with the systems that depend on it, so a new or unrecorded asset reaches depreciation, insurance, and tax processes as it’s found, not a year later during an audit.

Book a 30-minute strategy call at calendly.com/tim-harris-solotruth/30min to see what floor to book finds that your last count didn’t.

Last Updated: August 2026