Free Microsoft MB-800 Practice Exam with Questions & Answers | Set: 4

The requirement is:

“You need to train users on order processing requirements and how to process purchase invoices created from combined receipts.”

From the case study requirements:

“The company must be able to combine multiple purchase receipts into one vendor invoice.”

“Fully invoiced POs must not appear on the PO list page.”

“Posted vendor invoices must be reverted when damages are reported or a product is returned to the vendor.”

To meet these requirements:

Correct or cancel unpaid purchase invoices (B)

Users need to know how to reverse or correct vendor invoices that were created from combined purchase receipts if errors or issues occur.

Business Central provides Correct and Cancel actions for unpaid purchase invoices, ensuring proper reversal and audit trail.

Delete POs that are fully invoiced (C)

Once a PO has been fully invoiced (and all lines are closed), it should be deleted so it no longer appears in the purchase order list.

This keeps the purchase order list clean and ensures users don’t attempt to reuse completed POs.

Why not the others?

A. Create a purchase credit memo – This is used for vendor returns, not directly tied to the process of combined purchase receipts training.

D. Create recurring purchase lines – Used for repeated purchases of the same items (like monthly subscriptions or utilities), not relevant to combining receipts into one invoice.

Microsoft Learn references

Correct or Cancel Unpaid Purchase Invoices

Work with Purchase Orders

Combine Receipts on a Single Invoice

The requirement is:

“You need to configure the system to post to the receivables account for wholesale customers.”

From the case study, the G/L posting accounts required are:

Retail Receivables = 13100

Wholesale Receivables = 13200

In Business Central:

Customer Posting Groups (B)

Customer Posting Groups are used to map customers to specific Receivables G/L accounts.

You typically create separate posting groups, e.g., "RETAIL" and "WHOLESALE," and assign them to customers based on type.

This ensures postings go to the correct control account.

Receivables account 13200 (D)

For wholesale customers, the posting group must be configured to point to 13200 (Wholesale Receivables).

Why not the others?

A. Receivables account 13100 – This is for retail customers, not wholesale.

C. General Posting Setup – This setup manages how transactions post based on combinations of General Business Posting Groups and General Product Posting Groups, but it does not control receivables accounts.

E. General Business Posting Groups – These are used for revenue, COGS, and VAT postings, not receivables control accounts.

Microsoft Learn references

Posting Groups in Business Central

Set Up Customer Posting Groups

The requirement is: “Customer pricing is determined by the customer market type (Retail, Veterinarian, Breeder). Each customer is associated with only one market type.”

A. Assign the Customer Price Group code on the customer card → Correct, because each customer must be tied to its market type via a Customer Price Group.

C. Create a Sales Price List by using the assign-to type of Customer Price Group → Correct, because pricing and discounts should be managed at the group level, not per individual customer, ensuring easier maintenance.

E. Create Customer Price Groups that allow line discounts → Correct, because discounts are offered by item, brand, or product category, and must flow to sales lines automatically.

Incorrect options:

B. Exclude line discounts → Opposite of requirements.

D. Create a Sales Price List for the customer → Not scalable; must be done by group, not individual customer.

Correct answers: A, C, E

The Accounts Receivable (AR) team often needs to correct payment applications when cash is applied incorrectly. In Business Central, unapplied entries can be corrected in several ways:

From the Customer Card, under Navigate > Ledger Entries, users can select entries and use the Unapply Entries action.

From the Customer Ledger Entries page, users can directly select a posted application and choose Unapply Entries.

The Detailed Customer Ledger Entries page is used for analysis and shows how entries were applied, but the actual “Unapply” action is not typically performed here (it is read-only in terms of correction).

“Apply entries” can be done from Detailed Customer Ledger Entries, but unapplies are performed from Customer or Customer Ledger Entries.

Correct answers: A and C

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

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

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.

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.