Free Microsoft MB-800 Practice Test Questions MCQs

Explanation:
When processing a special order that requires a prepayment, the user must first create the sales order. The next step is to specify the prepayment percentage and the specific payment terms that apply to that prepayment. Once the sales order is correctly configured with these details, the system can generate and post the prepayment invoice to send to the customer.

Correct Sequence:
Create a sales order.

Enter 25 in the Prepayment % field.

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

Post and print the prepayment invoice.

Explanation of Correct Options:
Create a sales order: This is the foundational step. All transactions, including special orders and prepayments, must begin with a sales order document that records the customer, items, and quantities.

Enter 25 in the Prepayment % field: Once the sales order is created, the user must define the amount the customer needs to pay upfront. In this case, a 25% prepayment is required, so this percentage must be entered on the sales order.

Enter the code for due on receipt in the prepayment payment terms code: Prepayments typically require immediate payment. Setting the prepayment payment terms to "due on receipt" ensures the invoice generated will require payment right away, which is standard for a deposit.

Post and print the prepayment invoice: The final step in this part of the process is to generate the formal invoice for the prepayment amount. Posting it makes it a financial transaction, and printing it provides a document to send to the customer.

Why other actions are incorrect for this sequence:

Post and print the invoice: This action would post the final sales invoice for the entire order. This is done much later in the process, only after the items have been shipped and the prepayment has been applied.

Enter 15 in the Prepayment % field: This is an alternative percentage. The scenario specifically requires a 25% prepayment, so entering 15% would be incorrect.

Enter the code for net 30 in the prepayment payment terms code: "Net 30" means the customer has 30 days to pay. This is not appropriate for a prepayment, which is required before the goods are shipped or the service is fully delivered.

Reference:

Microsoft Learn: Set Up Prepayments

Microsoft Learn: Create Prepayment Invoices

Explanation:
This question tests your knowledge of which Microsoft integration tools connect with Business Central to fulfill specific business requirements. Each requirement maps to a specific integration that provides the most efficient and native solution for that particular business need.

Customer Requirement 1: Customer email collaboration

Correct Option: Business Central Outlook add-in

Explanation:
The Business Central Outlook add-in allows users to work with Business Central data directly from their email. For customer email collaboration, this integration enables salespeople to view customer details, convert emails to opportunities, and send quotes without leaving Outlook, streamlining communication and data entry.

Incorrect Options:

Business Central app for Teams: While useful for collaboration, it's more focused on chat-based sharing and approvals rather than direct email management.

Word template: Used for document formatting, not email collaboration.

Power Automate: Can automate workflows but isn't the primary tool for direct email collaboration with customers.

Customer Requirement 2: Sales team collaboration

Correct Option: Business Central app for Teams

Explanation:
The Business Central app for Microsoft Teams enables sales teams to share, review, and edit Business Central data within Teams conversations. Team members can collaborate on customer records, sales documents, and approvals in real-time without switching applications, making it ideal for sales team collaboration.

Incorrect Options:
Business Central Outlook add-in: Primarily for individual email management, not team-based collaboration.

Word template: Used for document creation, not team collaboration.

Power Automate: Automates processes but doesn't facilitate real-time team collaboration.

Customer Requirement 3: Customer notifications for sales campaign

Correct Option: Power Automate

Explanation:
Power Automate (formerly Microsoft Flow) connects Business Central to various communication channels. For sales campaign notifications, it can automate sending personalized emails, SMS, or Teams messages to customers based on campaign triggers, ensuring timely and consistent outreach without manual effort.

Incorrect Options:

Business Central Outlook add-in: Requires manual action within email, not automated campaign notifications.

Business Central app for Teams: Used for internal collaboration, not automated customer communications.

Word template: Used for document formatting, not sending notifications.

Reference:

Microsoft Learn: Business Central and Outlook Integration

Microsoft Learn: Business Central App for Teams

Microsoft Learn: Using Power Automate with Business Central

Explanation:
This question tests your understanding of how different report configuration components in Business Central are used to build financial reports. Each report description requires specific configuration elements to properly display the requested data in the financial report.

Report Description 1: Headcount

Correct Configuration: Row definition

Explanation:
A row definition in financial reporting determines which general ledger accounts or calculations appear on each line of the report. For a headcount report, the row definition would specify the specific accounts or dimensions where employee data is tracked, defining what information appears in each row of the report.

