MB-800 Practice Questions

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 correct solution to meet the company ' s order processing requirements involves two key components: the type of workflow to be created and the engine that will power it.

A.  

Create a purchase order approval workflow: This is a core component of most order processing systems. A purchase order approval workflow automates the process of submitting purchase orders for approval, sending notifications to the appropriate approvers, and ensuring that all orders comply with company policies. This is a common requirement to control spending and maintain an audit trail.

D.  

Use Power Automate as the engine for the workflow: Power Automate (formerly Microsoft Flow) is a powerful, cloud-based service that allows you to create automated workflows and connect various applications and services. It is the modern and highly versatile solution for creating complex and customized workflows that go beyond the basic capabilities of many built-in systems, including those in Business Central. While Business Central has a native workflow engine (as mentioned in option C), Power Automate is the recommended solution for more robust and integrated order processing workflows, especially when they need to interact with multiple systems or require advanced logic.

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

Comprehensive Detailed Explanation

In Business Central, financial reporting is built from several components:

Row definition

Used to define which accounts or statistical accounts appear as rows in the financial report.

Since Headcount and Square Footage are statistical accounts (non-financial data tracked for reporting), they must be added via Row definition.

G/L account categories

Used to structure the income statement and balance sheet into financial categories such as Income, COGS, Assets, Liabilities.

The requirement states: “The financial report structure must map to account categories.”

Therefore, Income, Retail must be configured using G/L account categories.

Financial Report page

Used to assemble and present the report, combining row definitions, column definitions, and filters.

Accounts Receivables, Wholesale is a financial reporting output that must be displayed using the Financial Report page where the actual data is gathered.

Why not Column definition?

Column definitions control time periods (month, quarter, year, variance, etc.) but are not needed for these particular requirements.

Microsoft Learn references

Financial Reporting in Business Central

Set Up Row and Column Definitions

G/L Account Categories

The requirement is to resolve the order entry issue:

“Customers often reorder the same items with similar quantities. The system must be configured to ask the user if recurring lines should be added to sales orders.”

Business Central has Standard (Recurring) Sales Lines functionality to address this.

Configure standard sales lines → Add items and quantities

Standard sales lines define templates of frequently ordered items and their quantities.

When configuring these, you specify which items and quantities belong to the recurring order.

This resolves the need to avoid retyping common order combinations.

Add recurring sales lines to customers → Set insert on orders to Always Ask

On the Customer Card, you assign the standard sales lines and configure how they should be inserted when creating sales orders.

The setting Always Ask prompts the user each time an order is created for that customer, allowing them to choose whether to insert the recurring sales lines.

This satisfies the requirement to “ask the user if recurring lines should be added.”

Why not other options?

Add valid from and to dates – Useful for time-limited campaigns, but not mentioned in the requirement.

Set insert on quotes to Automatic – Applies to sales quotes, not orders. The requirement specifically concerns sales orders.

Microsoft Learn references

Set Up Standard Sales and Purchase Lines

Assign Standard Sales Lines to Customers

FIFO is a widely used costing method where the oldest inventory items are sold first. This is a common and straightforward method for valuing inventory.

Automatic cost adjustment is a crucial setting for resolving inventory reconciliation issues. When this is enabled, Business Central automatically adjusts the cost of goods sold (COGS) to match the actual cost of the inventory. This helps prevent discrepancies between the inventory sub-ledger and the general ledger, ensuring that the financial data is accurate.

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

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.

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