Free Microsoft MB-310 Practice Questions

Correct answer: A. Yes

The solution correctly addresses all four requirements. Setting Delete close of year transactions to Yes allows the fiscal year close to be run again with only the most recent entry remaining. Setting Create closing transactions during transfer to Yes enables posting of Q1 adjustments to Period 13. Setting Fiscal year status to permanently closed to No keeps the year open for adjustments. Setting Transfer profit and loss dimensions to Close All carries all P&L dimensions to retained earnings. Setting Financial dimensions will be used on the Opening transactions to No is correct because dimensions are being transferred, not used on opening transactions. Setting all periods to On Hold status completes the requirements.

Why the other options are wrong

• B. This configuration does not meet the stated goals.

Correct answer: B. No

This solution fails to meet the requirements because setting Fiscal year status to permanently closed to Yes prevents posting of Q1 adjustments into Period 13 of the previous year. Additionally, setting Financial dimensions will be used on the Opening transactions to Yes contradicts the requirement that dimensions carry over from P&L to retained earnings; this setting would prevent proper dimension carryover. The Delete close of year transactions set to Yes is correct, but the other parameter settings create conflicts with the stated goals.

Why the other options are wrong

• A. This configuration does not meet the stated goals.

Correct answer: B. No

This solution fails because setting Delete close of year transactions to No means previous closing entries are not deleted, so running the close again will result in multiple closing entries rather than only the most recent one remaining. Setting Create closing transactions during transfer to No prevents the creation of new closing transactions, which contradicts the ability to run the close again. While not setting the year to permanently closed and setting Transfer profit and loss dimensions to Close All are correct, the other two parameter settings do not satisfy the core requirements.

Why the other options are wrong

• A. This configuration does not meet the stated goals.

Correct answer: A, C, E. Configure the Fiscal year close parameters; Set up the year end close template; Create the next fiscal year

Configuring the Fiscal year close parameters (A) establishes the rules for closing the period. Setting up the year-end close template (C) defines how dimensions and accounts are handled during closure. Creating the next fiscal year (E) ensures the system is ready for future transactions after closing. Configuring the ledger calendar for the new fiscal year (B) is handled as part of creating the fiscal year structure, not as a separate action. Validating the main account type (D) is a data quality check but not a primary configuration action required for year-end close.

Why the other options are wrong

• B. Ledger calendar configuration is part of fiscal year creation, not a separate prerequisite action.
• D. Main account type validation is a data check, not a core configuration action for year-end close.

Correct answer: C. when creating multiple balanced ledger entries based on transaction types or accounts

Posting definitions are used to create multiple balanced ledger entries automatically based on transaction types or accounts. This allows the system to post to multiple accounts simultaneously in a balanced way. Option A describes financial dimension defaulting, which uses dimension defaults, not posting definitions. Option B describes restriction logic handled by account structures or rules. Option D describes automatic posting to specific accounts, which is a posting definition feature but option C is the more comprehensive correct answer as it directly describes the primary purpose of posting definitions.

Why the other options are wrong

• A. Financial dimension defaults come from vendor records or dimension default settings, not posting definitions.
• B. Dimension restrictions are enforced through account structures and advanced rules, not posting definitions.
• D. While posting definitions can post to AR accounts, option C more accurately describes the core purpose of creating multiple balanced entries.

Correct answer: B, C, D. financial transactions; fixed asset depreciation; budget cycles

Fiscal calendars are used to define periods for financial transactions (B), establish cycles for budgeting (D), and determine depreciation schedules for fixed assets (C). Standard work hours (A) and shift work hours (E) are operational scheduling concerns handled by workforce management systems, not fiscal calendars. Fiscal calendars are specifically designed for financial and accounting period management, not for labor or shift scheduling.

Why the other options are wrong

• A. Standard work hours are part of workforce management, not fiscal calendar functionality.
• E. Shift work hours are operational scheduling concerns, not related to fiscal calendars.

Correct answer: C, D, E. Import bank statements from the Data management workspace; Navigate to Import statement on the Bank Statements page of Cash and Bank Management; Select Import statement for multiple bank accounts in all legal entities, and then upload a zip file

Bank statements can be imported from the Data management workspace (C), which is the standard import location for bulk data. Selecting Import statement for multiple bank accounts with a zip file (E) allows batch import across multiple accounts. Navigating to Import statement on the Bank Statements page (D) provides direct access to the import function. Selecting Account reconciliation on the bank account form (B) is for reconciliation setup, not for importing statements. Selecting all bank accounts and uploading all files together (A) is not the proper method; accounts must be handled individually or through proper batch processes.

Why the other options are wrong

• A. Uploading all files together for all accounts at once is not the correct import procedure.
• B. Account reconciliation is selected to enable the reconciliation feature, not to import statements.

Correct answer: D. Basis

The Basis allocation method allows definition of how and in what proportion source amounts are distributed to destination lines based on specified allocation bases. This method is appropriate for distributing overhead utility expenses to departments according to defined proportions such as square footage, headcount, or other business metrics. Equally (C) distributes amounts evenly regardless of actual usage. Fixed weight (B) uses predetermined weights but is less flexible for proportion-based allocation. Distributing source document amount equally (A) is a simple equal split unsuitable for proportional overhead distribution.

Why the other options are wrong

• A. Equal distribution does not account for department-specific consumption of utilities.
• B. Fixed weight is less suitable than Basis for proportion-based overhead allocation.
• C. Equally dividing amounts ignores the actual consumption needs of departments.

Correct answer: A. Yes

Creating two separate account structures directly addresses both requirements: one for expense accounts includes the department and division dimensions to enforce their use, while the second for balance sheet accounts excludes all financial dimensions, preventing users from selecting them. This is the most straightforward and effective approach in Dynamics 365 Finance for segment-specific dimension requirements.

Why the other options are wrong

• B. This solution is incomplete because it does not address how to prevent dimensions from appearing for balance sheet accounts.

Correct answer: B. No

Configuring only one account structure with advanced rules cannot fully meet the requirements. A single structure that attempts to hide dimensions for balance sheet accounts using advanced rules would still require those dimensions to be present in the structure itself. Advanced rules modify behavior but cannot eliminate the visual presence of dimension fields, so users would still see options to select dimensions for balance sheet accounts, violating the second requirement.

Why the other options are wrong

• A. A single account structure cannot provide the necessary differentiation between expense accounts requiring dimensions and balance sheet accounts that should not display dimension options.

Correct answer: B. No

The solution does not meet the goal because it is inconsistent and incomplete. Configuring posting profiles at the main account level and then also at individual vendor account and customer group levels creates redundancy and confusion. The correct approach is to configure currency revaluation posting profiles at the module level (General ledger, Accounts payable, Accounts receivable, and Bank) for each applicable currency with appropriate unrealized and realized gain/loss accounts, not at mixed granularity levels.

Correct answer: A. Add $100,-000 in the bank credit limit.

To prevent a bank account from going below a defined credit limit when posting transactions, you must add the credit limit amount (in this case $100,000) in the bank credit limit field. This ensures the system validates transactions against this threshold and prevents overdrafts beyond the allowed credit facility.

Why the other options are wrong

• B. While the amount is correct, this option lacks the proper specification needed in the actual system field.
• C. Setting a credit limit on an invoicing vendor account does not control the bank account balance; it applies to payables management.
• D. The Control Balance option on the general ledger account does not specifically prevent the bank account from exceeding credit limits.

Correct answer: A, C, E. Create an access group called month end access for Accounts payable and General ledger team members; Configure the financial period close workspace tasks to the Accounts payable and General ledger teams only; Assign the security group month end access on the ledger calendar form for the modules they need access to.

To restrict posting to only Accounts Payable and General Ledger during month-end closing, you must: Option A creates a security group containing only those team members, establishing role-based access. Option C configures the financial period close workspace to assign tasks and access permissions to only these teams. Option E applies the security group to the ledger calendar form to enforce module-specific access restrictions for the closing period. Option B setting all modules to none would block all users including AP and GL, which defeats the requirement. Option D moving the period to on hold is a status change but does not implement granular access control by team.

Why the other options are wrong

• B. Setting all modules to none prevents all posting, contradicting the requirement to allow AP and GL access.
• D. Period on-hold status is a global lock that does not enable selective team access.

Correct answer: B, C, E. Perform automatic matching and creation of reconciliation journals; Import bank statements through the Data entity framework; Configure matching rules and matching groups for bank transactions.

