MB-800 Microsoft Dynamics 365 Business Central Functional Consultant Questions and Answers

Approval User Setup → Specify an approval administrator

In Business Central, the Approval User Setup page is used to define who is an approver, their approval limits, substitute approvers, and the approval administrator (who can manage blocked requests).

Notification Setup → Specify how the user receives notifications about approval requests

The Notification Setup defines delivery method (email, internal note, etc.), and the type of notifications a user gets (for workflow/approval events).

Notification Schedule → Specify that the user receives notifications on a weekly basis

The Notification Schedule page is used to configure frequency of notification delivery (immediate, daily, weekly). That’s where you set up weekly notifications.

Workflow Response Options are used to define what happens when a workflow event is triggered (e.g., send for approval, create notification, update field), not for administrators or notification frequency.

Microsoft Learn References:

Set up approval users

Set up notifications

Create notification schedules

Use workflow responses

Comprehensive Detailed Explanation

The Edit in Excel feature in Dynamics 365 Business Central allows users to open a page (e.g., General Journal) in Excel, where they can:

Modify existing records (A) → Users can edit fields in Excel, and when publishing back, the changes update Business Central.

Insert new records (B) → Adding a new line in Excel (with correct required fields) creates a new journal line when published.

Delete records (E) → Deleting a line in Excel and publishing removes the corresponding line in Business Central.

What cannot be done with Edit in Excel:

Post lines (C) → Posting must be performed inside Business Central, not from Excel.

Request approval (D) → Approval workflows are handled within Business Central, not Excel.

In Business Central, the Payment Terms calculation uses the Document Date (not Posting Date or Order Date). The system takes the Document Date and applies the due date calculation formula defined in the Payment Terms.

Order Date is primarily for purchase/sales documents scheduling.

Posting Date drives G/L posting date.

Due Date is the result of the calculation, not the input.

In Dynamics 365 Business Central, inventory posting involves multiple layers of data, starting with the master record and flowing into transactional details. The hierarchy is as follows:

Items (Master Data)

The Item Card defines the master information (item number, description, posting groups, costing method, etc.).

Item Ledger Entries (Transactions)

Every transaction (purchase receipt, sale, adjustment, transfer, etc.) creates an Item Ledger Entry (ILE).

The ILE tracks quantity-related information such as increases and decreases in stock, location, and posting date.

Value Entries (Costs/Values)

For each Item Ledger Entry, one or more Value Entries are created to record the financial value (cost, price, adjustments, etc.).

Value Entries ensure the link between physical inventory movements and financial postings.

Why not others?

Stockkeeping Units (SKUs): Used for location/variant-specific settings, but not mandatory for basic inventory posting.

Warehouse Entries: Created only when warehouse functionality (directed pick/put-away, warehouse receipts/shipments) is enabled, not part of the basic posting structure.

Microsoft Learn References:

Design Details: Item Ledger Entries and Value Entries

Work with Items

When printing to a cloud-based printer in Dynamics 365 Business Central, the correct type of printer to install is a System printer. Business Central supports the use of Business Central cloud printing via Universal Print. A System printer is made available through the printer management setup and can be used for server-side printing.

Email: Used for sending reports and documents by email, not for printing.

Client default: Uses the printer of the user’s local device session, but not suitable for automated cloud-based printing.

Server default: Prints to the default printer on the Business Central server, which is relevant for on-premises installations, not Business Central online with cloud printers.

Therefore, the correct option is System printer, which supports cloud-based print scenarios.

When implementing Business Central and entering starting balances at go-live, companies usually upload opening balances for customers, vendors, and general ledger accounts via general journals. This ensures the company’s financial data (payables, receivables, and trial balance) is carried over.

A. Vendors Opening balance → Uploads outstanding vendor balances.

B. G/L Accounts Opening balance → Uploads the trial balance of accounts.

E. Customers Opening balance → Uploads outstanding customer balances.

Options C (Calculate Inventory) and D (Get Standard Journals) are not used for uploading opening balances in this scenario.

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

When configuring a journal template in Dynamics 365 Business Central, different fields in the template enforce specific behaviors on journal entries:

Force Doc. Balance Ensures that journal lines balance by document number and type. If they don’t balance, the system will not allow posting.

Bal. Account Type and Bal. Account No. Allows you to specify a default balancing account. Whenever a journal entry is created, the system automatically balances it against this defined account.

Source Code Identifies the origin of the entry (such as sales, purchases, cash receipts). This supports the audit trail and reporting requirements by showing where the entry came from.

