The fixed-asset register carries cost, categories, in-service dates and accumulated depreciation — all of which must land exactly so depreciation continues correctly. This guide covers migrating assets to Oracle Fusion Assets via the Mass Additions FBDI and reconciling cost and accumulated depreciation.
Assets migration is about preserving net book value: load original cost, the depreciation reserve (accumulated depreciation) and the right category/method so Fusion continues depreciation from the correct point.
You map legacy asset categories to Fusion asset categories (which drive default depreciation rules), and load the register via the Mass Additions / asset FBDI with cost, units, in-service date, life/method and accumulated depreciation.
The reconciliation is asset cost and accumulated depreciation by category and corporate book — and the resulting net book value must tie to the GL asset and accumulated-depreciation accounts you migrated.
What to get right.
Map legacy categories to Fusion categories that drive depreciation defaults.
Original cost and unit counts per asset.
Accumulated depreciation so net book value is correct.
Drive remaining depreciation correctly.
Load the corporate book; handle tax books if in scope.
Asset cost and accumulated depreciation must tie to the GL.
The mechanical sequence.
Map legacy asset categories to Fusion categories and confirm depreciation rules.
Pull assets with cost, units, in-service date, life/method and accumulated depreciation.
Populate Mass Additions with cost and depreciation reserve per asset.
Import, post mass additions, and review rejections (category, dates, book).
Run a depreciation cycle and confirm expense continues from the correct NBV.
Match asset cost and accumulated depreciation by category/book to source and tie to the GL.
What trips teams up.
Loading cost but not accumulated depreciation overstates net book value.
Wrong category applies the wrong depreciation method/life.
Wrong dates miscalculate remaining depreciation.
Corporate vs tax book amounts must be handled correctly.
Asset and accumulated-depreciation balances must tie to the GL.
Pre-built extraction, Assets FBDI generation and cost/depreciation reconciliation.
Map legacy asset categories to Fusion categories, extract the asset register with cost, units, in-service date, life/method and accumulated depreciation, load via the Mass Additions (Assets) FBDI, run a depreciation cycle to confirm continuity, and reconcile asset cost and accumulated depreciation by category and book — tying to the GL.
Yes — you must load the depreciation reserve (accumulated depreciation) alongside cost so net book value is correct and Fusion continues depreciation from the right point. Loading cost alone overstates NBV.
Legacy categories are mapped to Fusion asset categories, which drive default depreciation method, life and accounts. Correct category mapping is essential for accurate depreciation.
Match asset cost and accumulated depreciation by category and corporate book to the source, confirm net book value, and tie the asset and accumulated-depreciation balances to the GL accounts.
Yes — Syntra ETL automates register extraction, category mapping, Assets FBDI generation and cost/accumulated-depreciation reconciliation.
Tell us your source system and we'll migrate your fixed-asset register to Oracle Fusion with cost and depreciation reconciled.