Advanced bank reconciliation requires configuring bank statement import (B) to bring in external data, performing automatic matching and creation of reconciliation journals (C) to reconcile differences, and configuring matching rules and matching groups (E) to define how transactions match. A number sequence (D) is not required for bank reconciliation, and importing through data entity framework (A) is an alternative method not necessary when using the built-in import functionality.

Why the other options are wrong

• A. Data entity framework import is an alternative approach, not a standard requirement for advanced bank reconciliation.
• D. Number sequences are not a required configuration step for implementing advanced bank reconciliation.

Correct answer: D. two financial dimension sets

Financial dimension sets allow creation of predefined combinations of dimensions that appear as selectable options in inquiry reports. Two dimension sets address this requirement perfectly: one set containing main account with all four dimensions, and a second set containing main account with only Business Unit and Cost Center. Users can then select which dimension combination to use when running the trial balance inquiry, providing the flexibility needed for both reporting views.

Why the other options are wrong

• A. Account structures define dimension requirements for posting, not inquiry report parameter options.
• B. Derived financial dimension hierarchies organize dimension members hierarchically but do not provide multiple combination options for reports.
• C. Group dimension functionality is used for consolidation and does not provide selectable reporting combinations in inquiry parameters.

Correct answer: B, C, D. The revenue recognition reallocation process can be reversed after it is run; You can run the revenue recognition reallocation process multiple times; It multiple sales orders are involved, all sales orders must be for the same customer account.

The revenue recognition reallocation process in Dynamics 365 Finance can be reversed after execution (option B), allowing corrections if needed. The process can be run multiple times (option C) to accommodate multiple contract changes. When multiple sales orders are involved in a reallocation, all orders must be for the same customer account (option D) to ensure proper revenue recalculation and allocation consistency. These three characteristics define the flexibility and constraints of the reallocation functionality.

Why the other options are wrong

• A. The reallocation process can be run on project sales orders as well as standard sales orders.
• E. Sales orders involved in reallocation must use the same transaction currency; different currencies are not supported in a single reallocation.
• F. The process can be run multiple times as needed when contract terms change; it is not limited to a single execution.

Correct answer: C. Default financial dimension

Default financial dimension configuration on the journal name allows you to specify that all payments must post to a particular financial dimension value, in this case the headquarters' business unit. This setting automatically populates the financial dimension on journal lines, ensuring all customer payment journal entries are consistently posted to the correct business unit dimension.

Why the other options are wrong

• A. Journal control manages posting rules and restrictions but is not the mechanism for setting default financial dimension values.
• B. Posting restriction limits when journals can be posted but does not assign financial dimensions to journal entries.
• D. Journal approval manages the review workflow but does not control financial dimension assignments.

Correct answer: C. Balance sheet

Due to and Due from accounts are used to track intercompany balances and represent amounts owed between legal entities. These accounts must be Balance sheet accounts because they represent obligations and receivables that exist at a point in time, not transactions over a period. Balance sheet accounts (assets, liabilities, and equity) are the appropriate classification for tracking intercompany payables and receivables.

Why the other options are wrong

• A. Profit and loss accounts record income and expenses over a period, not balance sheet positions.
• B. Expense accounts are for recording costs incurred, not intercompany obligations.
• D. While Due to accounts may be liabilities, the question asks for the main account type category, which is Balance sheet.
• E. While Due from accounts may be assets, the question asks for the main account type category, which is Balance sheet.

Correct answer: A. Yes

This solution implements the complete workflow for recognizing unearned revenue over time. Posting project fees to the unearned revenue account captures the liability, the deferral template defines how revenue will be recognized, configuring the deferral default automates the process for project fees, and using the deferral schedule recognizes revenue systematically over the contract period. This approach properly handles extended warranty service revenue recognition.

Why the other options are wrong

• B. The described solution correctly addresses all components needed for proper revenue recognition of extended warranty services.

Correct answer: A, C. the revenue schedules details; the revenue schedules

In Microsoft Dynamics 365 Finance, the revenue recognition schedule can be viewed in two main locations: the Revenue Schedules page (option C), which shows all revenue schedules in a list view, and the Revenue Schedules Details page (option A), which provides detailed information about a specific revenue schedule including milestone breakdowns and revenue allocation. These are the dedicated pages designed for reviewing revenue recognition schedules for customers.

Why the other options are wrong

• B. An invoiced sales order displays order details but is not a dedicated page for viewing revenue recognition schedules.
• D. An invoiced purchase order is for procurement, not revenue recognition, which applies only to sales transactions.
• E. While this sounds relevant, there is no page specifically titled 'the revenue recognition schedule' as a distinct entity from the revenue schedules pages.

Correct answer: B. No

Selecting Balance + packing slip as the credit type only covers balance and packing slip amounts, not all customer documents. To set up mandatory credit limits for all documents, the credit type must be set to Balance + All, which encompasses all document types including orders, invoices, and packing slips.

Why the other options are wrong

• A. This solution fails to meet the goal because Balance + packing slip credit type does not cover all customer documents; it excludes orders and other document types.

Correct answer: B. 48 months

A four-year contract requires 48 months of revenue allocation since revenue recognition operates on a monthly basis. Setting up the revenue schedule with 48 months ensures that revenue is properly distributed across each month of the four-year period. Using years or incorrect month counts would not provide the granular monthly allocation needed for accurate revenue recognition over the contract term.

Why the other options are wrong

• A. 60 months exceeds the four-year contract period.
• C. Years are not the appropriate unit for a monthly revenue recognition schedule in Dynamics 365 Finance.
• D. 4 months does not cover the four-year contract duration.

Correct answer: A, D. Validate the default item sales tax group setup for the item being sold; Validate the sales tax group setting on the customer from the sales order.

To validate sales tax setup, you must check the default item sales tax group associated with the item being sold, as this group controls which tax codes apply to that item. Additionally, you must validate the sales tax group setting on the customer, as the customer's tax group determines which tax codes are applicable for that customer. Together, these validations ensure both the item and customer have proper tax groups assigned for correct calculation.

Why the other options are wrong

• B. Sales tax jurisdiction is associated with sales tax codes, not directly with item sales tax groups in the validation process.
• C. Sales tax codes are not assigned directly to customers; instead, customers are assigned to sales tax groups.
• E. Sales tax codes are not assigned directly to items; instead, items are assigned to item sales tax groups that contain codes.

Correct answer: A. Posting group

Posting groups are used to ensure that sales tax payable is posted to the same collection of accounts across all legal entities. A posting group defines the default GL accounts used for specific transaction types, and when configured at the entity level, it standardizes which accounts receive sales tax payable postings regardless of the legal entity processing the transaction. This provides consistency across the organization.

Why the other options are wrong

• B. Tax jurisdictions define geographic tax rules and rates but do not control account posting destinations.
• C. Use tax payable account is specific to use tax, not sales tax payable.
• D. Tax groups are collections of tax codes but do not directly control the GL accounts where sales tax payable is posted.

Correct answer: D. item sales tax group

When a sales order line is created with an item, the system calculates sales tax by matching the sales tax group (already populated) with the item sales tax group. The item sales tax group field must be populated on the item master record to enable this calculation. The system then intersects the customer's sales tax group with the item's sales tax group to determine applicable tax codes. Without the item sales tax group, the sales tax calculation cannot occur even if the sales tax group is present. Options A, B, and C address different configurations that do not directly trigger line-level sales tax calculation.

Why the other options are wrong

• A. Sales tax codes are associated with groups, not populated individually on line items.
• B. Item group is an inventory classification unrelated to sales tax calculation.
• C. Customer address is used for tax jurisdiction determination but doesn't directly enable tax calculation on the line.

Correct answer: A. a Ledger daily journal workflow that uses the organizational hierarchy for journal posting, associated with the General ledger journal name

A Ledger daily journal workflow associated with the General ledger journal name and using the organizational hierarchy is the system-led review process that enforces approval before posting. This workflow functionality automatically routes journal entries for controller review based on organizational structure, ensuring entries cannot be posted until approved.

Why the other options are wrong

• B. A saved query allows viewing posted journals but does not prevent posting or enforce a review process beforehand.
• C. Manual journal approval assigned to a user group does not establish a systematic workflow-driven review process.
• D. Assigning security roles does not create an enforced review process; it only grants permissions.

Correct answer: A, C, D. Select intercompany journal names; Create intercompany main accounts to use for the due to and due from accounting entries; Define intercompany accounting setup by creating legal entity pairs defining originating and destination companies.

To set up intercompany accounting between legal entities, you must: select intercompany journal names that will be used to record intercompany transactions, create intercompany main accounts for the due to and due from accounting entries that track balances between entities, and define intercompany accounting setup by creating legal entity pairs that clearly specify which entity is the originating company and which is the destination company. These three actions establish the foundation for systematic, auditable intercompany transactions.

