CCNA D365 Finance Questions

The correct answers are C (Accounts payable) and D (General ledger), which are core financial modules in Dynamics 365 Finance. Accounts payable manages vendor invoices and payments, while General ledger serves as the central repository for financial transactions. Option A (Sales and marketing) is part of Dynamics 365 Sales, not Finance.

Option B (Human resources) belongs to Dynamics 365 Human Resources. Option E (Project management) is a project accounting module but is not considered a core financial module in the same sense as Accounts payable and General ledger.

Options A, C, and D are correct. Intercompany accounting requires trading partner relationships, intercompany journals, and elimination rules. Option B is wrong because a shared chart of accounts is not required; each legal entity can have its own.

Option E is wrong because a single currency is not required; different currencies are allowed.

Intercompany elimination rules in Dynamics 365 Finance are specifically designed to automatically eliminate intercompany transactions during consolidation. Option A is incorrect because financial dimensions are used for reporting and analysis, not for eliminating transactions. Option B is incorrect because consolidation groups are used to group legal entities for consolidation, not to eliminate intercompany transactions.

Option D is incorrect because intercompany accounting processes intercompany transactions but does not automatically eliminate them during consolidation.

Half year convention starts depreciation at the midpoint of the year, not proportional per day. Declining balance is an accelerated method but does not handle mid-month acquisition proportionally. Straight line service life with prorated first month is the correct method to calculate depreciation based on the exact days the asset was in service.

Reducing balance is similar to declining balance. Option C is correct.

Invoice capture in Dynamics 365 Finance uses AI to automatically classify vendor invoices. Option A is incorrect because Intelligent order management is for sales orders, not invoices. Option B is incorrect because Vendor collaboration is a portal for vendor communication, not AI classification.

Option C is incorrect because OCR is a technology used within Invoice capture, but the feature itself is Invoice capture.

Options C and D are correct. A purchase order-based invoice is created when a vendor invoice is associated with an existing purchase order. Vendor invoice entry allows direct manual entry of vendor invoices without a purchase order.

Option A is incorrect because general journal entries are used for accounting adjustments, not for vendor invoices. Option B is incorrect because sales order invoices are used for customer transactions, not vendor invoices. Option E is incorrect because free text invoices are used for billing customers, not vendors.

Purchase order invoice requires a PO. Vendor invoice journal is for invoices without PO. Invoice pool is for hold.

Vendor invoice workspace is a landing page.

Setting up intercompany accounting and defining intercompany partners is required for automatic reconciliation of intercompany transactions. Option A is incorrect because elimination rules are part of consolidation processes used to remove intercompany balances, not for automatic reconciliation. Option B is incorrect because allocation rules are used for distributing costs, not for intercompany reconciliation.

Option D is incorrect because consolidation processes combine financial statements of multiple legal entities, which is distinct from intercompany transaction reconciliation.

The period status is 'On hold' with the posting restriction 'No posting allowed'. This means that no transactions can be posted in this period, regardless of user role or group membership. Therefore, the invoice dated January 15, 2024, cannot be posted until the period is opened by an authorized user.

Option D correctly states this. Option A is incorrect because manager approval does not override the period restriction. Option B is incorrect because no posting is allowed at all.

Option C is incorrect because the period status prevents posting.

Dynamics 365 Finance allows you to create a batch job that automatically posts sales orders to the general ledger at scheduled intervals. Option A is incorrect because recurring invoices are used for billing customers on a regular basis, not for posting aggregated daily sales. Option C is incorrect because the general journal is typically used for manual adjustments and one-time entries.

Option D is incorrect because the payment journal is for recording payments received, not for posting sales transactions.

Asset management (C) is used to track maintenance, repairs, and schedule preventive maintenance for assets. Fixed assets (E) manages the financial tracking, depreciation, and lifecycle of assets. Budgeting (A) is for financial planning and not for maintenance tracking.

Procurement and sourcing (B) handles purchasing and vendor management, not maintenance. Project management and accounting (D) is for project-based work, not asset maintenance. Therefore, the correct modules are Asset management and Fixed assets.

The command retrieves configuration parameters for the General ledger module, specifically the "Ledger" configuration. Option A is wrong because it retrieves a single setting, not all. Option C is wrong because it doesn't return module list.

Option D is wrong because it doesn't run diagnostics.

The tax code with a rate of 19% and calculation method 'WholeAmount' computes tax on the line amount and adds it: tax = 100 * 0.19 = 19, total = 119. Option A (110.00) implies a 10% tax rate, not 19%. Option B (138.00) implies a 38% tax rate, not 19%.

Option C (100.00) excludes tax entirely.

