MB-800 Microsoft Dynamics 365 Business Central Functional Consultant Free Practice Exam Questions (2026 Updated)

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

The requirement is:

“When viewing G/L entries, the finance and accounting teams must be able to see debits and credits instead of a positive or negative amount.”

In Business Central, the General Ledger Entries page can display amounts in two different ways:

Amount (positive/negative): This is the default display of entry amounts as signed numbers.

Debit Amount / Credit Amount (separate fields): This allows accounting teams to clearly see whether an entry is a debit or a credit, consistent with traditional accounting presentation.

The configuration option " Debit/Credit " is specifically provided to control this display. By enabling this setting, amounts are shown in two columns (Debit Amount and Credit Amount) instead of one column with positive/negative signs.

Why not the other options?

B. Show Amounts – This relates to toggling whether amounts are displayed on certain ledger pages but does not change the format to Debit/Credit.

C. Check G/L Account Usage – This is a validation function for checking how accounts are used, not related to entry display format.

D. G/L Account Card – Used to configure properties of individual G/L accounts (posting type, direct posting, account category), not the general display mode for entries.

Therefore, the correct configuration to meet the requirement is Debit/Credit.

Microsoft Learn references

Work with General Ledger Entries – explains how G/L entries can be displayed and filtered.

Business Central General Ledger Setup – includes configuration options such as showing amounts as debit/credit.

General Ledger Overview in Business Central – details on how entries are posted and viewed.

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 is to report profitability by business line (cash & carry vs. brokered). In Business Central, the way to achieve this is by creating a Global or Shortcut Dimension (for example, a dimension called Business Line) and ensuring that it is captured on every sales, purchase, and general ledger transaction.

Create a dimension → Value

The correct choice is Value because profitability reporting is driven by dimension values such as Cash & Carry and Brokered.

Combination, Default Priorities, and Account Type Default are used for control and automation of dimensions, not for the initial creation of reporting dimensions.

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

In BC, invoices can be generated from:

Sales Order Invoicing (D): Post invoices directly from sales orders.

Combine Shipments (A): Consolidate multiple shipments into a single invoice (used for customers who require weekly or monthly invoices).

Get Shipment Lines from Sales Order (B) is incorrect — shipment lines are retrieved in warehouse processing, not for invoicing.

Sales Order Shipping (C) posts shipment only, not invoices.

Get Shipment Lines from Sales Invoice (E) is used for service scenarios but is not the standard sales invoicing process here.

Correct: A and D

Regular price: $20.00

Buying group discount: $18.00

Autumn promotion price: $19.00

Overstock special: 15% off regular price ($20 × 0.85 = $17.00)

However, the case study requires the system to always give the lowest available price.

Comparison of all active prices:

Regular = $20.00

Buying group = $18.00

Autumn promotion = $19.00

Overstock 15% discount = $17.00

Lowest available = $17.00. But since the customer belongs to a buying group and it’s also an overstock day, the system applies stacking rules: the overstock discount applies on top of buying group price.

$18.00 × 0.85 = $15.30.

The scenario describes cash and carry sales, where customers pay immediately at the desk and sales invoices must be posted as paid in full at the time of sale. In Dynamics 365 Business Central, this is achieved by setting Payment Terms that indicate no delay between invoice date and due date.

Why D (Payment Terms = 0D)

The Payment Terms setup in Business Central allows you to define how the Due Date is calculated.

For cash and carry transactions, the invoice is due on the same day (zero days). Setting the Due Date Calculation to 0D ensures that the system always marks invoices as immediately due, reflecting the cash-and-carry business process.

This aligns with requirements: “Invoices must be posted at the cash and carry desk at the time of sale” and “Invoices already paid in full should not appear as outstanding on aging reports.”

Why not A (Payment Service)

Payment Services are used for integration with external services like PayPal or credit card gateways. Wide World Importers does not require a POS or online payment gateway—just simple cash handling at the desk.

Why not B (Direct Debit Mandate)

Direct Debit is used for recurring bank withdrawals (SEPA mandates, subscription-type payments). It does not apply to one-time, immediate cash payments.

Why not C (Payment Method = Bank Account)

While Payment Methods (e.g., Cash, Bank Transfer, Check) are also important for tracking how customers pay, the critical requirement in the scenario is ensuring the invoice is due immediately. That is achieved by Payment Terms = 0D, not by Payment Method alone.

Best Practice Setup in Business Central for Cash & Carry:

Payment Terms: 0D (ensures invoice due immediately).

Payment Method: Cash (ensures posted directly against the cash account).

Apply to invoices at posting: Invoices will automatically be shown as paid in full.

This combination ensures correct cash sales processing and eliminates the issue noted in the case study where invoices incorrectly appear in aging reports.

Microsoft References

Set Up Payment Terms in Business Central

Set Up Payment Methods in Business Central

Work with Payment Transactions

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

The requirement is to configure the new customer creation process in Dynamics 365 Business Central. The goal is to make sure that when users quickly add new customers (for example, at the Cash & Carry desk), all required fields and correct defaults are consistently applied.

1. Configuration Worksheet (B)

The Configuration Worksheet is used in RapidStart Services to plan and manage setup data across tables.

It lets you map out which tables (e.g., Customers, Vendors, Items) you want to configure and load master data into.

For customer creation, this ensures that the Customer table and related setup tables are properly configured before using templates.

This acts as the foundation of the process: deciding what must be included in the customer creation workflow.

2. Configuration Template (C)

Configuration Templates define default values for new master data records (e.g., customers, vendors, items).

For example, when creating a new customer, the template can pre-fill fields like:

Posting groups

Payment terms

Customer source dimension

Responsibility center (if required)

This ensures consistency and reduces errors when users add new customers.

In this scenario, since the company wants fast and accurate customer creation, templates are essential.

Why not A (Responsibility center)?

Responsibility centers are used to manage operations by location, department, or profit center.

They are useful for reporting and segregation of transactions, but not mandatory for customer creation setup.

Why not D (Permissions)?

Permissions define who can create or modify customers.

While important for security, this is not part of the configuration process for ensuring consistent field population and defaults in customer creation.

Microsoft References

Set Up Configuration Packages and Templates (RapidStart Services)

Configuration Templates for Customers, Vendors, and Items

Customer Table Setup and Creation

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

This sequence makes sense because you first create the series itself, then define the lines (the actual numbers within the series), and finally define the relationships to link the series to the specific data table (like the Accounts table) where it will be used.

Sequence 2: Using a Configuration Package to Manage Data

This sequence focuses on using a configuration package to manage and update data, which might include fixing issues with existing accounts or importing new ones.

Create a configuration package.

Configure the Vendor Table on the configuration package.

Create the Data template.

While this sequence is plausible, it has a significant flaw: the prompt mentions " Accounts, " but this sequence specifically mentions the Vendor Table. If we assume the " Vendor Table " is a placeholder for a generic data table like the Accounts table, the sequence makes sense. You create a package, configure it for a specific table, and then create a data template to import the data into that table.

Sequence 3: Resolving Issues by Defining the Number Series on the Configuration Template

This sequence focuses on resolving issues by directly modifying the configuration template within a configuration package.

Create a configuration package.

Create the Data template.

Define the No. Series on the configuration template.

This sequence is logical for a scenario where you ' re using a configuration package to manage both data and its associated number series. You first create the package, then create the data template (which is a core component of the package), and finally define the number series on that template to ensure the imported data uses the correct number sequencing.

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