Microsoft MB-800 - Microsoft Dynamics 365 Business Central Functional Consultant

Buying groups require all invoices in a month to be due on the 20th of the following month (from the case study).

In BC, this is achieved by setting up Payment Terms = CM+20D (Current Month + 20 Days). Example: Invoice on Sept 5 → due Oct 20.

Payment terms are assigned directly to the customer card, not to the posting group or price group.

Option E (D20) would set due date 20 days after invoice date, which is incorrect.

Assigning to Customer Posting Group or Price Group does not control due dates.

Correct: A and C

Comprehensive Detailed Explanation

The case study mentions reconciliation issues caused by manual entries being made directly into certain G/L accounts, which led to discrepancies between subledger balances (like customers, vendors, or inventory) and the General Ledger. To resolve this, Business Central allows you to restrict how accounts are posted.

Restrict use on → G/L Account Card

The most appropriate place to restrict usage of specific accounts (such as control accounts for A/R, A/P, or Inventory) is on the G/L Account Card.

Here, you can configure posting restrictions for each account individually (e.g., Accounts Receivable account should only be posted through the customer subledger, not by manual G/L journals).

Other options:

General Ledger Setup → Controls global accounting settings, not account-specific restrictions.

Sales & Receivable Setup → Defines control accounts but does not enforce restrictions.

Chart of Accounts → Displays accounts but restrictions are managed per account card.

Set value for → Direct posting

On the G/L Account Card, the field Direct Posting determines whether users can post manual entries directly into the account.

To prevent reconciliation issues, Direct Posting must be disabled (unchecked) for accounts controlled by subledgers (e.g., A/R, A/P, Inventory).

This ensures that postings only come from system-generated entries (like sales invoices, purchase invoices, or inventory adjustments) and not from manual journals that could break reconciliation.

Other options:

Reconciliation account → Relevant in SAP, not BC.

Check G/L account usage → Not a standard control in BC.

Gen. Posting Type → Defines how entries are posted (Sale, Purchase, Inventory), but does not enforce direct posting restrictions.

With this setup:

Reconciliation issues are avoided because control accounts cannot be posted to manually.

Users are guided to post through the proper subledger processes (sales, purchasing, inventory, etc.).

Financial integrity between subledgers and the G/L is maintained.

Microsoft References

G/L Account Card - Direct Posting Field

Prevent Direct Posting to Control Accounts

Chart of Accounts in Business Central

Comprehensive Detailed Explanation

The requirement is to configure the system so that sales discounts are visible and tracked correctly in Dynamics 365 Business Central.

Define simultaneous posting → General Ledger Setup

In Business Central, the General Ledger Setup page contains fields that control whether discounts are posted separately or combined with sales postings.

By defining discount posting behavior at the General Ledger Setup level, you ensure consistency across all sales transactions and financial reporting.

Other options (Sales & Receivable Setup, Customer, Item) do not define global simultaneous posting behavior for discounts; they control transaction processing but not the separation of discount postings.

Specify type to post separately → Discount Posting

To show sales discounts separately, you must enable Discount Posting.

This ensures discounts are posted to a dedicated G/L account, rather than being netted off directly against sales.

As a result, financial statements can show both gross sales and discounts given, which is critical for profitability analysis and discount tracking.

The other options in the list:

Invoice Disc. Code → Used to define specific invoice discounts, but not to enforce posting separately.

Special Prices & Discounts → Controls pricing rules but not posting behavior.

Adjust for Payment Disc. → Manages how payment discounts affect invoices, but again, not posting visibility.

With this setup, Wide World Importers can track gross sales, discounts, and net sales transparently in reports, allowing management to analyze the financial impact of discounts.

Microsoft References

General Ledger Setup in Business Central

Discount Posting Field (Post Discounts Separately)

Work with Sales Discounts in Business Central

Correct Answer:

Define simultaneous posting: General Ledger Setup

Specify type to post separately: Discount Posting

Create a Customer Discount Group

Create an Item Discount Group

Select the Item Discount Group for the Item

Comprehensive Detailed Explanation

To configure sales discounting in Dynamics 365 Business Central, you need to set up the relationship between customers and items so that the system can automatically apply the correct discounts during sales transactions. The process involves both customer grouping and item grouping.

1. Create a Customer Discount Group

This step defines which customers are eligible for group-based discounts (e.g., a retail chain, buying group, or brokers).

By creating a Customer Discount Group, you can later apply uniform discount rules across all customers belonging to that group, instead of configuring each customer individually.

2. Create an Item Discount Group

Next, you create Item Discount Groups to categorize items into discountable product lines (e.g., Olive Oils, Spices, Snacks).

This ensures that discount rules apply consistently across items in the same category, rather than having to define rules item by item.

3. Select the Item Discount Group for the Item

Finally, you link each relevant Item Card to the correct Item Discount Group.

This connection ensures that whenever a sales order/invoice is created for a customer belonging to a discount group and includes items in an item discount group, the system automatically applies the correct Sales Line Discounts.

Why not the other actions?

Define the Sales Invoice Discounts → Used for invoice-level discounts, but here the requirement is item/line-based discounting.

Define the Customer Special Sales Prices & Discounts → Used for customer-specific or promotional pricing, not for group-wide discount structures.

Configure Discount Posting in Sales & Receivable Setup → Relevant for accounting/reporting (whether discounts post separately) but not for setting up how discounts are determined and applied.

Define the Sales Line Discounts → This is the outcome of linking customer discount groups and item discount groups, but it requires the setup steps above first.

Microsoft References

Set Up Customer and Item Discount Groups

Work with Sales Line Discounts

Special Prices and Discounts in Business Central

Comprehensive Detailed Explanation

