MB-800 Questions and Answers

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.

The scenario requires configuring Business Central to meet sales department needs:

Sales discounts

Requirement: “Discounts must post to a unique general ledger (G/L) account.”

In Business Central, this is managed through the Discount Posting field in Sales & Receivables Setup.

When enabled, the system posts line discounts and invoice discounts to dedicated G/L accounts instead of combining them with revenue.

This ensures transparency and compliance with accounting’s requirement to track discounts separately.

Correct match: Sales discounts → Discount posting

Credit limits

Requirement: “The sales department should receive a warning when entering the order if a customer is over their credit limit.”

In Business Central, this behavior is controlled by Credit Warnings in the Sales & Receivables Setup.

This setup defines whether to warn the user, block posting, or allow posting when the customer’s balance exceeds the defined credit limit.

Correct match: Credit limits → Credit warnings

Why not the other options?

Calc. inv. discount – Controls whether invoice discounts are automatically calculated, but not relevant here.

Stockout warnings – Alerts when an item has insufficient inventory; unrelated to discounts or credit limits.

Microsoft Learn references

Set Up Sales and Receivables

Discount Posting setup – posting discounts to G/L accounts.

Credit Warnings setup – warnings and blocking options.

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

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

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

The requirement is: “Customer pricing is determined by the customer market type (Retail, Veterinarian, Breeder). Each customer is associated with only one market type.”

A. Assign the Customer Price Group code on the customer card → Correct, because each customer must be tied to its market type via a Customer Price Group.

C. Create a Sales Price List by using the assign-to type of Customer Price Group → Correct, because pricing and discounts should be managed at the group level, not per individual customer, ensuring easier maintenance.

E. Create Customer Price Groups that allow line discounts → Correct, because discounts are offered by item, brand, or product category, and must flow to sales lines automatically.

Incorrect options:

B. Exclude line discounts → Opposite of requirements.

D. Create a Sales Price List for the customer → Not scalable; must be done by group, not individual customer.

Correct answers: A, C, E

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

open general ledger setup

change global dimension

select a new dimension

Click "start"

Comprehensive Detailed Explanation

In Dynamics 365 Business Central, Global Dimensions are critical because they are applied across the system in posted entries, G/L entries, and reports. If they are set incorrectly, you can use the Change Global Dimensions function.

Since the database contains very few posted entries, we can use Sequential mode (faster and suitable for small databases). The correct steps are:

Open General Ledger Setup → Navigate to General Ledger Setup, which contains the Global Dimension fields.

Select the Change Global Dimensions action → This opens the dedicated page to change dimensions.

Select the new dimension → Choose which dimension you want to replace Global Dimension 1 with.

Select the Start action → Starts the sequential process to update entries and data tables.

⚠️ The actions Prepare and Sign out and back in are used for Parallel mode (suitable for larger datasets), where data preparation and session reset are required. For Sequential mode, those are not necessary.

Microsoft Learn References:

Change Global Dimensions in Business Central

General Ledger Setup

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.

The requirement is:

Post monthly general journal batches for purchase expenses.

Ensure unique incremental document numbers.

Numbers must increment by one and be sequential.

In Business Central, this is accomplished by No. Series and their assignment to General Journal templates/batches.

Step 1: Create the No. Series (B)

Go to No. Series and define a new number series that increments by 1.

Set starting number, ending number, increment = 1.

Step 2: Create a Template Batch with Posting No. Series (A)

In the General Journal Batch, set up the Posting No. Series so that posted documents get unique sequential numbers when posted.

Step 3: Create a Template Batch with No. Series (E)

Additionally, you can assign a No. Series in the General Journal Batch itself.

This ensures that while entering journal lines, the Document No. field uses the assigned No. Series.

Why not C or D?

C. General Journal with Purchase Reason Code → Reason Codes are optional and used for audit/analysis, not for sequential numbering.

D. General Journal Template with Purchase Type → There is no "Purchase Type" field in General Journal Templates. Not applicable.

Microsoft Learn References:

Work with General Journals

Set Up No. Series

Set Up General Journal Templates and Batches

In Dynamics 365 Business Central, workflows are the tool used to control document approvals, including purchase orders:

Lock the record for newly created blanket purchase orders with the specific item → Business Central workflows

Blanket purchase orders are controlled via approval workflows in Business Central.

Workflows enforce rules so records cannot be processed until approved.

Assign the security command that tells the system to lock the purchase order → Then Response

In workflow design:

When Event defines the triggering action.

On Condition specifies filter conditions.

Then Response is the action taken, e.g., Lock the record or Request Approval.

Therefore, locking the record is a response action.

Assign the items that the system will want to use to trigger the locking of the purchase order → When Event