Why the other options are wrong

• B. Intercompany accounting must be configured in both the originating entity and destination entity, not just one, to ensure proper bilateral recording.
• E. Intercompany accounting must be configured in both entities to maintain proper separation and audit trails in each legal entity's records.

Correct answer: A. Set up the length of the period to 1 year and divide the period according to the quarterly configuration.

To configure a 4-4-5 quarterly setup in Dynamics 365 Finance, you set up the period length to 1 year and then divide that annual period according to the 4-4-5 quarterly configuration, which means 4 weeks, then 4 weeks, then 5 weeks in each quarter. This approach allows you to structure the periods within the fiscal year to match the specific weekly configuration required.

Why the other options are wrong

• B. Configuring to 12 months and adjusting ending dates does not properly implement the 4-4-5 weekly structure needed for this configuration.
• C. While setting period length to 1 year is part of the process, simply adjusting ending dates without explicitly dividing according to the quarterly configuration does not ensure proper 4-4-5 setup.
• D. A 13-month period length is incorrect; the fiscal year should be 1 year in length, with the quarters internally structured as 4-4-5 weeks.

Correct answer: B. No

Using quotation marks in dimension fields makes dimensions optional, not required or prohibited as needed. The solution incorrectly treats all dimensions uniformly with quotations, which cannot enforce that liability accounts have zero dimensions or that expense account 6999 requires the customer dimension. Advanced rules alone on a single structure cannot differentiate the specific requirements across different account ranges and individual accounts.

Why the other options are wrong

• A. Quotation marks indicate optional dimensions, failing to require dimensions where mandatory (6000-6998, 6999) and failing to prohibit them entirely for liability accounts (2000-2999).

Correct answer: A, D. bank account; bank group

Bank accounts define individual accounts at each bank and store account-specific information. Bank groups allow you to group multiple bank accounts together, and when you configure a bank group, all accounts within that group can be updated simultaneously with default information. This setup enables the system to default bank information when new accounts are created and to update all balances for accounts in a group at the same time.

Why the other options are wrong

• B. Bank reasons are used to categorize and explain bank transactions, not to group accounts or manage defaults.
• C. Bank reconciliation is a process for matching bank statements to general ledger records, not a configuration entity for grouping accounts.

Correct answer: A, E. Configure the exchange rate provider; Run the import currency exchange rate process

To automate currency exchange rates from the European Central Bank, you must first configure the exchange rate provider (option A) to establish the connection to the ECB data source. Then, you must run the import currency exchange rate process (option E) to automatically pull and update the current rates into the system. Together, these eliminate manual entry and ensure the system always uses current ECB rates.

Why the other options are wrong

• B. Currency revaluation is used to adjust existing balances at period end, not to set up automated rate imports.
• C. Creating currencies defines which currencies exist in the system but does not automate rate imports.
• D. Dual currency configuration allows parallel currency tracking but does not establish automated ECB rate feeds.

Correct answer: C. payment reference

In the method of payment setup for electronic payments, the payment reference field must be set as mandatory to ensure accounts receivable clerks capture the wire number for each electronic payment transaction. This field is specifically designed to hold wire transfer identifiers and reconciliation information.

Why the other options are wrong

• A. Bank transaction type is used to categorize transactions but does not specifically capture wire number information.
• B. Payment ID is a system-generated identifier, not the field where wire numbers are entered by users.
• D. Deposit slip is used for check deposits and cash handling, not for electronic wire payment identification.

Correct answer: D. Designate EUR as the system reference currency for triangulation.

When requiring JPY to be converted to EUR and then to USD, EUR must be designated as the system reference currency for triangulation. This creates a conversion path where JPY→EUR→USD occurs automatically. A direct JPY-to-USD conversion would bypass the EUR intermediate step, defining an exchange rate type doesn't enable triangulation, and enabling JPY conversion doesn't specify the triangulation path.

Why the other options are wrong

• A. A direct conversion would not route through EUR as required by the business process.
• B. Defining an exchange rate type does not establish triangulation conversion paths.
• C. Enabling JPY conversion does not specify that EUR should be used as the triangulation reference currency.

Correct answer: C, D. Process hierarchy; Quiet days

To configure the automatic collection task in Dynamics 365 Finance credit and collections, you must set up the Process hierarchy (option C), which defines the workflow and sequence of collection activities, and Quiet days (option D), which specifies the waiting period before a collection task is triggered. The Process hierarchy determines how collection tasks are organized and prioritized, while Quiet days prevents excessive collection attempts by enforcing a minimum interval between actions.

Why the other options are wrong

• A. Posting profiles control how transactions are posted to the general ledger but are not part of automatic collection task configuration.
• B. Aging period definitions are used for customer aging analysis but are not required to configure automatic collection tasks specifically.

Correct answer: B, D. Print all of the collection letters; Post the collection letters.

Posting the collection letters creates the accounting entries that formally document collection efforts in the system. Printing collection letters produces the physical or electronic communications needed to contact customers about delinquent accounts. These two steps are essential to execute the collection process. Canceling or deleting letters would prevent proper collection management.

Why the other options are wrong

• A. Canceling collection letters after posting would reverse the collection effort documentation.
• C. Deleting collection letters prevents the record of collection attempts and proper audit trails.

Correct answer: B. No

The solution is incomplete and does not meet the goal. The currency revaluation posting profiles must be configured for all four modules mentioned (General Ledger, Accounts Payable, Bank, and Accounts Receivable), but the solution only addresses specific accounts for GL, vendors for AP, customers for AR, and bank accounts. The solution fails to configure profiles for all main accounts in General Ledger (only specific and all accounts are mentioned inconsistently), and does not establish a comprehensive approach that covers unrealized and realized gains/losses across all applicable currencies for each module systematically.

Why the other options are wrong

• A. The solution does not comprehensively address all required posting profiles for all four modules and their respective entities.

Correct answer: C, D. For new employees, use a Debit accrual scheme. In the ledger accrual, set the offset to the employee's first pay date; For current employees, use a Debit accrual scheme. In the ledger accrual, set the offset to the first day of the fiscal year.

For new employees, a Debit accrual scheme must be used with the offset set to the employee's first pay date, ensuring transactions are recognized when the new employee begins receiving pay. For current employees, a Debit accrual scheme with offset to the first day of the fiscal year ensures that bi-weekly payroll transactions are accrued systematically throughout the year, with the insurance premium expense recognized consistently with each pay period. This approach properly handles the timing difference between when insurance is paid (twice yearly) and when it must be recognized (twice monthly with payroll).

Why the other options are wrong

• A. Credit accrual schemes are used for liability accruals, not for expense accruals like insurance premiums, and setting offset to fiscal year start does not align with individual first pay dates.
• B. Using a Credit accrual scheme is incorrect for insurance expense recognition, and setting the offset to first pay date for current employees would not establish the consistent fiscal year baseline needed for systematic accrual.

Correct answer: A. Configure the account structure to specify which financial dimensions are valid for which main accounts.

The account structure in Dynamics 365 Finance is the primary control mechanism for enforcing valid combinations of main accounts and financial dimensions. By configuring the account structure, you define which financial dimensions are valid for which main accounts at the validation level, preventing invalid combinations from being posted to the general ledger. This provides proactive prevention rather than reactive training or post-entry correction.

Why the other options are wrong

• B. Training users to manually validate does not prevent invalid entries systematically and relies on human compliance rather than system controls.
• C. Financial dimension sets are used for filtering and grouping dimensions in user interfaces, not for validating main account and dimension combinations.
• D. Associating main accounts to dimensions on the dimension setup form does not enforce combination validity at the transaction posting level.

Correct answer: A. Create one revenue schedule with milestones.

To handle the complex revenue recognition scenario with multiple milestones (25% at sale, 50% at shipment, 25% at installation) plus warranty revenue recognized over three years, you should create one revenue schedule with milestones. This single schedule can define all the revenue recognition points and conditions for each unit, allowing the system to properly allocate revenue based on when each milestone event occurs. The milestones approach accommodates both the performance obligations and the warranty terms.

Why the other options are wrong

• B. Creating a new revenue schedule for each unit would be inefficient and difficult to manage at scale.
• C. Reallocation posting is used when contract terms change after initial recognition, not for initial configuration.
• D. While contract terms are important, the specific configuration method required is the milestone-based schedule structure.

Correct answer: C. Set up an import project for the bank statement in a Data management workspace using files provided by Microsoft.

