7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats

7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats

Quick Summary: Bank reconciliation is a critical internal control ensuring that cash recorded in the General Ledger accurately reflects cleared funds held at financial institutions. Dynamics 365 Finance provides two distinct reconciliation pathways: Standard Manual Bank Reconciliation (simple manual checkbox marking) and Advanced Bank Reconciliation (ABR). ABR automates high-volume treasury operations by importing electronic bank statements (ISO 20022 CAMT.053, SWIFT MT940, BAI2), parsing bank transaction codes, executing multi-tier Matching Rule Sets, automatically generating missing ledger entries (interest, bank fees), and maintaining detailed audit trails.

---

1. Manual Reconciliation vs. Advanced Bank Reconciliation (ABR)

Choosing the appropriate reconciliation methodology depends on transaction volume, file integration capabilities, and automation requirements.

+---------------------------------------------------------------------------------------------------+
|                         Manual Reconciliation vs. Advanced Bank Reconciliation                    |
+---------------------------------------------------------------------------------------------------+
|  Capability / Feature       | Standard Manual Reconciliation   | Advanced Bank Reconciliation (ABR) |
|  -------------------------- | -------------------------------- | ---------------------------------- |
|  **Activation Level**       | Default (per Bank Account)       | Enabled via Bank Account parameter |
|  **Electronic File Import** | No (Manual data entry)           | Yes (CAMT.053, MT940, BAI2)        |
|  **Automated Matching**     | None (User checks off lines)     | Multi-criteria Matching Rule Sets  |
|  **Tolerance Matching**     | Exact manual selection only      | Date & Amount tolerance thresholds |
|  **Auto-Post Bank Fees**    | Requires manual bank journal     | Auto-generated via Matching Rules  |
|  **Multi-Line Matching**    | Manual grouping                  | 1:1, 1:Many, Many:1, Many:Many      |
|  **Two-Way Unmatching**     | Unmark checkbox                  | Formal Unmatch / Statement Reversal|
+---------------------------------------------------------------------------------------------------+

Enabling Advanced Bank Reconciliation

To activate ABR on a bank account:

1. Navigate to Cash and bank management > Bank accounts > Bank accounts.
2. Open the bank account details form and expand the Reconciliation FastTab.
3. Set Advanced bank reconciliation to Yes.
4. (Optional) Set Import statements as pending to Yes to allow pre-validation before formal reconciliation.

[!CAUTION] Irreversible Operational Warning: Once transactions have been reconciled on a bank account using Advanced Bank Reconciliation, changing the Advanced bank reconciliation toggle back to No is blocked by the system if open or reconciled electronic statements exist.

2. Electronic Bank Statement Formats & Ingestion Pipeline

Advanced Bank Reconciliation ingests electronic statements through Electronic Reporting (ER) or the Data Management Framework (DMF).

+---------------------------------------------------------------------------------------------------------+
|                                Electronic Bank Statement Ingestion Pipeline                             |
+---------------------------------------------------------------------------------------------------------+
|  Inbound Statement File (Bank SFTP / Portal)                                                            |
|  ├── ISO 20022 CAMT.053 (XML) ──> Electronic Reporting Model: Bank Statement Mapping                    |
|  ├── SWIFT MT940 (Flat Text)  ──> DMF Data Package / ER Mapping Transform                               |
|  └── BAI2 (Formatted Text)    ──> BAI2 Composite Import Entity                                          |
+---------------------------------------------------------------------------------------------------------+
                                        |
                                        v
+---------------------------------------------------------------------------------------------------------+
|  Bank Statement Ingestion (`BankStmtTable` / `BankStmtLineTable`)                                       |
|  - Header: Statement Number, Date, Opening Balance, Ending Balance, Currency                            |
|  - Lines: Transaction Date, Bank Transaction Code, Amount, Payee/Payer, Reference/End-to-End ID        |
+---------------------------------------------------------------------------------------------------------+
                                        |
                                        v
