Explanation:

The requirement is to report discounts received on purchases separately from costs. In Business Central this is managed by:
* Purchase & Payables Setup
* This page contains checkboxes such as Invoice Discounts for Discount Posting and Line Discounts for Discount Posting.
* When enabled, the system posts purchase discounts to dedicated accounts rather than netting them off the purchase cost accounts.
* This ensures discounts are reported separately.
* General Posting Setup
* Here, you specify the G/L accounts for different posting types, including:
* Purch. Inv. Disc. Account # where invoice discounts are posted.
* Purch. Line Disc. Account # where line discounts are posted.
* By pointing these to dedicated discount accounts, you can report discounts independently from purchase costs.
Why not the others:
* Adjust for Payment Disc. and Calc. Inv. Discount only affect calculation logic, not how discounts are posted.
* Purch. Account or Purchase Variance Account are for actual purchase costs or variances, not discount reporting.
References:
Microsoft Learn: Set Up Purchases and Payables
Microsoft Learn: Posting Groups in Business Central

Explanation:

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.

Explanation:

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

Explanation:

In Dynamics 365 Business Central, the Due Date Calculation field in payment terms defines how the due date is calculated from the posting date or document date. The syntax uses a formula similar to date formulas elsewhere in Business Central.
* D10 # 10 days from today
* The D stands for "days."
* D10 means add 10 days to the document date/posting date.
* 10D # The next 10th day of the next month
* Writing the day number before the "D" means the due date is set to that specific day of the following month.
* Example: If the invoice date is January 25, the due date becomes February 10.
* 1M+10D # One month + 10 days
* 1M adds one month.
* +10D adds ten more days.
* Example: Invoice on Jan 15 # Feb 15 + 10 days # Feb 25.
This mapping ensures proper setup of payment terms for various business scenarios.
Microsoft Learn References
* Date Formulas in Business Central
* Set Up Payment Terms

When implementing Business Central Online, user authentication and management are handled through Microsoft 365 / Azure Active Directory. New users must first be created in Microsoft 365/Azure AD. To bring them into Business Central, you run the action Update Users from Office 365 on the Users page. This synchronizes the users from Microsoft 365 into Business Central for the first time.
* A. Get New Users from Office 365 - This is a distractor; the actual action name is Update Users from Office 365.
* B. Create a new entry on the User Setup page - The User Setup page is used for defining additional settings (permissions, time registration, approval, etc.) for already-existing users, not creating new ones.
* D. Import User Groups - This is for importing group permission sets, not adding users.
Therefore, the verified method is C. Update Users from Office 365.
:
Microsoft Learn - Manage Users and Permissions in Business Central Online Microsoft Learn - Add Users to Business Central Online