The requirement is to ensure that every transaction posted to a customer account includes the Customer Source dimension (e.g., Cash & Carry, Brokered). This is achieved by creating and enforcing a mandatory dimension rule in Business Central.

Step 1: Create a dimension code to identify the customer source

First, define a Dimension Code such as Customer Source.

This will hold values like Cash & Carry and Brokered.

Dimensions are the foundation for all reporting segmentation in Business Central.

Step 2: Create dimension values for the customer source dimension code

After creating the dimension, define the specific Dimension Values (e.g., Cash & Carry, Brokered).

These represent the business lines the company wants to track.

Step 3: Add the Customer table

To enforce the dimension on customers, link the dimension to the Customer table.

This ensures that every transaction involving a customer account requires this dimension.

Step 4: Set the Value Posting to Code Mandatory

On the Default Dimensions page, set Value Posting = Code Mandatory for the Customer Source dimension.

This forces users (or the system) to provide a dimension value on every transaction involving customers.

Without this, users might skip dimension assignment, leading to incomplete reporting.

Step 5: Select the Dimension Value Code that is used for the customer source

Finally, assign the correct Dimension Value (Cash & Carry or Brokered) to each customer record.

This ensures automatic defaulting during transaction entry, reducing user errors and maintaining consistency.

Why not the other actions?

Chart of Accounts: Not needed here, since the requirement applies to customers, not G/L accounts.

Account Type Default Dimension: Useful for G/L accounts, but here we are applying it at the Customer table level.

Search icon, Customers: While this helps you navigate, it’s not a required setup step in the sequence.

Microsoft References

Work with Dimensions in Business Central

Set Up Default Dimensions for Customers

Dimension Value Posting Options

Comprehensive Detailed Explanation

The requirement in the case study is that the company warehouses products as Case quantities but wants to expand capabilities by setting up all inventory in a quantity of Each. This means they need to configure Units of Measure (UoM) so that one item can be managed both by Case and by Each.

In Business Central:

Units of Measure Table – defines the available unit codes (e.g., EACH, CASE, BOX) with descriptions.

To use Case as a unit, you must first define it in the Units of Measure table.

Correct: D. Add a Code and Description to the Units of Measure table.

Item Units of Measure (Qty. per UoM) – links the item to multiple units of measure and specifies conversion (e.g., 1 Case = 10 Each).

For example, if a Case = 10 Each, you set Qty. per Unit of Measure = 10 for Case.

Correct: A. Set a Unit of Measure for case to a Qty. of 10.

Why the other options are incorrect:

B. Qty. per UoM = 1 is redundant (default Each already equals 1). It does not meet the requirement for Case-to-Each conversion.

C. Case with Qty. = 1 would make Case = Each, which is incorrect because Case must represent multiple units (10 Each).

Microsoft Learn References

Work with Units of Measure

Set Up Item Units of Measure

Requirement: Invoices must be automatically emailed to customers using a fixed template.

Solution:

A. Set Email to Yes (Use Default Settings) → ensures invoices are sent automatically without prompting.

E. Apply Office Server Settings to the SMTP Mail Setup → configures the company’s mail server (SMTP/Office 365) so that emails are sent.

F. Assign a Document Sending Profile to the Customer where Email is set to Yes → links customers to the correct sending method (Email with fixed template).

Other options:

B. Allow Sender Substitution is optional, not required.

C. Prompt for Settings requires manual action (not automatic).

D. Assigning “Email = No” contradicts the requirement.

Comprehensive Detailed Explanation

Deliver on a specific customer date

Salespeople must avoid promising inventory that is not available.

To check whether the requested delivery date can be met, the correct action is to review Item Availability by Periods.

This allows them to see when stock will be available across time periods, ensuring promised delivery dates are realistic.

Other options are less accurate:

Change the Requested Delivery Date → does not confirm if stock is available.

Check the Catalog on Sales Line → only for product lookup, not availability.

View the Location Code → shows location assignment, not time-phased availability.

Correct: View the Item Availability by Periods

Process quotes

Requirement: Salespeople must convert quotes to orders once they are finalized.

In Business Central, this is done by selecting Make Order from the Sales Quote.

Other options:

Make Invoice → bypasses order process, not applicable here.

Copy Document → creates a new document, not the required process.

Release → applies to orders but not to quotes-to-orders conversion.

Correct: Choose Make Order

Microsoft Learn References

Check Item Availability

Convert Sales Quotes to Orders

Comprehensive Detailed Explanation

Set up a new fiscal year

In Business Central, fiscal years are created in the Accounting Periods page.

To start a new fiscal year, you must Select Create Year, which generates the periods for the new fiscal year.

Other options like Close Year or Fiscal Year Balance are for closing or balancing, not for initial setup. Correct: Select Create Year

Define the fiscal year start date

The case study specifies that the company’s fiscal year starts on June 1.

Therefore, when creating the new fiscal year, you must ensure the first period begins on June 1.

The correct action is Check New Fiscal Year for June 1. Correct: Check New Fiscal Year for June 1

Restrict posting

The business requirement is:

Restrict users to post only in the current month.

Only certain accounting users may have broader posting permissions.

In General Ledger Setup, the Allow Posting From and Allow Posting To fields control the global posting date range.

For user-specific restrictions or exceptions, User Setup allows overriding posting ranges for individual users.

Since the requirement is to restrict all users generally, the best action is: In General Ledger Setup, set the Allow Posting From and Allow Posting To options to current dates. Correct: In General Ledger Setup, set the Allow Posting From and Allow Posting To options to current dates

Microsoft Learn References

Accounting Periods (Create and Close Fiscal Years)

General Ledger Setup – Allow Posting From/To

User Setup and Posting Date Permissions