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

Requirement: Invoices must be automatically emailed to customers using a fixed template.

Solution:

A. Set Email to Yes (Use Default Settings) → ensures invoices are sent automatically without prompting.

E. Apply Office Server Settings to the SMTP Mail Setup → configures the company’s mail server (SMTP/Office 365) so that emails are sent.

F. Assign a Document Sending Profile to the Customer where Email is set to Yes → links customers to the correct sending method (Email with fixed template).

Other options:

B. Allow Sender Substitution is optional, not required.

C. Prompt for Settings requires manual action (not automatic).

D. Assigning “Email = No” contradicts the requirement.

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.

The case study states:

The company often receives a higher quantity of produce items than ordered because vendors allow for spoilage/damage during transit.

The company wants to allow over-receipt only for produce but not for non-produce items.

In Dynamics 365 Business Central, this requirement is handled by Over-Receipt Codes:

You define a code with a tolerance percentage (e.g., 5% or 10%).

The code can be assigned to specific items (e.g., produce) or vendors.

This allows receiving slightly more than ordered, while blocking over-receipt for other items.

Why not the other options?

B. Payment Tolerance % → relates to differences in payment amounts (e.g., customer underpaying by a few cents), not receiving inventory.

C. Default Deferral Template → used to defer revenue/expense recognition over time, unrelated to item receipt.

D. Dampener Quantity → used in demand planning/MRP to avoid unnecessary changes to supply orders; not for receiving more items.

So the correct configuration is Over-Receipt Code with Tolerance %.

The scenario mentions that the company needs to properly record received items before invoices arrive.

In Business Central, enabling Expected Cost Posting ensures that receipts (goods received but not invoiced) are reflected in both inventory and the general ledger.

This avoids the need for a manual accrual process (one of the issues in the case study) and satisfies the requirement to record accounting impact for items received but not yet invoiced.

Other options:

A. Standard Costing is unrelated (they need FIFO/average etc. for produce).

B. Automatic Cost Posting just posts automatically but doesn’t address received-not-invoiced.

D. Automatic Cost Adjustment = Always updates inventory values for costing, not expected costs.

The case study specifies that:

Salespeople manage opportunities/quotes and release orders to the warehouse.

Warehouse staff fulfill orders and complete shipments.

Office/accounting staff are responsible for invoicing (separation of duties).

Therefore, the correct sequence for processing sales orders is:

Add External Document No. to Sales Order

An office employee enters this reference (often the customer’s PO number) before processing.

This step ensures traceability for auditors and aligns with required documentation.

Warehouse employee performs Post and Ship

The warehouse is responsible for picking, packing, and shipping items.

They must post the shipment in Business Central, creating a posted shipment record.

The warehouse does not invoice, since invoicing is the responsibility of the office.

Office employee performs Post and Invoice only

After confirmation that the order shipped, the office staff posts the invoice.

This matches the new division of duties and provides the financial document to the customer.

Why not the other options?

Warehouse performs Post, Ship, and Invoice: Incorrect because invoicing is not the warehouse’s responsibility.

Warehouse performs Post and Invoice only: Wrong, warehouse does not invoice.

Office employee performs Post, Ship, and Invoice: Wrong, because shipping is handled by warehouse.

Warehouse employee changes Posting Date: Not a standard requirement for fulfilling orders in this case.

Microsoft Learn References

Process Sales Orders

Post Shipments and Invoices Separately

The AR users reported an issue about reconciling AR subledger to the G/L. In Business Central, subledger control accounts (like Accounts Receivable and Accounts Payable) must not be posted to directly; they should only be posted through transactions (invoices, payments).

If Direct Posting = Yes, users can post directly into AR or AP control accounts, which causes reconciliation issues.

To prevent this, you set Direct Posting = No on the G/L Account Card for control accounts.

Why not others:

A. Switch Blocked on the Customer Card → Blocks transactions but does not solve reconciliation issues.

B. Switch Direct Posting on the G/L Account Card to Yes → Makes the issue worse.

C. Switch Blocked on the G/L Account Card to Yes → Prevents all postings, even system ones, which is incorrect.

