CCNA D365 Finance Questions

Correct: Financial reporting and Budgeting are core features of Dynamics 365 Finance. Option A is wrong because Human resources is a separate module handled by Dynamics 365 Human Resources, not by Finance. Option B is wrong because Inventory management is part of Dynamics 365 Supply Chain Management.

Option C is wrong because Customer relationship management is in Dynamics 365 Sales. Options D and E are correct as they are fundamental financial management features.

Department and Project are both financial dimensions in Dynamics 365 Finance, enabling expense tracking by department and project. Option B is wrong because Vendor is a party type, not a financial dimension. Option C is wrong because Item is a product dimension, not suitable for tracking expenses by department and project.

Option D is wrong because Location is a dimension but is not typically used for expense tracking in this context; Cost center alone would be more appropriate.

Purchase requisitions and purchase orders are valid document types that can be subject to budget control in Dynamics 365 Finance. Sales orders are not typically subject to budget control directly. General journals can be used for budget control but are not considered document types in this context; budget control is often applied to subledger documents.

Vendor invoices are also not typically subject to budget control directly.

Correct: Average rates are used for revaluation of balance sheet accounts. Option A is wrong because budget conversions use budget rates. Option B is wrong because transaction entry uses spot rates.

Option D is wrong because sales invoicing uses spot rates.

Budget control must be set to check at the purchase requisition stage. Since budget check is configured for journal approval, it does not occur when the requisition is approved, so funds are not consumed. Option A is wrong because budget thresholds affect warnings, not consumption timing.

Option B is wrong because document level determines when the check occurs, but the question specifies it is set to purchase order, which is later than requisition. Option C is wrong because the budget source being incorrect would cause other issues, not the lack of consumption at requisition approval.

Weighted average costing calculates an average cost over a period, smoothing out price fluctuations. Option B is wrong because standard cost uses predetermined costs, not actual costs. Option C is wrong because FIFO assigns the oldest cost to sales.

Option D is wrong because moving average recalculates after each transaction, not over a period.

Budget revisions in Dynamics 365 Finance require a new budget scenario; the existing approved record cannot be edited. Option A is incorrect because changing the budget status to Draft would not allow modification if the budget is already in a workflow that locks editing. Option B is incorrect because deleting and recreating is inefficient and loses history.

Option C is incorrect because modifying the BudgetModel changes the structure, not the amounts, and may affect other budgets using that model.

Exchange rates are required for currency translation. Option A is wrong because currency revaluation is for adjusting balances, not for translation. Option C is wrong because a consolidation company is used to combine results, but translation requires exchange rates.

Option D is wrong because intercompany accounting is for transactions between entities, not for translation.

The Fixed assets module is used to manage asset records, depreciation, and disposal. Option A (Budgeting) handles budgets, not fixed assets. Option B (Inventory management) manages stock items, not fixed assets.

Option D (General ledger) is for financial transactions and accounts, not asset records.

Inventory posting is used to define accounts for revenue, COGS, and inventory when items are sold. Option A is incorrect because Procurement and sourcing posting handles purchase-related transactions, not sales. Option B is incorrect because Accounts receivable posting manages customer balances and payments, not revenue/COGS.

Option D is incorrect because General ledger posting defines main accounts but does not specify the posting setup for sales orders; that is done in Inventory posting.

BudgetControl is enabled and AllowOverbudget is false, so the system will block the transaction and show a budget control error. Option A is wrong because the system will not allow posting; it will generate an error. Option B is wrong because there is no automatic approval workflow triggered by budget control.

Option D is wrong because the system will not create a warning without blocking; it blocks by default when AllowOverbudget is false.

The account structure comprises the main account (length 6), department (length 3), and cost center (length 5), totaling 14 (6+3+5=14). Option B (15) is incorrect because it adds an extra character. Option C (11) is incorrect because it likely omits the main account or miscalculates.

Option D (8) is incorrect because it only accounts for two segments.

Financial reporting (Management Reporter) allows creating custom financial statements in various formats. Option B is wrong because Power BI is for data visualization, not formal financial statements. Option C is wrong because the general ledger inquiry shows account balances but not formatted statements.

Option D is wrong because Excel integration can help but is not the native tool for regulatory reporting.

Absorption costing is correct because in Dynamics 365 Finance, it allocates overhead costs to production orders using predetermined rates based on activity drivers like machine hours. Variable costing (A) only includes variable costs, ignoring fixed overhead. Standard costing (B) uses standard rates for cost elements but does not specifically allocate overhead based on machine hours.

Job costing (C) tracks costs per individual job or order, not overhead allocation by machine hours.