The workflow must know what starts the approval process (such as A blanket purchase order is created).

This is always defined as a When Event.

Other options not correct:

Incoming Documents / Power Automate flows → Can be integrated, but the requirement here is internal approval and locking, which is a Business Central Workflow function.

On Condition → Used to apply filters (like a specific item), but the actual trigger is defined by When Event.

Trigger → Not a component in Business Central workflow terminology (more of a technical developer concept).

Microsoft Learn References

Set Up Approval Workflows

Workflows in Business Central

When migrating data (such as general ledger entries with analytical details/dimensions) into Dynamics 365 Business Central Online, the best practice is to use Configuration Packages (RapidStart Services).

Create a configuration package and select the appropriate table (A): You need to select the tables that hold historical financial information, such as G/L Entries or Ledger Entries.

Export to Excel and adjust the file (B): After exporting, you can enrich the data with dimension values or analytical information not included originally, then re-import it into BC.

Enable Dimensions as Columns (C): This makes it easier to map and load dimension values directly in the configuration package, ensuring analytical information is preserved.

Options not correct:

D (Export the configuration package): Exporting a package is usually done for backups or sharing, not part of the required migration steps.

E (Assign a data template): Data templates are used for master records (customers, vendors, items), not for migrating historical ledger entries.

Microsoft Learn References

Use Configuration Packages to Import Data

Work with Dimensions

Correct Answer: A, B, C

In Dynamics 365 Business Central, recurring sales invoices (subscription-type billing) are automated using Standard Sales Lines. Here’s how it works:

Configure Standard Sales Lines

Define a Standard Sales Lines Card with details of the subscription service, including description, quantity, unit price, and G/L account.

This acts as the template for recurring invoices.

Open Customer List → Recurring Sales Lines

Navigate to the customer that needs recurring billing.

From Customer Card → Related → Sales → Recurring Sales Lines, link the standard sales line to the customer.

Assign Standard Sales Lines Card

Attach the subscription template (Standard Sales Lines Card) to the customer so the system knows which items/services to bill.

Run the Create Recurring Sales Invoices task

Use the batch job to automatically create invoices each month for all customers with assigned recurring sales lines.

This step generates invoices without requiring manual entry.

Other options (Manual, Always Ask, Automatic on Insert Rec. Lines) control how recurring lines behave when entering orders/invoices manually. However, for automated monthly billing, the Standard Sales Lines + Recurring Sales Lines + batch job process is required.

Microsoft Learn References

Set Up Standard Sales and Purchase Lines

Create Recurring Sales and Purchase Documents

Recurring Sales Invoices Batch Job

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

Comprehensive Detailed Explanation

When creating or configuring new companies in Microsoft Dynamics 365 Business Central, there are different tools with specific roles:

Assisted Setup

Provides guided wizards to help you create a new company quickly, entering the first essential details like company name, address, VAT registration, etc.

Useful for getting the company started before loading more detailed configuration.

RapidStart Services

A framework in Business Central used for data migration and configuration tasks.

It allows you to create a set of setup tasks (like payment methods, posting groups, dimensions) and run them in a defined sequence. Users can mark tasks as done once finished.

Ideal for structured implementations.

Configuration Questionnaire

A part of RapidStart, used to template existing setup and data (master data, posting groups, setups) into packages.

These templates can then be applied to a new company in one process, essentially cloning configuration from an existing company.

Microsoft Learn References

Assisted Setup

RapidStart Services Overview

Configuration Packages and Questionnaires

The Microsoft Power Platform extends the capabilities of Dynamics 365 Business Central by adding automation, analytics, and low-code apps. Here’s how the requirements align:

Real-time financial reporting → Power BI

Power BI integrates directly with Business Central using OData feeds and APIs.

Provides dashboards and real-time reports for financial data (sales, budgets, cash flow, etc.).

Automated customer onboarding → Power Apps

Power Apps can create custom apps and forms for entering customer data, which integrate back into Business Central.

Example: A sales rep uses a mobile app to collect customer details → syncs automatically into BC.

Automated invoice approval workflow → Power Automate

Power Automate connects BC with approval workflows (e.g., invoice > $10,000 must go to Finance Manager for approval).

Automates notifications and approval tasks.

Integrated item scanning capabilities → Power Apps

Power Apps allows building mobile apps with barcode/QR scanning capabilities.

Warehouse staff can use phones or tablets to scan items, which update BC inventory in real time.

Other tool (OneDrive): Not relevant in this scenario—it’s for file storage, not automation, reporting, or scanning.

Microsoft Learn References

Integrating Business Central with Power BI

Power Automate and Business Central

Power Apps Integration with Business Central

