Drag and Drop Question A company uses Microsoft Dynamics 365 Finance. You receive a new purchase invoice. You must process the invoice as a fixed asset that complies with applicable tax regulations…

Question

Exhibit

Answer Area

Explanation

Explanation: Fixed Asset Configuration with Tax Compliance in D365 Finance

Background Concepts

Two core concepts drive this ordering:

• Posting layers: D365 Finance maintains separate posting layers - Current (for financial/accounting, e.g., IFRS/GAAP) and Tax (for tax authority reporting). Each requires its own value model (book).
• Derived value model: Because the scenario prohibits double entry for acquisitions, D365 uses a derived book relationship. When you post to the primary (current) book, the system automatically mirrors the transaction to the derived (tax) book - no second manual entry required.

Step-by-Step Reasoning

1. Create new value models - current layer and tax layer

You must build the infrastructure before anything else. Both value models need to exist as independent objects before you can configure any relationship between them or attach them to an asset. This is a prerequisite for every subsequent step. Skipping this or doing it later makes Steps 2 and 4 impossible.

2. On the current value model, select the tax value model as derived value model

With both books now existing, you wire them together. Opening the current value model and pointing to the tax model as derived is what enforces the "no double entry" constraint - D365 will post to the tax layer automatically when the current layer is posted to. This configuration belongs to the book itself, not to any individual asset, so it must be done at the book level before any asset is linked. If you linked books to the asset first and configured this later, the derived relationship might not propagate correctly.

3. Create a new fixed asset ID and complete the fixed asset group

Only now do you create the actual asset record. The fixed asset group carries default settings and determines which books will be associated. You need the books fully configured (Steps 1–2 complete) before creating the asset so that when you assign a group and link books in the next step, the derived relationship is already baked in. Creating the asset earlier - before the books are ready - means you'd be associating incorrectly configured or nonexistent books.

4. Link both value models to the fixed asset

The final step: attach the two configured books to the specific fixed asset. The asset must exist (Step 3) and the books must be properly set up with their derived relationship (Steps 1–2) for this to work correctly. After this, when the purchase invoice is posted against this asset's current book, D365 automatically posts the parallel tax entry via the derived relationship.

Common Mistakes

The key mental model: configure the tools (books + their relationship) fully, then create the asset, then attach the tools to the asset.

No community discussion yet for this question.