Setting up an import project in the Data management workspace using Microsoft-provided files is the correct approach for configuring BAI2 bank statement format import. This workspace provides the infrastructure and pre-built templates needed to properly import and process bank statements in the required format for the reconciliation process.

Why the other options are wrong

• A. Importing as a template does not establish the proper import framework needed for recurring bank statement processing.
• B. A batch job alone does not configure the import format itself; it only schedules execution.
• D. A journal name is not the appropriate configuration location for bank statement format import setup.

Correct answer: C, D. Assign posting profiles based on item groups and transaction types; Configure posting profiles to use different ledger accounts for physical and financial updates.

Assigning posting profiles based on item groups and transaction types allows control of posting for different transaction categories. Configuring profiles to use different ledger accounts for physical and financial updates enables separate posting control for receiving versus invoicing. Together, these configurations provide the granular control needed per legal entity and transaction type. Vendor-level configuration is too specific and global assignment lacks the required granularity.

Why the other options are wrong

• A. Vendor-level configuration does not provide the required control at the item group and transaction type level needed for separate receiving and invoicing posting.
• B. Global-level assignment cannot provide the separation required for different transaction types and individual legal entities.

Correct answer: C. Monthly by days

The 'Monthly by days' recognition basis is a valid option for allocating revenue across occurrences in Dynamics 365 Finance. This basis divides revenue allocation on a monthly basis calculated by the actual number of days in each month, providing accurate revenue distribution when the recognition period spans multiple months with varying day counts.

Why the other options are wrong

• A. Mid-month split is not a standard recognition basis available in the system.
• B. First of month is not a supported recognition basis option.
• D. First of next month is not a recognized basis for revenue allocation in Dynamics 365 Finance.

Correct answer: B, D. Set Create necessary currency pairs to True; Add a key named BaseCurrency and value of USD.

To resolve posting failures for the March 1 to June 30 period, you must set Create necessary currency pairs to True (option B) to ensure the system automatically generates all required Euro-USD currency pair records for every date in the period. You must also set Import as of start date to Apr01 (option D) to instruct the exchange rate provider to import rates starting from April 1, filling the gap where the fixed rate was previously configured and preventing import failures before the fixed rate period. Together, these ensure continuous rate availability for the entire period.

Why the other options are wrong

• A. FloatCurrencies key does not address the root cause of posting failures or exchange rate availability gaps.
• C. Setting Import as of start date to Apr01 alone does not create the necessary currency pairs required for all dates in the posting period.
• E. Preventing import on national holidays would further restrict data availability and worsen the posting failure problem.

Correct answer: A, D. Set the value of the override date field at the legal entity level to be more restrictive; Set the value of the override date field at the shared level to be less restrictive.

To configure main account overrides at the legal entity level for a six-month period, you can manipulate the restrictiveness of override dates at two levels: Option A sets the override date field at the legal entity level to be more restrictive, allowing that specific entity to have different main accounts during the override period. Option D sets the override date field at the shared level to be less restrictive, creating the time window necessary for the legal entity exception. Together, these create a controlled override window specific to that legal entity. Options B and C would either maintain or reduce restrictions at the wrong level, preventing the legal entity-specific override from functioning properly.

Why the other options are wrong

• B. Setting shared level to more restrictive would constrain all legal entities, not enable one entity's override.
• C. Setting legal entity level to less restrictive would apply to all periods, not create a six-month exception.

Correct answer: A. Assign an invoice template to a customer on the invoice tab of the customer record.

Recurring free text invoices are generated only for customers that have the invoice template assigned to them. You assign it from the customer record by using the Invoice tab to open recurring invoices and add the template with its start date and frequency. Without that customer assignment the Generate recurring invoices job has nothing to process.

Why the other options are wrong

• B. A maximum billing amount only limits how much is invoiced and does not make the job create invoices.
• C. The free text invoice template form does not have a customer association that drives recurring invoice generation.
• D. Customer posting profiles control ledger accounts and cannot hold invoice templates.

Correct answer: C. Enter a main account in the fixed asset posting profiles for the acquisition.

The error indicates that no main account is configured for the acquisition transaction type in the fixed asset posting profile. To resolve this error, you must enter a main account in the fixed asset posting profiles specifically for the acquisition transaction type. The posting profile is where transaction type accounts are defined and linked to asset groups, enabling the system to post acquisitions correctly.

Why the other options are wrong

• A. Linking a main account to the asset group book does not configure posting profiles for specific transaction types.
• B. Creating a main account alone does not resolve the error; the account must be configured in the posting profile.
• D. The offset account in the journal is a manual workaround, not a proper configuration of the posting profile where the transaction type account should be defined.

Correct answer: A. Yes

The solution correctly configures account structures to enforce dimensional requirements. Using asterisks marks dimensions as mandatory, while asterisks with quotation marks make dimensions optional. The configuration properly distinguishes between expense accounts 6000-6998 (requiring department, division, and project with optional customer), revenue accounts 4000-4999 (requiring department and division with optional project and customer), liability accounts 2000-2999 (no dimensions), and expense account 6999 (requiring all four dimensions). This meets all stated goals.

Correct answer: B. Planned costs

Planned costs costing version allows viewing and analyzing cost changes for manufactured items without affecting the currently active costs used in inventory valuations. This type maintains a separate version where future or alternative costs can be modeled and reviewed before activation. Indirect cost allocation configures overhead distribution methods. Standard costs are the active costs used for valuations. Actual cost tracking records historical costs without predictive capability. Only planned costs provide the isolation needed to view changes without affecting active operations.

Why the other options are wrong

• A. Indirect cost allocation configures overhead distribution, not cost change visualization.
• C. Standard costs are the active version used in inventory valuation, not for viewing alternative scenarios.
• D. Actual cost tracking records historical costs, not prospective changes without affecting current costs.

Correct answer: A, B, E. Configure the behavior for forecasts of transactions that affect the liquidity accounts of the company; Identify and list all the liquidity accounts; Run the cash flow calculation process.

Configuring cash flow reports requires three key steps. First, identify and list all liquidity accounts (option B) to determine which accounts affect cash flow. Second, configure the behavior for forecasts of transactions that affect liquidity accounts (option A) to establish how the system will project cash movements. Third, run the cash flow calculation process (option E) to execute the actual forecasting and generate the reports. These three actions work together to establish and execute cash flow reporting.

Why the other options are wrong

• C. Defining the number sequence is an administrative task for transaction numbering, not specific to cash flow report configuration.
• D. Account structure configuration is a general ledger setup task not specifically required for cash flow reports.

Correct answer: D. Enable the Post foreign currency realized gains/losses for ledger settlements feature.

To automatically handle realized gains and losses for foreign currency differences during ledger settlement without manual intervention, the 'Post foreign currency realized gains/losses for ledger settlements' feature must be enabled. This feature allows the system to automatically generate and post realized gains/loss transactions when settling foreign currency amounts, eliminating the need for manual journal entries. Creating a separate chart of accounts for foreign currency transactions adds unnecessary complexity. Disabling the Awareness feature contradicts the requirement to improve the settlement process. Restricting transactions to the same fiscal year is impractical and creates operational constraints that prevent proper settlement management.

Why the other options are wrong

• A. A separate chart of accounts for foreign currency is not required and adds unnecessary complexity.
• B. Disabling the Awareness feature contradicts the goal of improving the settlement process.
• C. Restricting all transactions to the same fiscal year is impractical and unnecessary for settlement.

Correct answer: B. No

Consolidate with import is used when source data comes from external systems or files outside of Dynamics 365 Finance. Since the scenario specifies that all companies and data already reside in Dynamics 365 Finance, using the import consolidation method is unnecessary and not the appropriate solution. The online consolidation method is the correct approach for this scenario.

Why the other options are wrong

• A. Import consolidation is designed for external data sources, not for data already within the same Dynamics 365 Finance instance.

Correct answer: C, D. Create an account structure for all the balance sheet accounts. Set up an advanced rule for the Shareholder distribution account for the Principal dimension; Create an account structure for balance sheet accounts without Shareholder distribution. Then, create a second account structure for Shareholder distribution that includes all required dimensions.

Both options C and D achieve the goal correctly. Option C uses a single account structure for balance sheet accounts with an advanced rule applied specifically to the Shareholder distribution account to add the Principal dimension requirement. Option D uses two separate account structures, segregating Shareholder distribution into its own structure with all required dimensions included. Both approaches ensure Business Unit and Department are available for all balance sheet accounts while adding Principal only for the Shareholder distribution account.

Why the other options are wrong