Incorrect Options:

Column definition: Defines time periods or data types across columns, not the specific data rows.

Financial Report page:This is the final report view, not a configuration element.

G/L account categories: These organize accounts but don't create the report structure itself.

Report Description 2: Square Footage

Correct Configuration: Row definition

Explanation:
Square footage reporting requires defining which accounts or dimensions contain facility and space data. The row definition is where you specify these line items, such as different buildings, departments, or cost centers, ensuring the report displays the correct square footage information by location or cost center.

Incorrect Options:

Column definition: Defines time periods across columns, not the row content.

Financial Report page: This is the output view, not the configuration.

G/L account categories: Organizes accounts but doesn't build report rows.

Report Description 3: Income, Retail

Correct Configuration: G/L account categories

Explanation:
G/L account categories in Business Central group similar accounts for financial reporting. For an income report focused on retail operations, using account categories allows you to quickly pull all retail-related income accounts that have been properly categorized, ensuring comprehensive and accurate income reporting without manually selecting individual accounts.

Incorrect Options:

Row definition: Can be used but account categories provide more efficient grouping.

Column definition: Defines time periods, not account groupings.

Financial Report page: This is the output, not the configuration source.

Report Description 4: Accounts Receivables, Wholesale

Correct Configuration: G/L account categories

Explanation:
Accounts receivable reporting for wholesale customers benefits from G/L account categories that have been properly set up to distinguish wholesale receivables from other receivable types. The account categories organize these specific customer groups, making it easier to generate accurate reports showing only wholesale-related accounts receivable balances.

Incorrect Options:

Row definition: Can specify accounts but categories provide better organization.

Column definition: Defines time periods, not account segmentation.

Financial Report page: This is the final report, not the configuration.

Reference:
Microsoft Learn: Financial Reporting Overview

Microsoft Learn: Row Definitions in Financial Reporting

Microsoft Learn: Column Definitions in Financial Reporting

Microsoft Learn: G/L Account Categories

Microsoft Official MB-800 Study Guide: Financial Report Setup

Explanation:
The question tests your ability to configure Inventory Setup in Dynamics 365 Business Central to establish the default costing method for new items and to fix a common inventory reconciliation problem (where inventory costs do not properly flow to the general ledger or related entries remain unadjusted). The two correct choices are setting the default costing method to FIFO and enabling automatic cost adjustment to ensure cost changes are propagated and reconciliation issues are resolved automatically.

Correct Options:

FIFO (Set default costing method)
FIFO (First-In, First-Out) assumes the oldest purchased items are sold or consumed first. Setting it as the default in Inventory Setup means every new item card will automatically use FIFO for cost calculation unless manually changed. This provides transparent, entry-sequence-based valuation and is a common requirement in many scenarios involving physical flow of goods or regulatory needs.

Automatic cost adjustment (Resolve inventory reconciliation issue)
This setting (often with a timeframe like Day, Week, Month, or Always) automatically adjusts and forwards cost changes from purchase receipts, revaluations, or invoice postings to all affected outbound entries (sales, consumption, assembly). It directly resolves reconciliation differences between item ledger entries and value entries, ensuring accurate G/L postings without manual Run Cost – Post Inventory Cost to G/L jobs.

Incorrect Options:

Average — This method calculates a running weighted average cost after each receipt. It is suitable for items with similar purchase prices but does not match the question if FIFO is the intended or required default costing method for the business scenario.

Standard — Standard costing uses a fixed cost set on the item card (ideal for variance analysis in manufacturing). It does not automatically handle cost variances for reconciliation purposes in the same way automatic adjustment does for actual costing methods like FIFO or Average.

Automatic cost posting — This controls whether inventory transactions post costs directly to G/L accounts at the time of posting (vs. batch posting later). While useful for real-time finance integration, it does not address the propagation of cost changes between item entries, which is the root cause of most reconciliation issues.

Prevent negative inventory — This blocks posting transactions that would drive inventory below zero. It is a quantity control setting, not related to cost reconciliation or valuation method issues.

Reference:

Microsoft Learn – Set Up Inventory

Microsoft Learn – Manage Inventory Costs

Microsoft Learn – Design Details: Inventory Costing

