Microsoft MB-800 - Microsoft Dynamics 365 Business Central Functional Consultant

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.

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 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.

To ensure timely payments:

You can assign a Priority value to vendors (lower value = higher priority).

When running Suggest Vendor Payments, the system considers vendor priority to decide which payments to suggest first.

Setting the vendor’s priority to 1 (highest priority) ensures this vendor’s payments are included early, helping avoid late payments.

Why not the others:

A & E (Priority 0): 0 is not valid; priority starts at 1.

B (Enable Late Payment Predictions): Useful for forecasting, but it doesn’t enforce actual payment scheduling.

D (Apply to Oldest): Relates to how payments are applied to invoices, not ensuring timely payments.

The scenario states:

The company wants to verify purchase invoices use agreed-upon prices and discounts.

They are configuring the Vendor Card.

When creating a purchase order, a validation error occurs.

In Dynamics 365 Business Central, agreed prices and discounts are validated using Purchase Prices and Purchase Line Discounts. These must be defined to prevent validation errors when posting purchase documents.

Option Review:

A. Order address → Defines delivery address, not related to price/discount validation.

B. Location code → Specifies default receiving warehouse, but not related to pricing.

C. Vendor Template → Used for initial setup defaults when creating a vendor, not for validation.

D. Purchase Prices → Correct. Purchase prices/discounts must be set up to validate against agreed pricing rules. Missing setup can cause errors.

E. Vendor Posting Group → Determines G/L accounts for posting, but does not affect price validation.

Therefore, the validation error stems from missing Purchase Prices setup.

For items that are infinite (water, electricity, gas), inventory tracking is not required. In Business Central:

Non-Inventory item type is used when you need to record purchases/sales but do not track stock levels.

Inventory type would track stock, which is not suitable for infinite resources.

Resource type is used for capacity (like labor or machine resources), not consumables.

Service type is used for intangible services, not utilities.

Comprehensive Detailed Explanation

The scenario: The company receives deliveries during the week and then a consolidated vendor invoice at week’s end. In Dynamics 365 Business Central, the correct procedure is:

Step 1. From the purchase order, post receipts for the items

Each delivery is recorded as a purchase receipt against the purchase order. This ensures inventory is updated as soon as items are received.

In Dynamics 365 Business Central, the General Journal Reconciliation feature allows reconciliation of ledger entries against G/L accounts (often bank, clearing, or control accounts).

To include a G/L account in the general journal reconciliation window:

You must enable the Reconciliation Account field on the G/L Account Card.

This setting flags the account as reconcilable, so it appears in the reconciliation process.

Why not the others?

B. Direct Posting field → Controls whether you can post directly to the account, not related to reconciliation.

C. Bank Account Posting Group → Links bank accounts to G/L accounts, but the reconciliation flag still must be set.

D. Create a new payment reconciliation journal → Used for bank statement reconciliation, not general ledger account reconciliation.

Microsoft Learn Reference

Reconcile General Ledger Accounts in Business Central

In Dynamics 365 Business Central, if a purchase receipt has been posted incorrectly (and not yet invoiced), you can undo it. The process must be done from the purchase order and related posted receipt, not by canceling the order directly.

Step 1: Open the purchase order that is with the receipt.

Navigate to the original purchase order that generated the posted receipt.

Step 2: Choose Receipts and then open the incorrectly posted receipts.

From the purchase order, check the Receipts action to view posted receipts.

Step 3: Select a line to be cancelled from the posted purchase receipt.

Identify the incorrect receipt line that you want to undo.

Step 4: Select Undo Receipt.

Use the Undo Receipt action to reverse the receipt. This action reopens the order line and updates inventory.

Why not other actions?

Change status from Released to Open → Not required for undoing receipts.

Select Cancel → Cancels documents, but undoing a posted receipt is specifically done using Undo Receipt.

Microsoft Learn References:

Undo Receipt in Business Central

Correct or Cancel Receipts

 Currency Code → USD

 Last Statement No. → 9075

Comprehensive Detailed Explanation

You are setting up a bank account in Dynamics 365 Business Central. The requirements are:

Use US dollars

The company’s local currency code (LCY) is US dollars ($).

On the Bank Account Card, the Currency Code must be set to USD (not or $).

means it uses LCY without explicitly specifying the currency, but since the requirement states "use US dollars," the correct explicit setup is USD.

Next statement number should be 9075

The Last Statement No. field on the Bank Account Card should be set to 9075, which will ensure the next bank reconciliation statement starts from this number.

Why not the other options?

Currency Code = would default to LCY, but requirement explicitly says "use US dollars," so USD is correct.

Currency Code = $ is incorrect because $ is a currency symbol, not a valid currency code in Business Central.

Last Statement No. = 9074 would make the next reconciliation 9075, but since requirement says "use 9075 as the next bank account statement," we must set 9075 directly.

Microsoft Learn References:

Set Up Bank Accounts in Business Central

Currencies in Business Central