Microsoft Microsoft Dynamics 365 Business Central Functional Consultant MB-800 Exam Dumps: Updated Questions & Answers (October 2025)

To manage multiple purchase prices for the same item depending on the vendor, you can configure:

Item Card (B): At the item level, you can define vendor-specific purchase prices and assign conditions such as starting date, minimum quantity, currency, etc.

Vendor Card (E): Vendor-specific purchase prices can also be linked, enabling the system to pull correct pricing when creating purchase orders.

In Dynamics 365 Business Central, the General Journal Reconciliation feature allows reconciliation of ledger entries against G/L accounts (often bank, clearing, or control accounts).

To include a G/L account in the general journal reconciliation window:

You must enable the Reconciliation Account field on the G/L Account Card.

This setting flags the account as reconcilable, so it appears in the reconciliation process.

Why not the others?

B. Direct Posting field → Controls whether you can post directly to the account, not related to reconciliation.

C. Bank Account Posting Group → Links bank accounts to G/L accounts, but the reconciliation flag still must be set.

D. Create a new payment reconciliation journal → Used for bank statement reconciliation, not general ledger account reconciliation.

Microsoft Learn Reference

Reconcile General Ledger Accounts in Business Central

In Dynamics 365 Business Central, default dimensions ensure that a required dimension is automatically suggested or enforced when creating transactions for entities such as Customers, Vendors, G/L Accounts, etc.

Step-by-step process to make a dimension mandatory for Customers:

Select Account Type Default Dim.

Navigate to Search → Default Dimensions.

Here you define which account type (Customer, Vendor, Item, etc.) will be linked to dimensions.

Select the relevant table ID.

Choose the entity (Customer table ID = 18) for which the default dimension setup will apply.

On the Dimensions page, select the required dimension.

For example, "DEPARTMENT" or "REGION."

This ensures the dimension is linked to the Customer entity.

Leave the dimension value blank, and in the Value Posting column, select Code Mandatory.

This ensures that a transaction cannot be posted without a dimension value being entered.

Leaving the dimension value blank enforces flexibility (any value allowed), while Code Mandatory ensures it is always required.

Other options not correct for this requirement:

Define the dimension value and set it in Value Posting → would automatically assign a fixed dimension value, but the requirement is just to make it mandatory, not fixed.

Disable the dimension value from posting → prevents posting, not useful here.

Microsoft Learn References

Set Up Default Dimensions for Customers, Vendors, and Other Accounts

Enforce Dimension Rules with Default Dimensions

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 requirement is:

You have created a role center page (profile) for all users.

Users must not be allowed to personalize the page.

In Dynamics 365 Business Central, personalization and profile management is handled from the Profiles (Role) page. The following steps apply:

A. On the Profiles (Role) page, select the profile and select the User as the default profile option.

Correct: This ensures that the custom role center is the default profile assigned to all users.

B. On the User card, set the status to Disabled.

Incorrect: This would disable the entire user account, not related to personalization.

C. On the Profiles (Role) page, select the profile and select the Show in Role Explorer column.

Incorrect: This only controls whether the profile is shown in the Role Explorer, not personalization rights.

D. On the Profiles (Role) page, select Enable the profile. Disable all other profiles.

Correct: This ensures that only the intended profile is available and enforced for all users.

E. On the Profiles (Role) page, select the profile and select the Disable Personalization option.

Correct: This is the direct control to prevent users from personalizing their Role Center page.

Microsoft Learn References

Create and Manage Profiles (Role Centers)

Personalizing Pages vs Customizing Profiles

Disable Personalization for a Profile

In Dynamics 365 Business Central, the Payment Reconciliation Journal can automatically match imported bank statement lines with open customer/vendor ledger entries. To reduce manual review, you can set up payment matching rules.

The goal here is: "Mark automatically matched payments as not requiring review if they match the highest degree of confidence."

The three most important criteria used to achieve a high-confidence match are:

Statement Amount (A)

Ensures that the bank statement line amount equals the open invoice amount.

This is the strongest indicator of a correct match.

Transaction Date (D)

Ensures the payment date aligns with the posting or due date window.

Helps differentiate between otherwise similar transactions.

Transaction Text (E)

The system uses transaction descriptions/reference text from the bank statement and compares it to invoice/customer reference numbers.

This greatly increases the confidence level of automatic matches.

Why not the others?

B. Account number: Bank account number is already tied to the journal; not typically part of the matching rules.

C. Related-party fields: More relevant to advanced compliance/KYC scenarios, not to standard payment application matching.

Microsoft Learn References

Apply Payments Automatically and Reconcile Bank Accounts

Set Up Payment Application Rules

Simply importing a CSV file is not sufficient to bring in opening balances into Dynamics 365 Business Central because the system requires structured mapping of data to the correct tables (e.g., G/L entries, customer/vendor balances, item journals). CSV import without RapidStart configuration packages or assisted setup does not guarantee correct posting, validations, and relationships. Business Central does not support direct raw CSV imports to ledger tables out of the box.

Outbound email can be configured in Business Central in two ways:

SMTP Mail Setup → Traditional configuration with mail server, port, credentials.

Email Setup Assisted Setup tool → Modern option for OAuth-enabled services (Exchange Online, Microsoft 365, SMTP).

Incorrect options:

B. Business Inbox in Outlook → Used to integrate Outlook add-in for processing documents, not sending emails.

C. Email logging assisted setup → Used for tracking customer interactions, not for sending emails.

When a company has limited funds in Dynamics 365 Business Central and must decide which vendors to pay first, the Vendor Priority functionality in the Suggest Vendor Payments batch job is used.

Here’s how it works:

Set Vendor Priority on the Vendor Card

On each vendor card, you assign a Vendor Priority value.

The lowest number (1) is the highest priority, except for zero, which means no priority defined.

In Dynamics 365 Business Central, once a document such as a Sales Invoice is posted, the general ledger (G/L) entries are created and cannot be directly edited. However, if the mistake is only in the dimension values (such as Department, Project, or Cost Center), there is a specific function available: Correct Dimensions.

Correct Dimensions allows you to change or fix dimension values on already-posted ledger entries without creating new G/L entries.

The correction updates the dimensions on the existing ledger entries for reporting and analysis consistency.

This differs from reversing or reposting transactions, which creates additional entries.

Why not the other options?

A. Edit List → Used to make inline edits to open documents or master data, not for posted ledger entries.

B. Reverse Transaction → Creates reversing entries to correct amounts, but it does not allow fixing dimension values without new entries.

C. Edit in Excel → Used to edit bulk data via Excel integration, but not for changing dimensions on posted entries.

Microsoft Learn References

Correct Dimensions on Posted Entries

Dimensions Overview