Explanation:
This question tests your understanding of how payment terms are configured in Business Central using date formulas. Different customer types (retail vs. wholesale) require different due date and discount date calculations based on standard business practices.

Customer Payment Term 1: Due Date Calculation for retail customer payment term

Correct Option: 15

Explanation:
Retail customers typically have shorter payment periods. In Business Central, a numeric value without "D" represents a specific day of the month. For retail payment terms, entering "15" means the payment is due on the 15th day of the month, which is a common retail billing practice where all invoices are due on a specific date rather than a set number of days after invoice.

Incorrect Options:

2: Too early in the month for standard retail terms.

10: Possible but less common than mid-month terms.

25: Late in the month, more typical for wholesale or corporate terms.

Customer Payment Term 2: Discount Date Calculation for wholesale customer payment term
Correct Option: 10D

Explanation:
Wholesale customers often receive early payment discounts. In Business Central, "10D" means the discount is available if payment is made within 10 days of the invoice date. This represents a standard "2/10, net 30" type term where customers get a discount for paying within 10 days.

Incorrect Options:

100: Too large; not a standard discount period.

15D: Possible but less common than 10-day discount periods.

30D: This would be the full payment term, not the discount period.

Customer Payment Term 3: Due Date Calculation for wholesale customer payment term

Correct Option: 30D

Explanation:
Wholesale customers typically receive longer payment periods. In Business Central, "30D" means the payment is due 30 days after the invoice date. This represents standard wholesale terms where business customers need additional time to process payments through their accounts payable departments.

Incorrect Options:
0D: Would require immediate payment, not appropriate for wholesale.

10D: Too short for wholesale terms; more like retail or cash terms.

15D: Still too short for standard wholesale payment terms.

Customer Payment Term 4: Due Date Calculation of wholesale customer payment term

Correct Option: 30D

Explanation:
Consistency is important in payment term configuration. For wholesale customers, standard due date calculations should be uniform. Using "30D" across wholesale payment terms ensures that all wholesale invoices follow the same payment expectations, making it easier for customers to manage their payables and for your company to forecast cash flow.

Incorrect Options:

0D: Would require immediate payment, not suitable for wholesale.

10D: Too short for wholesale business customers.

15D: Still too restrictive for most wholesale relationships.

Reference:

Microsoft Learn: Set Up Payment Terms

Microsoft Learn: Payment Terms in Business Central

Microsoft Official MB-800 Study Guide: Accounts Payable and Receivable Setup

Explanation:
This question tests your knowledge of how recurring sales lines are configured in Business Central to streamline order entry. Different configuration settings control how recurring lines behave when creating sales documents, helping resolve specific order entry issues.

Action 1: Configure standard sales lines

Correct Configuration: Add items and quantities

Explanation:
Configuring standard sales lines requires defining what items and quantities should appear on recurring sales documents. Adding items and quantities is the foundational step that establishes the actual product and amount information that will be reused when creating future sales orders or quotes for the customer.

Incorrect Options:

Add valid from and to dates: These define the effective period, not the actual line content.

Set insert on orders to Always Ask: This controls behavior, not the line configuration itself.

Set insert on quotes to Automatic: This controls behavior, not the line configuration.

Action 2: Add recurring sales lines to customers

Correct Configuration: Add valid from and to dates

Explanation:
When adding recurring sales lines to customers, setting valid from and to dates ensures the recurring lines are only available during specific time periods. This is essential for seasonal products, time-limited contracts, or promotional items, preventing incorrect orders outside the valid date range.

Incorrect Options:

Add items and quantities: This is done during configuration, not when assigning to customers.

Set insert on orders to Always Ask: This is a behavior setting, not a date range.

Set insert on quotes to Automatic: This is a behavior setting, not a date range.

Additional context on why other configurations are not used in these actions:

Set insert on orders to Always Ask: This configuration determines whether the system prompts users to insert recurring lines when creating sales orders. It's a behavior setting applied during or after configuration, not the primary action for configuring lines or adding them to customers.

Set insert on quotes to Automatic: Similar to the above, this controls whether recurring lines are automatically inserted when creating sales quotes. This is a system behavior setting rather than a content or validity configuration.

Reference:
Microsoft Learn: Recurring Sales Lines

Microsoft Learn: Standard Sales Lines in Business Central

