Translate the SYSPRO Assets Register into D365 fixed assets, design books for each depreciation basis, use posting layers where accounting bases must run in parallel, and load asset history so that net book value ties on day one.
Fixed assets is one of the better-supported domains in this path, for a straightforward reason: the SYSPRO adapter names an Assets Register as a distinct module inside the Finance pillar, alongside the general ledger, accounts payable, accounts receivable, the cash book and EFT.
Four constructs carry the D365 fixed asset model, and the relationships between them are what make the design work.
This is the part of the domain where an incorrect assumption produces a design that cannot be configured, so it is worth being exact.
The determination gap applies here as it does elsewhere in the finance track: the source's internal account-determination behaviour is not publicly documented, so it has to be recovered from evidence.
Because the group drives books and posting, the classification scheme deserves design attention rather than a direct copy of the source's asset types.
The target can create and acquire a fixed asset directly from a purchase order line. That is a genuine capability and a genuine decision, because it moves part of the capitalisation judgement into the procurement process.
The playbook places fixed assets in wave seven, alongside open accounts receivable and payable, intercompany positions and opening balances, gated on the trial balance tie-out.
The transaction types beyond acquisition and depreciation each carry their own posting profile entry, and each needs its path validated.
Assets is a small-volume, high-obligation domain with a target model that is precise about where each thing lives.