Fixed assets in Dynamics 365 Finance and Operations

How F&O handles fixed assets — books, depreciation profiles, acquisitions, disposals, and the integration with project, purchase, and tax accounting.

Updated 2026-09-11

A factory machine, a server rack, an office building, a fleet of trucks — fixed assets are capital expenditures depreciated over their useful life. F&O's Fixed Assets module captures the full lifecycle: acquisition, depreciation, revaluation, disposal — with multi-book support for parallel tax and financial reporting.

Core entities.

  • Fixed Asset — the asset record.
  • Asset Group — grouping for default depreciation profiles, accounts.
  • Book — a "view" of the asset with its own depreciation method.
  • Depreciation Profile — straight-line, declining-balance, etc.
  • Depreciation Convention — half-year, full-month, etc.

Multi-book architecture. A single asset can have multiple books:

  • Current (current book) — financial reporting per GAAP/IFRS.
  • Tax (tax book) — tax depreciation per local rules.
  • Statutory — country-specific reporting.
  • Custom — managerial purposes.

Each book has its own depreciation method, life, and posting. The asset accumulates value differently per book.

Why multi-book matters. Tax rules and accounting rules diverge:

  • Tax may allow accelerated depreciation (Section 179, bonus depreciation in US).
  • Accounting may require straight-line for matching.
  • Different lives, different methods.

Without multi-book, you'd run separate systems for tax and accounting. F&O integrates both.

Depreciation methods.

  • Straight-line — equal amount per period.
  • Declining balance — higher early, lower later.
  • Sum-of-years digits — accelerated.
  • Units of production — based on usage.
  • Manual — operator enters.

Each method's parameters configured per profile; profiles assigned to asset books.

Acquisition. When an asset is acquired:

  • From purchase order — receipt creates asset acquisition.
  • Manual entry — fixed asset journal directly.
  • From project — capitalised from a project's costs.
  • From inventory — inventory transferred to fixed assets.

Each path posts:

  • Asset value to balance sheet (debit).
  • Vendor payable or cash (credit).

Depreciation runs. A periodic batch:

  1. Identify assets with active depreciation.
  2. Calculate depreciation per book per period.
  3. Post depreciation expense (debit) and accumulated depreciation (credit).

Run monthly typically; some assets require daily for short-lived items.

Asset revaluation. Adjustments after initial recording:

  • Write-up — increase value (asset improvement, market revaluation).
  • Write-down — decrease (impairment).

Posted via specific journals; affects future depreciation.

Disposal. When an asset is retired or sold:

  • Sale — asset value out, sales price in, gain/loss to P&L.
  • Scrap — asset value out, loss to P&L.
  • Transfer — to another entity or fund.

The disposal journal handles the accounting; tax book may show different gain/loss than current book.

Asset groups and default values. Asset groups simplify configuration:

  • All "Buildings" — straight-line 30 years.
  • All "Computers" — straight-line 3 years.
  • All "Vehicles" — declining-balance 5 years.

New assets inherit defaults from their group; can be overridden per asset.

Integration with projects. For long-build assets:

  • Construction in progress (CIP) accumulates project costs.
  • On completion, CIP transfers to fixed asset.
  • Depreciation starts from in-service date.

This handles building, manufacturing line install, multi-month asset constructions.

Integration with maintenance.

  • Service work orders posted against the asset.
  • Maintenance costs tracked; not capitalised (usually).
  • Asset uptime / utilisation tracked.

For mining, manufacturing, fleet operations, this integration matters.

Tax depreciation specifics.

  • US — MACRS (Modified Accelerated Cost Recovery System) classes, bonus depreciation, Section 179.
  • EU — country-specific rules.
  • Asia-Pacific — varies.

F&O's tax book handles local rules with appropriate localisations.

Component depreciation (IFRS). IFRS requires separate depreciation of significant components:

  • A building's roof depreciated differently than the building shell.
  • F&O supports parent-child asset structures for components.

Component accounting adds complexity but is required for IFRS-reporting entities.

Mass disposal and mass acquisition. For fleet operations:

  • 50 trucks acquired together — mass acquisition.
  • 30 retired together — mass disposal.

Batch journals handle these efficiently.

Reporting.

  • Asset register — full list of active assets with values.
  • Depreciation forecast — future depreciation by period.
  • Disposal report — gains/losses.
  • Asset transactions — full ledger per asset.

For auditors, the asset register is the canonical source; reconciles to balance sheet.

Common pitfalls.

  • Tax book missed. Only current book set up; tax depreciation manual; compliance risk.
  • Acquisitions through wrong path. Direct journal entries bypass asset module; asset register incomplete.
  • Disposals not posted. Asset still depreciating after sale; balance sheet wrong.
  • Component accounting skipped. IFRS non-compliance for buildings and complex assets.
  • In-service date missing. Depreciation starts wrong; period overstates.

Strategic positioning. Fixed asset accounting is a core finance discipline. F&O's module is comprehensive and handles most scenarios; for very complex environments (oil and gas with depletion accounting, real estate with multiple component layers, government with fund accounting), specialty extensions or external systems may complement. For most enterprises, F&O Fixed Assets handles the lifecycle natively with appropriate setup. The investment in configuring books, profiles, and conventions at deployment pays back through automated, audit-ready depreciation processing for years.

Related guides