Microsoft Official MB-800 Study Guide: Sales Order Processing

Explanation:
When addressing costing adjustment concerns, the proper sequence involves first defining the time periods for inventory valuation, then ensuring costs are updated, and finally closing the periods to prevent further changes. This systematic approach ensures accurate cost accounting and inventory valuation.

Correct Sequence:
Set up inventory periods.

Run the Adjust Cost – Item Entries batch job.

Run Post Inventory Cost to G/L.

Close the inventory period.

Explanation of Correct Options:

Set up inventory periods:
This is the foundational step. Inventory periods define specific time frames (like months or quarters) during which inventory transactions can be posted. Setting them up first establishes the boundaries for cost adjustment and inventory valuation activities, ensuring that costs are managed within defined timeframes.

Run the Adjust Cost – Item Entries batch job:
After inventory periods are established, this batch job adjusts item costs based on updated purchase prices, manufacturing variances, or other cost changes. Running this ensures all item entries reflect accurate costs before posting to the general ledger, preventing valuation errors.

Run Post Inventory Cost to G/L:
Once item costs are adjusted, this action posts those inventory value changes to the general ledger accounts. This step ensures that the financial records accurately reflect the true cost of inventory, maintaining consistency between inventory sub-ledgers and the general ledger.

Close the inventory period:
The final step is closing the inventory period. This prevents any further posting or changes to inventory transactions within that period, locking the costs and values for financial reporting. Closing the period ensures historical data remains accurate and unalterable.

Why other actions are incorrect for this sequence:

Create an inventory revaluation journal:
While useful for manually changing inventory values, this is typically used for specific adjustments rather than the standard periodic cost adjustment process. The batch job handles most routine adjustments automatically.

Set up accounting periods:
Although related to financial reporting, accounting periods are broader than inventory-specific periods. For costing adjustments, inventory periods are the primary control mechanism, and they can be set up independently of accounting periods.

Close the accounting period:
This is a broader financial closure step that happens after inventory periods are closed and all inventory costs are posted. It comes later in the overall month-end closing process, not during the inventory-specific costing adjustment sequence.

Reference:

Microsoft Learn: Inventory Periods

Microsoft Learn: Adjust Item Costs

Microsoft Learn: Post Inventory Costs to General Ledger

Microsoft Official MB-800 Study Guide: Costing Methods and Inventory Valuation

Explanation:
This question tests your knowledge of how to handle corrections to posted sales invoices in Business Central based on payment status and whether the original invoice came from a sales order. Different actions are appropriate depending on these factors to ensure accurate accounting and customer records.

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

Correct Action: Correct

Explanation:

The Correct action in Business Central is specifically designed for posted invoices that haven't been paid and originated from a sales order. This function creates a corrective document that reverses the original invoice while maintaining the sales order link, allowing for edits and re-posting without manually creating credit memos or returns.

Incorrect Options:

Cancel: May not maintain proper audit trail or sales order linkage.

Sales return order: Used for physical returns, not just invoice corrections.

Create corrective credit memo: More manual process; Correct function automates this.

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

Correct Action: Create corrective credit memo

Explanation:

When an invoice wasn't created from a sales order (such as a general journal invoice), the Correct function isn't available. In this case, you must manually Create a corrective credit memo to offset the original invoice, then create a new invoice with the correct information. This ensures proper accounting despite the lack of sales order linkage.

Incorrect Options:


Correct:Only works for invoices originating from sales orders.

Cancel: Doesn't provide proper credit functionality for non-order invoices.

Sales return order: Designed for physical returns, not invoice corrections.

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

Correct Action: Sales return order


Explanation:
When an invoice has been paid, a Sales return order is the appropriate document. This creates a credit memo that can be applied to the paid invoice, and if no warehouse documents are required (no physical return), the process can be completed without warehouse entries. The return order properly handles the financial reversal for paid invoices.

Incorrect Options:

Correct: Only works for unpaid invoices.

Cancel: Not designed for paid invoice scenarios.

Create corrective credit memo: This is a result, but the process starts with sales return order.

Why "Cancel" is not used in these scenarios:

The Cancel action is typically used for unposted documents or in specific circumstances not covered by these scenarios. It doesn't provide the same audit trail and accounting accuracy as the other correction methods for posted invoices.

