A fixed asset really only becomes a hard number twice in its life: once when it is acquired, and once when it is disposed of. Everything between those two points, depreciation, adjustments, revaluation, is where the value can quietly drift if nobody is watching closely.
D365 fixed assets is built to keep that drift from happening, tracking an asset’s financial value through every stage instead of just the two that show up on a balance sheet. The Fixed asset management workspace already includes a cross-company Power BI analytics view covering acquisitions, depreciation, and disposals, so this is not a module starting from zero on reporting. This guide will explore how D365 fixed assets move through acquisition, depreciation, and disposal, and which fixed asset reporting use cases the platform covers well, versus where a heavier layer earns its place.
The fixed asset lifecycle in D365 F&O
D365 fixed assets moves every asset through four connected stages: acquisition, depreciation, adjustment or transfer, and disposal. Each stage posts its own transaction type, tied back to the same asset record, so the full history stays in one place rather than scattered across journals.
- Acquisition and acquisition adjustment establish and later correct an asset’s original cost basis.
- Depreciation, depreciation adjustment, and special depreciation allowance reduce that value on a schedule, or correct it when the schedule was wrong.
- Revaluation writes an asset’s value up or down outside the normal depreciation schedule, common after an appraisal or a currency restatement.
- Disposal sale and disposal scrap close the asset out, moving whatever value remains to a gain or loss.
The thread connecting all four stages is the book, the record that carries an asset’s financial value forward from one transaction to the next. Get the book wrong, and every stage after it inherits the error. This is the part of D365 fixed assets that decides whether the rest of the module can be trusted.
Getting an asset onto the books: acquisition and depreciation books
Asset acquisition, from purchase order to fixed asset record
Acquisition is the front door into D365 fixed assets, and it can run two ways. A purchase order links product receipt and vendor invoice postings directly to the asset, so the cost basis builds up from actual procurement documents rather than a manual number. Direct entry covers assets that never went through a purchase order at all, a building already owned, for instance, or an asset register carried over from a legacy system during an ERP transition.
Asset acquisition and acquisition adjustment are the two transaction types behind this stage: acquisition establishes the original cost, and acquisition adjustment corrects it later without disturbing anything posted since.
Books, and why depreciation books still matters as a concept
D365 fixed assets used to keep value models and depreciation books as two separate concepts. Since release 1611, they have been merged into a single Book concept, distinguished by one setting: Post to general ledger.
Set that option to Yes, and a book behaves the way a value model used to, posting to the general ledger for corporate financial reporting. Set it to No, and the book behaves like the older depreciation books, posting only to the fixed asset subledger, which is typically how organizations still handle tax reporting today.
Every book carries a primary depreciation profile, and can carry an alternative or switchover profile as well. Derived books add one more layer of convenience: they can automatically mirror acquisition and disposal transactions, though not depreciation, from a primary book onto a secondary one, keeping a tax book’s cost basis in sync without anyone re-entering the same transaction twice.
A book that posts to the general ledger and a tax-only depreciation book rarely tell the same story by month-end. See how the Metrixs analytics suite keeps both versions of the truth in one place.
Depreciation in practice: profiles, methods, and adjustments
Depreciation is where D365 fixed assets does its steady, quiet work. A depreciation profile tells the system how to reduce an asset’s value over time: it defines the method, straight line or reducing balance among the options available, the depreciation year, and the period frequency, and gets assigned to a book as that book’s primary profile.
- Alternative and switchover profiles let a book change method partway through an asset’s life, useful when a policy changes or a jurisdiction requires it.
- Depreciation adjustment corrects a posted transaction without unwinding everything after it.
- Extraordinary depreciation and special depreciation allowance handle one-off events and tax incentives, the second entered as a percentage or fixed amount and posted separately from routine depreciation.
- The Calculate depreciation setting on a book decides whether an asset is even included in a depreciation proposal, easy to overlook and a common reason an asset turns out to be silently under-depreciated months later.
None of this is complicated in isolation. It gets complicated when a D365 fixed assets deployment has dozens of books, each with its own profile, and nobody has checked in a year whether every asset that should be depreciating actually is.
Disposal and net book value: closing out an asset correctly
Disposal is the last test D365 fixed assets applies to a number that has been carried for years. Disposal sale and disposal scrap are the two transaction types that close an asset’s life out, and both credit the ledger account for whatever the disposal is worth.
Posting a disposal reverses the accumulated depreciation and the acquisition cost that have been sitting on the balance sheet, and the asset’s net book value at that exact moment moves to the profit and loss account as a gain or loss. That figure, the net book value at disposal, is usually the first thing an auditor checks against the fixed asset register.
- An asset that has fully depreciated to zero will not appear in a disposal proposal automatically; posting it requires a manual entry, which matters most in a demerger or spinoff where entire asset groups leave the business at once.
- Net book value is not a single static number. It is recalculated with every depreciation run, every adjustment, and every revaluation, which is exactly why a stale export of it is unreliable within a month.
Everything upstream, acquisition, the book it sits in, the depreciation profile attached to it, exists to keep this one number honest. Disposal is just the moment it finally gets tested.
If a disposal keeps posting a gain or loss that does not match the roll forward, a Metrixs consultant can trace it back to the book it actually happened in.
Fixed asset reporting use cases D365 F&O ships natively
D365 fixed assets does not leave reporting on this data entirely to spreadsheets. Two native tools cover a real share of what finance actually needs:
- The Fixed asset roll forward report: an Excel-format report built specifically for period closing, financial statements, and tax reporting. It shows opening and closing net book value for the period, alongside acquisitions, disposals, and valuation movements that happened along the way.
- The Fixed asset management workspace: summary tiles for assets not yet acquired, acquired this year, and disposed of this year, plus a genuine Power BI analytics tab covering every legal entity a user has access to.
That is a meaningfully better starting point than either the general ledger or the budgeting module gets natively, and it is worth saying plainly: this module is not starting from nothing on reporting.
Where it stops is more specific than a blanket gap. The roll forward report covers one book and one period at a time, so comparing a GL-posting book against a tax-only depreciation book for the same asset means running and reconciling two separate exports. A three-year trend means running the report three times and lining the results up by hand. And the workspace’s analytics view, useful as it is, reflects whatever is in the tables the moment it loads, not a dedicated layer built to hold D365 fixed assets history over time.
| What you need | Native D365 F&O tools | A dedicated layer such as Metrixs |
|---|---|---|
| Compare a GL book vs. a tax book | Two separate exports, reconciled by hand | Both books shown side by side |
| Multi-year roll forward | Re-run the report per year | Configurable history in one saved view |
| Cross-entity net book value | One entity at a time, or a summary tile | Consolidated across entities automatically |
| Refresh | Whatever is loaded when the workspace opens | 15 to 30 minutes via Synapse Link |
What a dedicated fixed asset reporting layer adds
Metrixs reads D365 fixed assets transactions and book balances the same way it reads the rest of D365 F&O, through Azure Synapse Link into a dedicated Azure Data Lake, then rebuilt into fact and dimension models shaped for reporting rather than for posting.
- A roll forward view that does not need re-running per year: acquisitions, depreciation, adjustments, and disposals held as configurable history, so a five-year trend is a saved report, not five separate exports.
- Side-by-side book comparison: a GL-posting book and a tax-only depreciation book shown together instead of pulled one at a time and reconciled by hand.
- Multi-entity roll-up, so a fixed asset register spread across several legal entities, even across a multi-ERP environment, consolidates into one net book value view.
- Refresh every 15 to 30 minutes, with the same row-level and object-level security D365 F&O already enforces.
The fixed asset module sits inside the same suite covering the rest of D365 F&O reporting: 12 analytics modules, 100+ prebuilt reports, and 1,000+ configurable metrics, with most deployments live in under 6 weeks and client ROI running 290% to 450% across engagements. For an organization already running D365 fixed assets across more than one book or entity, that is the difference between chasing down a number every quarter and simply looking at it.
Curious what a live, multi-book net book value view actually looks like? The D365 F&O finance and accounting analytics use case shows exactly that.
Frequently asked questions
What is included in D365 fixed assets management?
D365 fixed assets management covers the full lifecycle of an asset: acquisition, depreciation, adjustment or revaluation, and disposal. Every stage posts against a book, the record that carries an asset’s financial value forward, and native reports plus a Power BI-enabled workspace cover a real share of the reporting finance needs from that data.
What is a depreciation book in D365 F&O?
A depreciation book is a book, in the modern unified Book concept, set up with Post to general ledger switched off, so it posts only to the fixed asset subledger. This is typically how organizations run tax reporting alongside a separate book that does post to the general ledger for corporate financial statements.
How does asset acquisition work in D365 F&O?
Asset acquisition runs either through a purchase order, linking product receipt and vendor invoice postings to the asset automatically, or through direct entry for assets that never went through procurement. The acquisition transaction establishes the original cost basis, and an acquisition adjustment corrects it later without disturbing anything posted since.
How is net book value calculated in D365 F&O?
Net book value is an asset’s original cost, adjusted for any revaluation, minus accumulated depreciation, recalculated with every depreciation run, adjustment, and revaluation posted against the asset’s book. It is not a static number, which is why an exported figure is only accurate as of the moment it was pulled.
What happens when a fixed asset is disposed of in D365 F&O?
A disposal sale or disposal scrap transaction reverses the accumulated depreciation and acquisition cost sitting on the balance sheet, and the asset’s net book value at that moment moves to profit and loss as a gain or loss. A fully depreciated asset needs a manual disposal posting, since it will not appear in an automatic proposal.
What does the Fixed asset roll forward report show?
The Fixed asset roll forward report shows opening and closing net book value for a chosen period, alongside acquisitions, disposals, and valuation movements that happened during it, in an Excel format built for period closing, financial statements, and tax reporting. It covers one book and one period at a time.
Does D365 F&O support reporting across multiple asset books or entities?
Natively, this kind of reporting works one book and one legal entity at a time, though the Fixed asset management workspace does include a Power BI analytics tab covering every entity a user can access. Comparing a GL-posting book against a tax-only book, or consolidating several entities into one net book value view, usually still means exporting and reconciling by hand.
The verdict
D365 fixed assets covers real ground on its own: a full lifecycle from acquisition through disposal, a native roll forward report, and a workspace with genuine Power BI analytics built in. Where the native tools stop is specific, not total: reconciling more than one book for the same asset, holding more than one year of roll forward history, and refreshing faster than whatever the workspace has loaded at that moment.
Metrixs closes that gap: reading the same books and transactions, refreshing every 15 to 30 minutes, and shipping fixed asset reporting as part of the same suite that already covers the rest of D365 F&O.
Ready to see what your own asset register looks like as one multi-book, multi-year view? Book a Metrixs reporting assessment, and we will map your books and disposals against what the reporting layer already covers.