Advanced bank reconciliation automatically matches bank transactions with general ledger entries, automating the reconciliation process. Option A is wrong because cash flow forecast is used to predict future cash flows, not reconcile transactions. Option B is wrong because budget control enforces budget limits, not reconciliation.

Option C is wrong because payment proposal generates payments to vendors, not reconciles bank transactions.

The vendor invoice journal is the standard method to record vendor invoices with automatic tax calculation. Option A is wrong because a purchase order is not required for a simple vendor invoice; it is typically used for procure-to-purchase processes. Option C is wrong because the general journal is for manual journal entries, not vendor invoices.

Option D is wrong because the payment journal is used for recording payments, not invoices.

Dynamics 365 Finance allows multiple ledgers to be attached to the same legal entity, each with a different accounting framework (e.g., local GAAP and IFRS). Option B is wrong because using two separate instances would require duplicate data entry and is not necessary. Option C is wrong because the consolidation module is used to consolidate financial results from multiple entities, not for dual reporting within one entity.

Option D is wrong because financial dimensions are for segmenting financial data, not for applying different accounting standards.

The vendor invoice journal allows direct entry and posting of vendor invoices that are not linked to purchase orders. Option B is correct because the purchase order invoice posting process posts invoices that are linked to purchase orders after receipt. Option C is wrong because sales order invoices are for customer invoices, not vendor invoices.

Option D is wrong because the vendor payment journal is used for recording payments to vendors, not invoices. Option E is wrong because production orders are for manufacturing processes, not vendor invoicing.

Trial balance shows the balance of each ledger account for a specified period, allowing the accountant to view the current balance. Option B is incorrect because Ledger settlement is used for matching debits and credits, not for viewing balances. Option C is incorrect because Chart of accounts is a list of accounts, not balances.

Option D is incorrect because Financial reporting generates reports but not real-time balance for a single account.

Cash and bank management includes cash flow forecasting tools. Option B (Accounts receivable) manages customer payments, not forecasting. Option C (Accounts payable) manages vendor payments, not forecasting.

Option D (General ledger) is for posting, not forecasting.

The 'CheckLevel' for purchase invoices is set to 'None', which disables budget checks for that document type. Option B is incorrect because purchase invoices are a supported source document type for budget control. Option C is incorrect; while the account structure may lack financial dimensions, the primary issue is the CheckLevel setting.

Option D is incorrect because budget control is enabled (as shown in the exhibit).

Enabling budget control in General ledger parameters and defining budget check rules allows the system to perform a budget check when posting purchase invoices. Option B is incorrect because commitment accounting is used to track commitments for purchase orders, not to trigger budget checks during invoice posting. Option C is incorrect because budget planning workflows are for creating and approving budgets, not for checking them at transaction time.

Option D is incorrect because creating budget register entries only records budget amounts; it does not enable automatic budget checks.

Correct: Standard costing uses predetermined costs for materials and labor, making it suitable for tracking costs across multiple production stages in manufacturing. Option A (Moving average) calculates cost based on average cost of goods. Option B (LIFO) is an inventory valuation method that assumes last units added are sold first, but it is not designed for predetermined cost tracking across production stages.

Option C (FIFO) is another inventory valuation method that assumes oldest inventory is sold first.

Department, Cost center, and Project are standard financial dimensions in Dynamics 365 Finance. Vendor is not a financial dimension; it is a default dimension used in transactions. Location is not a financial dimension; it is part of operating units or inventory dimensions.

Therefore, the correct three options are B (Cost center), D (Project), and E (Department).

Consolidate [Eliminate] is for intercompany eliminations. Consolidate [Inquire] is for viewing. Consolidate [Transfer] only moves data.

Consolidate [Online] performs the actual consolidation.

Interest codes define the interest calculation rules. Collection letters are for dunning. Customer posting profiles define posting accounts.

Payment schedules define installment plans.

Inventory management is the primary module for tracking raw material costs from purchase through production to finished goods. It integrates with production control to calculate actual costs. Accounts payable handles vendor invoices, not cost tracking.

Budgeting is for financial planning, not operational cost tracking. General ledger provides high-level financial reporting, not detailed cost tracking.

Purchase order workflow editor. Workflow configuration, including conditions, is reviewed and edited within the workflow editor in Dynamics 365 Finance. Option A (Power Automate flows) is incorrect because Power Automate is used for external automation, not for native Dynamics 365 workflows.

Option B (System administration parameters) is incorrect as it deals with system-wide settings, not specific workflow logic. Option D (Vendor master form) is incorrect because the vendor master does not contain workflow configuration details.

Consolidations in Dynamics 365 Finance allow consolidation of multiple legal entities with currency translation. Financial reporting is for individual reports. Budgeting is for planning.

Intercompany accounting is for transactions. Option A is correct.

