ERP Bank Reconciliation: Match Statement Lines Without Hiding Exceptions – ERP Finance World

Quick answer: Validate the statement before matching, use references and transaction details—not amounts alone—and investigate every unmatched item. Carry supported timing differences forward, post only explained and approved corrections, and retain evidence for review. In Dynamics 365 Finance, matching rules can select the first qualifying transaction, so enable manual review when multiple documents match on amount. (learn.microsoft.com)

This guide separates a recommended finance-control workflow from Microsoft-specific instructions. The product reference is Dynamics 365 Finance 10.0.43, with Modern bank reconciliation enabled. Microsoft lists that feature as on by default in this release; confirm your environment’s actual feature state and configuration. Product details were checked against published documentation on October 26, 2026. This is documentation-based guidance, not a claim of hands-on testing. (learn.microsoft.com)

1. Establish the account, period and evidence before matching

Treat reconciliation as an explanation of differences, not a target number of cleared lines. Start with a control sheet that identifies:

Legal entity, bank account and currency.
Statement identifier and reporting period.
Reconciliation cutoff date.
Opening and closing statement balances.
ERP bank balance and relevant general ledger cash balance.
Preparer, reviewer and unresolved items from the previous period.

In Dynamics 365 Finance, the reconciliation cutoff determines which statement and company bank transactions appear on the worksheet. Check it explicitly rather than accepting the default system date. (learn.microsoft.com)

For this workflow, retain the original bank file, an accessible statement copy, import results and the prior reconciliation. Use authorized access and test changed import mappings or matching rules in a sandbox before production use.

Keep two checks separate: whether statement activity agrees to ERP bank transactions, and whether the ERP bank balance agrees to the relevant ledger cash accounts. Record the reports, filters and dates used for each check. A reviewer should not have to reconstruct your reporting population.

2. Validate statement completeness and catch duplicate imports

For Dynamics 365 Finance, Microsoft documents Electronic reporting configurations for BAI2, MT940 and ISO 20022 CAMT.053. The bank account’s selected statement format must correspond to the incoming file. (learn.microsoft.com)

Once an authorized administrator has configured the format:

Go to Cash and bank management > Bank statement reconciliation > Bank statements.
Select Import statement.
Confirm the bank account and statement format.
Upload the bank file and review the import result. (learn.microsoft.com)

Finance validates account and currency, opening-balance continuity, overlapping statement dates, line dates within the statement period, and whether opening balance plus statement movements equals ending balance. Modern bank reconciliation provides separate Validate and Confirm actions. (learn.microsoft.com)

Add a practical completeness check: compare the imported movement totals and transaction count, where available, with the bank’s source output. Record unexplained gaps before proceeding.

Microsoft’s duplicate-statement check uses the combination of AccountNo, StatementID, FromDate and ToDate. Do not treat this as proof that repeated economic activity cannot appear under different identifiers. Before retrying an import, check whether the statement already exists. Do not rename identifiers simply to bypass rejection. (learn.microsoft.com)

Expected result: a traceable statement whose account, period, balances and imported activity have been checked—not merely a successful upload message.

3. Use restrictive matching rules and stop ambiguous matches

Microsoft documents that matching rules select the first bank transaction meeting their criteria by default. Multiple plausible candidates therefore need explicit attention. (learn.microsoft.com)

For this workflow, use the strongest available evidence in this order:

Check	Recommended matching approach
Account and currency	Confirm the correct reconciliation population first
Amount and direction	Distinguish receipts from payments; investigate differences
Payment or document reference	Compare meaningful identifiers, not just description text
Date	Apply a justified settlement window
Transaction type	Distinguish transfers, checks, fees and other activity
Grouped settlements	Obtain a batch or settlement breakdown before grouping

Finance’s cash and bank management validation parameters override matching-rule selections. Allowed date differences and transaction-type mapping can therefore restrict both manual and automatic matching. Check these settings before assuming a rule has failed. (learn.microsoft.com)

Enable the parameter at:

Cash and bank management > Setup > Cash and bank management parameters > Bank reconciliation > Require manual matching when advanced bank reconciliation matching rules find multiple documents that match on amount. (learn.microsoft.com)

Rule sets execute in sequence. Put narrowly defined rules before broader ones, and test repeated amounts, missing references, reversals and grouped receipts—not only straightforward matches. Keep posting rules out of initial automation until their accounting consequences have been reviewed. (learn.microsoft.com)

Common mistake: expanding date or amount tolerances until an exception disappears. Instead, identify which evidence is missing and route the item for investigation.

4. Work through a deposit in transit, fee and ambiguous receipt

The following example is entirely synthetic. Amounts are in USD, with no foreign-currency differences, tax effects or other reconciling items.

At September 30:

