CCNA D365 Finance Questions

Option D is correct because the 'escalationAction' is set to 'Approve', which means when the time limit is exceeded, the system automatically approves the PO instead of routing to the fallback approver. To route to the VP, the escalationAction should be 'Escalate' or similar. Option A is wrong because the fallback is defined as VP of Procurement.

Option B is wrong because the time limit is 48 hours. Option C is wrong because the assignee is Manager.

Option C is correct because using intercompany journals and setting up intercompany purchase orders with direct delivery and intercompany elimination rules meets the requirements: centralized purchasing, direct receipt, and automatic elimination. Option A is wrong because it relies on manual journals and does not automate elimination. Option B is wrong because inventory transfers do not handle purchase order centralization.

Option D is wrong because creating separate purchase orders in each entity defeats the centralization requirement.

Option A is correct because AI Builder requires a Power Apps license and must be configured for Copilot capabilities. Option B is wrong because data entities are for data import/export, not AI. Option C is wrong because workflow is for approval processes.

Option D is wrong because electronic reporting is for document generation.

Options A and C are correct. Option A is correct because the General ledger provides a chart of accounts to categorize financial transactions. Option C is correct because it provides real-time financial insights through reports and inquiries.

Option B is wrong because managing vendor payments is done in Accounts payable. Option D is wrong because managing customer invoices is done in Accounts receivable. Option E is wrong because inventory valuation is part of Inventory management.

A consolidation company and conversion rate determination are required. Option C is optional, not required. Option D is not required for consolidation.

Option E is for reporting.

Option B is correct because Dynamics 365 Finance includes AI-driven customer payment predictions that provide insights and recommendations. Option A is wrong because Copilot in Finance is for conversational assistance, not specifically payment predictions. Option C is wrong because the cash flow forecasting feature does not include customer payment delay predictions.

Option D is wrong because budgeting and planning is for budget creation.

Option A is correct because the 'Average' translation method uses the average exchange rate for the period, which is appropriate for income statement accounts. Option B is wrong because 'Current' is for balance sheet. Option C is wrong because 'Historical' is for equity.

Option D is wrong because 'Ending' is not a standard method.

Option A is correct because the purchase order workflow can be configured with conditional approval rules based on amount. Option B is wrong because an approval journal is not a standard Dynamics 365 concept. Option C is wrong because the budget manager role is for budget control, not purchase order approval.

Option D is wrong because procurement and sourcing is a module that includes purchase order workflows, but the specific feature is the workflow itself.

Intercompany accounting is the feature that automates intercompany transactions. Option A is correct. Option B is wrong because consolidation is for combining financials, not for day-to-day transactions.

Option C is wrong because elimination is for removing intercompany balances. Option D is wrong because transfer orders are for inventory transfers.

Correct: A and D. Budget control is a core feature; Fixed asset management is also part of Finance. Option B (Customer service) is a Dynamics 365 Sales/Service module.

Option C (Project scheduling) is in Project Operations. Option E (Marketing automation) is in Dynamics 365 Marketing.

Option A is correct. Payment proposals allow users to select multiple invoices for a vendor and generate a single payment. Option B is wrong because payment schedules spread a single invoice into installments.

Option C is wrong because positive pay is a fraud prevention feature. Option D is wrong because electronic payment format is for file generation, not grouping.

Option A is correct because Dynamics 365 Finance allows creating separate fixed asset records for land and building, each with different depreciation profiles. Option B is wrong because a single record cannot have a non-depreciable portion. Option C is wrong because the system does not automatically split cost.

Option D is wrong because a sub-asset would still be depreciable, not non-depreciable.

Option A is correct because financial dimensions are used for tracking attributes like department and project. Option B is wrong because account structures define the chart of accounts. Option C is wrong because advanced rules set conditions for dimensions.

Option D is wrong because dimension sets are for reporting, not transaction capture.

Correct: Set up a journal approval workflow. Option A is wrong because Financial dimension sets are for reporting. Option B is wrong because Audit trail settings track changes.

Option D is wrong because General ledger parameters include various settings but not approval workflow.

Option D is correct because recurring journal voucher is designed for recurring entries like depreciation. Option A is wrong because general journal is for manual entries. Option B is wrong because periodic processing is a broader term, not a specific tool.

Option C is wrong because fixed assets journal is for asset acquisitions and disposals, not depreciation posting.

