Advanced Bank Reconciliation in Dynamics 365 Finance
- Alfredo Iorio
- May 24
- 4 min read
Advanced bank reconciliation in Dynamics 365 Finance lets you import an electronic bank statement and reconcile it automatically against bank transactions. A matching engine pairs statement lines with D365 bank transactions according to rules you configure. What the engine cannot match is left on a worksheet for manual handling.
Three bank statement formats are supported out of the box: ISO20022 (camt. 053), MT940, and BAI2.
The Modern Bank Reconciliation feature, available from version 10.0.41, is an enhancement on top of advanced bank reconciliation. It adds matching types, automatic posting of customer and vendor payment journals from the worksheet, and an updated worksheet interface.
Once advanced bank reconciliation is enabled on a bank account, switching back is constrained. A feature management option allows deactivation only when there are no unreconciled statements outstanding.
Importing bank statements and configuring automatic matching rules
The statement format is configured through Electronic Reporting. From Workspaces > Electronic Reporting, open the Microsoft repository, find the format your bank supports, and import the latest version. The imported configuration is then assigned in Cash and bank management > Setup > Advanced bank reconciliation setup > Bank statement format.
On the bank account, set Advanced bank reconciliation to Yes, assign the statement format, and set the bank account number to match the value carried in the statement file exactly. The Bank name in the statements field on the account must also match the bank name as it appears in the file.
Matching rules are defined at Cash and bank management > Setup > Advanced bank reconciliation setup > Reconciliation matching rules. A rule combines criteria (amount, date tolerance, reference, transaction code, document type) with an action (match, generate voucher, generate customer payment journal, generate vendor payment journal, clear reversal). A matching rule set groups rules in a sequence that runs during reconciliation.
Two parameters on Cash and bank management parameters > Bank reconciliation are set at this stage. Validate date difference allows automatic matching across a defined date tolerance. Validate transaction type mapping requires bank transaction codes to be mapped to D365 bank transaction types before matching runs. The transaction code mapping itself is at Advanced bank reconciliation setup > Transaction code mapping, set per bank account.
Two further options on the bank account control the import. Reconcile after import, when enabled, validates the statement, creates the worksheet, and runs the default matching rule set automatically on import. The Allowed penny difference field sets the tolerance for matching when the statement and D365 amounts differ slightly.
How the matching engine works and what it leaves for manual review
The reconciliation worksheet shows unmatched bank statement lines and unmatched D365 bank transactions, with matched pairs in a separate view.
When matching rules run, the engine processes each rule in the rule set order. For each unmatched statement line, the engine applies the rule criteria and looks for D365 bank transactions that fit. A successful match moves both records to the matched view.
If a rule's criteria match more than one D365 transaction, the parameter Require manual matching when advanced reconciliation matching rules find multiple documents that match on amount controls the behaviour. With the parameter on, the engine leaves the line for manual review. With it off, the engine selects the first matching transaction.
Matches can be one-to-one, many-to-one (a single bank line against several D365 transactions, such as a deposit slip with multiple cheques), or many-to-many.
Manual matching is performed by selecting one statement line and one or more D365 transactions, then clicking Match. Differences within the allowed penny tolerance are recorded for posting as corrections when the worksheet is marked reconciled.
Posting unreconciled differences and closing the reconciliation
Bank-initiated transactions on the statement that have no corresponding D365 transaction (fees, interest, charges, returned items) are handled with Mark as new. The line is added to a bank statement journal associated with the reconciliation. The journal is then posted from the Bank statement page to the appropriate main account. If transaction code mapping is configured, the main account is suggested from the bank transaction type.
Penny differences within the configured tolerance post as corrections automatically against the main account on the bank transaction type when the worksheet is marked reconciled. Differences above tolerance must be resolved manually.
D365 transactions not yet on a bank statement (outstanding cheques, recent transfers) are left unmatched. They appear on a future statement and are picked up at the next reconciliation.
Once all required entries have been matched, marked as new, or posted, click Mark as reconciled. The worksheet locks. The reconciliation statement is generated. Bank transactions for the period are flagged as reconciled. The closing balance becomes the opening balance for the next reconciliation.
If you are working through advanced bank reconciliation as part of a D365 Finance deployment, the user training starter kit covers how to plan adoption training around features like this.
Comments