Advanced Bank Reconciliation in D365 Finance: Setup and Use

Quick Answer: Advanced bank reconciliation in Dynamics 365 Finance (D365) imports an electronic bank statement, validates it, and matches its lines to the bank transactions already posted in Finance using matching rules you define. You turn it on per bank account (Reconciliation FastTab), import ISO 20022 camt.053, MT940 or BAI2 files, run matching rules on the Bank reconciliation worksheet, mark bank-initiated items such as fees as New, then mark the reconciliation as reconciled and post the new lines from the Bank statement page.

Advanced bank reconciliation is the Dynamics 365 Finance feature that replaces ticking off bank lines by hand with an imported statement and rule-based matching. Setup has three parts (statement format, bank account, matching rules), and each month's work has four (import, validate, match, mark reconciled and post). The steps below follow Microsoft Learn's documentation as of October 2026.

Which bank statement formats does advanced bank reconciliation accept?

Microsoft's Electronic reporting (ER) setup page lists three formats, each with its own ER configuration under the Advanced bank reconciliation statement model:

Microsoft also describes extending the import to other formats, and a second route through the data entity framework using two entities, Bank statement header and Bank statement lines. That second route matters if your bank can't produce any of the three files; more on that near the end.

Note one change in Microsoft's documentation: the older setup that built a Data management processing group from XSLT transformation files carries a deprecation note on Microsoft Learn, and new users are pointed to Electronic reporting. If you inherited an environment set up the old way, it may still be running on those transformation files.

Setting it up, in order

1. Import the ER configuration for your bank's format

In Workspaces > Electronic reporting, open Repositories on the Microsoft configuration provider tile, choose Dataverse, and select Open. Find the Advanced bank reconciliation statement model in the list, select the format that matches your bank's file, pick the latest version on the Versions FastTab and select Import. Microsoft's page says to confirm afterwards that the configuration appears on the Configurations page without validation errors.

2. Create a bank statement format

Go to Cash and bank management > Setup > Advanced bank reconciliation setup > Bank statement format and select New. Fill in Statement format and Name, set the File type (TXT or XML; for a ZIP of several file types, list them separated by semicolons), tick Generic electronic import format, and choose the ER configuration from step 1 in Import format configuration.

3. Turn on advanced bank reconciliation for the bank account

Open the account under Cash and bank management > Bank accounts > Bank accounts. On the Reconciliation FastTab set Advanced bank reconciliation to Yes and pick the Statement format that matches the bank's file. Microsoft warns that a mismatch between the account's format and the file you upload can make the import fail. The overview also lists setting up a number sequence for advanced bank reconciliation as part of setup, so check that one exists before the first import.

Two fields on the same account are worth setting now: Allowed penny difference, which lets a single statement line and a single Finance transaction match when they differ by a few cents, and the Default matching rule set, which runs automatically on import (see below).

4. Define matching rules and a rule set

Rules live under Cash and bank management > Setup > Advanced bank reconciliation setup > Reconciliation matching rules. For each rule: New, a name and description, an action, a Matching type, the selection criteria on the step FastTabs, Save, then Activate. An inactive rule does nothing, which is an easy thing to miss on the first run.

Then group rules on Reconciliation matching rule sets. A set runs its rules top to bottom, so put the strictest rule first (exact amount plus reference) and the looser ones after it.

What do the matching rule actions do?

The action decides what a rule does with the lines it finds. Some need the Modern bank reconciliation feature turned on in Feature management.

• Match with bank document (base): pairs statement lines with Finance bank transactions. This is the workhorse rule.
• Mark new transactions (base, not available when Modern is on): flags statement lines that have no Finance transaction as New.
• Clear reversal statement lines (base, enhanced in Modern): clears a bank error and its reversal against each other, matched on document number and payment reference.
• Generate customer payment / Generate vendor payment (Modern): posts a payment journal from a statement line. The bank account needs default customer and vendor payment journals.
• Settle customer invoice (Modern): generates the customer payment and settles a matched open invoice.
• Generate voucher (Modern): posts non-payment lines such as interest and fees straight to the general ledger with an offset account you choose.
• Clear reversal company transaction (Modern): clears reversed company payment journals that never reached the bank; the transactions must net to zero.

By default a rule matches to the first Finance transaction that meets its criteria. If several invoices of the same amount could match, turn on Require manual matching when advanced bank reconciliation matching rules find multiple documents that match on amount in Cash and bank management parameters > Bank reconciliation, so the system leaves those for a person instead of guessing.

