CCNA D365 Finance Questions

The exchange rate date on the journal may default to a date different from the payment date, causing the system to use an incorrect rate even if the rate table was updated correctly. Option A is wrong because the exchange rate table was updated, but the journal date mismatch is the key issue. Option B is wrong because if the currency were not set up for updates, payments would likely fail entirely.

Option C is wrong because rounding rules affect the calculated amounts, not the rate applied.

System administration contains settings for languages, currencies, and localization features that apply across the entire organization. Option A is incorrect because Accounts payable focuses on vendor transactions, not system-wide configurations. Option C is incorrect because Organization administration manages legal entities and organizational structures, but the multilingual and multi-currency settings are configured in System administration.

Option D is incorrect because General ledger deals with the chart of accounts and financial dimensions, not language and currency settings.

Options A and E are correct. The chart of accounts can be shared across multiple legal entities (A) and it defines the list of main accounts used in the general ledger (E). Option B is incorrect because account structures, not the chart of accounts itself, define valid dimension combinations.

Option C is incorrect because main accounts with posted transactions cannot be deleted. Option D is incorrect because the chart of accounts does not have to be unique per legal entity; it can be shared.

When posting an invoice using the invoice register journal, the credit is recorded to the default offset account (200110) temporarily. This is a standard behavior in Dynamics 365 Finance for invoice registers. Option A is incorrect because the vendor account is not credited until the invoice is approved and posted.

Option B is incorrect because the expense account is typically debited, not credited. Option C is incorrect because there is no separate vendor balance account in this context; the vendor balance is updated later.

Financial dimensions allow tracking by department, project, and other dimensions. Option A is wrong because the chart of accounts structures the main accounts but does not capture additional dimensions. Option B is wrong because cost accounting is for internal cost management.

Option D is wrong because budgeting is for planning.

Workflows in Dynamics 365 Finance allow you to define automated approval processes based on criteria such as dollar amount and department. Option B is incorrect because procurement categories are used to classify items, not to automate approvals. Option C is incorrect because role-based security controls access permissions, not approval flows.

Option D is incorrect because budget control monitors spending against budgets, not the approval of purchase requisitions.

Elimination rules automate the removal of intercompany balances. Option A is wrong because manual journal entries are not automated. Option C is wrong because intercompany accounting is for transaction posting, not elimination.

Option D is wrong because the consolidation online feature is for real-time consolidation but does not automatically eliminate.

Automated data entry suggestions (A) and natural language query for financial reports (C) are key benefits of Copilot in Dynamics 365 Finance. Option B is incorrect because automatic tax calculation is already a standard feature in the system. Option D is incorrect because manual journal entries are still required for various transactions.

Option E is incorrect because direct ledger postings require proper approval workflows.

Setting the 'Fixed asset acquisition' type on purchase lines and enabling automatic creation in Fixed assets parameters automates asset creation from purchase orders. Option B is wrong because the asset inventory module is for tracking, not financial acquisition. Option C is wrong because manual creation is not automated.

Option D is wrong because integration with Asset Management is not for financial acquisition.

Financial Reporting (Management Reporter) is designed to combine data from multiple legal entities into a single report using row definitions and reporting trees. Option B is incorrect because General ledger inquiry displays data for only one legal entity at a time. Option C is incorrect because Power BI requires separate data integration and does not natively consolidate multiple legal entities without additional setup.

Option D is incorrect because Excel integration typically accesses data from a single legal entity, not multiple.

Advanced bank reconciliation allows automatic matching of bank statement lines with bank transactions in the system. Option A is wrong because cash flow forecasting predicts future cash flows, not reconciliation. Option C is wrong because the payment journal is used to record payments, not reconciliation.

Option D is wrong because the general journal is used for manual journal entries, not reconciliation.

The Financial reporting module in Dynamics 365 Finance allows creation and management of financial statements for multiple reporting standards. Option A is wrong because Budgeting is for budget planning, not for local reporting standards. Option B is wrong because General ledger is the core ledger but does not directly manage local reporting requirements.