Reference:

Microsoft Learn: Correct or Cancel Posted Sales Invoices

Microsoft Learn: Process Sales Returns and Credit Memos

Microsoft Official MB-800 Study Guide: Sales Invoice Processing

Explanation:
The Calc. inv. discount (Calculate Invoice Discount) setting in Sales and Receivables Setup controls whether the system automatically calculates invoice discounts based on the total invoice amount. When enabled, this configuration allows sales documents to apply discounts when invoice totals meet predefined discount tiers set up for customers.

Incorrect Options:

Credit warnings: Related to credit limit monitoring, not discounts.

Discount posting: This controls how discounts are posted to G/L accounts.

Stockout warnings: Related to inventory availability, not discounts.

Sales and Receivables Setup Area 2: Credit limits

Correct Configuration: Credit warnings

Explanation:
Credit warnings is the configuration in Sales and Receivables Setup that controls how the system responds when a customer exceeds their credit limit. Options include warnings only, blocking further orders, or requiring approval. This setting ensures proper credit management by alerting users before processing orders that would exceed customer credit limits.

Incorrect Options:

Calc. inv. discount: Related to discount calculations, not credit management.

Discount posting: Controls G/L posting of discounts.

Stockout warnings: Related to inventory availability alerts.

Why other configurations are not used in these setup areas:

Discount posting:
This configuration belongs in the General Ledger Setup or specific posting group setups, as it determines which accounts receive the discount amounts when posted. It's not a direct setting in the Sales Discounts section.

Stockout warnings:
This configuration is primarily managed in Inventory Setup or item card settings, controlling whether users receive alerts when attempting to sell items that are out of stock.

Reference:

Microsoft Learn: Sales and Receivables Setup

Microsoft Learn: Set Up Invoice Discounts

Microsoft Learn: Set Up Credit Limits

Explanation:
To track revenue by market in retail store customer cards in Dynamics 365 Business Central, configure default dimensions on the customer cards (or via defaults for the customer table). Assign the Market dimension code to categorize sales transactions by market segment (e.g., Retail, Treats). Select the specific Sales value (likely representing the retail market) and use Same code posting to enforce that every transaction for these customers automatically uses this fixed market value—no user selection or variation allowed—ensuring consistent revenue tracking by market without manual entry errors.

Correct Options:

Market (Assign the dimension code)
The Market dimension is specifically designed to categorize customers/transactions by market type (e.g., Retail store customers vs. other segments like Breeder or Treats). Assigning Market as the dimension code on retail store customer cards tags all related sales postings (invoices, orders) with this dimension, enabling accurate revenue analysis and reporting filtered or grouped by market in financial reports or analysis views.

Sales (Assign the dimension value code)
Sales is the appropriate dimension value for retail store customers, representing the retail market segment. Setting this value ensures every sales transaction from these customers is automatically tagged with the Sales market value, allowing precise tracking of revenue generated from retail stores separately from other markets (e.g., wholesale or breeder).

Same code (Select a value posting)
Same code posting rule forces the fixed dimension value (Sales) on every transaction involving these customers. It prevents users from changing or leaving it blank, guaranteeing consistent and reliable market-based revenue tracking. This is ideal when all retail store customers belong to the same market category and variation is not desired.

Incorrect Options:

Location —
This dimension typically tracks physical sites (e.g., stores, warehouses) rather than market segments. It would not correctly categorize revenue by market type like Retail vs. other customer groups.

Department —
Department dimension is used for internal organizational units (e.g., Sales dept, Admin). It does not align with tracking external revenue by market/customer segment.

Product Category —
This would categorize revenue by item types/categories, not by customer market. It is irrelevant for market-based tracking on customer cards.

Blank —
Blank posting allows any (or no) dimension value, leading to inconsistent or missing market tags on transactions, defeating the purpose of reliable revenue tracking by market.

No code —
This prohibits any dimension value for Market, blocking market tagging entirely and preventing revenue analysis by market.

Code mandatory —
Requires a value but allows user selection of any valid market value (not fixed to Sales). This risks inconsistency if users pick different markets for retail customers.

Reference:
Microsoft Learn – Work with dimensions to track and analyze data

Microsoft Learn – Troubleshoot and correct dimensions

Microsoft Learn – Enum "Default Dimension Value Posting Type"