The monthly cycle

Import. On the Bank statements page, select Import statement, choose the bank account, browse to the file and Upload. One file can hold several accounts, even across legal entities, if you set Import statement for multiple bank accounts in all legal entities to Yes; a ZIP of several files works the same way. The system identifies the account from the bank name, account number, routing number, SWIFT code and IBAN on the statement. It skips a statement whose account number, statement ID and from- and to-dates match one already imported.

Setting Reconcile after import to Yes validates the statement, creates the reconciliation and worksheet, and runs the default rule set in one step. Microsoft describes this as automating everything up to the point where lines need a manual match.

Validate. If you didn't use Reconcile after import, select Validate on the statement. Validation checks that the statement belongs to the account and its currency, that its opening balance equals the previous statement's closing balance, that its dates don't overlap another statement for the account, that every line date sits inside the statement period, and that opening balance plus line amounts equals the ending balance. A statement you can't validate can't be reconciled, so a missing month shows up here.

Match. On Bank reconciliation, select New, pick the account and check the cut-off date (it defaults to today and decides which transactions appear). A bank account can have only one open reconciliation. Open the Worksheet, select Run matching rules if they didn't run on import, then work the leftovers by hand: select lines in the bank statement grid and the Finance bank transactions grid and choose Match. One-to-one, many-to-one and many-to-many matches are allowed within the date-difference and transaction-type rules set on Cash and bank management parameters. Unmatch sends a wrong pair back to the unmatched grids.

For a fee or interest line that isn't in Finance yet, select it and choose Mark as new.

Mark reconciled and post. When the worksheet looks right, mark it as reconciled. Penny-difference corrections post automatically to the main account on the bank transaction type. Unmatched lines roll forward to the next worksheet. This step can't be undone, and the reconciliation can't be edited afterwards, so review before you click. Lines marked New are posted from the Bank statement page with Post, and posting can be done only once per statement; View distributions and View accounting on the Accounting menu show the ledger entries first.

Why does a statement fail to import or validate?

When an import fails, Microsoft points to the job's Execution details and View execution log in the Data management workspace's Job history for the errors. The usual causes, going by the checks Microsoft documents:

1. Format mismatch. The account is set to MT940 and the file is camt.053, or the reverse.
2. Account identification. The account number, IBAN or SWIFT code on the statement doesn't match the bank account record, so the statement is skipped while others in the same file import.
3. Duplicate statement. Same account, statement ID and dates as one already in the system.
4. Balance chain broken. The opening balance doesn't equal last month's closing balance, usually because a statement was skipped or imported out of order.
5. Time zone. Dates are treated as UTC unless a Time zone preference is set on the source data format, which can push a line just outside the statement period.

What if your bank only sends PDF statements?

First ask the bank. Many banks offer business customers camt.053, MT940 or BAI2 files through a cash management portal or a direct connection, so check before you build a workaround. That file is what advanced bank reconciliation is built around. If you're stuck reading an MT940 file in the meantime, opening MT940 in Excel explains the field tags.

If PDFs are all you can get (a small foreign subsidiary account, a credit union, an account being closed), the data entity route is the realistic option. The Bank statement header entity takes STATEMENTID, BANKACCOUNT, CURRENCY, OPENINGBALANCE, ENDINGBALANCE, FROMDATE and TODATE; Bank statement lines takes LINENUMBER, BANKACCOUNT, STATEMENTID, BOOKINGDATE and AMOUNT among other optional fields. You need those values as rows first. QuickBankConvert reads the PDF and returns one row per transaction with date, description and signed amount, plus the opening and closing balance and statement period it found, which as CSV can be rearranged into the two entity templates. It does not produce camt.053, MT940 or BAI2 files, so this is a spreadsheet-to-entity path, and building the Data management import project is a job for whoever administers your Finance environment.

Before importing, check that the lines sum to closing minus opening balance. Validation will reject the statement if they don't, so it's better to catch it in the spreadsheet.

Related guides

• Bank statement reconciliation guide for the principles behind any reconciliation
• NetSuite bank reconciliation if you're comparing ERPs
• Automating bank reconciliation for matching-rule ideas outside D365
• Microsoft Learn: Reconcile bank statements by using advanced bank reconciliation and Set up bank reconciliation matching rules