• A. Creating new main accounts for each principal does not configure the account structures or dimensions needed to support the reporting structure.
• B. Creating a main account and using an advanced rule alone does not ensure that Business Unit and Department dimensions are properly configured for all balance sheet accounts.

Correct answer: A. Customer groups

Customer groups define clusters of customers that share common characteristics and enable the finance team to perform all the required functions: creating sales budgets by customer group, generating trade statistics such as weekly sales by group, defining ledger posting profiles at the group level, and defining terms of payment that apply to groups of customers. Customer groups are the configuration functionality that organizes customers into logical sets for these purposes.

Why the other options are wrong

• B. Customer payment terms define payment conditions but do not cluster customers for budget creation, statistics generation, or ledger posting configuration.
• C. Customer posting profiles define accounting posting rules by customer group, but this is typically configured after customer groups are established and does not serve as the primary clustering mechanism.
• D. Customer sales agreements are contracts for specific sales terms and do not provide the grouping functionality needed for budgets, statistics, posting, and payment term management across customer clusters.

Correct answer: B. No

Setting up posting restrictions on the general journal controls which types of accounts or transactions can be posted, but this does not specifically restrict journals to only ledger-type transactions. Posting restrictions address allowed accounts or dimensions, not transaction types. To restrict general journals to ledger-type transactions only, you would need to configure the journal to reject non-ledger transaction types at a different level, such as through posting profiles or validation rules tied to account types.

Why the other options are wrong

• A. Posting restrictions alone do not differentiate between ledger-type and non-ledger-type transactions; they control account or dimension restrictions, not transaction type restrictions.

Correct answer: D. a manual journal approval with the journal assigned to the controller’s user group

Manual journal approval must be configured with the journal assigned to the controller's user group. This ensures that all journal entries from employees are routed to the controller for review and approval before posting. Assigning the journal to the employee user group (as in option A) would not ensure controller review. Modifying the controller's security role alone does not create the approval workflow mechanism. An alert when a journal name is created is administrative notification, not a review control mechanism. Option D correctly establishes the approval routing where the controller must approve before posting occurs.

Why the other options are wrong

• A. Assigning the journal to the employee user group does not route entries to the controller for review.
• B. Modifying security roles alone does not create an automated approval workflow process.
• C. An alert on journal name creation is administrative notification, not an approval control mechanism.

Correct answer: D. Financial period close workspace

The Financial period close workspace is specifically designed to enable collaboration and track progress toward month-end close across multiple legal entities. This workspace provides visibility into closing tasks, assigns responsibilities to team members, monitors task completion status, and maintains an audit trail of all closing activities across the organization's legal entities. It directly addresses the need to track and coordinate closing activities across entities.

Why the other options are wrong

• A. Financial reporting is used for generating financial statements and reports, not for tracking or managing the close process.
• B. Financial insights workspace provides analytical dashboards and insights but does not manage the period close workflow or cross-entity coordination.
• C. Electronic reporting is used for exporting data in various formats for compliance and regulatory purposes, not for managing the closing process.

Correct answer: A. Yes

Creating a separate elimination company and manually entering elimination entries is a valid and supported approach in Dynamics 365 Finance. This elimination company can then be incorporated into the financial reporting consolidation process or used directly in the consolidation module. This method meets the goal of moving consolidation and elimination functionality from an external tool into Dynamics 365 Finance, providing better control and integration with the financial data.

Why the other options are wrong

• B. Manual elimination companies are a recognized and supported consolidation approach in Dynamics 365 Finance.

Correct answer: A, D, E. workflow approval; default values; journal control

To meet all stated requirements, three elements must be configured: Workflow approval provides the internal control and materiality limits, Account type restrictions satisfy the requirement to restrict account types and segment values, and Default values ensure accurate capture of offset accounts, currency, and financial dimensions. Journal control is subsumed under account type configuration, and journal type is a basic structural choice rather than a specific control element.

Why the other options are wrong

• B. Account type restrictions are part of the overall account type element configuration.
• C. Journal type is a structural classification, not a configuration element for meeting these specific control requirements.

Correct answer: A. Use the Specified allocation method.

The schedule has an uneven first installment of $10,000 followed by three equal $5,000 installments due on the 15th. The Specified allocation method lets you enter each payment line with its own amount and due date, which is the only method that can represent this mix. Fixed amount and fixed quantity methods split the balance into equal installments and cannot produce the larger first payment.

Why the other options are wrong

• B. Entering the $25,000 total alone does not define how the amount is divided into installments or when each one is due.
• C. A fixed quantity of 5 would split the total into five equal payments, which does not match the $10,000 plus three $5,000 schedule.
• D. The Fixed amount method generates equal installments of the fixed amount, so it cannot create the different $10,000 first payment.

Correct answer: A. Yes

Enabling the 'Block activation of pending cost' setting in the costing version configuration prevents pending costs from being automatically activated and applied to inventory valuations. This creates a formal control mechanism requiring manual review and explicit approval before new standard costs become active, ensuring that cost changes cannot be applied without a deliberate, documented decision. This directly addresses the requirement that new costs must not be automatically applied without formal review.

Why the other options are wrong

• B. The 'Block activation of pending cost' setting is the correct configuration to prevent automatic application of unreviewed costs.

Correct answer: A. Yes

Selecting the Balance + All credit type in the Accounts Receivable parameters form combined with selecting the Mandatory credit limit checkbox on the Customers form ensures that credit limits are enforced across all customer document types, including orders, invoices, packing slips, and all other transactions. This configuration comprehensively implements mandatory credit limits.

Why the other options are wrong

• B. This solution successfully meets the goal by combining the correct credit type setting (Balance + All) with the mandatory flag at the customer level.

Correct answer: D. Age customer balances.

Before using the Collections list page to monitor the collection process, you must age customer balances. Aging the customer balances calculates how long invoices have been outstanding and categorizes them by age buckets (current, 30 days, 60 days, etc.). This aged data is essential for the Collections list page to display delinquent customers and enable effective collection monitoring and prioritization.

Why the other options are wrong

• A. Setting up customer groups organizes customers for reporting but is not a prerequisite for collections monitoring.
• B. While customer pools can be used for collections, aging balances is the foundational prerequisite that must occur first.
• C. Updating financials is a period-end process and not required before using the Collections list page.

Correct answer: A. Jacksonville Duval CT FL FL Special 1 FL Special 2 FL Special 3 FL Special 4 Lake Worth Palm Beach CT

When a sales tax group and an item sales tax group are both assigned, the tax codes used for calculation are the intersection (common codes) of both groups. The JAX sales tax group contains: Jacksonville, Duval CT, FL, FL Special 1, FL Special 2, FL Special 3, FL Special 5. The default item sales tax group contains: Jacksonville, Duval CT, FL, FL Special 1, FL Special 2, FL Special 3, FL Special 4, Lake Worth, Palm Beach CT. The codes appearing in both are: Jacksonville, Duval CT, FL, FL Special 1, FL Special 2, and FL Special 3, which corresponds to option A.

Why the other options are wrong

• B. This option includes FL Special 5, which appears only in the JAX sales tax group and not in the default item sales tax group, and excludes FL Special 4, which appears in the item group but not the sales group; neither should be selected as they are not in the intersection.

Correct answer: A. Configure exchange rate provider, create exchange rate type, and import the currency exchange rates.

The standard approach to configuring currency exchange rates involves three steps: configure the exchange rate provider, create the appropriate exchange rate type, and import the currency exchange rates. Dynamics 365 Finance provides built-in providers and does not require custom development. Users select from predefined providers, set up rate types based on their business needs, and then import the rates for use in transactions.

Why the other options are wrong

• B. Selecting HTML key values is not part of the standard exchange rate provider configuration process.
• C. Developer involvement with HTML code is not required for standard exchange rate provider setup.
• D. Developer involvement with XML code is not required for standard exchange rate provider setup.

Correct answer: A, B. Asynchronous; Scheduled batch

To automatically transfer subledger entries to the general ledger in Dynamics 365 Finance, you must configure both asynchronous processing and a scheduled batch. Asynchronous processing allows the transfer to happen without blocking user operations, while scheduled batch ensures the transfer runs automatically at defined intervals. Together, these settings enable the automatic, unattended transfer of subledger transactions to the general ledger.

Why the other options are wrong

• C. Batch jobs is a broader concept; the specific configuration requires scheduled batch and asynchronous settings.
• D. Scheduler job is not the correct terminology for this configuration in Dynamics 365 Finance subledger setup.

Correct answer: B. No

Creating a costing version with planned costs instead of standard costs does not address the requirement for manual approval and formal review of standard costs. The company specifically needs standard costs to be manually approved before use in inventory valuations. Using planned costs changes the costing methodology rather than implementing the required approval workflow.

