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

Based on the provided image, the correct values to select for the customer payment terms are the ones already highlighted.

Due Date Calculation for retail customer payment term:

Select the value 10.

Discount Date Calculation for wholesale customer payment term:

Select the value 10D.

Due Date Calculation for wholesale customer payment term:

Select the value 30D.

Due Date Calculation for wholesale customer payment term:

Select the value 15D.

The requirement is to match each integration requirement with the correct Microsoft integration solution in Business Central.

Customer email collaboration → Business Central Outlook add-inThe Business Central Outlook add-in allows users to create sales documents such as quotes, orders, or invoices directly from Outlook emails. This supports the requirement to create sales orders while collaborating with customers by email.

Sales team collaboration → Business Central app for TeamsThe Business Central app for Teams enables users to view, share, and even edit Business Central data such as customer records while working inside Microsoft Teams chat or channels. This aligns with the requirement to edit customer information while collaborating with the sales team in a group chat.

Customer notifications for sales campaign → Power AutomatePower Automate is designed for automating workflows such as sending notifications, approval requests, or bulk communications. To notify all customers at once about a sales campaign, Power Automate can integrate Business Central data with email or marketing tools.

Why not Word template?

Word templates are mainly used for document formatting and mail merges but do not handle automated notifications at scale. For distributing campaign notifications to multiple customers, Power Automate is the correct tool.

Microsoft Learn references

Business Central and Outlook integration

Use Business Central in Teams

Automate Business Central with Power Automate

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: “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

In BC, invoices can be generated from:

Sales Order Invoicing (D): Post invoices directly from sales orders.

Combine Shipments (A): Consolidate multiple shipments into a single invoice (used for customers who require weekly or monthly invoices).

Get Shipment Lines from Sales Order (B) is incorrect — shipment lines are retrieved in warehouse processing, not for invoicing.

Sales Order Shipping (C) posts shipment only, not invoices.

Get Shipment Lines from Sales Invoice (E) is used for service scenarios but is not the standard sales invoicing process here.

Correct: A and D

Comprehensive Detailed Explanation

The requirement is to configure the system so that sales discounts are visible and tracked correctly in Dynamics 365 Business Central.

Define simultaneous posting → General Ledger Setup

In Business Central, the General Ledger Setup page contains fields that control whether discounts are posted separately or combined with sales postings.

By defining discount posting behavior at the General Ledger Setup level, you ensure consistency across all sales transactions and financial reporting.

Other options (Sales & Receivable Setup, Customer, Item) do not define global simultaneous posting behavior for discounts; they control transaction processing but not the separation of discount postings.

Specify type to post separately → Discount Posting

To show sales discounts separately, you must enable Discount Posting.

This ensures discounts are posted to a dedicated G/L account, rather than being netted off directly against sales.

As a result, financial statements can show both gross sales and discounts given, which is critical for profitability analysis and discount tracking.

The other options in the list:

Invoice Disc. Code → Used to define specific invoice discounts, but not to enforce posting separately.

Special Prices & Discounts → Controls pricing rules but not posting behavior.

Adjust for Payment Disc. → Manages how payment discounts affect invoices, but again, not posting visibility.

With this setup, Wide World Importers can track gross sales, discounts, and net sales transparently in reports, allowing management to analyze the financial impact of discounts.

Microsoft References

General Ledger Setup in Business Central

Discount Posting Field (Post Discounts Separately)

Work with Sales Discounts in Business Central

Correct Answer:

Define simultaneous posting: General Ledger Setup

Specify type to post separately: Discount Posting

This sequence makes sense because you first create the series itself, then define the lines (the actual numbers within the series), and finally define the relationships to link the series to the specific data table (like the Accounts table) where it will be used.

Sequence 2: Using a Configuration Package to Manage Data

This sequence focuses on using a configuration package to manage and update data, which might include fixing issues with existing accounts or importing new ones.

Create a configuration package.

Configure the Vendor Table on the configuration package.

Create the Data template.

While this sequence is plausible, it has a significant flaw: the prompt mentions "Accounts," but this sequence specifically mentions the Vendor Table. If we assume the "Vendor Table" is a placeholder for a generic data table like the Accounts table, the sequence makes sense. You create a package, configure it for a specific table, and then create a data template to import the data into that table.

Sequence 3: Resolving Issues by Defining the Number Series on the Configuration Template

This sequence focuses on resolving issues by directly modifying the configuration template within a configuration package.

Create a configuration package.

Create the Data template.

Define the No. Series on the configuration template.

This sequence is logical for a scenario where you're using a configuration package to manage both data and its associated number series. You first create the package, then create the data template (which is a core component of the package), and finally define the number series on that template to ensure the imported data uses the correct number sequencing.

The scenario describes cash and carry sales, where customers pay immediately at the desk and sales invoices must be posted as paid in full at the time of sale. In Dynamics 365 Business Central, this is achieved by setting Payment Terms that indicate no delay between invoice date and due date.

Why D (Payment Terms = 0D)

The Payment Terms setup in Business Central allows you to define how the Due Date is calculated.

For cash and carry transactions, the invoice is due on the same day (zero days). Setting the Due Date Calculation to 0D ensures that the system always marks invoices as immediately due, reflecting the cash-and-carry business process.

This aligns with requirements: “Invoices must be posted at the cash and carry desk at the time of sale” and “Invoices already paid in full should not appear as outstanding on aging reports.”

Why not A (Payment Service)

Payment Services are used for integration with external services like PayPal or credit card gateways. Wide World Importers does not require a POS or online payment gateway—just simple cash handling at the desk.

Why not B (Direct Debit Mandate)

Direct Debit is used for recurring bank withdrawals (SEPA mandates, subscription-type payments). It does not apply to one-time, immediate cash payments.

Why not C (Payment Method = Bank Account)

While Payment Methods (e.g., Cash, Bank Transfer, Check) are also important for tracking how customers pay, the critical requirement in the scenario is ensuring the invoice is due immediately. That is achieved by Payment Terms = 0D, not by Payment Method alone.

Best Practice Setup in Business Central for Cash & Carry:

Payment Terms: 0D (ensures invoice due immediately).

Payment Method: Cash (ensures posted directly against the cash account).

Apply to invoices at posting: Invoices will automatically be shown as paid in full.

This combination ensures correct cash sales processing and eliminates the issue noted in the case study where invoices incorrectly appear in aging reports.

Microsoft References

Set Up Payment Terms in Business Central

Set Up Payment Methods in Business Central

Work with Payment Transactions

Buying groups require all invoices in a month to be due on the 20th of the following month (from the case study).

In BC, this is achieved by setting up Payment Terms = CM+20D (Current Month + 20 Days). Example: Invoice on Sept 5 → due Oct 20.

Payment terms are assigned directly to the customer card, not to the posting group or price group.

Option E (D20) would set due date 20 days after invoice date, which is incorrect.

Assigning to Customer Posting Group or Price Group does not control due dates.

Correct: A and C

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.