Options B and D are correct. Cash flow forecasting (option B) is a feature of the Cash and bank management module. Bank reconciliation (option D) is also a core feature of the Cash and bank management module.

Option A (Credit management) is incorrect; credit management is handled in the Accounts receivable module. Option C (Budget control) is incorrect; budget control is part of the Budgeting module. Option E (Fixed asset depreciation) is incorrect; fixed asset depreciation is managed in the Fixed assets module.

The Consolidation module (Option B). This module is specifically designed to combine financial data from multiple legal entities into a single consolidated report. Option A (Budget consolidation) is incorrect because it deals with budget data, not general financial consolidation.

Option C (Financial reporting module) is incorrect because it is used for creating reports, but the consolidation process is handled by the Consolidation module. Option D (Intercompany accounting) is incorrect because it manages transactions between entities, not the consolidation of their financial statements.

The allocation rule transfers balances from main account 601100 to main account 601200, using the cost center dimension as the basis for allocation. Option B correctly describes this. Option A is incorrect because although it identifies the correct source and destination accounts, it states 'based on main account' rather than 'based on cost center.' Option C is wrong because it reverses the source and destination accounts.

Option D is incorrect because the rule uses a dimension basis (cost center) rather than a fixed percentage.

Options C and E are correct because Electronic reporting allows configuring tax and financial reports per regulatory formats, and Financial reporting enables designing reports compliant with GAAP/IFRS. Option A is incorrect because Budget control is for monitoring budgets, not reporting. Option B is incorrect because Intercompany accounting is for internal transactions.

Option D is incorrect because Fixed assets management is for asset tracking, not reporting.

The cash flow forecasting feature in Dynamics 365 Finance uses historical and expected data to predict future cash positions. Option A (General ledger) is wrong because it records transactions, not forecasts. Option C (Bank reconciliation) is wrong because it matches bank statements, not predicts cash flow.

Option D (Payment schedules) is wrong because it manages installment payments, not forecasts.

The Periodic journal in Dynamics 365 Finance can be set up to automatically generate recurring journal entries for prepayments, accruals, and other periodic transactions. Option B is wrong because Financial Reporting is for reporting, not posting. Option C is wrong because Allocation journals allocate costs but do not handle prepayments/accruals automatically.

Option D is wrong because the General journal is for manual entries.

The Bank reconciliation module in Dynamics 365 Finance automates matching bank statement lines to ledger entries. Option A is wrong because Cash and bank management is a module that includes bank reconciliation, but not the specific feature. Option B is wrong because Advanced bank reconciliation is an optional add-on that provides more automation, but the standard bank reconciliation feature is available in Cash and bank management.

Option C is wrong because Payment journal is for recording payments, not reconciliation.

The Payment proposal feature in Accounts payable allows automatic generation of vendor payments based on criteria such as due dates and available cash. Option A (Check management) is used for managing check payments, not for automatic payment generation. Option B (Manual payment journal) requires manual entry for each payment.

Option D (Vendor payment schedule) is a field on purchase orders, not a feature for automatic payment generation.

The query filters for Year == 2023, groups by AccountCategory, sums the Amount for each category, orders by total amount descending, and uses take 5 to return the top 5 categories. Option A is incorrect because it says 'all account categories' but the query only returns the top 5. Option B is incorrect because it suggests grouping by month, while the query groups by AccountCategory.

Option C is incorrect because it refers to 2024, but the filter is for 2023.

Options A, B, and C are correct. Dynamics 365 Finance supports revenue recognition schedules (A) for deferred revenue under IFRS 15, multi-currency accounting with exchange rate adjustments (B) for IAS 21, and depreciation profiles (C) for IAS 16. Option D (vendor collaboration portal) is a procurement feature unrelated to IFRS compliance.

Option E (budget control) is for internal management, not external financial reporting standards.

Correct: A purchase order approval workflow can be configured to require approval based on thresholds such as amount. Option B is wrong because procurement policies govern vendor selection and procurement processes, not approval thresholds. Option C is wrong because budget control rules enforce budget limits but do not trigger approvals for specific amounts.

Option D is wrong because security roles control access to features, not approval processes.

Options A and E are correct. Financial Reporting can produce balance sheets and income statements (E) and can combine data from multiple legal entities using reporting trees (A). Option B is incorrect because configuring payment terms is done in Accounts payable, not in Financial Reporting.

Option C is incorrect because configuring budget control rules is a separate feature in Budgeting. Option D is incorrect because posting journal entries is a general ledger function.

The company is in Germany (DEU), but the bank's validation likely requires a specific country context that matches the bank's local requirements. ISO 20022 credit transfer formats are country-specific; using the default DEU format may omit required fields or use incorrect codes. Option A is wrong because model mapping missing fields would cause a different error during generation, not validation failure.