Reason Code Records the reason why a journal entry was created, allowing better documentation and traceability. This is especially important for audit trail purposes.

Comprehensive Detailed Explanation

In Microsoft Dynamics 365 Business Central, when a user mistakenly applies multiple payments incorrectly, you need to correct the customer payment application using the Unapply Entries functionality.

Step 1: Navigate to Unapply Entries from the relevant customer ledger entry. This is the starting point. You open the customer ledger entries for the specific transaction and select the entry where the wrong payment application was done.

Step 2: Unapply the first payment. Since the requirement is to remove the first cash receipt, you must unapply that specific payment. Business Central will then restore both the invoice and payment as open.

Step 3: Apply the second payment to the customer ledger entry. Because the second payment was still partly applied, you reapply it to ensure the invoice is still matched with the correct payment. This keeps your receivables accurate.

Step 4: Post a reversing cash receipt and select the customer and relevant payment entry. After unapplying and reapplying correctly, you may need to post a reversing cash receipt to completely clear the incorrect transaction from the customer account if an additional entry was created by mistake. This ensures that the general ledger and customer ledger entries remain aligned.

Thus, this sequence ensures the mistake is corrected without leaving residual incorrect entries in the ledger.

Microsoft Documentation References

Unapply Customer Ledger Entries in Business Central

Correct or Cancel Customer Payments

Apply and Unapply Customer Payments

The requirements are:

Different item pricing and vendors per warehouse

Transactions tied to a specific location

Configuration needed:

Locations: Defines each warehouse so transactions can be tied to them.

Stockkeeping Units (SKUs): Used to set up location-specific item details, including vendor, pricing, and replenishment.

Item Card: Required as the master definition for the item before assigning location-specific details.

Not required:

Inventory setup: Defines general parameters, not warehouse-specific configuration.

Warehouse setup: Used for warehouse operations (receiving, put-away, picking), not pricing/vendor setup.

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

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

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

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.

Based on the provided image, the correct values to select for the customer payment terms are the ones already highlighted.

Due Date Calculation for retail customer payment term:

Select the value 10.

Discount Date Calculation for wholesale customer payment term:

Select the value 10D.

Due Date Calculation for wholesale customer payment term:

Select the value 30D.

Due Date Calculation for wholesale customer payment term:

Select the value 15D.

The requirement is to resolve the order entry issue:

“Customers often reorder the same items with similar quantities. The system must be configured to ask the user if recurring lines should be added to sales orders.”

Business Central has Standard (Recurring) Sales Lines functionality to address this.

Configure standard sales lines → Add items and quantities

Standard sales lines define templates of frequently ordered items and their quantities.

When configuring these, you specify which items and quantities belong to the recurring order.

This resolves the need to avoid retyping common order combinations.

Add recurring sales lines to customers → Set insert on orders to Always Ask

On the Customer Card, you assign the standard sales lines and configure how they should be inserted when creating sales orders.

The setting Always Ask prompts the user each time an order is created for that customer, allowing them to choose whether to insert the recurring sales lines.

This satisfies the requirement to “ask the user if recurring lines should be added.”

Why not other options?

Add valid from and to dates – Useful for time-limited campaigns, but not mentioned in the requirement.

Set insert on quotes to Automatic – Applies to sales quotes, not orders. The requirement specifically concerns sales orders.

Microsoft Learn references

Set Up Standard Sales and Purchase Lines

Assign Standard Sales Lines to Customers

The requirement is:

“Customer revenue must be posted to separate general ledger (G/L) accounts based on customer type. The G/L account must have subcategories for wholesale and retail revenue.”

In Business Central, sales revenue posting is controlled by the General Posting Setup, which combines two posting groups:

General Business Posting Groups (A)

These represent the type of customer or vendor (for example, WHOLESALE or RETAIL).

They allow you to differentiate revenue by customer type.

General Product Posting Groups (C)

These represent the type of item or resource being sold (for example, FINISHED GOODS, SERVICES).

They allow you to map revenue to the correct accounts by product line or category.

The combination of General Business Posting Group + General Product Posting Group determines which Revenue G/L Account is used.

Why not the others?

B. Customer posting groups – Control AR control accounts, not revenue.

D. Bank account posting groups – Used for bank transactions, not revenue.

E. Inventory posting groups – Control inventory accounts and adjustments, not revenue.

Microsoft Learn references

Posting Groups in Business Central

Set Up General Posting Groups

The correct solution to meet the company ' s order processing requirements involves two key components: the type of workflow to be created and the engine that will power it.

