Pass Using MB-800 Exam Dumps

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 AR users reported an issue about reconciling AR subledger to the G/L. In Business Central, subledger control accounts (like Accounts Receivable and Accounts Payable) must not be posted to directly; they should only be posted through transactions (invoices, payments).

If Direct Posting = Yes, users can post directly into AR or AP control accounts, which causes reconciliation issues.

To prevent this, you set Direct Posting = No on the G/L Account Card for control accounts.

Why not others:

A. Switch Blocked on the Customer Card → Blocks transactions but does not solve reconciliation issues.

B. Switch Direct Posting on the G/L Account Card to Yes → Makes the issue worse.

C. Switch Blocked on the G/L Account Card to Yes → Prevents all postings, even system ones, which is incorrect.

Correct answer: D. Switch Direct Posting on the G/L Account Card to No

To integrate Power BI with Dynamics 365 Business Central, you need to make Business Central data available to Power BI. The standard and recommended method is to use OData web services.

Option A: Enable the Power BI Embedded service (Incorrect)

This allows embedding Power BI reports inside Business Central but does not expose Business Central data to Power BI.

Option B: Publish the OData web services for the required entities (Correct)

Power BI can consume Business Central data through OData feeds or APIs.

You expose the required data by publishing OData web services in Business Central (e.g., Customers, Vendors, G/L Entries).

Once published, you connect to these OData URLs from Power BI Desktop to build reports.

Option C: Select the Share action in Business Central (Incorrect)

The Share action is used for sharing reports or documents within Business Central, not for exposing data to Power BI.

Option D: Create a user account in Business Central for Power BI access (Incorrect/Not sufficient)

While a licensed user account is needed to authenticate, just creating a user does not expose data. You still need OData or APIs.

Thus, the correct way to expose Business Central data to Power BI is by publishing OData web services.

Microsoft Learn References

Connect to Business Central data from Power BI

Publish a Web Service

Using OData in Business Central