Comprehensive Detailed Explanation

In Dynamics 365 Business Central, pricing and discounts are managed with different setup types:

Sales Prices

Used to define special prices for specific customers, customer groups, items, or date ranges.

Correct setup when " customers receive special prices for a certain amount of time. "

Sales Line Discounts

Used to configure line-level discounts based on item, item group, or quantity.

Correct when " the company offers different discounts for different item types. "

Customer Invoice Discounts

Applied at the invoice (header) level when the total sales amount on an order/invoice exceeds a defined threshold.

Correct when " loyal customers are rewarded with additional discounts when a certain sales amount on an order is reached. "

Unit Price

Not a separate setup type in this context; it ' s the actual price per item on a line. For structured price/discount management, Sales Prices and Discounts are used.

Microsoft Learn References:

Set Up Sales Prices

Set Up Sales Line Discounts

Set Up Customer Invoice Discounts

The Custom Report Layouts page allows you to manage and update layouts (Word or RDLC) for a given report object. However, simply updating the layout does not make a new report object the system default. You must still assign the new report in Report Selection – Purchase. Thus, this solution does not meet the goal.

In Dynamics 365 Business Central, the Payment Registration feature is used to quickly apply customer payments to outstanding invoices. In this scenario, one lump sum payment is received that covers two invoices. Because Auto Fill Date Received is enabled, you don’t have to manually enter the Date Received.

Step-by-step:

Open Payment Registration

Navigate to the Payment Registration page to start applying the payment.

In the Amount Received field, enter amounts

Enter the total amount the customer paid. Since it ' s one payment covering two invoices, enter the combined amount.

Select Payment Made for the first invoice

Apply the payment to the first outstanding invoice.

Select Payment Made for the second invoice

Apply the payment to the second outstanding invoice.

Select Post As Lump Payment

This option ensures the payment posts as one lump transaction, not two separate ones, since the customer made a single combined payment.

Select Post Payments

Finally, post the payment to update the customer ledger and bank account.

In Business Central, the Payment Terms calculation uses the Document Date (not Posting Date or Order Date). The system takes the Document Date and applies the due date calculation formula defined in the Payment Terms.

Order Date is primarily for purchase/sales documents scheduling.

Posting Date drives G/L posting date.

Due Date is the result of the calculation, not the input.

Based on the provided image, the correct values to select for the customer payment terms are the ones already highlighted.

Due Date Calculation for retail customer payment term:

Select the value 10.

Discount Date Calculation for wholesale customer payment term:

Select the value 10D.

Due Date Calculation for wholesale customer payment term:

Select the value 30D.

Due Date Calculation for wholesale customer payment term:

Select the value 15D.

In Dynamics 365 Business Central, workflows are the tool used to control document approvals, including purchase orders:

Lock the record for newly created blanket purchase orders with the specific item → Business Central workflows

Blanket purchase orders are controlled via approval workflows in Business Central.

Workflows enforce rules so records cannot be processed until approved.

Assign the security command that tells the system to lock the purchase order → Then Response

In workflow design:

When Event defines the triggering action.

On Condition specifies filter conditions.

Then Response is the action taken, e.g., Lock the record or Request Approval.

Therefore, locking the record is a response action.

Assign the items that the system will want to use to trigger the locking of the purchase order → When Event

The workflow must know what starts the approval process (such as A blanket purchase order is created).

This is always defined as a When Event.

Other options not correct:

Incoming Documents / Power Automate flows → Can be integrated, but the requirement here is internal approval and locking, which is a Business Central Workflow function.

On Condition → Used to apply filters (like a specific item), but the actual trigger is defined by When Event.

Trigger → Not a component in Business Central workflow terminology (more of a technical developer concept).

Microsoft Learn References

Set Up Approval Workflows

Workflows in Business Central

Requirement: Each salesperson must be assigned to only one region, and combinations must be enforced automatically to avoid inconsistent commission reporting.

In Business Central, this is achieved by defining a Dimension Combination rule between the Salesperson dimension and the Region dimension.

Setting it to Blocked prevents users from posting with an invalid salesperson-region combination.

Other options:

A. Limited restricts only dimension values on certain accounts.

B. Default Dimension Priorities controls which default dimension wins, but does not enforce uniqueness.

D. Default Dimensions on Customer Cards helps with defaults, but doesn’t prevent invalid combos.