CCNA D365 Finance Questions

Intercompany accounting setup allows automated balancing entries. Consolidation is for combining financial statements, not automatic balancing. Intercompany journal posting is a manual process.

Intercompany transaction pairs are used for matching transactions but do not automatically generate balancing entries. Option A is correct.

Options A and B are correct. Multiple legal entities must exist, and chart of accounts must be consistent. Option C is wrong because intercompany transactions are not required.

Option D is wrong because different fiscal calendars are not a prerequisite. Option E is wrong because workflow is optional.

Correct: Allocation rules distribute costs based on defined criteria. Option A is wrong because Fixed asset depreciation is for asset value reduction. Option B is wrong because Cost accounting is for internal cost analysis but not allocation rules.

Option D is wrong because Budget transfer is for moving budget amounts.

Option A is correct because budget control in Dynamics 365 Finance enables real-time tracking of budget vs. actuals. Option B is wrong because budget planning is for creating budgets. Option C is wrong because the General ledger records actuals but does not automatically compare to budget in real time.

Option D is wrong because financial reports can be generated on demand but are not real-time by default.

Option A is correct because 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.

Option B is correct: 2% discount if paid by January 30, so payment = 5000 * 0.98 = 4900. Option A is wrong because it doesn't apply discount. Option C is wrong because it applies wrong percentage.

Option D is wrong because it miscalculates.

Options A and C are correct. Balance sheet accounts and profit and loss accounts are the main types. Option B is wrong because budget accounts are not part of the chart of accounts.

Option D is wrong because statistical accounts are for non-financial data. Option E is wrong because reporting accounts are not a standard account type.

Option C is correct because Project accounting in Dynamics 365 Finance integrates with sales invoicing to create project transactions automatically. Option A is wrong because Accounts receivable integration is for customer payments, not project transactions. Option B is wrong because Procurement integration is for purchase orders.

Option D is wrong because Budgeting integration is for budget control.

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.

Option A is correct because OCR can capture invoice data automatically. Option B is correct because purchase order matching automates invoice posting. Option C is correct because vendor collaboration allows vendors to submit invoices electronically.

Option D is wrong because manual posting is what you want to reduce. Option E is wrong because the payment journal does not automate invoice posting.

Option B is correct because the vendor invoice approval workflow in Dynamics 365 Finance enforces manager approval before payment. Option A is wrong because vendor collaboration is for external vendors to submit invoices, not approval. Option C is wrong because budget control manages budget funds, not invoice approval.

Option D is wrong because the financial journal workflow is for journal entries, not vendor invoices.

Correct: Financial reporting and Budgeting are core features. Option C is wrong because Customer relationship management is in Dynamics 365 Sales. Option D is wrong because Inventory management is part of Supply Chain Management.

Option E is wrong because Human resources is in Dynamics 365 Human Resources.

Option A is correct because department and project are financial dimensions. Option B is wrong because vendor is a party, not a dimension. Option C is wrong because location is a dimension but not typically used for expense tracking.

Option D is wrong because item is a product dimension.

Options A and C are correct because Purchase requisitions and Purchase orders are common document types that can be subject to budget control. Option B is wrong because Sales orders are not typically subject to budget control in standard Dynamics 365 Finance. Option D is wrong because General journals can be subject but are not document types in the same sense; budget control is often on subledger documents.

Option E is wrong because Vendor invoices are not typically subject to budget control directly.

Option A is correct because consolidating with elimination allows combining data from different legal entities with different configurations while eliminating intercompany transactions. Option B is wrong because data integration would require manual mapping and is not the recommended approach for consolidation. Option C is wrong because recreating the chart of accounts is unnecessary and time-consuming.

Option D is wrong because the consolidation functionality in Dynamics 365 Finance supports different fiscal calendars and charts of accounts.

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

Option D is wrong because sales invoicing uses spot rates.

Option C is correct because Budget control is typically enabled at the purchase order or journal level; if configured for journal approval, the budget check does not occur at requisition approval. Option A is wrong because the budget source is not related to the check timing. Option B is wrong because document level might be set to a later stage.

Option D is wrong because budget thresholds affect warnings, not consumption.

