CCNA Describe Dynamics 365 Finance Questions

Copilot for Finance leverages AI Builder for AI-powered invoice matching, and AI Builder requires a Power Apps license to be enabled. Option A is incorrect because electronic reporting formats are used for document generation, not for AI matching. Option B is incorrect because workflow for invoice approval is a process control feature, not a prerequisite for AI.

Option D is incorrect because data entities are for data import/export, not for enabling AI capabilities.

Options C and D are correct. Option C is correct because the General ledger provides a chart of accounts to categorize financial transactions. Option D is correct because it offers real-time financial insights and reporting.

Option A is wrong because managing vendor payments and invoices is done in Accounts payable. Option B is wrong because handling customer invoicing and collections is done in Accounts receivable. Option E is wrong because inventory valuation is part of Inventory management.

Dynamics 365 Finance includes AI-driven customer payment predictions that provide insights and recommendations for proactive actions. Option B is wrong because cash flow forecasting focuses on projecting cash inflows and outflows, not specifically predicting payment delays. Option C is wrong because Microsoft Copilot in Finance is for conversational assistance and does not specialize in payment predictions.

Option D is wrong because budgeting and planning is for creating and managing budgets, not predicting payment delays.

The 'Average' translation method uses the average exchange rate for the period, which is appropriate for income statement accounts per accounting standards. Option A is wrong because 'Ending' is not a standard translation method in Dynamics 365 Finance. Option B is wrong because 'Current' (end of period rate) is typically used for balance sheet accounts, not income statement.

Option D is wrong because 'Historical' (transaction date rate) is used for equity accounts.

Purchase order workflow in Dynamics 365 Finance allows configuration of conditional approval rules, such as requiring director approval for purchase orders exceeding a certain amount. Option A is incorrect because an approval journal is not a standard concept in Dynamics 365 Finance for this purpose. Option B is incorrect because procurement and sourcing parameters cover general settings but not specific approval workflows.

Option C is incorrect because the budget manager role is related to budget control, not purchase order approval.

Intercompany accounting is the feature that automates intercompany transactions, making Option D correct. Option A (Elimination rules) is used to remove intercompany balances during consolidation, not for day-to-day transactions. Option B (Consolidations) combines financial statements of multiple entities, not for processing individual transactions.

Option C (Transfer orders) are for inventory transfers between locations, not for general intercompany transactions.

Correct: C and E. Fixed asset management (C) is a core module within Dynamics 365 Finance, handling asset lifecycle, depreciation, and disposal. Budget control (E) is a key feature for monitoring and enforcing budget limits.

Option A (Project scheduling) belongs to Project Operations, not Finance. Option B (Marketing automation) is part of Dynamics 365 Marketing. Option D (Customer service management) is in Dynamics 365 Customer Service.

Payment proposals allow users to select multiple invoices for a vendor and generate a single payment. Option A is wrong because electronic payment format is for generating payment files, not for grouping invoices. 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.

Financial dimensions (Option D) are used to track attributes like department and project in Dynamics 365 Finance. Account structures (Option A) define the chart of accounts, not for tracking additional attributes. Dimension sets (Option B) are used for reporting and analysis, not for transaction capture.

Advanced rules (Option C) allow for conditional dimension combinations, but the base dimension type for capturing department and project is financial dimensions.

Correct: Create a journal approval workflow. Option A is wrong because Financial dimension sets are for reporting, not for approval. Option B is wrong because General ledger parameters include various settings but not journal approval workflows.

Option D is wrong because Audit trail settings track changes but do not enforce approvals.

The shared chart of accounts feature in Dynamics 365 Finance allows a single chart of accounts to be used across multiple legal entities, ensuring consistency and simplifying maintenance. Option A is incorrect because deleting unused accounts is irrelevant to sharing. Option C is incorrect because financial dimensions are used for tracking, not for sharing the chart of accounts.

Option D is incorrect because separate charts per entity increase complexity and are not a best practice.

Consolidation in Dynamics 365 Finance automatically aggregates financial data from multiple legal entities. Option A is wrong because currency revaluation adjusts exchange rates, not consolidate data. Option C is wrong because financial dimension sets are used for reporting and analysis hierarchies, not for consolidating data across entities.

Option D is wrong because elimination rules remove intercompany transactions during consolidation, but they do not perform the consolidation itself.