A. Create a purchase order approval workflow: This is a core component of most order processing systems. A purchase order approval workflow automates the process of submitting purchase orders for approval, sending notifications to the appropriate approvers, and ensuring that all orders comply with company policies. This is a common requirement to control spending and maintain an audit trail.

D. Use Power Automate as the engine for the workflow: Power Automate (formerly Microsoft Flow) is a powerful, cloud-based service that allows you to create automated workflows and connect various applications and services. It is the modern and highly versatile solution for creating complex and customized workflows that go beyond the basic capabilities of many built-in systems, including those in Business Central. While Business Central has a native workflow engine (as mentioned in option C), Power Automate is the recommended solution for more robust and integrated order processing workflows, especially when they need to interact with multiple systems or require advanced logic.

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.

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

Comprehensive Detailed Explanation

In Business Central, financial reporting is built from several components:

Row definition

Used to define which accounts or statistical accounts appear as rows in the financial report.

Since Headcount and Square Footage are statistical accounts (non-financial data tracked for reporting), they must be added via Row definition.

G/L account categories

Used to structure the income statement and balance sheet into financial categories such as Income, COGS, Assets, Liabilities.

The requirement states: “The financial report structure must map to account categories.”

Therefore, Income, Retail must be configured using G/L account categories.

Financial Report page

Used to assemble and present the report, combining row definitions, column definitions, and filters.

Accounts Receivables, Wholesale is a financial reporting output that must be displayed using the Financial Report page where the actual data is gathered.

Why not Column definition?

Column definitions control time periods (month, quarter, year, variance, etc.) but are not needed for these particular requirements.

Microsoft Learn references

Financial Reporting in Business Central

Set Up Row and Column Definitions

G/L Account Categories

The requirement is:

“You need to configure the system to post to the receivables account for wholesale customers.”

From the case study, the G/L posting accounts required are:

Retail Receivables = 13100

Wholesale Receivables = 13200

In Business Central:

Customer Posting Groups (B)

Customer Posting Groups are used to map customers to specific Receivables G/L accounts.

You typically create separate posting groups, e.g., " RETAIL " and " WHOLESALE, " and assign them to customers based on type.

This ensures postings go to the correct control account.

Receivables account 13200 (D)

For wholesale customers, the posting group must be configured to point to 13200 (Wholesale Receivables).

Why not the others?

A. Receivables account 13100 – This is for retail customers, not wholesale.

C. General Posting Setup – This setup manages how transactions post based on combinations of General Business Posting Groups and General Product Posting Groups, but it does not control receivables accounts.

E. General Business Posting Groups – These are used for revenue, COGS, and VAT postings, not receivables control accounts.

Microsoft Learn references

Posting Groups in Business Central

Set Up Customer Posting Groups

Comprehensive Detailed Explanation

The requirement: “You need to train users on how to process a special order for an established customer.”

From the case study:

“Special orders from new customers have a 25% prepayment. Established customers have only a 15% prepayment.”

Prepayments must be invoiced before the final invoice is posted.

Step-by-step process in Business Central:

Create a sales order

The user begins by creating a sales order for the special order.

Enter 15% in the Prepayment % field

Since this is for an established customer, the prepayment percentage is 15%.

The Prepayment % field on the sales order line or header controls how much must be prepaid before the order can be processed.

Enter the code for due on receipt in the prepayment payment terms code

Prepayments are typically due immediately. The code for “due on receipt” ensures that the prepayment invoice requires immediate payment.

Post and print the prepayment invoice

This generates the prepayment invoice for the customer and ensures that prepayment is received before delivery.

Why not “Enter the code for net 30 in the prepayment payment terms code”?

That applies to wholesale customer regular payment terms, not to prepayments. Prepayments are due immediately.

Why not 25%?

25% prepayment applies to new customers. For established customers, the requirement specifies 15%.

Microsoft Learn references

Set Up Prepayments

Process Sales Prepayments

Create Sales Orders with Prepayments

The requirement is to match each integration requirement with the correct Microsoft integration solution in Business Central.

Customer email collaboration → Business Central Outlook add-in The Business Central Outlook add-in allows users to create sales documents such as quotes, orders, or invoices directly from Outlook emails. This supports the requirement to create sales orders while collaborating with customers by email.

Sales team collaboration → Business Central app for Teams The Business Central app for Teams enables users to view, share, and even edit Business Central data such as customer records while working inside Microsoft Teams chat or channels. This aligns with the requirement to edit customer information while collaborating with the sales team in a group chat.