Option A is correct. Weighted average costing calculates an average cost after each receipt, smoothing out price fluctuations. Option B is wrong because FIFO assigns the oldest cost to sales.

Option C is wrong because standard costing uses predetermined costs. Option D is wrong because moving average recalculates after each transaction, not over a period.

Correct: To create a revision, a new budget scenario like 'Revision' should be used. Option A (Status) is already approved. Option B (Model) is valid.

Option C (Type) is correct.

Correct: Consolidation [elimination] and currency translation are the key features for multi-currency, multi-standard consolidation. Option A (Intercompany accounting) handles transactions between entities but not automatic consolidation. Option B (Budget planning) is for budgeting.

Option D (Fixed assets) is irrelevant.

Option B is correct because 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.

Option C is correct because project budgets allow tracking actual vs budget, and budget control ensures costs do not exceed budget. Forecasting can be done using project forecasts. Option A is wrong because fixed-price projects do not allow flexible forecasting.

Option B is wrong because expense journals are not for budget tracking. Option D is wrong because work breakdown structures are for task management, not budget control.

Option A is correct because Consolidation [Elimination] in Dynamics 365 Finance is designed to consolidate financial data from multiple legal entities and eliminate intercompany transactions. Option B is wrong because Intercompany accounting records transactions but does not eliminate them. Option C is wrong because Global budgeting is for budget control.

Option D is wrong because Ledger allocation rules allocate costs, not consolidate.

Option A is correct because Inventory posting is used to define accounts for revenue, COGS, and inventory when items are sold. Option B is wrong because Accounts receivable posting handles customer balances, not revenue/COGS. Option C is wrong because General ledger posting is for account definitions, but specific posting setups for sales are in Inventory posting.

Option D is wrong because Procurement and sourcing posting is for purchases, not sales.

Option C is correct because a single unposted invoice would cause a discrepancy for that vendor. Option A is wrong because vendor currency affects exchange rates, not posting status. Option B is wrong because a payment journal being deleted would affect cash, not the AP subledger.

Option D is wrong because vendor hold affects future transactions, not existing balances.

Option C is correct because 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.

Option C is correct. The main account length is 6, department segment length is 3, cost center segment length is 5. Total = 6+3+5 = 14.

Option A is wrong because it omits the main account. Option B is wrong because it miscalculates. Option D is wrong because it adds extra characters.

Enabling the 'Post inventory to general ledger' parameter ensures that inventory transactions automatically post to the general ledger. The 'Inventory closing process' recalculates inventory costs and corrects discrepancies. Other options do not address synchronization.

Option A is correct.

Option A is correct because 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.

Option C is correct because absorption costing uses predetermined overhead rates based on machine hours. Option A is wrong because variable costing only includes variable costs. Option B is wrong because standard costing uses standard rates but not specifically for overhead allocation.

Option D is wrong because job costing tracks costs per job but not overhead allocation.

Option B is correct because the 'Advanced bank reconciliation' feature automatically matches bank statements with ledger entries. Option A is wrong because the payment proposal generates payments, not reconciliations. Option C is wrong because the cash flow forecast predicts cash flow.

Option D is wrong because the budget control process manages budgets.

Option A is correct because the vendor invoice journal is the standard method to record vendor invoices with automatic tax calculation. Option B is wrong because the general journal is not for vendor invoices. Option C is wrong because the purchase order is not needed for a simple invoice.

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

Option C is correct because activating dimensions and integrating them with budgets allows tracking and budgeting by department and project. Option A is wrong because using default dimensions does not enforce entry. Option B is wrong because deactivating dimension values would prevent tracking.

Option D is wrong because restricting posting to existing dimensions would block new combinations, but the requirement is to add new dimensions.

Option D is correct. Dynamics 365 Finance supports multiple ledgers, each representing a different accounting standard. Option A is wrong because using two instances is unnecessary and complex.

Option B is wrong because consolidations are for combining entities, not dual reporting. Option C is wrong because financial dimensions cannot replace separate ledgers for different GAAPs.