Budget control must be enabled and configured to check funds availability for purchase orders. Option A is wrong because budget plans are for planning, not control. Option B is wrong because budget register entries record budget amounts, but do not enforce control.

Option D is wrong because budget models define the budget structure, not control.

Customer payment predictions use AI to forecast when customers will pay invoices. This feature is designed to help businesses predict payment times and manage cash flow more effectively. Option C is correct.

Option A (Cash flow forecasting) is for predicting cash inflows and outflows, not specifically customer payment times. Option B (Financial reporting) is for generating financial statements and reports. Option D (Invoice capture) is for automating invoice data entry, not for payment predictions.

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

Budget model is a structure.

In Dynamics 365 Finance, the period closing checklist includes various tasks, but not all are mandatory for the period to be closed. The critical prerequisite is that all vendor invoices must be posted before the period close can be executed. Unposted invoices would prevent the closing process.

Generating the vendor aging report or running currency revaluation are optional or can be done after closing. Therefore, posting vendor invoices is the task that must be completed.

Invoice matching validation enforces three-way matching between the purchase order, receipt, and invoice, ensuring quantities and amounts align before payment. Option A (vendor payment journal) is for recording payments, not matching. Option B (purchase agreement) is for long-term contracts and pricing.

Option C (payment schedule) is for installment payment terms. Only Option D enables the necessary validation.

In Dynamics 365 Finance, financial dimensions (e.g., Department and Project) are attributes attached to a main account to enable tracking by multiple dimensions simultaneously. Option A is wrong because cost centers and cost objects belong to cost accounting, not general ledger dimension tracking. Option B is wrong because main accounts and subaccounts are for chart of accounts structure, not for multi-dimensional tracking.

Option C is wrong because budget codes and budget classes are used for budgeting, not for expense tracking across dimensions.

The 'Post inventory in ledger' parameter in Dynamics 365 Finance enables automatic posting of inventory transactions to the general ledger when using a perpetual inventory system. Option A (Warehouse management parameters) controls warehouse processes, not general ledger posting. Option B (Inventory model group) defines the costing method and inventory model but does not control automatic posting.

Option C (Item model group) is synonymous with inventory model group and thus also not for posting. Only Option D correctly enables the required automatic ledger posting.

Correct: The VendTrans table is from Accounts payable, making D the correct answer. Option A is wrong because Fixed assets uses AssetTrans. Option B is wrong because General ledger uses LedgerTrans.

Option C is wrong because Sales tax uses TaxTrans.

Budget control is a capability of the Budgeting module that monitors budget consumption against actual expenditures. Option C is correct because budget register entries allow users to record and manage budget amounts. Option E is correct because budget planning enables the creation and management of budget proposals.

Option B is incorrect because processing vendor invoices is handled in the Accounts payable module, not the Budgeting module. Option D is incorrect because generating financial statements is performed in the Financial reporting module.

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.

Intercompany elimination rules in Dynamics 365 Finance allow automatic elimination of intercompany transactions during the consolidation process. Option B is wrong because consolidation companies aggregate data but do not eliminate intercompany transactions automatically. Option C is wrong because manual identification and removal is error-prone and not automatic.

Option D is wrong because intercompany accounting posts transactions to both legal entities but does not eliminate them during consolidation.

Dynamics 365 Finance allows you to configure intercompany parameters to automatically generate intercompany invoices when purchase orders are confirmed. Option B is incorrect because using vendor invoices manually is not automatic and does not streamline the process. Option C is incorrect because purchase agreements define terms between legal entities but do not automatically create invoices upon purchase order confirmation.

Option D is incorrect because recurring invoices are for repetitive invoicing to customers, not for intercompany transactions triggered by purchase orders.

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.

Financial dimension sets allow users to group and analyze financial data by selected dimensions for reporting and analysis purposes. Option A is incorrect because the main account and dimension structure is defined by account structures, not dimension sets. Option B is incorrect because validation of dimension combinations is done by advanced rule structures, not dimension sets.

Option C is incorrect because dimension sets do not control access; security roles and policies handle data access.

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

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

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 shows "DataEntity": "GeneralJournalAccountEntry", so that is the entity being exported. Option D is correct. Option A (DimensionSetEntry) is for dimension sets, not general journal entries.