Option A is correct. In Dynamics 365 Finance, the shared chart of accounts feature allows a single chart of accounts to be used across multiple legal entities, ensuring consistency and simplifying maintenance. Option B is incorrect because separate charts per entity increase complexity.

Option C is incorrect because financial dimensions are used for tracking, not for sharing accounts. Option D is incorrect because deleting accounts is not a best practice.

Correct: Payment proposals automate payment generation. Option A is wrong because Vendor invoice capture is for invoice data entry. Option B is wrong because Purchase agreements are for contract pricing.

Option D is wrong because Cash flow forecasting is for predictions, not payments.

Option B is correct because consolidation in Dynamics 365 Finance automatically aggregates financial data from multiple legal entities. Option A is wrong because elimination rules remove intercompany transactions, not consolidate. Option C is wrong because currency revaluation adjusts exchange rates.

Option D is wrong because financial dimension sets are used for reporting hierarchies.

Option A is correct because budget control must be enabled and configured to check funds availability for purchase orders. Option B is wrong because budget plans are for planning, not control. Option C is wrong because budget register entries record budgets, not control.

Option D is wrong because budget models are used in planning.

Customer payment predictions use AI to forecast when customers will pay invoices. Option A is correct. Option B is wrong because it is for reducing invoice processing time.

Option C is wrong because it is for cash flow forecasting. Option D is wrong because it is for financial reporting.

Budget control configuration enables checking against budget. Budget plans are for planning. Budget register entries are for recording.

Budget model is a structure.

All tasks shown are part of the closing process. However, the question asks which must be completed. Typically, posting vendor invoices should be done before closing.

Option B is correct. Option A is wrong because generating a report is not a prerequisite. Option C is wrong because currency revaluation can be done after closing in some setups.

Option D is wrong because the exhibit shows all as tasks, but the key is that unposted invoices must be posted.

Invoice matching policy enforces three-way matching (PO, receipt, invoice). Payment schedule is for installment payments. Vendor payment journal is for recording payments.

Purchase agreement is for long-term contracts. Option B is correct.

Option A is correct because inventory posting profiles determine how inventory transactions are posted to the general ledger. If they are not correctly set up, posting may fail or update the wrong accounts. Option B is wrong because payment schedules affect payment timing, not general ledger updates.

Option C is wrong because audit policies review transactions after posting, not during. Option D is wrong because budget control settings prevent posting when budget is exceeded, but the issue is intermittent and not related to budget.

Option A is correct because 'Department' and 'Project' are financial dimensions that can be used together. Option B is wrong because cost centers and cost objects are for cost accounting. Option C is wrong because main accounts and subaccounts are for chart of accounts.

Option D is wrong because budget codes and budget classes are for budgeting.

The 'Post inventory in ledger' parameter enables automatic posting of inventory transactions. Option A is for valuation method but not posting. Option B is for item model groups.

Option D is for warehouse management.

Option A is correct. By setting the 'Date criterion' to 'Due date' with a 'Payment date' offset of 0, only invoices with due dates on or before the payment date are included. To correctly calculate cash discounts, the payment terms must be set up with the discount percentage and the number of days.

Option B is wrong because 'Payment date' criterion uses the invoice date, not due date. Option C is wrong because 'Discount date' criterion is not standard; the system uses payment terms. Option D is wrong because setting offset would include future invoices.

Correct: The VendTrans table is from Accounts payable. Option A is wrong because General ledger uses LedgerTrans. Option B is wrong because Sales tax uses TaxTrans.

Option D is wrong because Fixed assets uses AssetTrans.

Options A, B, and D are correct. Option A is correct because the Budgeting module includes budget planning for creating budget proposals. Option B is correct because budget control is part of budgeting to monitor budget consumption.

Option D is correct because budget register entries allow recording budget amounts. Option C is wrong because generating financial statements is done in Financial reporting. Option E is wrong because processing vendor invoices is done in Accounts payable.

Time and material bills actual hours. Fixed-price milestone bills based on predefined milestones. Progress billing is for percentage complete.

Cost plus bill is for cost plus contracts.

Option C is correct because Accounts payable invoice matching policies enforce three-way matching (invoice, PO, receipt). Option A is wrong because budget control is for expenditure limits. Option B is wrong because vendor invoice workflow is for approval routing.

Option D is wrong because payment schedules define installment plans.

Option D is correct because intercompany elimination rules are specifically designed to automatically eliminate intercompany transactions during consolidation. Option A is wrong because manual elimination is error-prone and not automated. Option B is wrong because consolidation companies aggregate data but do not eliminate intercompany transactions automatically.