Bank statement closing balance: $48,220.
ERP book cash balance before correction: $50,250.
A $2,000 deposit recorded on September 30 appears on the bank’s October 2 statement.
A $30 bank fee appears on the September statement but is absent from the books.
A $750 bank receipt has two possible ERP receipt candidates of $750 each.

Use the example as an investigation worksheet:

Item	Evidence and action	September treatment
$2,000 deposit	Retain deposit support and trace to the October 2 statement	Carry as a supported deposit in transit; do not post it again
$30 fee	Confirm the charge, check for an existing posting and obtain approval	Illustrative entry: debit bank-fee expense $30; credit bank cash $30
$750 receipt	Inspect bank reference and remittance details to identify the actual receipt	Match only the supported candidate; investigate the other separately

The adjusted-balance calculation is:

Bank statement closing balance          $48,220
Add: supported deposit in transit         2,000
Adjusted bank balance                   $50,220

ERP book cash before correction          $50,250
Less: previously unrecorded bank fee         30
Adjusted book cash                       $50,220

Assume subsequent evidence shows that the bank’s $750 reference belongs to receipt R-104, while receipt R-109 was already cleared on another statement line. Check that earlier clearing, then match R-104. Do not choose the first candidate merely because the amount agrees.

If that identifying evidence were unavailable, the $750 match would remain unresolved—even though the adjusted balances agree. This example deliberately separates balance agreement from transaction-level support.

5. Resolve exceptions according to their cause

Use a short exception log with the statement line or ERP transaction ID, amount, cause, evidence, owner, next action and review date.

Recommended treatment:

Timing difference: retain support and trace subsequent clearing. Do not repost an existing cash transaction.
Missing book entry: establish the business reason, check for an existing posting and obtain approval before recording it.
Duplicate import: investigate statement and transaction identifiers before removing or reversing anything.
Ambiguous match: obtain a reference, remittance or batch breakdown.
Unexplained difference: keep it open and escalate; do not label it a fee without evidence.

For documented nonpayment activity such as bank fees or interest, Modern bank reconciliation supports Generate voucher from the worksheet. Prerequisites include enabled Modern bank reconciliation, bank transaction types, a bank statement reversal reference number sequence and an imported statement. Review the accounting date, offset account, description and applicable dimensions before posting. (learn.microsoft.com)

Distinguish two reversal situations. Microsoft provides functionality to clear an original bank statement line against its bank reversal, and separate functionality for reversed company transactions without corresponding bank activity. Opposite amounts alone should not be your evidence that unrelated entries belong together. (learn.microsoft.com)

If a posting or match was wrong, use the supported correction process. Microsoft documents reconciliation and voucher reversal options for Modern bank reconciliation; assess the dependencies and test the applicable procedure rather than assuming every completed reconciliation is permanently irreversible. (learn.microsoft.com)

6. Review automation before allowing it to post

Dynamics 365 Finance’s Reconcile after import option can validate a statement, create a reconciliation worksheet and run the default matching rule set. Matching-rule actions can also generate payments or vouchers, depending on the enabled functionality and setup. Review the whole rule set before activating unattended processing. (learn.microsoft.com)

Recommended release checks include:

A repeated amount with different references does not clear incorrectly.
Missing references reach a review queue.
A bank fee rule selects only supported fee transactions.
A changed bank description does not trigger an unrelated posting.
Duplicate-file retries do not create unnoticed activity.
Rule changes have documented approval and a recovery plan.

Do not assume that a payment created from reconciliation follows your usual journal approval route. Microsoft states that cash application in advanced bank reconciliation supports only journal names without approval workflow. Have the control owner assess access restrictions, review evidence and monitoring before using that route. (learn.microsoft.com)

For this 10.0.43 baseline, do not assume a newer matching-preview screen exists. The 10.0.46 release notes identify automatic matching-results preview as a private-preview capability for nonproduction environments; availability requires separate verification. (learn.microsoft.com)

7. Give the reviewer an evidence pack, not just a cleared status

Use the following recommended close checklist:

Population: correct account, currency, statement period and cutoff.
Completeness: original file retained; balances and activity checked.
Matches: references support ambiguous or grouped selections.
Postings: fees and corrections have explanations, approvals and voucher IDs.
Outstanding items: every item has an owner, age, support and next action.
Balances: adjusted bank and book balances agree; relevant ledger balances are checked.
Review: reviewer records conclusions and challenges unsupported carryforwards.

For each timing item, record when subsequent clearing was checked. For each correction, retain its source evidence and posting reference. If evidence remains unavailable, record that limitation plainly rather than treating system acceptance as approval.

The closing test is simple: Can another accountant explain every remaining difference and reproduce the reconciliation from the retained evidence? If not, keep the exception visible and investigate further.