fixed asset subledger net book value does not match the GL depreciation account at quarter-end
Fixes a fixed asset subledger net book value that does not match the GL depreciation account at quarter-end: reconcile by asset class and depreciation area, find assets posted in only one layer, and correct the depreciation run or asset transfer. Use for fixed assets close. Not for a physical asset verification count.
TL;DR
Compare like with like before hunting errors: the subledger net book value is an asset-register number, while the GL holds accumulated depreciation and cost in separate accounts, sometimes for several depreciation areas. Rebuild the expected GL figure from the register by asset class: cost less accumulated depreciation per class, for the book depreciation area only, at the same period end. The mismatch will localise to one class or one area, and then to named assets: an asset capitalised in the register whose posting went to a clearing account, a disposal processed in the GL only, or a depreciation run that posted twice or not at all for one class. Correct the asset transaction through the register so both layers move together, and rerun depreciation if the run itself was the gap.
fixed asset subledger net book value does not match the GL depreciation account at quarter-endUse this when
- Quarter-end close shows the fixed asset register net book value disagreeing with the GL asset and depreciation accounts.
- Assets were acquired, transferred between classes, or disposed of during the quarter.
- The ERP keeps multiple depreciation areas, such as book and tax, with only one posting to the GL.
Not for this skill when
- The task is counting or locating physical assets. That is asset verification, a different control.
- Only the tax depreciation area disagrees. Tax areas often do not post to the GL by design; compare the book area.
Steps
- Define the comparison precisely: register net book value by asset class for the book area at quarter-end, against GL cost and accumulated depreciation balances by class. Verify: both sides are stated on identical scope before any difference is judged
- Compute the expected GL net figure per class from the register and subtract the actual GL per class. Verify: the total mismatch decomposes into one or two asset classes
- List asset transactions in the differing class for the quarter: acquisitions, transfers, retirements and depreciation, and trace each to its GL posting. Verify: the specific assets present in one layer only are named
- Correct through the asset register: post the missing capitalisation, reverse the GL-only entry, or rerun the failed depreciation for that class. Verify: register and GL both reflect the correction from the same transaction
- Re-run the class comparison and file the reconciliation with explanations for any remaining timing items. Verify: net book value ties by class, or only documented timing items remain
Variant phrasings
fixed asset subledger net book value does not match GL depreciation
The quarter-end symptom verbatim in spirit.
asset register vs GL reconciliation by asset class depreciation area
The structured comparison phrasing.
depreciation run posted twice asset class GL difference fix
One of the frequent causes.
Compatibility: Fixed asset registers in SAP Asset Accounting, Oracle Assets, NetSuite Fixed Assets and Dynamics, with depreciation areas or books and class-level GL accounts.
Why it happens
Two systems record the same assets for different purposes: the register tracks each asset's life, while the GL carries summarised balances by class. They drift whenever an event is processed in one layer by a shortcut - a journal straight to the GL for an urgent disposal, a capitalisation parked in clearing, a depreciation run interrupted mid-class. Because summaries hide the culprits, only a class-level, transaction-by-transaction comparison exposes which asset events bypassed the other layer.
Edge cases / pitfalls
- Assets under construction often sit in a clearing account by design; agree their treatment in the rec template so they are not flagged monthly.
- Mid-quarter class transfers change both classes at once; check transfers first when two classes are out by offsetting amounts.
- Lock GL asset accounts against manual journals in the same way as other control accounts.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_473kzN56hVL7C1faTKhgcw