Option B is correct because invoices can be posted directly from the vendor invoice journal. Option D is correct because the purchase order invoice posting process posts invoices after receipt. Option A is wrong because payment journals are for payments, not invoices.

Option C is wrong because sales orders are for customers. Option E is wrong because production orders are for manufacturing.

Option B is correct because Trial balance shows the balance of each ledger account for a specified period. Option A is wrong because Chart of accounts is a list of accounts, not balances. Option C is wrong because Financial reporting generates reports but not real-time balance for a single account.

Option D is wrong because Ledger settlement is for matching debits and credits.

Option C is correct because Cash and bank management includes cash flow forecasting tools. Option A is wrong because Accounts payable manages vendor payments, not forecasting. Option B is wrong because Accounts receivable manages customer payments.

Option D is wrong because General ledger is for posting, not forecasting.

Option B is correct because if budget control is enabled but the budget register entries have not been created, there is no budget to control against. Option A is wrong because user permissions affect access, not budget control. Option C is wrong because budget control configuration works with budget register entries.

Option D is wrong because budget control can be enabled for purchase requisitions.

Option B is correct because the CheckLevel is set to "None", meaning budget checks are disabled for purchase invoices. Option A is wrong because the account structure is defined. Option C is wrong because the source document type is correct.

Option D is wrong because budget control is enabled.

Option B is correct. The 'Post invoice automatically' option in the accounts payable parameters allows automatic posting of vendor invoices when goods are received. Option A is wrong because vendor invoice policies are for approval.

Option C is wrong because purchase order workflows handle approvals. Option D is wrong because invoice matching ensures accuracy but doesn't automate posting.

Option A is correct because the budget check is a prerequisite for budget control. Option B is wrong because budget register entries are used to record budget amounts, not to enable checks. Option C is wrong because budget planning is a separate process.

Option D is wrong because commitment accounting is for encumbrances, not budget checks.

Options B, C, and E are correct. Bank account reconciliation matches transactions, cash flow forecasting predicts future cash positions, and bank statement import brings in external data. Option A is wrong because check reversal is not a standard cash management action.

Option D is wrong because credit card processing is part of accounts receivable, not cash management.

Option B is correct because Dynamics 365 Finance supports multiple fiscal calendars at the legal entity level. Option A is wrong because shared fiscal calendars are not used across legal entities with different calendars. Option C is wrong because fiscal year templates are for standard patterns, not entity-specific calendars.

Option D is wrong because ledger periods are part of the calendar, not the feature for managing multiple calendars.

Option A is correct because the Due date proposal selects invoices due on or before a specified date, considering cash discounts. Option B is wrong because the Discount proposal selects invoices with available discounts but may ignore due dates. Option C is wrong because the Specific invoices proposal is for selected invoices only.

Option D is wrong because the Open transactions proposal is not standard.

Correct: Standard costing uses predetermined costs for materials and labor, suitable for manufacturing cost tracking. Option A (FIFO) is an inventory valuation method. Option C (Moving average) is another valuation method.

Option D (LIFO) is not supported in Dynamics 365 Finance.

Option C is correct by setting the 'Tax code override' option to 'No' in accounts payable parameters. Option A is wrong because workflow approval does not prevent override. Option B is wrong because audit trail records changes but does not prevent them.

Option D is wrong because tax settlement is a separate process.

Option A is correct because reorder point planning in Dynamics 365 Finance automatically creates planned purchase orders when inventory reaches the reorder point. Option B is incorrect because vendor collaboration is for communication, not automated PO generation. Option C is incorrect because purchase requisition workflow requires manual approval steps.

Option D is incorrect because procurement catalogs are for indirect procurement, not automated inventory replenishment.

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.

Correct: Inventory management handles cost tracking of raw materials. Option A is wrong because Accounts payable manages vendor invoices, not cost tracking. Option B is wrong because General ledger is for financial reporting.

Option D is wrong because Budgeting is for planning, not tracking.

Correct: Workflow configuration can be reviewed in the workflow editor. Option A (Vendor master) does not show workflow logic. Option C (Power Automate) is for external automation, not native workflows.

Option D (System administration) is for system settings.

