Drag and Drop Question A company is processing rebate management deals in Dynamics 365 Supply Chain Management. The company must post a customer rebate provision for each relevant deal. The source…

The correct answer is Set up a deal line that creates the rebate provision when sales invoices post.; Process the series of transactions for the rebate management deals.; Process the provision for the rebate management deals.; Post the provision. Rebate Provision Workflow in D365 SCM - Explained The Core Concept In D365 SCM Rebate Management, a provision is an accrual entry that recognizes a rebate liability before the rebate is actually paid. The workflow follows a strict configuration-then-process-then-post pattern…

Implement additional supply chain management features

Question

Drag and Drop Question A company is processing rebate management deals in Dynamics 365 Supply Chain Management. The company must post a customer rebate provision for each relevant deal. The source transactions are created automatically. You need to recommend the steps to create and post the rebate provision. Which four actions should you recommend be performed in sequence? To answer, move the appropriate actions from the list of actions to the answer area, and arrange them in the correct order. Answer:

Exhibit

Answer Area

Drag items

Process the series of transactions for the rebate management deals.Set up a deal line that creates the rebate provision when sales invoices post.Process the provision for the rebate management deals.Post the sales order invoices.Post the provision.

Correct arrangement

Set up a deal line that creates the rebate provision when sales invoices post.
Process the series of transactions for the rebate management deals.
Process the provision for the rebate management deals.
Post the provision.

Explanation

Rebate Provision Workflow in D365 SCM - Explained

The Core Concept

In D365 SCM Rebate Management, a provision is an accrual entry that recognizes a rebate liability before the rebate is actually paid. The workflow follows a strict configuration-then-process-then-post pattern.

Why Each Step Is Placed Where It Is

Step 1: Set up a deal line that creates the rebate provision when sales invoices post

This is the mandatory foundation. The deal line configuration tells the system:

What conditions trigger a rebate
Which posting profile to use (determining the ledger accounts)
That the trigger event is sales invoice posting

Nothing else can happen without this. The system has no rebate logic to execute until this exists.

Step 2: Process the series of transactions for the rebate management deals

The question states source transactions are "created automatically" (when invoices post per your deal line setup). This step processes/calculates those accumulated source transactions into rebate amounts. Think of it as the calculation engine run - it reads the raw transaction data and computes what is owed per deal terms.

This must follow Step 1 because the deal line must exist before any transactions can be processed against it.

Step 3: Process the provision for the rebate management deals

This step takes the calculated amounts from Step 2 and generates the actual provision journal (the accounting accrual). It creates an unposted journal that records the rebate liability.

It cannot precede Step 2 because the provision has nothing to pull from if the amounts haven't been computed.

Step 4: Post the provision

This finalizes the provision journal to the general ledger, making it an official accounting entry. It is always last - you can only post what has been created.

Why "Post the sales order invoices" Is Excluded

This is the key distractor. The question explicitly states that source transactions are created automatically - meaning invoice posting triggers them behind the scenes as part of normal sales operations. It is an implicit prerequisite, not a distinct step in the rebate provision workflow you are recommending. Including it would confuse the sales process with the rebate management process.

Common Mistakes

Mistake	Why It's Wrong
Including "Post the sales order invoices"	The question tells you source transactions are automatic - invoice posting is outside the rebate workflow scope here
Swapping Steps 2 and 3	You must calculate amounts (process series) before you can generate the provision journal (process provision)
Moving "Post the provision" earlier	You cannot post a journal that hasn't been created yet
Skipping Step 1	Without deal line configuration, the system has no basis for any rebate calculation

The overall pattern to memorize: Configure → Calculate → Generate journal → Post journal.

Topics

#rebate management#rebate provision#sales invoices#deal lines

Community Discussion

No community discussion yet for this question.

Full MB-335 Practice