Option B (GeneralJournalTransaction) is for individual transaction lines. Option C (GeneralJournalEntry) is for the journal header. Only GeneralJournalAccountEntry contains the detailed account-level lines.

Cash flow forecasting is the correct feature because it uses historical data to predict future cash positions. Option B, Cash flow forecasting, is designed for this purpose. Budgeting (D) is for planning, not forecasting.

Bank reconciliation (C) matches transactions. Payment proposals (A) generate payments. Therefore, B is correct.

Correct: The period status for fiscal year 2025 is set to 'Closed', which prevents any new postings. Option A correctly identifies this. Option B is incorrect because the module setting does not affect journal posting in General ledger.

Option C is incorrect because USMF is a valid legal entity for general ledger posting. Option D is incorrect because the fiscal calendar year 2025 is opened, but the period status itself is closed.

Options B and D are correct. B: Credit and collections management is a core feature of Dynamics 365 Finance, handling customer credit limits and collections processes. D: Budget planning is another core feature, enabling organizations to create and manage budgets.

Options A, C, and E are incorrect: A (Power BI dashboards) is a reporting capability often integrated but not a core Finance feature; C (Warehouse management) is part of Dynamics 365 Supply Chain Management; E (Omnichannel order management) belongs to Dynamics 365 Commerce.

Intercompany accounting setup enables automatic generation and elimination of intercompany transactions, ensuring automatic reconciliation in the general ledger. Option A (Currency revaluation) is used to adjust foreign currency balances, not for intercompany transactions. Option B (Organization hierarchy) defines reporting structures but does not handle intercompany accounting.

Option D (Consolidation) combines financial data from multiple entities into a single set of statements, but does not automatically reconcile intercompany transactions.

If tax codes are not assigned to items or customers, the system cannot determine the appropriate tax rate, leading to incorrect calculations. Option B is wrong because the tax authority configuration is about reporting and remittance, not calculation. Option C is wrong because ledger posting groups only affect where tax amounts are posted, not how they are calculated.

Option D is wrong because withholding tax is a separate deduction and does not impact sales tax calculation.

Settlement functionality in the customer payment journal allows the clerk to apply a partial payment to a specific invoice, such as the oldest one. Option A is incorrect because the collections process is used for managing overdue accounts, not for applying payments. Option B is incorrect because credit and collections parameters can auto-apply payments, but that is not the specific feature the clerk needs to manually apply to the oldest invoice.

Option C is incorrect because a payment schedule is for installment payments, not for applying a single partial payment to an existing invoice.

A shared chart of accounts allows a single chart of accounts to be used across all legal entities, ensuring consistency. Option A is incorrect because financial dimensions are used to add additional segmentation to transactions, not to enforce a chart of accounts structure. Option B is incorrect because legal entity overrides are used to customize configurations for specific entities, not to enforce consistency.

Option C is incorrect because main account categories group main accounts for reporting but do not enforce the chart of accounts across entities.

The Tax engine in Dynamics 365 Finance allows you to configure tax rules and rates without customizing code, supporting multi-country compliance. Option A (General ledger parameters) is wrong because it deals with ledger setup, not specific tax configurations. Option B (Electronic reporting module) is wrong because it is used for generating regulatory reports, not for configuring tax rules.

Option D (Feature management) is wrong because it enables or disables features, but does not manage tax configurations.

General ledger foreign currency revaluation adjusts account balances for exchange rate fluctuations. Accounts payable and accounts receivable foreign currency revaluation adjust vendor and customer balances, respectively. Reporting currency translation is used for converting financial statements to a reporting currency, not for revaluation.

Therefore, the correct three actions are: Run Accounts payable foreign currency revaluation (A), Run General ledger foreign currency revaluation (C), and Run Accounts receivable foreign currency revaluation (D).

Options A, B, and C are correct. Budget proposal from historical data, cash flow forecasting, and customer payment predictions are AI-driven features in Dynamics 365 Finance. Option D (Financial reporting) is not AI-driven; it is a standard reporting capability.

Option E (Vendor collaboration workspace) is a portal for vendor interactions, not an AI feature.

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.

