Fixed assets, enterprise asset management, and field service

How Epicor Kinetic's asset and maintenance management translate to D365's dual asset model — Fixed assets for the financial register and Asset management for the maintenance register — and where Field Service fits.

What you will be able to do

Introduction

Asset management in Epicor Kinetic spans two concerns that D365 deliberately separates: the financial asset (a balance-sheet item with acquisition cost, depreciation, and a net book value that appears on the trial balance) and the maintenance asset (a physical piece of equipment with preventive schedules, work orders, and service…

The dual asset model in D365

Asset records (AssetTable) — the identity of each capitalised asset. Books (AssetBook) — one or more books per asset, each carrying acquisition cost, depreciation method, useful life, and accumulated depreciation. A book represents an accounting treatment (e.g., corporate book, tax book, statutory book).

Fixed-asset migration — data requirements and reconciliation

The fixed-asset migration is a state migration, not a history migration. For each asset, per book:

Depreciation profiles and methods

D365 depreciation profiles define the calculation method. Common mappings from Epicor:

Asset management — configuring the maintenance estate

D365 functional locations represent the physical hierarchy where assets are installed:

Asset disposal and revaluation

Epicor asset disposal (sale, scrap, or write-off) maps to D365 disposal transactions:

Field Service Management — the honest answer

Epicor Field Service Management provides technician scheduling, service contracts, mobile dispatch, and field work-order management. D365 F&O does not have a built-in field service module. The D365 ecosystem answer is one of:

Knowledge check

Summary

Asset migration in an Epicor context requires recognising that D365 separates what Epicor combines. The financial asset register (Fixed assets) and the maintenance asset register (Asset management) are distinct modules with distinct data models, distinct configuration, and distinct migration approaches.