Why the other options are wrong

• A. Changing the costing type to planned costs does not establish the required manual approval process for standard costs.

Correct answer: B. No

The solution is incomplete and does not fully meet the goal. Configuring a single account structure for expense accounts addresses the first requirement, but it does not prevent users from selecting dimensions for balance sheet accounts. To fully meet both requirements, you need a separate account structure for balance sheet accounts that excludes the dimensions, or you need to configure the account structure with different rules for different account types. A single account structure cannot simultaneously allow dimensions on expenses while preventing them on balance sheet accounts.

Why the other options are wrong

• A. While the solution addresses part of the requirement, it fails to prevent dimension selection on balance sheet accounts, making it an incomplete solution.

Correct answer: B. Payment method: Net Month: 1 Days: 0 Payment days: 10th -

To set a due date on the 10th of the following month, configure Net with Month: 1 and Days: 0, then set the payment day to the 10th. Month: 1 adds one month from the invoice date, Days: 0 adds no additional days, resulting in the 10th of the following month. Option A adds 10 days to the next month making it the 20th, Option C sets current month making it this month's 10th, and Option D leaves payment day blank making the configuration incomplete.

Why the other options are wrong

• A. This configuration would result in the 20th of the following month (1 month + 10 days), not the 10th.
• C. Current month with Month: 0 would make the due date the 10th of the current month, not the following month.
• D. Leaving the payment days blank means the configuration is incomplete and will not calculate the correct due date.

Correct answer: A. Actual start date

When allocating revenue across occurrences using recognition basis in Dynamics 365 Finance, 'Actual start date' is a valid recognition basis option. This basis allows revenue to be allocated based on the actual start date of the revenue recognition period, providing flexibility in how revenue is distributed across the contract term.

Why the other options are wrong

• B. Mid-month split is not a standard recognition basis option in the system.
• C. First of month is not a recognized basis option for revenue allocation.
• D. Monthly by dates is not a standard recognition basis in Dynamics 365 Finance revenue recognition configuration.

Correct answer: B, D, E. Create a row definition that includes all appropriate accounts in all companies in the rows; Create a reporting tree that includes a reporting node for each company; Use the Reporting Unit field to select the tree and reporting unit for each column.

To generate consolidated financial statements using a building block group, you must create a row definition that includes all appropriate accounts across all companies (option B) to establish what data is reported. You must create a reporting tree that includes a reporting node for each company (option D) to structure the consolidation hierarchy. Finally, you must use the Reporting Unit field to select the tree and reporting unit for each column (option E) to map each column to the appropriate company data within the consolidated structure. These three elements work together to aggregate data across the organization.

Why the other options are wrong

• A. Creating a column definition for period and year mapping is not necessary when using building block groups and reporting trees, as the reporting units and tree structure handle the period mapping.
• C. Creating a column definition with a financial dimension column for each company is not the appropriate approach for building block group consolidation; the reporting tree structure serves this purpose instead.

Correct answer: A. an Advanced ledger entry workflow that uses the organizational hierarchy for journal posting, associated with the Advanced ledger journal name

An Advanced ledger entry workflow configured with the organizational hierarchy for journal posting, associated with the Advanced ledger journal name, provides a system-led review process. This workflow automatically routes journal entries through the organizational hierarchy for approval before posting, ensuring the controller can review all standard journal entries as required. This is the proper configuration for establishing an automated approval workflow.

Why the other options are wrong

• B. An alert only notifies the controller but does not establish a review and approval process before posting.
• C. Manual journal approval requires the controller to actively intervene; a workflow-based approach is more systematic and scalable.
• D. Modifying security roles grants approval privileges but does not create a structured review process or enforce approval before posting.

Correct answer: A. Reporting tree definition

A reporting tree definition is used to configure the organizational structure and hierarchy in financial reports. It defines how business units, departments, and cost centers are organized and related to one another, allowing the system to roll up financial data according to the company's organizational structure for hierarchical financial reporting. Row definitions control which GL accounts and dimensions appear in reports. Column definitions specify the time periods and calculations shown. Financial reports themselves are the output, not the configuration of structure.

Why the other options are wrong

• B. Row definitions specify which accounts and dimensions display, not organizational structure.
• C. Financial reports are the output, not the configuration mechanism for organizational hierarchy.
• D. Column definitions control time periods and calculations, not organizational structure.

Correct answer: B. Select payment reference

Setting the payment reference as mandatory enforces users to enter the wire number for electronic payments. The payment reference field is the standard location where wire transfer numbers, check numbers, and other payment identifiers are recorded in Dynamics 365 Finance accounts receivable. This configuration ensures compliance with the requirement to document electronic payment identifiers.

Why the other options are wrong

• A. Bank transaction type selection does not enforce entry of a wire number.
• C. Payment ID is not the standard field for wire number entry in accounts receivable payment methods.
• D. Deposit slip is used for physical deposit documentation, not electronic payment wire numbers.

Correct answer: B. No

While this solution uses two account structures appropriately, the notation is incorrect for the requirements. Asterisks with quotes (asterisk and quotes together) make dimensions optional, not required. To require dimensions, only asterisks should be used. To prohibit dimensions, they should not appear in the structure. The mixed notation in the customer dimension for account 6999 does not achieve the requirement to make customer mandatory for that account.

Why the other options are wrong

• A. The solution's use of combined asterisks and quotes fails to enforce mandatory dimensions where required and cannot properly distinguish between optional and required dimension states.

Correct answer: A, D, E. Create templates that contain the required tasks within the closing process and assign to closing role; Create task areas and descriptions; Designate resources and their scope based on closing roles.

To configure the Financial period close workspace, you should: create templates that contain required tasks within the closing process and assign them to closing roles to standardize the workflow, designate resources and their scope based on closing roles to clarify responsibilities and permissions, and assign a ledger calendar to the closing process to align the close schedule with the organization's fiscal calendar. These configurations enable structured collaboration and tracking of period-end activities.

Why the other options are wrong

• B. Creating a separate closing schedule for every legal entity adds unnecessary complexity; a single schedule can be applied across multiple entities with appropriate filtering.
• C. While a ledger calendar is important, the specific configuration of assigning it is part of the overall setup but is not listed as a primary configuration process in the workspace setup sequence.

Correct answer: A. Associate the vendor record to the tax authority.

To configure the system to remit tax payments to tax authorities in Dynamics 365 Finance, you must associate a vendor record to each tax authority. This links the tax authority (Florida, Nebraska, Washington) to a vendor record so that the system knows where to send payments and how to process the remittance transactions.

Why the other options are wrong

• B. A customer record is used for sales transactions and receivables, not for tax payment remittance to authorities.
• C. While settlement periods are relevant to tax processing, they are not the primary configuration needed for tax payment remittance; the vendor association is.
• D. Jurisdictions are used for tax determination on transactions, not for configuring payment remittance to tax authorities.

Correct answer: B. Configure the internet service as essential.

For a cable and internet company, the internet service is the primary recurring revenue stream and should be configured as essential. The router and modem are one-time hardware sales that accompany the essential service. Marking internet service as essential ensures proper revenue recognition treatment for the main business line while other items are handled as supplementary components.

Why the other options are wrong

• A. Creating a revenue schedule for all items together does not properly distinguish between recurring service revenue and one-time product sales.
• C. Configuring all items as essential is incorrect because only the internet service is the primary essential revenue stream; routers and modems are supplementary.
• D. Posting router and modem sales to deferred revenue is unnecessary; only the service subscription should be deferred, not one-time hardware sales.

Correct answer: C. financial dimension sets

Financial dimension sets allow users to select predefined combinations of dimensions for reporting. By creating two financial dimension sets, one containing main account, department, and division, and another with main account and department only, these options become available as parameters in the trial balance report. This is the standard Dynamics 365 Finance feature for providing multiple dimension combination choices in inquiry reports.

Why the other options are wrong

• A. Ledger validation enforces posting rules but does not configure report parameter options.
• B. Configuring financial dimensions themselves does not automatically create selectable parameter options for specific combinations in reports.
• D. Account structures define which dimensions can be used with accounts but do not provide parameter selection options for inquiry reports.

Correct answer: C. a manual journal approval with the journal assigned to the controller’s user group

Manual journal approval assigned to the controller's user group ensures that journal entries created by employees are routed to the controller for review before posting. This creates a system-led review process where the controller's group receives and approves the journals. Assigning approval to the employee user group (D) would create a circular review, Advanced ledger entry workflows address advanced entries not standard journals, and signing limit policies manage approval thresholds by amount rather than creating a review workflow.