Dynamics 365 Finance allows defining a reporting currency in the ledger setup, which automatically translates amounts using exchange rates and translation methods like current rate or temporal method. Option A is incorrect because manual adjustments are error-prone and inefficient. Option C is incorrect because separate legal entities are not needed; reporting currency is a ledger-level feature.

Option D is incorrect because periodic exchange rate adjustments are used for revaluation of open transactions, not for financial reporting translation.

The Dynamics 365 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 approval workflows for unmatched invoices. Option A is wrong because hiring temporary staff does not address automation.

Option B is wrong because vendor collaboration allows vendors to enter invoices but does not automate extraction from PDFs/emails. Option D is wrong because Power Automate alone cannot perform OCR/AI invoice capture and still requires manual entry.

Correct: Accounts payable invoice matching (option A) automates the three-way matching process among purchase orders, product receipts, and vendor invoices. Option B (Vendor collaboration) is for communication with vendors, not matching. Option C (Budget control) manages budgets.

Option D (Fixed assets management) handles asset lifecycle.

It configures a 'Time and material' project group with WIP accounting enabled and defines billing rules. This setup automatically recognizes revenue as costs are incurred (WIP method) and allows automatic invoice generation based on progress. Option A (accruals) is for non-WIP methods and periodic tasks are not automated.

Option B (Fixed-price) is incorrect because the company uses time and materials billing. Option C (manual invoices) does not automate invoice generation. D matches all requirements using standard features.

The asset cost is $50,000 with a 5-year useful life and 200% declining balance method with half-year convention. Straight-line rate = 1/5 = 20%. Double-declining rate = 2 × 20% = 40%.

First-year depreciation with half-year convention: $50,000 × 40% × 0.5 = $10,000. Option A ($20,000) ignores the half-year convention. Option C ($12,000) is not a valid calculation.

Option D ($10,000 straight-line) is incorrect because the method used is declining balance, not straight-line.

Options A and B are correct. Intercompany accounting sequences must be set up to define the document numbering for intercompany transactions, and intercompany partners must be defined to establish the legal entities involved. Option C is incorrect because a shared chart of accounts is beneficial but not required.

Option D is incorrect because currency revaluation is a separate process not mandatory for intercompany accounting. Option E is incorrect because budget control configuration is unrelated to intercompany accounting.

Financial reporting is the dedicated tool for creating financial statements like balance sheets and income statements in Dynamics 365 Finance. Option A is wrong because Management reporter is a separate legacy tool, but Financial reporting is the primary tool in D365 Finance. Option B is wrong because Power BI requires integration and is not specifically designed for financial statements.

Option D is wrong because Excel integration requires manual work and is not a dedicated reporting solution.

A fiscal year starting July 1 and ending June 30 is defined as a 'July through June' fiscal year in Dynamics 365 Finance. Option B (October through September) is a different fiscal year pattern. Option C (Calendar year) runs January to December.

Option D (April through March) is another fiscal year variant.

The budget register entries for accounts 601500-001-023 (50,000 USD) and 601500-001-024 (30,000 USD) both have Department 001. With budget control enabled for that department, the total budget available is 50,000 + 30,000 = 80,000 USD. Therefore, option C (80,000 USD) is the correct answer.

Option D is a duplicate and not considered a separate correct answer.

Archiving historical transactions reduces the data volume, which directly addresses the performance issue caused by a high number of open transactions during month-end close. Option A is incorrect because increasing concurrent users would place more load on the system, likely worsening performance. Option B is incorrect because modifying financial reporting to use summary data might improve report generation but does not reduce the volume of open transactions.

Option C is incorrect because running processes in batch mode can help with scheduling but does not reduce data volume.

Copilot in Dynamics 365 Finance can generate a cash flow forecast report, assisting financial analysis. Option A is wrong because Copilot cannot configure system parameters for the General ledger; it is an AI assistant that provides insights but does not perform system configuration. Option B is wrong because Copilot cannot run batch jobs for period-end closing; these are automated background processes.

Option D is wrong because Copilot cannot automatically post pending invoices; transaction posting requires manual or workflow-driven actions, not Copilot's direct execution.

Correct: Invoice matching validates amounts against purchase order and receipts. Partial receipt causes mismatch. Option A (Invoice not approved in workflow) would not cause this error.

Option B (Vendor blocked for posting) would prevent posting entirely. Option C (Invoice currency differs from PO currency) would give a different error.