Bank Reconciliation in Business Central: The Five-Minute Setup

If your finance team is still spending more than ten minutes on bank reconciliation in Business Central every month-end, this guide will show you exactly why that happens and how to fix it in under thirty minutes. Most of the wait is a configuration issue, not the software — and every step here takes under two minutes once you know where to look.

What holds most teams back

The most common blocker is the bank account card. When the Bank Account Posting Group is missing or points to the wrong G/L account, Business Central cannot auto-match incoming transactions. Finance teams end up matching manually, which turns a two-minute job into a two-hour one. See our guide to Business Central posting groups for the full picture.

A second blocker is the payment tolerance setting. If your tolerance is set to zero, Business Central will refuse to close invoices that are a few pence off because of currency rounding — so they sit unmatched on the reconciliation until someone manually adjusts them. Microsoft's official documentation on bank account setup covers the tolerance fields in detail.

Key InsightBusiness Central handles this automatically once configured correctly — no manual steps required.

The third blocker, and the one nobody talks about, is the bank statement import format. Business Central supports OFX, CSV and CAMT, but the default column mapping rarely matches what UK banks export. A five-minute mapping setup at the start saves hours every month. Our Business Central bank setup walkthrough has the import format settings step by step.

How to configure automatic matching

Go to Bank Accounts, open the account you want to configure, and check that the Bank Account Posting Group is set. This links the reconciliation to your cash G/L account. Without it, Business Central has nowhere to post the matched entries.

Next, go to Payment Application Rules. These rules tell Business Central how confident it needs to be before it auto-applies a payment. Set the Document No. Matched and Amount Matched thresholds to 100 for fully automatic matching, or 60 if you want the engine to propose matches that you confirm.

Pro TipSave time by setting up default values at the posting group level rather than editing each transaction.

Finally, import a test bank statement. Go to Bank Acc. Reconciliation, choose Import Bank Statement, and select a recent file from your bank. If the columns map correctly, you will see transactions appear in the right-hand pane immediately.

What to do when matches do not appear

If transactions appear but do not match, the most likely cause is a date offset. UK banks often export statement dates in DD/MM/YYYY format, while Business Central defaults to the regional setting on the server. Check your company settings under Company Information > Regional Settings.

If the amounts match but the document numbers do not, check whether your customers are including the correct invoice reference on their bank transfers. Business Central matches on the payment reference first, then falls back to amount and date.

Key PointThe key difference between these two approaches is how they handle multi-currency transactions.

Clearing Unmatched Transactions

For transactions that genuinely cannot be matched automatically — bank charges, interest payments, FX gains — use the Transfer to G/L Account function to post them directly and clear the reconciliation line. This keeps your reconciliation clean without leaving open entries on the bank account. See our guide on Business Central chart of accounts setup for how to structure these G/L codes.

Checking your results

Once you have matched all transactions, run the Bank Account Statement report before posting. This shows the opening balance, all matched entries, and the closing balance — it should match your bank statement exactly. If it does not, look for a missed transaction or a manually entered bank entry that duplicates an imported one.

Post the reconciliation and the matched entries move to the G/L. Your bank account balance in Business Central now matches the bank statement balance. The whole process — from import to post — should take under five minutes once your matching rules are in place.

By the NumbersFinance teams that automate this step report saving an average of three to four hours per month-end close.

Multi-entity and currency setups

For teams running multiple entities or currencies, make sure each bank account is configured with its own posting group and the currency code matches what your bank exports. Mismatched currencies are the single biggest cause of failed matches in multi-entity setups.

If you are running a Business Central health check, reconciliation setup is one of the first areas to review. You can also find guidance on month-end close in the Microsoft Business Central community forum.