Why the other options are wrong

• A. Advanced ledger entry workflows are for advanced ledger entries, not standard General ledger journals.
• B. Signing limit policies manage approval based on transaction amounts, not review workflows.
• D. Assigning to the employee user group creates a review by those who entered the transactions, defeating the purpose.

Correct answer: D. On the Cash flow forecasting setup form, use the Dependent Accounts setup to specify which account and percentage is associated to the main account.

In Dynamics 365 Finance, the Dependent Accounts setup on the Cash flow forecasting setup form allows you to specify which accounts contribute percentages to main accounts. This feature enables the client's requirement that specific percentages of main accounts contribute to different cash flow forecasts. Option A is vague and doesn't reference the correct form structure. Option B discusses parent/child relationships for accounts, which is a chart of accounts configuration, not cash flow forecasting setup. Option C addresses Accounts Payable configuration sequencing, which is unrelated to the cash flow forecasting percentage allocation requirement.

Why the other options are wrong

• A. This describes the process incorrectly and doesn't specify the Dependent Accounts feature.
• B. Parent/child account relationships address hierarchy, not cash flow forecast percentage allocation.
• C. AP and vendor posting profile configuration sequencing is unrelated to cash flow forecasting percentage setup.

Correct answer: B. No

Setting a default offset account on the journal name does not restrict the journal to ledger-type transactions only. A default offset account merely provides a convenience feature for common postings, but it does not prevent non-ledger transactions from being entered. The journal would still accept other transaction types.

Correct answer: C. Create a sales tax ledger posting group for each state. Associate a settlement account to a main account for vendor accounts in the vendor posting profile.

The sales tax ledger posting group holds the settlement account that receives the tax liability when the settle and post sales tax process runs. Creating one ledger posting group per state, each with that state's main account as the settlement account, and assigning it to the state's tax codes moves each state's liability to the correct account automatically every month.

Why the other options are wrong

• A. A settlement period controls how often tax is settled and for which authority, but it does not determine the main account that receives the liability.
• B. The sales tax group does not hold a vendor account, and a vendor account would not direct liability to state main accounts.
• D. A sales tax authority links to a vendor for payment and reporting, not to the main account used when settling tax.

Correct answer: C. a Ledger daily journal workflow that uses the organizational hierarchy for journal posting, associated with the General ledger journal name

A Ledger daily journal workflow associated with the General ledger journal name enables a system-led review process where journal entries can be held for approval before posting. This workflow uses organizational hierarchy to route approvals to the controller, meeting the requirement for a review process before posting. Advanced ledger entry workflows are not the standard approach for this scenario, alerts do not enforce review, and signing limit policies do not create a workflow-based approval process.

Why the other options are wrong

• A. Advanced ledger entry workflows are not the standard configuration for general ledger journal review processes.
• B. An alert merely notifies the controller but does not enforce a review and approval workflow before posting.
• D. Signing limit policies define monetary thresholds for approval authority but do not create a structured workflow for journal entry review.

Correct answer: A, E. The sales tax group is populated on the line, but the item sales tax group is missing; The sales tax group and item sales tax group are selected, but the sales tax code is not associated with both groups.

Two scenarios prevent sales tax calculation: Option A identifies that if the sales tax group is populated on the line but the item sales tax group is missing from the item master, the system cannot intersect the two groups to find applicable tax codes, resulting in no calculation. Option E states that if both the sales tax group and item sales tax group are selected but the sales tax code is not associated with both groups, the intersection produces no valid tax codes to apply. Options B and C address post-calculation configurations (settlement accounts and authorities) that do not prevent the initial calculation. Option D describes an incomplete scenario where the sales tax group lacks proper code associations.

Why the other options are wrong

• B. Sales tax settlement accounts affect posting, not the calculation decision.
• C. Sales tax authority configuration affects remittance, not initial calculation triggers.
• D. This scenario describes a configuration issue but not a complete explanation for calculation failure.

Correct answer: A, C. General ledger entry; Customer entry

When writing off a delinquent customer balance in Dynamics 365 Finance, two journal line types are created: a General ledger entry to record the expense or allowance adjustment, and a Customer entry to clear the accounts receivable balance from the customer's account. These two entries work together to remove the balance from the books while maintaining proper accounting records.

Why the other options are wrong

• B. NSF payment entries are used for returned checks and insufficient funds situations, not for customer write-offs.
• D. Item transaction entries relate to inventory and product transactions, not customer receivables write-offs.

Correct answer: A. Yes

The solution correctly describes the proper approach for consolidation in Dynamics 365 Finance when all entities reside in the same system. Using Consolidate online with eliminations handled during the process or as a proposal, and setting up transactions to post in the consolidation legal entity, is the appropriate method. This approach allows the system to manage intercompany transactions and produce consolidated financial statements directly within Dynamics 365 Finance, meeting the stated goal of replacing the external reporting tool.

Why the other options are wrong

• B. The solution accurately describes the standard consolidation process in Dynamics 365 Finance for entities within the same system.

Correct answer: D. Monthly

In Dynamics 365 Finance, recognition basis for allocating revenue across occurrences uses time-based periods. Monthly is the standard recognition basis used for revenue allocation schedules, allowing revenue to be recognized over equal monthly intervals. This is the proper method for systematic revenue recognition in the system.

Why the other options are wrong

• A. Median price is not a recognition basis; it is a pricing concept not used for revenue allocation timing.
• B. Revenue schedule is the object that contains the recognition basis, not a basis itself.
• C. First of next month is not a standard recognition basis option in the system.

Correct answer: D. Delete the 14D2% cash discount code from the next discount code list value of 10D5%.

To enforce the constraint that cash discounts can only be given if payments are made within 10 days, you must delete the 14D2% cash discount code from the next discount code list value of 10D5%. This prevents the sequential chain from extending to the 14-day period, ensuring that once the 10D5% discount window closes, no further discounts are available. This configuration maintains the business rule that limits cash discount eligibility to the 10-day window.

Why the other options are wrong

• A. Creating a new 14D10% code does not address the requirement to limit discounts to within 10 days and contradicts the stated constraint.
• B. Creating a 10D14% code does not align with the discount structure and fails to enforce the 10-day limit.
• C. Simply deleting the 14D2% code without removing it from the next discount code list does not prevent the sequential chain from operating.

Correct answer: A. a Ledger daily journal workflow that uses the organizational hierarchy for journal posting, associated with the General ledger journal name

A Ledger daily journal workflow associated with the General Ledger journal name and configured to use the organizational hierarchy creates a system-led review process. This workflow automatically routes journal entries to appropriate reviewers based on the organizational hierarchy before posting, ensuring controlled and systematic review without manual assignment. A saved query allows viewing but does not enforce a review process. Manual journal approval assigned to user groups does not create an automated workflow. Signing limit policies are for purchase orders and payment approvals, not journal entry reviews.

Why the other options are wrong

• B. A saved query only enables viewing of journals after posting, not a review process before posting.
• C. Manual journal approval with user group assignment does not create a systematic workflow-driven process.
• D. Signing limit policies apply to procurement and payments, not General Ledger journal reviews.

Correct answer: B. No

Setting up journal control to specify account structure and ledger segment does not restrict journals to ledger-type transactions only. Account structure and ledger segment configuration manage dimensional requirements and account validation but do not filter by transaction type. This approach does not meet the goal of restricting to ledger-type transactions exclusively.

Correct answer: A. Yes

Setting up elimination rules and running elimination proposals is the proper method for handling intercompany eliminations in Dynamics 365 Finance. Configuring rules to post to companies marked with 'Use for financial elimination process' in the legal entity setup is the correct configuration. This approach automates the elimination process and ensures transactions post to the appropriate elimination company, meeting the goal of performing eliminations within Dynamics 365 Finance.

Why the other options are wrong

• B. Elimination rules with proposals are the standard Dynamics 365 Finance mechanism for automated elimination processing.

Correct answer: C. a Ledger daily journal workflow that uses the organizational hierarchy for journal posting, associated with the General ledger journal name

A Ledger daily journal workflow associated with the General ledger journal name enables a system-led review process where journal entries are held pending approval before posting. This workflow can use organizational hierarchy to route approvals appropriately. This is the proper workflow-based configuration that enforces mandatory review and approval before posting, meeting the controller's requirement for a systematic review process.

Why the other options are wrong

• A. Adjusting security roles alone does not create a workflow; it only grants permissions and does not enforce a mandatory review process.
• B. Advanced ledger entry workflows are not the standard configuration for general ledger journal review; they are used for a different purpose.
• D. Manual journal approval with user group assignment does not constitute a system-led process; the Ledger daily journal workflow provides the automated, system-led approach required.

