In Dynamics 365 Business Central, the General Ledger Setup page controls how amounts are displayed and rounded.
* Amount Decimal Places specifies how many decimal places will be displayed for all monetary amounts in local and foreign currencies.
* A value of 3:3 means exactly 3 decimals will always be shown.
* This directly matches the requirement: "Monetary amounts for local currency must always display three decimal places."
* Unit-Amount Decimal Places controls the decimals for unit costs or prices on items, not for general monetary amounts.
* Inv. Rounding Precision sets the rounding for invoice totals, not for displaying all local currency amounts.
* Unit-Amount Rounding Precision applies to rounding of item unit costs/amounts.
* Amount Rounding Precision determines how monetary amounts are rounded during posting (for example, rounding to 0.01 or 0.001), but does not control how they are displayed.
Therefore, the correct configuration is to set Amount Decimal Places = 3:3 in General Ledger Setup.
:
Microsoft Learn: General Ledger Setup in Business Central
Microsoft Learn: Set Up Currencies

Explanation:
Create security rules that will grant users required access # Permission Sets Assign the predefined security rule sets to the requested users # User Card Comprehensive Detailed Explanation In Dynamics 365 Business Central, security is managed using Permission Sets and then assigned to users.
* Create security rules # Permission Sets
* A Permission Set defines which tables, reports, and pages a user can access (read, insert, modify, delete).
* To restrict access to a particular set of customer data, you would configure a Permission Set that includes only the required tables/records, possibly combined with security filters.
* Assign rules to users # User Card
* After creating or selecting predefined permission sets, you assign them to users via the User Card page.
* The User Card links Business Central users with the permissions they need to perform their job roles.
Other options not correct:
* Profiles (Roles): These control the Role Center (UI experience) but not security.
* Microsoft 365 admin center: Used for licensing and user account management but not Business Central data security.
Microsoft Learn References
* Permissions and Permission Sets
* Assign Permission Sets to Users
* Manage Users and Permissions

* You don't assign a purchase account directly on the G/L account.
* Instead, the system uses the combination of the General Business Posting Group (vendor side) and General Product Posting Group (item/service side).
* In the General Posting Setup table, this combination points to the appropriate Purchase Account in the chart of accounts.
Thus, the correct answer is C.
Reference:
Set Up General Posting Groups

RapidStart Services is the recommended tool in Business Central to migrate opening balances. It allows importing of master data (vendors, customers, items, chart of accounts) and transaction data (like opening G/L balances, customer/vendor ledger entries) by using configuration packages (Excel templates). This ensures correct table mapping, validation rules, and system integrity, which directly meets the goal.
References:
Use RapidStart Services to Import Data
Migrate Business Data from Other Finance Systems

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.
Reference:
Record Purchase Prices and Discounts - Microsoft Learn
Vendor Card Overview - Microsoft Learn