Option C is wrong because the intercompany accounting module records transactions but does not eliminate them during consolidation.

Option A is correct because payment proposals can automatically apply payments to open invoices based on matching criteria. Option B is wrong because payment journal templates only set default values, not automation. Option C is wrong because settlement priority is a manual setting.

Option D is wrong because it describes a manual process.

Option B is correct because the intercompany setup in Dynamics 365 Finance includes a setting to automatically create intercompany invoices when purchase orders are confirmed. Option A is wrong because recurring invoices are for regular customer invoices, not intercompany. Option C is wrong because purchase agreements are for long-term contracts, not automatic intercompany invoicing.

Option D is wrong because vendor invoices are for external purchases.

Option D is correct because tax codes define rates and rules, tax groups combine taxes for different jurisdictions, item tax groups define item-level tax, and tax reporting codes map to tax return boxes. Option A is wrong because it misses item tax groups. Option B is wrong because tax groups are not for item-level.

Option C is wrong because tax reporting codes are needed for returns.

Option A is correct. Financial dimension sets are used for reporting and analysis, allowing users to view data by selected dimensions. Option B is wrong because dimension sets do not control access.

Option C is wrong because they are not used for validation. Option D is wrong because they do not define accounting rules.

Option D is correct because Management Reporter (now part of Financial reporting) is the tool for custom financial reports. Option A is wrong because Power BI is for analytics, not report design. Option B is wrong because Excel integration is for ad-hoc analysis.

Option C is wrong because the General ledger inquiry shows data, not reports.

Option A is correct because advanced bank reconciliation uses matching rules to automate reconciliation. Option B is wrong because bank accounts are required, but the key feature is matching rules. Option C is wrong because cash flow forecasting is separate.

Option D is wrong because it describes a manual process.

The exhibit clearly shows "DataEntity": "GeneralJournalAccountEntry", so that is the entity being exported. Option C is correct. Option A is wrong because it is a different entity.

Option B is wrong because it is for ledger dimensions. Option D is wrong because it is for transactions.

Cash flow forecasting uses historical data to predict future cash positions. Budgeting is for planning, not forecasting. Bank reconciliation matches transactions.

Payment proposals generate payments. Option A is correct.

Correct: The period status is 'Closed', preventing posting. Option A (Legal entity) is valid. Option B (Module) is correct.

Option D (Action) is standard.

Option A is correct because the chart of accounts defines the financial structure used for reporting. Option D is correct because main accounts can be shared across legal entities using shared main accounts. Option B is wrong because main accounts are not created automatically; they must be defined.

Option C is wrong because the chart of accounts is not limited to 100 accounts; it can have many. Option E is wrong because posting profiles are required for transaction posting.

Options A and C are correct. A: Budget planning is a core feature. C: Credit and collections management is part of accounts receivable.

Options B, D, and E are incorrect: B is a Power Platform feature, D is a supply chain feature, E is a commerce feature.

Option A is correct because the opening balance is 100,000 and the account is a debit account, so it has a debit balance. Option B is wrong because the type is Asset, not Liability. Option C is wrong because the category is Cash, not Bank.

Option D is wrong because the DebitCredit is Debit.

Intercompany accounting setup enables automatic generation and elimination of intercompany transactions. Option A is for currency translation. Option C is for consolidation.

Option D is for company information.

Option B is correct because incorrect assignment of tax codes to items or customers is a common cause of tax calculation errors. Option A is wrong because tax authority setup does not directly affect calculation. Option C is wrong because ledger posting groups affect posting, not calculation.

Option D is wrong because withholding tax is separate.

Option A is correct because a payment proposal with a 'Due by' date filter will select invoices due within that period. Option B is wrong because a payment schedule is for recurring payments, not for due date filtering. Option C is wrong because a payment journal is used to post payments but does not automatically select invoices.

Option D is wrong because a vendor payment retention is for holding payments, not for selecting due invoices.

Correct: Assign the role in Security configuration. Option A is wrong because Workflow can include role but roles are assigned via Security. Option B is wrong because Organization hierarchy defines structure.

Option D is wrong because Audit policy is for monitoring.

Option A is correct because settlement is used to apply payments to invoices. Option B is wrong because collections is for managing overdue payments. Option C is wrong because credit and collections is a module, not a specific feature for applying payments.

Option D is wrong because payment schedules are for installment payments.

