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

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

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

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

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.

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

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 Report Layout Selection page allows you to change the layout (Word/RDLC) used for a report object, but it does not change which report object is used by default.

To set a new report object as the default for purchase orders, you must configure it in Report Selection – Purchase with Usage = Order.

The requirement is to import vendor opening balances from Excel, where many vendors use foreign currencies. Since balances must be entered via General Journal Lines (table 81), the correct process with configuration packages is:

Create configuration package for table 81 Gen. Journal Line

This table holds general journal transactions and is required to import opening balances.

Select the fields with correct processing order including Currency Code

Since vendors use foreign currencies, the Currency Code field must be included along with Account Type, Account No., Posting Date, Document No., Description, Amount, and Amount (LCY).

Export to Excel and populate the data

Export the template from the configuration package, then copy/paste the vendor balances into Excel.

Import and validate the Excel file, then apply package

Load the populated Excel back into the configuration package, validate the data, and then apply it to the general journal for posting.

Incorrect alternatives:

Options that omit Currency Code would not support foreign currency vendors.

" Import from Excel and then post to the general journal " skips the validation step and configuration package flow.

Microsoft Learn References

Use Configuration Packages to Import Data

General Journal Lines (Table 81)

In Dynamics 365 Business Central, when using Approval User Setup with Approver Chain as the limit type:

Each approver has a defined Approval Limit (the maximum amount they can approve).

If a document exceeds the requester’s approval limit, the workflow escalates through the Approver Chain until a user with sufficient limit is found.

The workflow continues until the purchase order reaches an approver with authority greater than or equal to the document amount.

For this question:

User1 creates a purchase order for $1,100.

Since the order is above User1’s limit, it escalates to User2.

If User2’s limit is not sufficient to fully approve $1,100, it then escalates to User3, who has a higher approval limit.

The workflow only releases the purchase order once all required approvers (User2 and User3 in this case) approve it.

Therefore, the correct chain of events is:

User2 receives the approval request first.

After User2 approves, it is routed to User3.

Once both User2 and User3 approve, the purchase order is released.

Microsoft Learn References:

Set up approval users and approval chains

Use approval workflows in Business Central

Profiles (roles) define what a user sees when they sign in. They can be assigned in three ways:

By linking User Groups (profiles can be attached to groups).

On the User Personalization page directly per user.

By default profile assignment (if no explicit profile is set, the system applies a default).

The User Card and Profile Card don’t directly assign profiles.

When a cash receipt is applied incorrectly, you cannot simply delete or reverse it — instead, you must unapply the entries.

Steps:

From the relevant Customer Ledger Entry, select Unapply Entries.

Unapply the second payment first (because payments are applied in sequence).

Unapply the first payment (the erroneous one).

Reapply the second payment correctly to the customer ledger entry.

This way, the first erroneous cash receipt is removed, and the correct receipt remains applied.

Why not B or C?

Reverse Transaction is for reversing journal entries or posted G/L transactions, not for applied customer ledger entries. Why not D?

Posting a reversing cash receipt is unnecessary; the built-in Unapply Entries function is the proper approach.

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.

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.

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

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

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

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

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

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:

“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

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

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

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

To configure payment terms in Dynamics 365 Business Central:

Due Date Calculation (B → 30D): Sets the invoice due date to 30 days after the document date.

Discount Date Calculation (C → 10D): Allows a payment discount if the invoice is paid within 10 days.

Discount % (D → 2): Grants a 2% discount for early payment.

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, the Payment Reconciliation Journal can automatically match imported bank statement lines with open customer/vendor ledger entries. To reduce manual review, you can set up payment matching rules.

The goal here is: " Mark automatically matched payments as not requiring review if they match the highest degree of confidence. "

The three most important criteria used to achieve a high-confidence match are:

Statement Amount (A)

Ensures that the bank statement line amount equals the open invoice amount.

This is the strongest indicator of a correct match.

Transaction Date (D)

Ensures the payment date aligns with the posting or due date window.

Helps differentiate between otherwise similar transactions.

Transaction Text (E)

The system uses transaction descriptions/reference text from the bank statement and compares it to invoice/customer reference numbers.

This greatly increases the confidence level of automatic matches.

Why not the others?

B. Account number: Bank account number is already tied to the journal; not typically part of the matching rules.

C. Related-party fields: More relevant to advanced compliance/KYC scenarios, not to standard payment application matching.

Microsoft Learn References

Apply Payments Automatically and Reconcile Bank Accounts

Set Up Payment Application Rules

The scenario:

The customer wants to sell items that are not normally counted in the company ' s warehouse.

In Microsoft Dynamics 365 Business Central, you can define items as different Types:

Inventory → Stocked, physically tracked in the warehouse with inventory valuation.

Non-Inventory → Items that are not tracked in inventory. They can still be sold or purchased but are not included in inventory counts or valuations. This is commonly used for items like office supplies, spare parts not worth tracking, or resale products not stocked.

Service → Used for non-physical services (consulting, labor).

Resource → Used for capacity (e.g., machine or person for projects).

Item Charge → Used to distribute costs (freight, customs, handling) to item costs, not for selling tangible items.

Why the correct choice is A (Non-Inventory Item type):

Non-Inventory items allow the company to sell or purchase items without managing them in warehouse stock.

This matches the requirement that the company does not want the items counted in inventory.

Why not the others:

B. Item charge → Adds costs to items (e.g., freight), not for selling goods.

C. Inventory Item type → This would force tracking and counting in the warehouse.

D. Resource → Represents labor or machine capacity, not goods for sale.

Microsoft Learn References

About Item Types in Business Central

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

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

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

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

Service type is used for intangible services, not utilities.

The scenario states:

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

They are configuring the Vendor Card.

When creating a purchase order, a validation error occurs.

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

Option Review:

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

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

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

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

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

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

In Dynamics 365 Business Central, if an incorrect quantity has been received on a purchase order but not yet invoiced, you can undo the receipt directly from the Posted Purchase Receipt. This action reverses the item ledger entries created by the receipt and reopens the purchase order line so it can be corrected.

Step-by-step:

Navigate to the Posted Purchase Receipts page

Go to Search → Posted Purchase Receipts to find receipts already posted.

Open the posted purchase receipt

Select the document that contains the incorrect receipt quantity.

Select Undo Receipt

On the receipt Lines, use Functions → Undo Receipt.

This action will reverse the receipt posting.

Confirm the action

The system will ask for confirmation in a pop-up. Select Yes to complete.

⚠️ Notes:

Undo is only possible if the purchase receipt is not yet invoiced.

If invoiced, you must instead use purchase credit memos to correct.

Actions like Find Entries or Order Tracking are useful for reviewing entries but not required to undo receipts.

Microsoft Learn References

Undo Receipt Posting in Business Central

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.