Option D is wrong because Accounts payable is for vendor transactions.

Journal names setup allows configuration of parameters including the requirement that journals must be balanced before posting. Therefore, Option B is correct. Option A (Journal approval workflow) handles approval processes, not balance enforcement.

Option C (Financial period close) manages period closing activities. Option D (User role permissions) controls user access but does not enforce balance checks.

Cost allocations distribute costs based on allocation bases. Cost accounting is the module. Overhead calculation is for manufacturing.

Cost rollup is for bill of materials.

Budget control in Dynamics 365 Finance allows tracking budget versus actual expenses at the department level. Option A is wrong because financial dimensions allow segmentation of transactions but do not track budget versus actuals by themselves. Option B is wrong because the chart of accounts structures the general ledger accounts, not budget tracking.

Option D is wrong because the general journal is used to record journal entries, not to track budget versus actuals.

The most efficient way to achieve automated consolidation with intercompany elimination in Dynamics 365 Finance is to set up a consolidation company and define elimination rules. This automates the elimination of intercompany transactions during the consolidation process. Option A (manual elimination) is inefficient and error-prone.

Option C (Budget control) is unrelated to consolidation. Option D (Financial reporting with a reporting tree) handles currency translation and reporting, not the actual consolidation process.

Options C and E are correct. Vendor invoice automation automatically processes invoices, reducing manual effort in accounts payable. Payment proposal generates payments based on due dates and vendor terms, streamlining payment processes.

Option A is wrong because collections management is for accounts receivable, not accounts payable. Option B is wrong because bank reconciliation is a cash management function, not directly related to accounts payable automation. Option D is wrong because customer payment predictions is for accounts receivable.

Workflows in Dynamics 365 Finance allow you to create approval processes based on conditions like amount. Option A is wrong because budget control limits spending but doesn't enforce approval workflow. Option B is wrong because manually notifying approvers is not efficient or automated.

Option D is wrong because vendor invoice policies are for invoices, not purchase orders.

The Project management and accounting module is designed for project cost tracking and budgeting. It supports cost categories and budgets per project, which is ideal for construction projects. Option A is incorrect because the Fixed assets module is for tracking fixed assets, not project expenses.

Option B is incorrect because the Budgeting module is for general financial budgets, not project-specific cost tracking. Option D is incorrect because the Expense management module is for employee expense reports, not project cost tracking.

Acquisition records the purchase of a fixed asset. Option B is wrong because impairment records a permanent decline in value. Option C is wrong because disposal records the sale or retirement.

Option D is wrong because depreciation records the value decrease over time.

The collection letter feature in Dynamics 365 Finance automatically sends payment reminders to customers. Option C is wrong because interest notes are for charging interest on overdue payments, not for sending reminders. Option B is wrong because customer payment journals record payments.

Option D is wrong because invoice journals record invoices.

The budget control configuration includes a warning threshold (e.g., 80%), and since the purchase order uses 90% of the available budget, it exceeds the warning threshold but not the error threshold (100%), so a warning is displayed but the purchase order can still be posted. Option A is incorrect because the purchase order is not blocked unless it exceeds the error threshold. Option B is incorrect because budget overrun (exceeding 100%) does not occur.

Option C is incorrect because purchase orders are configured for budget checking as shown in the exhibit.

The department segment 'IT' is only 2 characters long, but the account structure requires a department of 3 characters. This violation of segment length causes the journal to be rejected. Option A is incorrect because the cost center segment length is not the primary issue (though it may also be incorrect).

Option C is incorrect because the main account segment '1234567' has exactly 7 characters. Option D is incorrect because the issue is segment length, not the existence of the department value.

Recurring invoice templates with subscription items can be used with the 'Generate recurring invoices' batch job to create invoices on a schedule. Option A is incorrect because credit note templates are for issuing credit notes, not invoices. Option B is incorrect because free text invoice templates are for one-off charges, not recurring subscriptions.

Option D is incorrect because sales order templates are for physical goods, not subscription services.