Option B is wrong because the format name (ISO 20022 Credit Transfer) is standard and correct. Option C is wrong because version 10.0.30 is current and generally compatible.

To comply with the Sarbanes-Oxley (SOX) act, segregation of duties is enforced through security roles and duties in Dynamics 365 Finance. Option D is correct. Option A (Electronic reporting) is used for generating and processing electronic documents, not for separation of duties.

Option B (Audit trail) tracks changes made to the system but does not enforce separation of duties. Option C (Batch job) is used for automated background processing, unrelated to security.

Setting up an Expense report workflow with an approval step assigned to the employee's manager ensures that expense reports are routed to the manager for approval before reimbursement. Option A is incorrect because project workflows are for project-related transactions, not general expense reports. Option B is incorrect because expense policies define validation rules (e.g., receipt requirements) but do not route approvals.

Option C is incorrect because the Electronic reporting module is for generating documents and reports, not for approval routing.

Bank reconciliation and cash flow forecasting are part of Cash and Bank Management. Fixed assets management is in Fixed assets. Budget control is in Budgeting.

Vendor payments are in Accounts payable.

Financial reporting in Dynamics 365 Finance provides customizable, regulatory-compliant financial statements. Option A (Electronic reporting) is used for configuring electronic documents and tax reports, not specifically for financial statements. Option B (Financial reporting) is the correct feature for generating financial statements.

Option C (Intercompany accounting) handles transactions between legal entities, not reporting. Option D (Budget control) manages budget allocations and monitoring, not financial statement generation.

Batch job processing in Dynamics 365 Finance allows scheduling and automation of periodic tasks like ledger settlements and month-end closing. This feature enables the finance team to set up recurring processes that run without manual intervention. Option B (Bank reconciliation) is for reconciling bank transactions, not for automating ledger settlements.

Option C (Vendor invoice pool) is for managing vendor invoices, not for periodic automation. Option D (Financial reporting) is for generating reports, not for scheduling tasks.

Multiple posting layers allow organizations to maintain parallel accounting standards for compliance with IFRS and other international accounting standards. Option D is correct because dual currency support enables financial reporting in multiple currencies, which is essential for IFRS compliance. Option B (Vendor payment proposal) is incorrect as it relates to accounts payable, not compliance.

Option C (Budget control) is incorrect as it is an internal budgeting tool. Option E (Fixed asset management) is incorrect as it pertains to asset lifecycle management, not specific compliance features.

Options A, C, and D are correct. Intercompany accounting requires defining intercompany relationships, setting up intercompany parameters, and creating intercompany agreements. Option B is wrong because intercompany journals are a result, not a prerequisite.

Option E is wrong because consolidation is a separate process.

An unbalanced journal entry, where total debits do not equal total credits, will cause the general ledger balance to not match the sum of debits and credits. Option A is incorrect because the voucher number series merely assigns identifiers and does not affect accounting balances. Option B is incorrect because posting profile configuration determines how transactions are posted to accounts but does not cause an imbalance if the journal entry itself is balanced.

Option D is incorrect because user permissions control access rights, not the balancing of journal entries.

General journals are used for non-standard transactions such as adjustments and accruals. Option C is correct because general journals can be configured with approval workflows. Option B is incorrect because general journals post directly to the general ledger, not automatically to subledgers; subledger posting is handled through dedicated modules.

Option D is incorrect because reversing entries are supported in general journals. Option E is incorrect because a single general journal can include multiple legal entities.

The Project management and accounting module is specifically designed to track project costs and revenues, including materials, labor, and overhead. Option A is wrong because Procurement and sourcing handles purchasing and vendor management. Option B is wrong because Production control is for manufacturing operations.

Option D is wrong because Fixed assets manages asset depreciation and lifecycle.

Starting balance is 50000. A debit of 10000 increases the balance to 60000. A credit of 5000 decreases it to 55000.

Another credit of 20000 decreases it to 35000. Option A (30000) is incorrect because it miscalculates the net effect. Option C (40000) is incorrect because it might ignore one of the credits.

Option D (45000) is incorrect because it incorrectly adds the credits instead of subtracting.

Dynamics 365 Finance provides data migration tools that allow importing historical financial data from legacy systems, preserving details for reporting. Option B is wrong because manual re-entry is inefficient and error-prone. Option C is wrong because migrating only summary balances loses transactional detail needed for reporting.

Option D is wrong because maintaining the legacy system is costly and does not leverage the new system's capabilities.

Advanced bank reconciliation allows automatic matching of bank statements with ledger transactions. Option A is wrong because budget control manages budgets, not reconciliation. Option B is wrong because intercompany accounting handles transactions between legal entities.

Option D is wrong because cash flow forecasting predicts future cash positions.