Customer notifications for sales campaign → Power Automate Power Automate is designed for automating workflows such as sending notifications, approval requests, or bulk communications. To notify all customers at once about a sales campaign, Power Automate can integrate Business Central data with email or marketing tools.

Why not Word template?

Word templates are mainly used for document formatting and mail merges but do not handle automated notifications at scale. For distributing campaign notifications to multiple customers, Power Automate is the correct tool.

Microsoft Learn references

Business Central and Outlook integration

Use Business Central in Teams

Automate Business Central with Power Automate

Query successful

Based on the image, the correct sequence of actions to configure a purchase order process is:

Add a vendor

Add a Purchaser Code

Add Items, including Quantity, to the lines

Change the Purchase Order to a Status of Released

This sequence follows the logical flow of creating and finalizing a purchase order for an audit trail:

Add a vendor: A purchase order must be linked to a specific supplier (vendor).

Add a Purchaser Code: This identifies who is creating the order, which is crucial for accountability and audit purposes.

Add Items, including Quantity, to the lines: You must specify what is being purchased and in what quantity.

Change the Purchase Order to a Status of Released: Releasing the purchase order locks it from further changes and makes it ready for processing, fulfilling the auditor ' s requirement for a finalized, traceable document.

Comprehensive Detailed Explanation

The requirement is to ensure that every transaction posted to a customer account includes the Customer Source dimension (e.g., Cash & Carry, Brokered). This is achieved by creating and enforcing a mandatory dimension rule in Business Central.

Step 1: Create a dimension code to identify the customer source

First, define a Dimension Code such as Customer Source.

This will hold values like Cash & Carry and Brokered.

Dimensions are the foundation for all reporting segmentation in Business Central.

Step 2: Create dimension values for the customer source dimension code

After creating the dimension, define the specific Dimension Values (e.g., Cash & Carry, Brokered).

These represent the business lines the company wants to track.

Step 3: Add the Customer table

To enforce the dimension on customers, link the dimension to the Customer table.

This ensures that every transaction involving a customer account requires this dimension.

Step 4: Set the Value Posting to Code Mandatory

On the Default Dimensions page, set Value Posting = Code Mandatory for the Customer Source dimension.

This forces users (or the system) to provide a dimension value on every transaction involving customers.

Without this, users might skip dimension assignment, leading to incomplete reporting.

Step 5: Select the Dimension Value Code that is used for the customer source

Finally, assign the correct Dimension Value (Cash & Carry or Brokered) to each customer record.

This ensures automatic defaulting during transaction entry, reducing user errors and maintaining consistency.

Why not the other actions?

Chart of Accounts: Not needed here, since the requirement applies to customers, not G/L accounts.

Account Type Default Dimension: Useful for G/L accounts, but here we are applying it at the Customer table level.

Search icon, Customers: While this helps you navigate, it’s not a required setup step in the sequence.

Microsoft References

Work with Dimensions in Business Central

Set Up Default Dimensions for Customers

Dimension Value Posting Options

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

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

Regular price: $20.00

Buying group discount: $18.00

Autumn promotion price: $19.00

Overstock special: 15% off regular price ($20 × 0.85 = $17.00)

However, the case study requires the system to always give the lowest available price.

Comparison of all active prices:

Regular = $20.00

Buying group = $18.00

Autumn promotion = $19.00

Overstock 15% discount = $17.00

Lowest available = $17.00. But since the customer belongs to a buying group and it’s also an overstock day, the system applies stacking rules: the overstock discount applies on top of buying group price.

$18.00 × 0.85 = $15.30.

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.

Comprehensive Detailed Explanation

The case study mentions reconciliation issues caused by manual entries being made directly into certain G/L accounts, which led to discrepancies between subledger balances (like customers, vendors, or inventory) and the General Ledger. To resolve this, Business Central allows you to restrict how accounts are posted.

Restrict use on → G/L Account Card

The most appropriate place to restrict usage of specific accounts (such as control accounts for A/R, A/P, or Inventory) is on the G/L Account Card.

Here, you can configure posting restrictions for each account individually (e.g., Accounts Receivable account should only be posted through the customer subledger, not by manual G/L journals).

Other options:

General Ledger Setup → Controls global accounting settings, not account-specific restrictions.

Sales & Receivable Setup → Defines control accounts but does not enforce restrictions.

Chart of Accounts → Displays accounts but restrictions are managed per account card.

Set value for → Direct posting

On the G/L Account Card, the field Direct Posting determines whether users can post manual entries directly into the account.

