Implementing Advanced Bank Reconciliation in Dynamics 365 Finance
Short answer
ADE Configure Bank statement import, Configure a number sequence, and Configure matching rules and matching groups for bank transactions.
Question
You need to implement advanced bank reconciliation.
Which three actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Key Takeaways
Distinguish between configuring the infrastructure (imports, number sequences, rules) versus performing the operational task (matching/importing data).
Learn the three key configuration steps for advanced bank reconciliation in Dynamics 365 Finance: importing bank statements, setting up number sequences, and defining matching rules.
Common mistake: Choosing Option B because it sounds like the goal of automation, but it is an action, not a configuration step. Choosing C because it mentions data entities, but A is the more comprehensive configuration requirement.
Expert Analysis
The question asks for configuration steps to implement advanced bank reconciliation in Dynamics 365 Finance. This feature automates the matching of bank statement lines with ledger transactions.
First, you must configure a number sequence (Option D) for bank statements and reconciliation journals. This ensures unique identifiers are generated for imported statements and created journal entries, which is a foundational setup requirement.
Second, you need to configure Bank statement import (Option A). This involves setting up the file formats (such as ISO20022, BAI2, or MT940) so that the system can ingest external bank data. Without this import configuration, the automation cannot begin.
Third, you must configure matching rules and matching groups (Option E). Advanced bank reconciliation relies heavily on these rules to automatically match bank statement lines with existing ledger transactions based on criteria like amount, date, and reference numbers. Defining these rules is the core of the 'advanced' automation.
Options B and C describe operational actions rather than configuration steps. Performing automatic matching is part of the reconciliation process itself, not the initial implementation setup. Importing bank statements through the Data entity framework is a method of data ingestion but is encompassed by the broader 'Bank statement import' configuration; moreover, the specific mention of 'Data entity framework' is less precise than the general import configuration required for the feature to function. The comments highlight that A, D, and E are the structural prerequisites for enabling the feature.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked about 'implementing' or 'configuring' a feature, look for setup tasks (number sequences, parameters, rule definitions) rather than execution tasks (running jobs, importing files). In Dynamics 365, advanced features often require explicit enablement of number sequences and specific matching logic before they can be used.
Frequently Asked Questions
What file formats are supported for bank statement imports?
Why is a number sequence needed for bank reconciliation?
Community Votes
27% of anonymous learners picked answer E. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
f43adb2 👍 2The question is to implement, not execute adv bank rec session. Seems ADE are the better answers.
-
Mukhtartij 👍 1Microsoft lays the advanced bank reconciliation flow out in three main steps. The first is to set up a bank statement import. The second covers the matching rules, since you can set up reconciliation matching rules and reconciliation matching rule sets to help with the bank reconciliation process. The third is to reconcile bank statements with Dynamics 365 Finance bank transactions. A. Configure bank statement import is step one. E. Configure matching rules and matching groups is step two. B. Perform automatic matching and creation of reconciliation journals is step three. The overview’s list of what the feature does includes performing automatic matching and creation of reconciliation journals. Why not the others: C. Import bank statements through the data entity framework. This is a sub-point of step one. Microsoft lists it as one way of setting up the import, under import bank statements through the data entity framework. It isn’t a separate action alongside the other three. D. Configure a number sequence. This is a real setup task, as MS says: you must also configure number sequences on the Cash and bank management parameters page, but it sits inside the preparation for step two as a supporting setting. The overview names it together with the matching rules (set up a number sequence to use for advanced bank reconciliation, and define the bank reconciliation matching rules), so it isn’t one of the three top-level actions. Caveat: C and D are both true statements, and I’m choosing between them and A, B and E by how MS groups the steps.
-
Invatare 👍 1Set up a bank statement import. Import bank statements through the data entity framework. Three typical bank statement formats are supported in Finance: ISO20022, BAI2, and MT940. The functionality can be extended to any format. Set up a number sequence to use for advanced bank reconciliation and define the bank reconciliation matching rules. A reconciliation matching rule is a set of criteria that is used to filter bank statement lines and Finance bank transaction lines during the reconciliation process. Depending on your business practice, you can set up more than one matching rule to automate and optimize your reconciliation process.
-
globeearth 👍 1A. Configure Bank statement import: Set up the bank statement format to enable file imports. D. Configure a number sequence: Ensure a number sequence is set up for bank statements or reconciliation journals. E. Configure matching rules and matching groups for bank transactions: Define rules for automated transaction matching. why not B and C? B -This describes an operational process, not a configuration step. C - Data entity framework is not the standard method for importing bank statements in advanced bank reconciliation.
-
NatKae 👍 1seems correct https://learn.microsoft.com/en-us/training/modules/configure-periodic-processes-dyn365-finance/02-bank-reconciliations
Show 1 more comment
-
Neuwe 👍 1https://learn.microsoft.com/en-us/dynamics365/finance/cash-bank-management/advanced-bank-reconciliation-overview
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All MB-310 Questions
Access 100 questions with complete answers and detailed explanations.
View Full MB-310 Practice Test →