Correct: Use Data management framework for import, as it supports bulk data import with financial dimensions. Option A is wrong because the Excel add-in is for simple data entry, not complex imports. Option C is wrong because Power Platform is for extensions and custom apps, not the recommended import tool.

Option D is wrong because Entity store is for reporting, not data import.

Options D and E are correct. Audit trails and change logs track changes to financial data, providing transparency required for regulatory compliance. Financial reporting (Management Reporter) enables organizations to create custom reports that meet specific regulatory formats.

Option A is incorrect because vendor invoice automation is an operational feature, not directly related to regulatory reporting. Option B is incorrect because payment schedules manage cash flow, not compliance. Option C is incorrect because budget control focuses on spending limits, not reporting requirements.

The entry debits Cash (account 1100, an asset) and credits Accounts Payable (account 2100, a liability). A debit increases Cash, and a credit increases Accounts Payable. This results in both an increase in cash and an increase in a liability, which matches option C.

Such an entry could represent receiving a deposit or a loan, where the company receives cash and incurs a liability to repay.

A main account starting with 1 and having a posting type 'Balance' typically indicates a balance sheet asset account. Option D is correct. Option A is wrong because revenue accounts start with 4.

Option B is wrong because liability accounts start with 2. Option C is wrong because expense accounts start with 6.

Three-way matching in Dynamics 365 Finance compares the purchase order, product receipt, and vendor invoice. Options B (Product receipt) and C (Purchase order) are the two components required for three-way matching, along with the vendor invoice. Option A (Vendor invoice) is the third component, not one of the two required in addition to itself.

Therefore, A is incorrect. Option D (Packing slip) is not used in three-way matching, and Option E (General journal entry) is unrelated.

Three-way matching in Dynamics 365 Finance requires all three components: accounts payable parameters (to enable matching), the invoice matching workflow (to define the approval process), and vendor tolerances (to set acceptable variances). Option A is wrong because only the workflow is insufficient without enabling matching in parameters and setting tolerances. Option B is wrong because only accounts payable parameters are insufficient without the workflow and tolerances.

Option D is wrong because only vendor tolerances are insufficient without the parameters and workflow.

The correct first step is to run the 'Troubleshoot GL balance' report in Accounts payable. This report is specifically designed to identify discrepancies between the general ledger and the subledger for accounts payable. Option A is incorrect because the invoice approval workflow affects approval processes, not GL-subledger balances.

Option B is incorrect because reviewing the vendor payment settlement process pertains to payments, not balance discrepancies. Option D is incorrect because re-running the payment journal report shows payment details, not balance reconciliation.

Electronic reporting (ER) is the correct feature as it allows configuring electronic documents for different countries/regions, including electronic invoices. Option B (Payment formats) is used for defining payment formats, not for electronic invoicing compliance. Option C (Financial reporting) is for creating financial statements and reports, not for electronic invoicing.

Option D (Data management) is a framework for data import/export and entity management, not specifically for electronic invoicing.

A purchase requisition workflow can be configured to automatically generate a purchase order when the requisition is approved. Option A is incorrect because a procurement catalog defines approved items but does not automate PO creation. Option B is incorrect because vendor collaboration enables external communication, not PO creation from requisitions.

Option D is incorrect because the Request for quotation (RFQ) process is for competitive bidding, not automatic PO generation from approved requisitions.

Dynamics 365 Finance supports custom period templates like 4-4-5. Option A is wrong because fiscal year date intervals define date ranges, not period patterns. Option B is wrong because the standard calendar is 12 months and does not support a 4-4-5 pattern.

Option C is wrong because the period close template manages closing processes.

The exchange rate type 'Average' is designed for reporting and is not used for automatic conversion during document posting. Dynamics 365 Finance requires a rate type such as 'Spot' or 'Daily' to trigger automatic currency conversion. Option B is incorrect because the CurrencyCode is set correctly to USD (the target currency).

Option C is incorrect; a future date does not prevent the rate from being used—it would simply apply when that date becomes current. Option D is incorrect; tolerance settings control rate variance checks, not whether a rate is applied at all.

Standard costing updates costs based on predetermined standards, not automatically from purchase invoices. Weighted average and moving average can update on invoice posting. FIFO tracks actual cost layers.

Moving average is commonly used for real-time cost updates.

The AI anomaly detection feature in the Finance insights module uses machine learning to identify unusual financial transactions. Option A is incorrect because 'Activate Copilot for Finance insights to generate reports' focuses on report generation, not anomaly detection. Option B is irrelevant as Copilot for Sales is designed for sales processes, not financial anomaly detection.

Option D is also incorrect as Copilot for Service is for customer service scenarios, not financial transactions.