Pass the Microsoft Microsoft Certified: Dynamics 365 Business Central Functional Consultant Associate MB-800 Questions and answers with CertsForce

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

In Dynamics 365 Business Central, if you want to track inventory separately across different sites/branches/warehouses, you must set up Locations. Each location represents a physical site where inventory is stored and can be managed separately.

Warehouse (A): Refers to advanced warehouse functionality inside a location (bins, picks, put-aways).

In-Transit location (B): Used for transfer shipments, not for permanent site tracking.

Responsibility center (D): Used for reporting/management responsibility, not for inventory tracking.

Outbound email can be configured in Business Central in two ways:

SMTP Mail Setup → Traditional configuration with mail server, port, credentials.

Email Setup Assisted Setup tool → Modern option for OAuth-enabled services (Exchange Online, Microsoft 365, SMTP).

Incorrect options:

B. Business Inbox in Outlook → Used to integrate Outlook add-in for processing documents, not sending emails.

C. Email logging assisted setup → Used for tracking customer interactions, not for sending emails.

The requirement is to automate purchase order entries for a vendor (the hardware store) so that a default G/L account is automatically included. This is accomplished in Business Central using Standard Purchase Codes (recurring purchase lines).

Configure Standard Purchase Code and set up relevant G/L account.

Create a Standard Purchase Code card.

Add the recurring line that points to the G/L account where purchases should post (e.g., Cleaning Supplies Expense).

Choose Standard Purchase Code for the selected vendor as a recurring purchase line.

Link the Standard Purchase Code to the vendor card.

This ensures whenever a purchase document (orders or invoices) is created for this vendor, the recurring lines are suggested.

Change the Insert Rec. Lines on Orders to Automatic, and then close the window.

On the Vendor card, under Recurring Purchase Lines, set Insert Rec. Lines on Orders = Automatic.

This ensures the line is automatically inserted without prompting.

Not required in this scenario:

Payment Terms Code → Controls due dates/payment schedule, not G/L automation.

Insert Rec. Lines on Invoices → Could also be set, but the question specifically refers to purchase orders.

Microsoft Learn References

Set Up Standard Purchase Codes

Create Purchase Documents with Recurring Purchase Lines

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

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 requirement is to configure the new customer creation process in Dynamics 365 Business Central. The goal is to make sure that when users quickly add new customers (for example, at the Cash & Carry desk), all required fields and correct defaults are consistently applied.

1. Configuration Worksheet (B)

The Configuration Worksheet is used in RapidStart Services to plan and manage setup data across tables.

It lets you map out which tables (e.g., Customers, Vendors, Items) you want to configure and load master data into.

For customer creation, this ensures that the Customer table and related setup tables are properly configured before using templates.

This acts as the foundation of the process: deciding what must be included in the customer creation workflow.

2. Configuration Template (C)

Configuration Templates define default values for new master data records (e.g., customers, vendors, items).

For example, when creating a new customer, the template can pre-fill fields like:

Posting groups

Payment terms

Customer source dimension

Responsibility center (if required)

This ensures consistency and reduces errors when users add new customers.

In this scenario, since the company wants fast and accurate customer creation, templates are essential.

Why not A (Responsibility center)?

Responsibility centers are used to manage operations by location, department, or profit center.

They are useful for reporting and segregation of transactions, but not mandatory for customer creation setup.

Why not D (Permissions)?

Permissions define who can create or modify customers.

While important for security, this is not part of the configuration process for ensuring consistent field population and defaults in customer creation.

Microsoft References

Set Up Configuration Packages and Templates (RapidStart Services)

Configuration Templates for Customers, Vendors, and Items

Customer Table Setup and Creation