+---------------------------------------------------------------------------------------------------------+
|  Bank Transaction Code Mapping (`Cash and bank management > Setup > Bank transaction codes`)            |
|  - External Code: `NTRF` (Credit Transfer) ──> D365 Bank Trans Type: `EFT_REC`                          |
|  - External Code: `NCHG` (Bank Charges)    ──> D365 Bank Trans Type: `BANK_FEE` (Auto-Post Main 618500) |
|  - External Code: `175`  (BAI2 Check Paid) ──> D365 Bank Trans Type: `CHECK_DISB`                       |
+---------------------------------------------------------------------------------------------------------+

Core Bank Statement Formats

1. ISO 20022 CAMT.053 (Bank-to-Customer Statement):
   • Industry-standard structured XML format providing granular transaction elements: <Amt>, <ValDt>, <BkTxCd>, <RmtInf> (Structured Remittance Information).
   • Optimal format for automated reconciliation due to strict schema standards and rich reference tags.
2. SWIFT MT940 (Customer Statement Message):
   • Standard structured text message widely used in European and global commercial banking.
   • Field :60F: (Opening Balance), Field :61: (Statement Line: value date, debit/credit mark, amount, transaction type), Field :86: (Information to Account Owner / payment references).
3. BAI2 (Bank Administration Institute Format):
   • Standard US format utilizing comma-delimited record types: Record 01 (Header), 02 (Group Header), 03 (Account Identifier), 16 (Transaction Detail with 3-digit type codes), 88 (Continuation), and 49/98/99 (Trailers).

Bank Transaction Codes Configuration

To map external statement codes to internal ERP transaction behavior:

1. Navigate to Cash and bank management > Setup > Advanced bank reconciliation setup > Bank transaction codes.
2. Click New and define the external bank code (e.g., NCHG or 475).
3. Map to an internal Bank transaction type (e.g., FEE).
4. Assign default General Ledger posting accounts and financial dimensions to allow automated voucher generation for unrecorded bank charges.

3. Enabling Advanced Bank Reconciliation per Bank Account

Advanced Bank Reconciliation is switched on per bank account, not globally. On the bank account, set Advanced bank reconciliation to Yes and assign the statement format the bank actually sends. From that point the account reconciles through the Bank statements / Reconciliation worksheet pages, and the classic manual Account reconciliation form is no longer the working surface for that account.

Exam trap: Turning on Advanced Bank Reconciliation part-way through a year does not migrate historical manual reconciliations. Prior periods stay reconciled under the old model, and the first advanced reconciliation must start from the correct opening bank balance.

4. The Three Supported Statement Formats

Each format is delivered as an Electronic Reporting import configuration. Importing a bank's file therefore requires the matching ER configuration to be imported and set as the statement format on the bank account. When a case study says the bank "sends an ISO 20022 file", the setup answer is an ER configuration plus a bank account statement format — not a customisation.

5. Bank Transaction Codes and Bank Transaction Types

The imported statement classifies every line with a bank transaction code issued by the bank (for example, a BAI2 type code for "ACH credit received"). Dynamics 365 Finance maps those codes to internal bank transaction types so that:

• matching rules can filter on transaction type rather than on raw bank codes;
• unmatched bank-side items such as interest, bank fees, and returned items can be turned into general ledger entries automatically, posting to the account configured for that transaction type.

An unmapped code is the usual reason a statement line refuses to match anything and cannot be auto-generated into a voucher.

6. Manual Reconciliation: When It Is Still Right

Manual reconciliation remains appropriate for low-volume accounts — a petty cash account, a rarely used foreign account, or an account at a bank that does not supply electronic statements. The clerk opens Cash and bank management > Bank accounts > Reconcile > Account reconciliation, enters the statement date and closing balance, ticks each cleared bank document, and the form reports the difference between the statement balance and the marked transactions. The reconciliation cannot be completed until that difference is zero.