The Inv. Rounding Precision (ICY) field in the General Ledger Setup defines how invoice amounts are rounded in the local currency.

Since the requirement is to round amounts to the hundredths place (two decimal places), you must set this value to 0.01.

Other options:

0.20, 1.00, 2.00 → Round to larger increments, not cents.

1-11 → Not a valid rounding precision value.

The requirement is to:

Import a series of payments from a bank account (file from bank, e.g., CAMT.053, MT940, BAI2, or CSV).

Automatically match the imported payments against customer/vendor ledger entries already in Business Central.

Apply those matched entries automatically, while allowing review and manual matching for exceptions.

This is exactly what the Payment Reconciliation Journal is designed for:

The Payment Reconciliation Journal page lets you import bank statement files or manually enter bank transactions.

The system then attempts to auto-apply payments to open customer/vendor ledger entries using match rules (based on amount, document number, or text).

Any unmatched payments can be handled manually or left open for investigation.

Once complete, posting the journal reconciles the bank account and applies the payments.

Why not the other options?

A. Payment Application Rules – These define how automatic application should work (match tolerance, priorities), but they are not the form to process the payments themselves.

B. Payment Services – Used for online payment processing (e.g., PayPal, WorldPay), not for bank file imports.

D. Payment Registration – A manual process to register payments (e.g., marking invoices as paid when receiving cash or checks at the counter). It does not support bank file imports or auto-matching.

Thus, the correct form is Payment Reconciliation Journal.

Microsoft Learn References

Apply Customer Payments Using Payment Reconciliation Journals:https://learn.microsoft.com/en-us/dynamics365/business-central/bank-how-reconcile-payments-auto-application

Import Bank Statements and Match Automatically:https://learn.microsoft.com/en-us/dynamics365/business-central/bank-how-import-bank-statement

Payment Registration vs Payment Reconciliation:https://learn.microsoft.com/en-us/dynamics365/business-central/receivables-apply-payments

Correct Answer: C. Payment Reconciliation Journal

In Dynamics 365 Business Central, security is defined by assigning permissions to users. Each permission is associated with an object type. The allowed permission types differ depending on the object type:

Table

This refers to the table object definition, not its data.

Permissions allowed: Execute only (to access the table object, metadata).

Actual data permissions (read, insert, modify, delete) are handled separately by Table Data.

Page

A page is an interface object (e.g., Card, List).

Permissions allowed: Execute (grants access to run or view the page).

Table Data

Refers to the actual records stored in the database.

Permissions allowed: Read, Insert, Modify, Delete (CRUD).

This is where you control access to data, not just the object structure.

System

System objects are internal to the platform (system tables, codeunits).

Permissions allowed: Execute to allow access to system-level functionality.

Microsoft Learn References

Permissions and Permission Sets in Business Central

Types of Objects and Their Permissions

FIFO is a widely used costing method where the oldest inventory items are sold first. This is a common and straightforward method for valuing inventory.

Automatic cost adjustment is a crucial setting for resolving inventory reconciliation issues. When this is enabled, Business Central automatically adjusts the cost of goods sold (COGS) to match the actual cost of the inventory. This helps prevent discrepancies between the inventory sub-ledger and the general ledger, ensuring that the financial data is accurate.

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.

Comprehensive Detailed Explanation

The company requires:

Preset vendor invoice discounts applied automatically.

Automatic calculation of invoice-level discounts.

Ability to keep a copy of purchase orders for historical reference (for vendor contract negotiations).

Let’s break each down:

1. Configure the preset invoice level discounts

Vendors give regular discounts at the invoice level.

In Business Central, you configure this in Vendor Invoice Discounts.

You set a discount % (e.g., 5%, 10%) for the vendor.

Correct action: Set Discount % on Vend. Invoice Discount

2. Configure the automatic invoice level discounts calculation

After defining vendor invoice discounts, you must enable automatic calculation.

This is controlled in Purchase & Payables Setup by setting Calc. Inv. Discount = Yes.

Correct action: Set Calc. Inv. Discount to Yes on Purchase & Payables Setup

3. Configure purchase order history

The requirement is to be able to “see a copy of the completed purchase order in the system” for reference during vendor contract negotiations.

Business Central provides this via the Archive Orders function.

When archiving is enabled, every time an order is changed or posted, the system retains a copy.

Correct action: Set Archive Orders to Yes

Microsoft Learn References

Set Up Vendor Invoice Discounts

Set Up Purchases and Payables

Archive Sales and Purchase Orders

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

Comprehensive Detailed Explanation

The requirement in the case study is that the company warehouses products as Case quantities but wants to expand capabilities by setting up all inventory in a quantity of Each. This means they need to configure Units of Measure (UoM) so that one item can be managed both by Case and by Each.