Correct answer: D. Switch Direct Posting on the G/L Account Card to No

The requirement is:

“When viewing G/L entries, the finance and accounting teams must be able to see debits and credits instead of a positive or negative amount.”

In Business Central, the General Ledger Entries page can display amounts in two different ways:

Amount (positive/negative): This is the default display of entry amounts as signed numbers.

Debit Amount / Credit Amount (separate fields): This allows accounting teams to clearly see whether an entry is a debit or a credit, consistent with traditional accounting presentation.

The configuration option " Debit/Credit " is specifically provided to control this display. By enabling this setting, amounts are shown in two columns (Debit Amount and Credit Amount) instead of one column with positive/negative signs.

Why not the other options?

B. Show Amounts – This relates to toggling whether amounts are displayed on certain ledger pages but does not change the format to Debit/Credit.

C. Check G/L Account Usage – This is a validation function for checking how accounts are used, not related to entry display format.

D. G/L Account Card – Used to configure properties of individual G/L accounts (posting type, direct posting, account category), not the general display mode for entries.

Therefore, the correct configuration to meet the requirement is Debit/Credit.

Microsoft Learn references

Work with General Ledger Entries – explains how G/L entries can be displayed and filtered.

Business Central General Ledger Setup – includes configuration options such as showing amounts as debit/credit.

General Ledger Overview in Business Central – details on how entries are posted and viewed.

Step-by-Step Explanation

Set up inventory periods: Before performing any inventory costing adjustments, you must first define the period for which the adjustments will be made. This step is a prerequisite for most inventory management tasks, ensuring that the work is contained within a specific timeframe.

Run the Adjust Cost – Item Entries batch job: This is the core action for adjusting inventory costs. This batch job automatically recalculates and updates the costs of all inventory items to reflect the most current and accurate valuation. It ' s a critical step for systems that use costing methods like average cost or FIFO, which might require periodic re-evaluation.

Run Post Inventory Cost to G/L: Once the inventory item costs have been adjusted, the next logical step is to post these updated values to the general ledger (G/L). This action synchronizes the inventory sub-ledger with the financial records, ensuring that the company ' s financial statements accurately reflect the true value of its inventory.

Close the inventory period: After all adjustments are made and costs are posted to the G/L, you must close the inventory period. Closing the period prevents any new entries or changes from affecting the adjusted costs, thereby maintaining the integrity of the financial data and satisfying audit and compliance requirements.

The requirement is: “You need to configure retail store customer cards to track revenue by market.”

In Business Central, to track revenue by customer market (Retail, Veterinarian, Breeder), you configure default dimensions on the Customer Card.

Assign the dimension code → Market

The business wants to analyze revenue by Market (Retail, Veterinarian, Breeder).

Therefore, the dimension code must be Market.

Assign the dimension value code → Retail

For this specific setup, the customer is a retail store, so the dimension value must be Retail.

Select a value posting → Same code

To ensure that every posting for this customer always carries the same dimension value, use Same Code.

Other options:

Blank = no default dimension.

No code = optional dimension.

Code mandatory = requires entry but allows flexibility in values.

Since we want strict tracking by a fixed market (Retail), Same code is correct.

This ensures that every transaction posted for the customer will always have Market = Retail, enabling accurate revenue tracking.

Microsoft Learn references:

Work with Dimensions

Set Up Default Dimensions

Dimension Value Posting Options

The Accounts Receivable (AR) team often needs to correct payment applications when cash is applied incorrectly. In Business Central, unapplied entries can be corrected in several ways:

From the Customer Card, under Navigate > Ledger Entries, users can select entries and use the Unapply Entries action.

From the Customer Ledger Entries page, users can directly select a posted application and choose Unapply Entries.

The Detailed Customer Ledger Entries page is used for analysis and shows how entries were applied, but the actual “Unapply” action is not typically performed here (it is read-only in terms of correction).

“Apply entries” can be done from Detailed Customer Ledger Entries, but unapplies are performed from Customer or Customer Ledger Entries.

Correct answers: A and C