# Business Central Bank Reconciliation, Step by Step

- Author: PreciseBankFlow (https://www.precisebankflow.com)
- Published: 2026-04-25
- Updated: 2026-04-25
- Category: Reconciling in accounting software
- Canonical: https://www.precisebankflow.com/blog/business-central-bank-reconciliation

> Business Central bank reconciliation step by step: statement lines, the matching proposal, posting differences and reconciliations that won't post.
A Business Central bank reconciliation runs on the Bank Acc. Reconciliation page. You enter the statement date and ending balance, fill the bank statement lines by importing the bank's file or with Suggest Lines, match them to bank account ledger entries, post any missing fees through a general journal, and post once no line shows a difference.

## Starting a Business Central bank reconciliation: statement date and ending balance

A Business Central bank reconciliation starts with a header: the bank account, the statement date and the statement ending balance. The statement date also works as a filter. Once you enter it, the page shows only ledger entries dated on or before it, so the reconciliation describes one cut-off and nothing later.

Microsoft's article [Reconcile bank accounts](https://learn.microsoft.com/en-us/dynamics365/business-central/bank-how-reconcile-bank-accounts-separately) describes the page and its two panes. The Bank Statement Lines pane on the left holds the bank's transactions. The Bank Account Ledger Entries pane on the right holds what your books recorded for that bank account. Reconciling means pairing lines across the two.

To create one:

1. Search for **Bank Account Reconciliation** and open the page.
2. Choose **New**.
3. In **Bank Account No.**, select the account. Its ledger entries appear in the right pane.
4. In **Statement Date**, enter the statement's closing date.
5. In **Statement Ending Balance**, enter the closing balance printed on the statement.

A third header field, **Balance Last Statement**, fills itself from the previous reconciliation for the same account. Microsoft notes it is zero on your first reconciliation. Check it against the opening balance on the bank statement before doing anything else. If they differ, an earlier month is wrong, and no amount of matching this month will fix it.

Enter the statement date before you match anything. Microsoft warns that if you enter a statement ending date after matching, Business Central undoes the matches for lines and entries dated after it. It also says the Test Report will be wrong if you match first and then enter a later ending date.

The North American versions add a wrinkle. They offer an older **Bank Rec. Worksheet** page, better suited to checks and deposits, which cannot import bank statement files. You switch between the two with the **Bank Recon. with Auto. Match** field on the General Ledger Setup page. Firms coming from Dynamics GP will recognise the older style; the [Dynamics GP electronic bank reconciliation guide](/blog/dynamics-gp-electronic-bank-reconciliation) covers how GP handled it.

## Should Business Central statement lines come from an import or Suggest Lines?

Import the bank's file whenever you have one. An import fills the left pane with the bank's own record, which is the independent evidence a reconciliation needs. Suggest Lines builds the left pane from Business Central's own entries with outstanding payments, which is quicker but compares the books with themselves.

Microsoft lists both routes. With **Import Bank Statement**, you pick the file and its transactions load into the Bank Statement Lines pane. The article says CSV files work once you define a format with the **Set up a bank statement file format** assisted setup and attach it to the bank account. A bank feed through the Envestnet Yodlee service is a third source, set up separately.

With **Suggest Lines**, you enter a starting and ending posting date, and Business Central proposes lines from entries in that range. An **Exclude Reversed Entries** toggle keeps reversed pairs out.

Suggest Lines has a place. It suits an account with a handful of checks each month, where you tick the statement against the list by hand. But it changes what the reconciliation proves. A reviewer looking at a reconciliation built from Suggest Lines must see the bank statement itself, because the left pane is not the bank's record. If you use it, attach the statement PDF to the work.

## Business Central matching: Match Automatically versus Match Manually

Matching pairs each bank statement line with one or more ledger entries. Match Automatically compares text and dates across the two panes and proposes pairs. Match Manually lets you select lines on both sides and link them yourself. Most months need both: automatic first, manual for what is left.

**Match Automatically** opens a small page asking for a **Transaction Date Tolerance (Days)**. Microsoft explains that this is the span of days before and after the ledger entry's posting date in which Business Central searches for a matching bank date. Zero or blank means same-day only. Matched lines turn bold green. Entries matched on other reconciliations show in italic blue. The **Match Details** action shows which fields produced each match.

**Match Manually** handles the rest. Select an unapplied statement line on the left, hold Ctrl and select one or more ledger entries on the right, then choose **Match Manually**. You can also match several statement lines to one ledger entry. Microsoft gives the example of a deposit the bank split into separate lines for each card issuer.

A tolerance of two or three days catches most timing gaps between posting and clearing. A wider window starts pairing the wrong items when the same amount repeats, such as weekly rent or payroll. Read the proposed pairs for repeating amounts before you accept them. Manual matches are safe from later automatic runs; Microsoft says automatic matching will not overwrite them.

Odoo takes a different approach, with reconciliation models that write off or create counterpart entries as part of matching. The [Odoo bank reconciliation guide](/blog/odoo-bank-reconciliation) compares those rules with this kind of pairing.

## Posting bank fees from Business Central with Transfer to General Journal

Some statement lines have nothing to match: bank fees, interest, a direct debit nobody entered. Business Central handles these with Transfer to General Journal, which turns unmatched statement lines into journal lines. You complete each line with a balancing account, post the journal, and then match the new ledger entries.

The steps from Microsoft's article:

1. On the Bank Acc. Reconciliation page, choose **Transfer to General Journal**.
2. Pick the general journal to use and choose **OK**. The General Journals page opens with a line for each statement line missing a ledger entry.
3. Fill in the balancing account on each line, for example a bank charges expense account for a monthly fee.
4. Run the journal's **Test Report** to check the result before posting.
5. Choose **Post**.
6. Refresh the reconciliation page. The new entries appear in the right pane.
7. Match each one to its statement line.

Use this only for items that truly belong in the books. A statement line you cannot explain is not a bank fee. Posting it to an expense account to clear the reconciliation turns a question into a cost, and nobody will ask about it again. That is the problem described in [plugging a bank reconciliation](/blog/plugging-a-bank-reconciliation): the reconciliation balances, and the error survives.

## Why won't a Business Central bank reconciliation post?

A Business Central bank reconciliation will not post while any statement line has a value in its Difference field. A difference means a statement line is not fully matched to ledger entries of the same total. The totals rule also applies: the statement lines must equal the Balance Last Statement plus the balance to reconcile.

Microsoft's article states it plainly: you cannot post a bank account reconciliation that has differences. It also lists the usual causes:

- **A ledger entry has no bank transaction.** Your books recorded a payment the bank never processed. Create the missing transaction or wait for it, then reimport.
- **A bank transaction has no ledger entry.** The bank charged something your books never recorded. Post it, for example through Transfer to General Journal.
- **The two sides disagree on details.** The amount or the name differs enough to block a match. Review, match manually, and correct the entry if needed.

### Offsetting differences still block posting

One rule surprises people. Microsoft notes that you cannot post if you match many-to-one and the combined amounts contain differences, even when those differences net to zero across lines.

A worked example with made-up figures:

| Statement line | Statement amount | Ledger entries matched | Ledger total | Difference |
| --- | --- | --- | --- | --- |
| Deposit 14 Sept | 1,640.00 | Two customer receipts | 1,600.00 | 40.00 |
| Deposit 21 Sept | 2,210.00 | Two customer receipts | 2,250.00 | -40.00 |
| Net across both lines | 3,850.00 | | 3,850.00 | 0.00 |

The month nets to zero, but each line has a difference, so posting is blocked. That is a feature. Each deposit pairs with the wrong receipts. Swap one receipt between the deposits, and both differences disappear. If no swap fixes it, Microsoft's advice is to post the differences and then match them against the posted entries.

Unmatched ledger entries are a separate case. A check written on September 29 that has not cleared can stay unmatched, and the reconciliation still posts. It shows as an outstanding check and carries to the next month.

## The Business Central Test Report as reviewer evidence

The Test Report previews the reconciliation before you post it, and it is the document a reviewer should see. It shows the statement balance, the outstanding checks and outstanding bank transactions, and the G/L account balance at the statement date. When those agree, the bank account, the bank ledger and the general ledger all tell one story.

Run it from the Bank Acc. Reconciliation page with the **Test Report** action. Microsoft describes its fields, and a few matter most:

- **Balance Last Statement** and **Statement Ending Balance**, the two ends of the period.
- **Outstanding Checks** and **Outstanding Bank Transactions**, the items in your books that the bank has not processed yet.
- **Sum of Differences**, which must be zero to post. Turn on **Print Outstanding Transactions** to see the detail.
- **G/L Account No. Balance at date**, the general ledger balance on the statement date.

That last field catches a quiet problem. Microsoft explains that a mismatch between the G/L balance and the bank account balance can mean someone posted directly to the G/L account, or that one G/L account serves several banks. The report shows a warning when direct postings exist. Microsoft's advice is to avoid a G/L account that allows direct posting in the bank account posting group, because those entries never reach the bank ledger and the reconciliation cannot see them. Opening balances posted straight to the general ledger are the usual cause.

File the Test Report, the bank statement and the posted Bank Account Statement together. Desktop accounting packages keep similar reports, and the [QuickBooks Desktop reconciliation guide](/blog/how-to-reconcile-in-quickbooks-desktop) shows how its summary and detail reports compare.

## Mistake: undoing a posted Business Central reconciliation without fixing the statement number

Business Central lets you undo a posted reconciliation from the Bank Account Statement List. The entries move back to an open reconciliation, unreconciled, so you can correct and repost. The mistake is reposting without checking the statement number and Balance Last Statement, which do not roll forward on their own.

Microsoft's example: March's statement was number 100, and it missed entries from the 31st. You open the Bank Account Statement List, choose March, and choose **Undo**. The new reconciliation gets number 101. To keep 100, use **Change Statement No.** and enter 100. Then set the statement date back to March 31 and check **Balance Last Statement**.

The harder case is undoing a month in the middle. Microsoft notes there is no feature that moves a corrected balance forward to all later statements. If you undo and repost February after March is done, the Bank Account card shows February's balance as the last statement. Before you create April's reconciliation, correct **Last Statement No.** and **Balance Last Statement** on the card, or change them on the new reconciliation.

North American users have one more condition. Undo works only with the **Bank Recon. with Auto-Match** toggle on, and it is not available for statements posted from the older bank reconciliation worksheets.

Keep a short log of every undo: the statement, the reason, who approved it and the corrected balance. For firms reviewing client reconciliations, PreciseBankFlow foots each statement and lists the lines that match the ledger and those that do not, so a reviewer can check the Test Report against the bank's figures. It is opening to firms in small groups; [see how it works](/).