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

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.

Comprehensive Detailed Explanation

The company’s reporting requirements are:

They need to analyze which customers are buying which items.

They need to analyze which salespeople are selling in which regions.

They also need consistent reporting for Customer Groups, Item Groups, Salesperson, and Region.

In Business Central, dimensions are the mechanism to capture these classifications (customer groups, item groups, salesperson, region). To configure reporting dimensions properly, the following steps are required:

Set up dimensions

Before using any dimensions, you must define them in the Dimensions page. This is where new entries such as Customer Group, Item Group, Salesperson, and Region are created.

Correct action: Create a new entry on Dimensions.

Configure global dimensions

Business Central allows two global dimensions that become available on all transaction lines and entries. These are the most used reporting breakdowns.

Since the company must always report sales by customer and item, these should be set as global dimensions.

Correct action: Change global dimensions on General Ledger Setup.

Configure shortcut dimensions

Shortcut dimensions (up to 8) are additional reporting dimensions that can be made available for entry on journals, documents, and transactions. These are perfect for Region and Salesperson requirements.

Correct action: Choose a shortcut dimension code on General Ledger Setup.

This setup ensures reporting can directly answer the business questions in financial results and enable analysis across Customer Groups, Item Groups, Salespeople, and Regions.

Microsoft Learn References

Work with Dimensions

Set Up Dimensions

General Ledger Setup – Global and Shortcut Dimensions

Analysis by Dimensions

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

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