Drag and Drop Question You need to set up a process of tracking, recording, and analyzing costs associated with the products or activities of a nonmanufacturing organization. You need to configure…

Question

Exhibit

Answer Area

Explanation

Standard Costing Setup - Prerequisite Configuration Order

This question is from Microsoft Dynamics 365 Finance (formerly AX), covering the setup of standard costing for a nonmanufacturing organization.

Why This Order?

The logic follows a strict dependency chain: each step creates or depends on something the next step needs. You cannot assign what doesn't exist, and you cannot reference a group or account before it's defined.

Step-by-Step Breakdown

1. Create an item model group for standard costs

This must come first because the item model group is what tells the system which costing method to use (standard cost). Every inventory item must be assigned to a model group - without one, items have no costing policy. All downstream configuration is meaningless if no group exists to enforce standard costing behavior.

Common mistake: Skipping this step and assuming a default group already uses standard costing. Generic groups often use FIFO or average cost - you must explicitly create one for standard costs.

2. Define ledger accounts that are related to standard cost variances

Before you can assign accounts to anything, the accounts themselves must exist in the chart of accounts. Standard cost variances (purchase price variance, production variance, etc.) need dedicated GL accounts. You're creating the accounts here, not yet wiring them up.

Common mistake: Trying to go straight to posting profiles without first confirming the GL accounts exist. This causes errors or forces you to create accounts mid-configuration.

3. Assign ledger accounts to item postings that are related to standard cost variances

Now that the accounts exist (Step 2), you map them to the correct inventory posting profiles. This is where you tell Dynamics 365 which account to hit when a standard cost variance event occurs (e.g., a purchase price variance posting).

Common mistake: Confusing "defining" accounts (Step 2) with "assigning" them (Step 3). These are two separate actions - definition is in the chart of accounts; assignment is in the posting setup.

4. Define inventory parameters that are related to standard costs

This comes last because inventory parameters act as global switches and defaults that govern how the system processes standard cost transactions. By configuring parameters after the structural setup is complete, you're activating and fine-tuning a system that is already properly built. Some parameters reference the posting setup and model groups, so those must exist first.

Common mistake: Doing parameters first as a "general setup" step. Parameters reference objects that don't exist yet if done too early, leading to incomplete or incorrect configurations.

Summary of the Dependency Chain

Item Model Group → GL Accounts Defined → GL Accounts Assigned → Inventory Parameters
(costing policy)    (accounts exist)       (accounts wired up)    (system activated)

Each step is a prerequisite for the next. The pattern is: create the entity → define the resources → connect the resources → configure the behavior.

No community discussion yet for this question.