The Consolidations module in Dynamics 365 Finance is designed to consolidate financial data from multiple legal entities. Option A is wrong because Intercompany accounting handles transactions between entities, not consolidation. Option B is wrong because Financial reporting uses data from the ledger but does not perform the consolidation process itself.

Option D is wrong because the General ledger does not consolidate automatically.

Cash discounts are configured at the vendor payment terms level and automatically applied during invoice entry. Option B is wrong because procurement categories are for item classification, not discounts. Option C is wrong because invoice policies are for approval, not discounts.

Option D is wrong because vendor master only stores company details.

The General ledger is the core module for recording all financial transactions for each legal entity. Option A (Accounts payable) manages vendor invoices and payments. Option B (Accounts receivable) manages customer invoices and receipts.

Option D (Budgeting) is for budget planning and control.

Options B, D, and E are correct. Intercompany relationships define the legal entities involved, intercompany journals handle transactions between those entities, and intercompany settlement ensures that balances are settled properly. Option A (budget control rules) is not essential for intercompany accounting; it is an optional feature for budget management.

Option C (vendor groups) is used for vendor categorization but is not specific to intercompany setup.

Depreciation profiles define the method (e.g., straight-line, declining balance) and can be assigned to different fixed asset groups to accommodate different depreciation methods. Option A is wrong because value models are used for different valuation purposes, not to define depreciation methods. Option B is wrong because asset groups categorize assets but do not directly define depreciation methods.

Option D is wrong because fixed asset journals are for posting acquisitions, disposals, and depreciation, but they do not automate the calculation based on method.

The dimension value 'CC001' must be used exactly as defined. Option A is wrong because the description is not used for posting. Option B is wrong because the dimension name ('CostCenter') is not included in the value; only the value itself is entered.

Option D is wrong because cost centers are a type of financial dimension.

The query selects MainAccount and sum of Amount from GeneralJournalEntry for a specific date range, groups by MainAccount, filters groups with total amount > 10000, and orders by total descending. Option A is wrong because it does not filter by a specific account. Option C is wrong because it returns only accounts with total > 10000.

Option D is wrong because it is not ordered ascending.

Budget control configuration allows monitoring of budget funds and analysis of budget vs. actuals. Option A (Budget planning) is for creating budgets, not analyzing variances. Option B (Budget register entries) is for recording budget amounts, not analysis.

Option C (Fixed asset management) is unrelated to budget analysis. Therefore, D is correct.

Accounts payable and Budgeting are both core functional modules within Dynamics 365 Finance. Accounts payable handles vendor invoices and payments, while Budgeting enables financial planning and control. Customer relationship management (Option B) is a separate Dynamics 365 application (Sales), not a module within Finance.

Project management (Option D) is also a separate application (Project Operations), not part of Finance. Power Apps (Option E) is a low-code platform for building custom apps, not a Finance module.

The correct answers are A, C, and E. In Dynamics 365 Finance, posting profiles define how transactions from subledgers are posted to the general ledger. Customer posting profile (A) manages accounts receivable transactions, Vendor posting profile (C) manages accounts payable transactions, and Inventory posting profile (E) manages inventory transactions.

Sales tax posting group (D) is a sales tax configuration, not a posting profile. Ledger posting setup (B) is a general ledger setup, not a posting profile.

Options B, C, and D are correct. Budgeting, General ledger, and Accounts payable are core modules in Dynamics 365 Finance. Option A is incorrect because Human resources is a separate Dynamics 365 app, not part of Finance.

Option E is incorrect because Project management and accounting is part of Dynamics 365 Project Operations, not Finance.

Correct: Bank reconciliation automates the matching of bank statements with ledger entries, streamlining the reconciliation process. Option A is wrong because Budget control is used for enforcing budget limits, not reconciliation. Option B is wrong because Cash flow forecasting predicts future cash flows, not reconciliation.

Option C is wrong because Payment proposals generate payment suggestions, not reconciliation.

The workflow first checks if the amount exceeds $10,000. Since $15,000 is greater than $10,000, the invoice requires manager approval first. After that, the second step always requires director approval.