To prevent reconciliation issues, Direct Posting must be disabled (unchecked) for accounts controlled by subledgers (e.g., A/R, A/P, Inventory).

This ensures that postings only come from system-generated entries (like sales invoices, purchase invoices, or inventory adjustments) and not from manual journals that could break reconciliation.

Other options:

Reconciliation account → Relevant in SAP, not BC.

Check G/L account usage → Not a standard control in BC.

Gen. Posting Type → Defines how entries are posted (Sale, Purchase, Inventory), but does not enforce direct posting restrictions.

With this setup:

Reconciliation issues are avoided because control accounts cannot be posted to manually.

Users are guided to post through the proper subledger processes (sales, purchasing, inventory, etc.).

Financial integrity between subledgers and the G/L is maintained.

Microsoft References

G/L Account Card - Direct Posting Field

Prevent Direct Posting to Control Accounts

Chart of Accounts in Business Central

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

The scenario describes cash and carry sales, where customers pay immediately at the desk and sales invoices must be posted as paid in full at the time of sale. In Dynamics 365 Business Central, this is achieved by setting Payment Terms that indicate no delay between invoice date and due date.

Why D (Payment Terms = 0D)

The Payment Terms setup in Business Central allows you to define how the Due Date is calculated.

For cash and carry transactions, the invoice is due on the same day (zero days). Setting the Due Date Calculation to 0D ensures that the system always marks invoices as immediately due, reflecting the cash-and-carry business process.

This aligns with requirements: “Invoices must be posted at the cash and carry desk at the time of sale” and “Invoices already paid in full should not appear as outstanding on aging reports.”

Why not A (Payment Service)

Payment Services are used for integration with external services like PayPal or credit card gateways. Wide World Importers does not require a POS or online payment gateway—just simple cash handling at the desk.

Why not B (Direct Debit Mandate)

Direct Debit is used for recurring bank withdrawals (SEPA mandates, subscription-type payments). It does not apply to one-time, immediate cash payments.

Why not C (Payment Method = Bank Account)

While Payment Methods (e.g., Cash, Bank Transfer, Check) are also important for tracking how customers pay, the critical requirement in the scenario is ensuring the invoice is due immediately. That is achieved by Payment Terms = 0D, not by Payment Method alone.

Best Practice Setup in Business Central for Cash & Carry:

Payment Terms: 0D (ensures invoice due immediately).

Payment Method: Cash (ensures posted directly against the cash account).

Apply to invoices at posting: Invoices will automatically be shown as paid in full.

This combination ensures correct cash sales processing and eliminates the issue noted in the case study where invoices incorrectly appear in aging reports.

Microsoft References

Set Up Payment Terms in Business Central

Set Up Payment Methods in Business Central

Work with Payment Transactions

Create a Customer Discount Group

Create an Item Discount Group

Select the Item Discount Group for the Item

Comprehensive Detailed Explanation

To configure sales discounting in Dynamics 365 Business Central, you need to set up the relationship between customers and items so that the system can automatically apply the correct discounts during sales transactions. The process involves both customer grouping and item grouping.

1. Create a Customer Discount Group

This step defines which customers are eligible for group-based discounts (e.g., a retail chain, buying group, or brokers).

By creating a Customer Discount Group, you can later apply uniform discount rules across all customers belonging to that group, instead of configuring each customer individually.

2. Create an Item Discount Group

Next, you create Item Discount Groups to categorize items into discountable product lines (e.g., Olive Oils, Spices, Snacks).

This ensures that discount rules apply consistently across items in the same category, rather than having to define rules item by item.

3. Select the Item Discount Group for the Item

Finally, you link each relevant Item Card to the correct Item Discount Group.

This connection ensures that whenever a sales order/invoice is created for a customer belonging to a discount group and includes items in an item discount group, the system automatically applies the correct Sales Line Discounts.

Why not the other actions?

Define the Sales Invoice Discounts → Used for invoice-level discounts, but here the requirement is item/line-based discounting.

Define the Customer Special Sales Prices & Discounts → Used for customer-specific or promotional pricing, not for group-wide discount structures.

Configure Discount Posting in Sales & Receivable Setup → Relevant for accounting/reporting (whether discounts post separately) but not for setting up how discounts are determined and applied.

Define the Sales Line Discounts → This is the outcome of linking customer discount groups and item discount groups, but it requires the setup steps above first.

Microsoft References

Set Up Customer and Item Discount Groups

Work with Sales Line Discounts

Special Prices and Discounts in Business Central