Option C is correct. To consolidate with different charts of accounts, you must create a consolidation company that uses a chart of accounts for US GAAP, and set up consolidation groups and accounts to map the source accounts. Intercompany elimination rules can be defined to automate eliminations.

Option A is wrong because it suggests changing all entities to use the same chart, which contradicts the requirement. Option B is wrong because Power BI is not the consolidation module. Option D is wrong because the consolidation company should not be used for daily transactions.

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. Option B is correct because bank reconciliation is a core feature of Cash and bank management. Option D is correct because cash flow forecasting is available in the module.

Option A is wrong because budget control is in the Budgeting module. Option C is wrong because fixed asset management is in Fixed assets. Option E is wrong because credit management is in Accounts receivable.

Option C is correct because Dynamics 365 Finance allows you to configure alternate approver or escalation rules in the approval workflow, ensuring that when primary approvers are unavailable, the workflow routes to a designated fallback. Option A is wrong because Microsoft Power Automate can be used but is not the native built-in method. Option B is wrong because reassigning manually is not an automated fallback.

Option D is wrong because workflow history does not provide fallback.

Option C is correct because consolidation in Dynamics 365 Finance combines financial data from multiple entities. Option A is wrong because financial reporting is for reports within one entity. Option B is wrong because intercompany accounting posts transactions between entities, not consolidation.

Option D is wrong because budget consolidation is for budgets.

Correct: It allocates balances from main account 601100 to 601200 based on cost center values. Option A is wrong because it allocates from 601100 to 601200, not the reverse. Option B is wrong because both source and destination use cost center, not main account.

Option D is wrong because it is not a fixed percentage method.

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

Option E is wrong because Fixed assets management is for asset tracking, not reporting.

Option C is correct because the cash flow forecasting feature in Dynamics 365 Finance uses historical and expected data to predict cash positions. Option A is wrong because payment schedules are for installment payments. Option B is wrong because the bank reconciliation module reconciles statements, not forecasts.

Option D is wrong because the general ledger is for posting transactions, not forecasting.

Option C is correct because 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 A is wrong because the General journal is for manual entries. Option B is wrong because Allocation journals allocate costs but do not handle prepayments/accruals automatically.

Option D is wrong because the Financial reporting module is for reporting, not posting.

Option D is correct because 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 payments based on criteria. Option A is for creating payment schedules on purchase orders, not for automatic generation. Option C is for checks.

Option D is for manual payment.

Option A is correct. The query filters transactions for the year 2023, groups by AccountCategory, and returns the top 5 categories with highest total amounts. Option B is wrong because it sums by month, not category.

Option C is wrong because it returns all, not top 5. Option D is wrong because it's for 2024, not 2023.

Options A, B, and D are correct. Dynamics 365 Finance supports multiple currencies, revenue recognition, and asset depreciation which are key IFRS requirements. Option C is wrong because budget control is for internal management, not IFRS.

Option E is wrong because vendor collaboration is for procurement, not financial reporting.

Correct: Configure a workflow for purchase order approval. Option A is wrong because Budget control only enforces budget limits. Option B is wrong because Procurement and sourcing policies are for vendor selection.

Option D is wrong because Security roles control access, not approval thresholds.

Options A and B are correct. Financial Reporting can produce balance sheets and income statements, and can combine data from multiple legal entities using reporting trees. Option C is wrong because posting journal entries is a general ledger function.

Option D is wrong because configuring budget control is a separate feature. Option E is wrong because configuring payment terms is done in accounts payable.

Option A is correct because the country context is set to DEU (Germany), but ISO 20022 credit transfer may have specific requirements not met by the standard format. Option B is wrong because version 10.0.30 is current. Option C is wrong because model mapping is required.

Option D is wrong because the format name is correct.

Setting up vendor invoice approval journals with workflow is standard. Workflow can handle amount-based and vendor-type conditions. The vendor invoice automation feature does not handle approval routing by itself.

Option A is correct.

Segregation of duties in Dynamics 365 Finance is managed through security roles and duties. Option D is correct. Option A is wrong because it is for tracking changes.

Option B is wrong because it is for period closing. Option C is wrong because it is for electronic documents.