Correct answer: B, E. ledger posting group; tax code for each legal entity

To track Use Tax in Dynamics 365 Finance, two parameters are required: a tax code for each legal entity to handle jurisdiction-specific Use Tax rules, and a ledger posting group to ensure Use Tax is posted to the correct single ledger account for sales tax payable as specified in the requirement. These two elements together enable proper Use Tax tracking across multiple legal entities and jurisdictions.

Why the other options are wrong

• A. A single sales tax code for Brazil is not sufficient and does not address Use Tax tracking for the United States, Canada, and Mexico destinations.
• C. A single sales tax code for the United States does not account for the multiple legal entities and jurisdictional requirements needed for Use Tax.
• D. Taxation rule configuration is not the primary parameter needed for Use Tax setup in this scenario.

Correct answer: B. a Ledger daily journal workflow that uses the organizational hierarchy for journal posting, associated with the General ledger journal name

A Ledger daily journal workflow using organizational hierarchy for journal posting, associated with the General ledger journal name, implements a system-led review process where journals are routed through the hierarchy before posting. This allows the controller to review entries before they are posted to the ledger. Signing limit policies apply to approval amounts rather than workflow routing, Advanced ledger entry workflows are for advanced ledger entries not standard GL journals, and alerts only notify but don't enforce review.

Why the other options are wrong

• A. Signing limit policies are based on transaction amounts, not workflow routing for reviews.
• C. Advanced ledger entry workflows apply to advanced ledger entries, not standard General ledger journals.
• D. Alerts notify the controller but do not enforce a system-led review process before posting.

Correct answer: A. Use journal control to specify which account types are valid for the General ledger journal.

Journal control is the feature in Dynamics 365 Finance that restricts which account types can be used in specific journals. By using journal control on the General journal, you can specify that only Ledger account types are valid, preventing users from posting project or bank transactions to the general ledger. This is the standard method for enforcing account type restrictions at the journal level.

Why the other options are wrong

• B. Advanced ledger entries are used for specific reconciliation and adjustment scenarios, not for restricting account types in journals.
• C. Voucher series manage number sequences and do not control account type restrictions.
• D. Journal templates define structure but journal control is the specific feature for account type restrictions.

Correct answer: B. Check number as mandatory

To ensure that a refund check is generated before a user can post the refund payment journal, you must configure the check number as mandatory (option B). This ensures that the check number is assigned and the physical check is prepared before the payment journal entry can be posted, maintaining proper control over check issuance and reconciliation.

Why the other options are wrong

• A. Payment reference as mandatory does not enforce check generation; it only requires a reference description.
• C. Bank transaction type is a classification field but does not control check generation requirements.
• D. Payment status as sent indicates the payment has been transmitted but does not prevent posting before check generation.

Correct answer: A, C, E. the Sales tax group on the Customer record; the Item Sales tax group on the Item record; the Sales tax codes

To ensure taxable customers are charged sales tax for taxable items in their delivery location, you must configure: the Sales tax group on the Customer record to identify which customers are taxable, the Item Sales tax group on the Item record to identify which items are subject to tax, and the Sales tax codes which define the actual tax rates and rules that apply based on the delivery location and other factors. These three elements work together to determine when and how much sales tax to charge.

Why the other options are wrong

• B. Terms of delivery setup handles shipping and delivery logistics but does not directly configure tax application rules.
• D. Sales reporting codes are used for reporting and analysis purposes, not for determining tax applicability at the point of transaction.

Correct answer: C. Monthly by dates

Monthly by dates is the correct recognition basis for allocating revenue across occurrences. This basis allows revenue to be recognized based on specific dates within each month, providing flexibility for distributing revenue according to the company's revenue recognition policy and the nature of the service delivery or contractual obligations.

Why the other options are wrong

• A. First of month is not a standard recognition basis option in Dynamics 365 Finance for revenue allocation across occurrences.
• B. Mid-month split is not a recognized revenue allocation basis in the system for revenue recognition purposes.
• D. Revenue schedule refers to the overall schedule of payments or recognition, not a specific recognition basis method for allocating revenue.

Correct answer: C. letters of credit

Letters of credit are the appropriate financial instrument for managing international sales transactions. They provide security for both the buyer and seller in cross-border commerce by ensuring payment is made upon fulfillment of conditions. This is a standard mechanism used in international trade and is the correct feature to configure in Dynamics 365 Finance for managing international sales.

Why the other options are wrong

• A. Bank statements are records of account activity, not a configuration tool for international sales management.
• B. Purchase agreements are used for procurement, not for managing international sales transactions.
• D. Promissory notes are debt instruments and are not the standard mechanism for international sales transactions.

Correct answer: A. Accounts payable, Accounts receivable, Bank, Budget, Payroll, and Purchasing

Posting definitions in Dynamics 365 Finance can be implemented for Accounts payable, Accounts receivable, Bank, Budget, Payroll, and Purchasing transactions. These modules allow customization of how transactions post to the general ledger by defining posting profiles that map source transactions to specific ledger accounts based on transaction characteristics. This comprehensive list represents all transaction types that support posting definition functionality.

Why the other options are wrong

• B. This list excludes Accounts receivable and Purchasing, which are supported transaction types for posting definitions.
• C. This list excludes Bank and Budget, which are supported transaction types for posting definitions.
• D. This list is incomplete, missing Accounts payable, Accounts receivable, Bank, and Payroll which all support posting definitions.

Correct answer: B. No

Defining a credit limit and selecting the Mandatory credit limit checkbox on the Customers form alone does not guarantee enforcement for all customer documents. Additional configuration is required at the Accounts Receivable parameters level to specify the credit type (such as Balance + All) and ensure the credit limit applies to all document types comprehensively.

Why the other options are wrong

• A. This solution is incomplete because it lacks the required Accounts Receivable parameters configuration needed to enforce credit limits across all document types.

Correct answer: B. No

The requirement covers General ledger, Accounts payable, Accounts receivable and Bank, but the solution never configures revaluation posting for Bank. Realized and unrealized gain and loss accounts are also defined per currency in the currency revaluation accounts setup rather than per vendor or customer group. The solution therefore does not meet the goal.

Why the other options are wrong

• A. The solution omits Bank revaluation posting and uses incorrect setup levels for realized gains and losses, so it does not meet the goal.

Correct answer: B. No

Using asterisks uniformly across all dimensions for all account ranges makes every dimension required for every account type. This violates the requirement that liability accounts (2000-2999) should have no dimensions posted and that customer is optional (not required) for revenue accounts. A single account structure with uniform asterisks cannot differentiate the nuanced requirements across different account types.

Why the other options are wrong

• A. Asterisks require all dimensions for all accounts, which incorrectly requires dimensions on liability accounts and makes customer mandatory for revenue accounts when it should be optional.

Correct answer: C. Tax code

The tax code is where you configure the specific sales tax percentage and its posting behavior, including recoverable and non-recoverable amounts. In this scenario, you would configure the tax code to reflect that 60 percent of the 5 percent tax is recoverable (posted to a tax receivable or input tax account) and 40 percent is non-recoverable (posted to an expense account), allowing the system to split the tax posting appropriately.

Why the other options are wrong

• A. Sales tax groups are used to assign multiple tax codes to transactions, not to configure individual tax percentages and their posting behavior.
• B. Ledger posting groups determine where totals are posted, but the detailed tax percentage configuration occurs at the tax code level.
• D. Item sales tax groups are used to assign tax treatment to items, not to configure the specific tax percentage posting split for recoverable and non-recoverable amounts.

Correct answer: A. Yes

Setting up journal control on the General journal to restrict the account type to ledger directly meets the requirement. This configuration prevents other account types (such as customer, vendor, or bank accounts) from being used in that journal, ensuring only ledger-type transactions can be posted through it.

Correct answer: D. Advanced bank reconciliation

Advanced bank reconciliation in Dynamics 365 Finance provides the capability to reconcile bank accounts daily with a timely view of check deposits and other pending transactions. It offers better visibility into cash flow by tracking deposits in transit and reconciling accounts more frequently, enabling more accurate cash flow forecasting and account management.

Why the other options are wrong

• A. Pending balance is a status in reconciliation but is not the feature that enables daily reconciliation with better timing visibility.
• B. Account posting type determines how transactions are recorded but does not improve cash flow visibility or daily reconciliation capability.
• C. Bridging accounts are used for intercompany transactions, not for improving bank reconciliation timing or cash flow visibility.