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

With Check G/L Account Usage = Yes enabled in General Ledger Setup, deletion of a G/L account is only possible if:

The account has no ledger entries.

The account has no balance.

The account is not used in setup fields (posting groups, posting setup, etc.).

The most direct requirement is no balance amount.

Business Central Functional Consultant at end of each question below

In Business Central, posting periods and deferral posting control are managed through the User Setup page.

The User Setup table/page allows you to assign user-specific posting restrictions by specifying Allow Posting From and Allow Posting To dates.

These restrictions apply to all posting transactions for that user, including deferrals. This ensures you can control in which periods each user is allowed to post.

This setup overrides the company-wide settings in General Ledger Setup (where you also have global Allow Posting From/To dates).

Why the other options are incorrect:

A. User Tasks – Provides task reminders or workflow assignments for users, not posting date control.

B. My Settings – Lets a user configure personal settings like Role Center, company, region, or work date, but it does not control posting periods.

D. Profiles (Roles) – Define user interface profiles (role-tailored experience), not transactional posting periods.

Therefore, the correct configuration page is User Setup.

Microsoft Learn References

Define Posting Periods for Users (User Setup with Allow Posting From/To):https://learn.microsoft.com/en-us/dynamics365/business-central/finance-how-specify-posting-periods

User Setup (fields and functionality including posting restrictions):https://learn.microsoft.com/en-us/dynamics365/business-central/ui-how-users-permissions

Deferrals in Business Central (and how they respect posting periods):https://learn.microsoft.com/en-us/dynamics365/business-central/finance-how-defer-revenue-expenses

This ensures users can only post deferrals in the periods defined in their User Setup.

The requirement:

An accountant must post sales services in a journal by using a predefined alphanumeric sequence. The accountant is using multiple general journal batches. You need to configure invoice numbers for the journal.

In Dynamics 365 Business Central, when you post journals (such as General Journals, Sales Journals, or Cash Receipt Journals), the system assigns posting numbers based on No. Series defined at either the General Journal Template or General Journal Batch level.

Field Details

Posting No. Series (General Journal Templates)

Defines the default number series for posting across all batches that use this template.

For example, the GENERAL template can have a posting number series assigned that applies to all batches under it.

Posting No. Series (General Journal Batches)

Allows overriding the template’s posting number series on a per-batch basis.

This is essential when multiple batches are in use and each requires a different posting sequence.

For example, batch SERVICES might use a series SRV-0001, while batch SALES uses SAL-0001.

Why not the other options?

B. No. Series field in General Journal Batches

This field applies to document numbers on the journal lines, not the posting number. It controls the numbering for the lines entered, not the posting entries.

D. No. Series field in General Journal Templates

Same reasoning as above: it relates to the entry/document numbering at line level, not the posting number that is required in this case.

Since the question explicitly requires configuring invoice numbers for posting, the correct fields are the Posting No. Series fields.

Microsoft Learn References

Set Up General Journal Templates and Batches

No. Series in Business Central

General Journal Fields Explained

Comprehensive Detailed Explanation

In Dynamics 365 Business Central, the Value Posting field on dimensions defines how dimensions behave during posting:

No Code

The dimension is optional.

Users can change or skip the default dimension value when entering a transaction.

Used when you want flexibility.

Code Mandatory

A dimension value must be entered before posting is allowed.

Ensures the transaction always contains a dimension value, but users can pick any valid one.

Used when dimension entry is required for reporting.

Same Code

The system enforces that only the default dimension value assigned to the account type can be used.

Users cannot change the default value, ensuring strict consistency.

Microsoft Learn References

Default Dimensions and Value Posting Types

Set Up Dimensions

In Dynamics 365 Business Central, default dimensions ensure that a required dimension is automatically suggested or enforced when creating transactions for entities such as Customers, Vendors, G/L Accounts, etc.

Step-by-step process to make a dimension mandatory for Customers:

Select Account Type Default Dim.

Navigate to Search → Default Dimensions.

Here you define which account type (Customer, Vendor, Item, etc.) will be linked to dimensions.

Select the relevant table ID.

Choose the entity (Customer table ID = 18) for which the default dimension setup will apply.

On the Dimensions page, select the required dimension.

For example, "DEPARTMENT" or "REGION."

This ensures the dimension is linked to the Customer entity.

Leave the dimension value blank, and in the Value Posting column, select Code Mandatory.

This ensures that a transaction cannot be posted without a dimension value being entered.

Leaving the dimension value blank enforces flexibility (any value allowed), while Code Mandatory ensures it is always required.

Other options not correct for this requirement:

Define the dimension value and set it in Value Posting → would automatically assign a fixed dimension value, but the requirement is just to make it mandatory, not fixed.

Disable the dimension value from posting → prevents posting, not useful here.

Microsoft Learn References

Set Up Default Dimensions for Customers, Vendors, and Other Accounts

Enforce Dimension Rules with Default Dimensions

You don’t assign a purchase account directly on the G/L account.

Instead, the system uses the combination of the General Business Posting Group (vendor side) and General Product Posting Group (item/service side).

In the General Posting Setup table, this combination points to the appropriate Purchase Account in the chart of accounts.

Thus, the correct answer is C.

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

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

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.