In Business Central:

Units of Measure Table – defines the available unit codes (e.g., EACH, CASE, BOX) with descriptions.

To use Case as a unit, you must first define it in the Units of Measure table.

Correct: D. Add a Code and Description to the Units of Measure table.

Item Units of Measure (Qty. per UoM) – links the item to multiple units of measure and specifies conversion (e.g., 1 Case = 10 Each).

For example, if a Case = 10 Each, you set Qty. per Unit of Measure = 10 for Case.

Correct: A. Set a Unit of Measure for case to a Qty. of 10.

Why the other options are incorrect:

B. Qty. per UoM = 1 is redundant (default Each already equals 1). It does not meet the requirement for Case-to-Each conversion.

C. Case with Qty. = 1 would make Case = Each, which is incorrect because Case must represent multiple units (10 Each).

Microsoft Learn References

Work with Units of Measure

Set Up Item Units of Measure

Comprehensive Detailed Explanation

Set up a new fiscal year

In Business Central, fiscal years are created in the Accounting Periods page.

To start a new fiscal year, you must Select Create Year, which generates the periods for the new fiscal year.

Other options like Close Year or Fiscal Year Balance are for closing or balancing, not for initial setup.Correct: Select Create Year

Define the fiscal year start date

The case study specifies that the company’s fiscal year starts on June 1.

Therefore, when creating the new fiscal year, you must ensure the first period begins on June 1.

The correct action is Check New Fiscal Year for June 1.Correct: Check New Fiscal Year for June 1

Restrict posting

The business requirement is:

Restrict users to post only in the current month.

Only certain accounting users may have broader posting permissions.

In General Ledger Setup, the Allow Posting From and Allow Posting To fields control the global posting date range.

For user-specific restrictions or exceptions, User Setup allows overriding posting ranges for individual users.

Since the requirement is to restrict all users generally, the best action is:In General Ledger Setup, set the Allow Posting From and Allow Posting To options to current dates.Correct: In General Ledger Setup, set the Allow Posting From and Allow Posting To options to current dates

Microsoft Learn References

Accounting Periods (Create and Close Fiscal Years)

General Ledger Setup – Allow Posting From/To

User Setup and Posting Date Permissions

Comprehensive Detailed Explanation

The company’s reporting requirements are:

They need to analyze which customers are buying which items.

They need to analyze which salespeople are selling in which regions.

They also need consistent reporting for Customer Groups, Item Groups, Salesperson, and Region.

In Business Central, dimensions are the mechanism to capture these classifications (customer groups, item groups, salesperson, region). To configure reporting dimensions properly, the following steps are required:

Set up dimensions

Before using any dimensions, you must define them in the Dimensions page. This is where new entries such as Customer Group, Item Group, Salesperson, and Region are created.

Correct action: Create a new entry on Dimensions.

Configure global dimensions

Business Central allows two global dimensions that become available on all transaction lines and entries. These are the most used reporting breakdowns.

Since the company must always report sales by customer and item, these should be set as global dimensions.

Correct action: Change global dimensions on General Ledger Setup.

Configure shortcut dimensions

Shortcut dimensions (up to 8) are additional reporting dimensions that can be made available for entry on journals, documents, and transactions. These are perfect for Region and Salesperson requirements.

Correct action: Choose a shortcut dimension code on General Ledger Setup.

This setup ensures reporting can directly answer the business questions in financial results and enable analysis across Customer Groups, Item Groups, Salespeople, and Regions.

Microsoft Learn References

Work with Dimensions

Set Up Dimensions

General Ledger Setup – Global and Shortcut Dimensions

Analysis by Dimensions

Comprehensive Detailed Explanation

Deliver on a specific customer date

Salespeople must avoid promising inventory that is not available.

To check whether the requested delivery date can be met, the correct action is to review Item Availability by Periods.

This allows them to see when stock will be available across time periods, ensuring promised delivery dates are realistic.

Other options are less accurate:

Change the Requested Delivery Date → does not confirm if stock is available.

Check the Catalog on Sales Line → only for product lookup, not availability.

View the Location Code → shows location assignment, not time-phased availability.

Correct: View the Item Availability by Periods

Process quotes

Requirement: Salespeople must convert quotes to orders once they are finalized.

In Business Central, this is done by selecting Make Order from the Sales Quote.

Other options:

Make Invoice → bypasses order process, not applicable here.

Copy Document → creates a new document, not the required process.

Release → applies to orders but not to quotes-to-orders conversion.

Correct: Choose Make Order

Microsoft Learn References

Check Item Availability

Convert Sales Quotes to Orders

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.