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

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.

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.

The requirement is: “You need to configure retail store customer cards to track revenue by market.”

In Business Central, to track revenue by customer market (Retail, Veterinarian, Breeder), you configure default dimensions on the Customer Card.

Assign the dimension code → Market

The business wants to analyze revenue by Market (Retail, Veterinarian, Breeder).

Therefore, the dimension code must be Market.

Assign the dimension value code → Retail

For this specific setup, the customer is a retail store, so the dimension value must be Retail.

Select a value posting → Same code

To ensure that every posting for this customer always carries the same dimension value, use Same Code.

Other options:

Blank = no default dimension.

No code = optional dimension.

Code mandatory = requires entry but allows flexibility in values.

Since we want strict tracking by a fixed market (Retail), Same code is correct.

This ensures that every transaction posted for the customer will always have Market = Retail, enabling accurate revenue tracking.

Microsoft Learn references:

Work with Dimensions

Set Up Default Dimensions

Dimension Value Posting Options

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

The scenario requires configuring Business Central to meet sales department needs:

Sales discounts

Requirement: “Discounts must post to a unique general ledger (G/L) account.”

In Business Central, this is managed through the Discount Posting field in Sales & Receivables Setup.

When enabled, the system posts line discounts and invoice discounts to dedicated G/L accounts instead of combining them with revenue.

This ensures transparency and compliance with accounting’s requirement to track discounts separately.

Correct match: Sales discounts → Discount posting

Credit limits

Requirement: “The sales department should receive a warning when entering the order if a customer is over their credit limit.”

In Business Central, this behavior is controlled by Credit Warnings in the Sales & Receivables Setup.

This setup defines whether to warn the user, block posting, or allow posting when the customer’s balance exceeds the defined credit limit.

Correct match: Credit limits → Credit warnings

Why not the other options?

Calc. inv. discount – Controls whether invoice discounts are automatically calculated, but not relevant here.

Stockout warnings – Alerts when an item has insufficient inventory; unrelated to discounts or credit limits.

Microsoft Learn references

Set Up Sales and Receivables

Discount Posting setup – posting discounts to G/L accounts.

Credit Warnings setup – warnings and blocking options.

Query successful

Sales Invoice Correction

Based on the scenarios, here is the correct action for each:

Scenario 1: Use this action when the posted invoice has not been paid and the original invoice was posted from a sales order.

Action: Correct

The Correct action is specifically designed for this scenario. It automatically creates a new sales order, reverses the original posted invoice, and copies the original lines to the new order. The new sales order is then ready for editing, allowing you to make corrections and post it again.

Scenario 2: Use this action when the posted invoice has not been paid and the original invoice was not posted from a sales order.

Action: Cancel

The Cancel action is used when the invoice wasn't created from a sales order. It creates a credit memo to fully reverse the posted invoice. This effectively cancels the invoice without needing to go through a new sales order process, as no original sales order exists.

Scenario 3: Use this action when the posted invoice has been paid and warehouse documents are not required.

Action: Create corrective credit memo

The Create corrective credit memo action is the appropriate choice when the invoice has already been paid. Since the payment has been applied, you can't simply "correct" or "cancel" the invoice directly. Instead, you create a credit memo that can then be applied against the payment, effectively reversing the transaction. This action is also used when warehouse documents are not necessary, as a separate sales return order with warehouse processes is not required.

The requirement is:

“Customer revenue must be posted to separate general ledger (G/L) accounts based on customer type. The G/L account must have subcategories for wholesale and retail revenue.”

In Business Central, sales revenue posting is controlled by the General Posting Setup, which combines two posting groups:

General Business Posting Groups (A)

These represent the type of customer or vendor (for example, WHOLESALE or RETAIL).

They allow you to differentiate revenue by customer type.

General Product Posting Groups (C)

These represent the type of item or resource being sold (for example, FINISHED GOODS, SERVICES).

They allow you to map revenue to the correct accounts by product line or category.

The combination of General Business Posting Group + General Product Posting Group determines which Revenue G/L Account is used.

Why not the others?

B. Customer posting groups – Control AR control accounts, not revenue.

D. Bank account posting groups – Used for bank transactions, not revenue.

E. Inventory posting groups – Control inventory accounts and adjustments, not revenue.

Microsoft Learn references

Posting Groups in Business Central

Set Up General Posting Groups

Comprehensive Detailed Explanation

The requirement: “You need to train users on how to process a special order for an established customer.”

From the case study:

“Special orders from new customers have a 25% prepayment. Established customers have only a 15% prepayment.”

Prepayments must be invoiced before the final invoice is posted.

Step-by-step process in Business Central:

Create a sales order

The user begins by creating a sales order for the special order.

Enter 15% in the Prepayment % field

Since this is for an established customer, the prepayment percentage is 15%.

The Prepayment % field on the sales order line or header controls how much must be prepaid before the order can be processed.

Enter the code for due on receipt in the prepayment payment terms code

Prepayments are typically due immediately. The code for “due on receipt” ensures that the prepayment invoice requires immediate payment.

Post and print the prepayment invoice

This generates the prepayment invoice for the customer and ensures that prepayment is received before delivery.

Why not “Enter the code for net 30 in the prepayment payment terms code”?

That applies to wholesale customer regular payment terms, not to prepayments. Prepayments are due immediately.

Why not 25%?

25% prepayment applies to new customers. For established customers, the requirement specifies 15%.

Microsoft Learn references

Set Up Prepayments

Process Sales Prepayments

Create Sales Orders with Prepayments