Therefore, the manager approves first, followed by the director. Option A is incorrect because the order is reversed. Option C is wrong because the director's approval is also required.

Option D is wrong because the manager's approval is required first.

The Foreign currency revaluation feature in Dynamics 365 Finance automates the process and posts differences to the specified accounts. Option A is wrong because manual journal entries are error-prone and not automated. Option B is wrong because the General journal does not automatically revalue accounts.

Option C is wrong because exchange rate types define rates, not automate revaluation.

Options A, B, and E are correct. The chart of accounts (A) is the foundational structure for organizing financial accounts. Main accounts (B) represent individual accounts within the chart of accounts, such as cash or revenue.

Financial dimensions (E) provide additional segmentation for reporting, like department or cost center. Option C (Payment schedule) is used for vendor payments and is not part of the general ledger setup. Option D (Customer payment journal) is a subledger journal for recording customer payments, not a component of the general ledger setup.

The Revenue recognition module in Dynamics 365 Finance is specifically designed for automating revenue recognition under standards like ASC 606 and IFRS 15. Option A is incorrect because Project management and accounting handles project-based costing but not revenue recognition by default. Option C is incorrect because Accounts receivable manages invoices and payments.

Option D is incorrect because General ledger is the core accounting but lacks specialized revenue recognition features.

Options C and D are correct. Consolidation in Dynamics 365 Finance requires multiple legal entities to be set up and the chart of accounts must be consistent across entities. Option A is incorrect because entities can use different fiscal calendars; adjustments can be made during consolidation.

Option B is incorrect because intercompany transactions are not a prerequisite; consolidation can be performed without them. Option E is incorrect because workflow is optional and not required for consolidation journals.

Correct: Allocation rules in General ledger allow distribution of overhead costs based on defined criteria like square footage. Option A is wrong because Budget transfer is for moving budget amounts, not overhead allocation. Option B is wrong because Cost accounting focuses on internal cost analysis, not direct allocation rules.

Option D is wrong because Fixed asset depreciation deals with asset value reduction, not cost allocation.

Budget control in Dynamics 365 Finance enables real-time tracking of budget versus actual expenses by automatically checking budget balances against actual expenditures. Therefore, option C is correct. Option A (Budget planning) is used for creating and approving budgets, not for tracking in real time.

Option B (General ledger) records actual transactions but does not automatically compare to budget in real time. Option D (Financial reports) can be generated on demand but are not inherently real-time.

The bank reconciliation module imports bank statements and automates matching. Option B is wrong because the general journal is for manual entries. Option C is wrong because the cash and bank management module is broader but the specific feature is bank reconciliation.

Option D is wrong because data import/export is a utility, not a reconciliation tool.

2% discount if paid by January 30, so payment = 5000 * 0.98 = 4900. Option A (4800) is wrong because it applies a 4% discount instead of 2%. Option B (5000) is wrong because it does not apply any discount.

Option D (4950) is wrong because it applies only a 1% discount.

Options C and D are correct. Profit and loss accounts and balance sheet accounts are the two main account types in a standard chart of accounts for Dynamics 365 Finance. Option A is incorrect because statistical accounts are used for non-financial data, not as primary account types.

Option B is incorrect because budget accounts are separate from the chart of accounts and used for budgeting purposes. Option E is incorrect because reporting accounts are not a standard account type in the chart of accounts.

Project accounting integration in Dynamics 365 Finance automatically creates project transactions from posted sales invoices when work breakdown structure (WBS) elements are linked. Option B (Procurement integration) is for purchase-related transactions, not sales invoices. Option C (Budgeting integration) handles budget control, not project transaction creation.

Option D (Accounts receivable integration) focuses on customer payments and receivables, not project transactions.

Payment proposals automate the selection of invoices for payment. Electronic payment formats enable automated payment files for banks. Vendor hold prevents payment but does not automate.

Payment calendar is for scheduling. Vendor invoice pool is for holding invoices, not automation. Options A and D are correct.