Option C is correct because if variances are not calculated and posted, the WIP account will not clear properly. Option A is wrong because BOM version approval affects costing but not WIP clearing. Option B is wrong because item coverage settings affect planning, not accounting.

Option D is wrong because a single cost category record does not prevent WIP clearing.

Option B is correct because shared chart of accounts allows a single chart of accounts to be used across legal entities. Option A is wrong because financial dimensions are for segmentation, not enforcement. Option C is wrong because each legal entity can have its own chart of accounts.

Option D is wrong because main accounts are part of the chart but not the enforcement mechanism.

Option C is correct because cost allocation in Dynamics 365 Finance allows distributing costs based on allocation bases such as square footage. Option A is wrong because absorption costing assigns costs to products, not departments. Option B is wrong because standard costing is for inventory valuation.

Option D is wrong because activity-based costing assigns costs based on activities, but the feature to allocate by square footage is cost allocation.

Option B is correct because the tax engine allows configuration of tax rules without code. Option A is wrong because the general ledger is for accounting entries. Option C is wrong because the electronic reporting module is for generating reports, not managing tax rules.

Option D is wrong because the feature management tool enables/disables features, not tax configurations.

General ledger foreign currency revaluation adjusts account balances. Accounts payable and accounts receivable foreign currency revaluation adjust vendor and customer balances. Bank foreign currency revaluation adjusts bank account balances.

Reporting currency is for translation, not revaluation. Exchange rate adjustment is not a standard term. Options A, B, and D are correct.

Options A, C, and D are correct. Cash flow forecasting, budget proposal, and customer payment predictions are AI features. Option B is wrong because financial reporting is not AI-driven.

Option E is wrong because vendor collaboration is a portal, not AI.

Custom dimensions are user-defined. Entity-backed dimensions are based on system entities like Cost centers. Fixed dimensions are not a type; they are default dimension values.

Main account is an account, not a dimension. Budget dimensions are a concept, not a type.

Correct: B and D. Audit trail tracks changes; Financial reporting generates compliant statements. Option A (Vendor collaboration) is not compliance-specific.

Option C (Cash flow forecasting) is for planning. Option E (Expense management) is for employee expenses.

Option D is correct because Dynamics 365 Finance supports reporting currencies that automatically translate amounts based on exchange rates. Option A is wrong because manual adjustment is error-prone. Option B is wrong because separate legal entities are not required for reporting.

Option C is wrong because periodic exchange rate adjustments are for revaluation, not reporting.

Option A is correct because the Invoice capture add-in uses AI to extract data from PDFs and emails, and can be integrated with Dynamics 365 Finance. It supports PO matching and workflow. Option B is wrong because Power Automate alone cannot perform OCR/AI invoice capture.

Option C is wrong because manual entry is what they want to avoid. Option D is wrong because vendor collaboration does not automate invoice extraction.

Correct: Accounts payable invoice matching automates the three-way matching process. Option A (Vendor collaboration) is for communication, not matching. Option C (Budget control) manages budgets.

Option D (Fixed assets) manages asset lifecycle.

Option D is correct because using standard configurations for a single-entity scenario is the simplest and most efficient approach. Option A is wrong because the chart of accounts is required. Option B is wrong because multiple legal entities are not needed.

Option C is wrong because intercompany setup is unnecessary.

Option C is correct. 200% declining balance doubles straight-line rate. Straight-line rate = 1/5 = 20%. Double = 40%.

First year with half-year convention: 50000 * 40% * 0.5 = 10000. Option A is wrong because it ignores half-year convention. Option B is wrong because it uses straight-line.

Option D is wrong because it uses full year double declining after half-year.

Options B and D are correct. Intercompany partners must be defined, and intercompany accounting sequences must be set up. Option A is incorrect because a shared chart of accounts is beneficial but not required for intercompany accounting.

Option C is incorrect because budget control is unrelated. Option E is incorrect because currency revaluation is a separate process.

Option D is correct because Financial reporting is the dedicated tool for creating financial statements. Option A is wrong because Management reporter is a separate tool, but Financial reporting is the primary one in D365 Finance. Option B is wrong because Power BI requires integration.

Option C is wrong because Excel integration requires manual work.

Option A is correct because invalid account combinations are a common cause of posting failures. Option B is wrong because invoice approval status does not affect account validation. Option C is wrong because vendor holds prevent payment, not posting.

Option D is wrong because general ledger journal entries are not directly related.