Bank reconciliation in Business Central

Bank reconciliation is the routine financial task that benefits most from Business Central's recent investment in automation and AI. What used to be a half-day spreadsheet exercise is now mostly a click-through.

The model

Each bank account in BC is represented by a bank account card with its own ledger entries (the bank account ledger), currency, and posting setup. Reconciliations match BC's posted bank ledger entries against the bank's statement to confirm both sides agree, surface differences, and create journal entries for items only the bank knows about (fees, interest, direct debits).

Importing the statement

Three patterns are common:

• Live bank feeds via partner connectors (Envestnet | Yodlee in North America, regional bank-feed services in Europe and Australia/NZ) refresh transactions daily without manual import.
• MT940 / camt.053 files uploaded into BC, the standard formats most European banks support.
• CSV files with a configurable mapping for banks that don't provide structured exports.

Bank feeds and statement import covers the data-exchange framework behind all three in more depth, and the physical-deposit side that happens before any of this — counting the till, batching cheques — is bank deposits and cash management.

The Bank Account Reconciliation page

Imported statement lines appear alongside BC bank ledger entries. BC auto-matches by amount, document number, and date, marking matches as green. Unmatched lines are highlighted for manual review.

AI-assisted matching (Copilot)

The Copilot for Bank Reconciliation learns from prior reconciliations to suggest matches on lines that don't auto-match cleanly — payments where the customer reference is slightly off, batched payments covering multiple invoices, payments early or late, foreign currency conversions. The user accepts, modifies, or rejects each suggestion; the engine improves over time.

Posting transfer entries

Lines on the bank statement that don't have a counterpart in BC (bank fees, interest, direct debits, undeposited cheques) can be posted directly from the reconciliation as journal entries to user-defined GL accounts, eliminating a separate journal step.

Closing the reconciliation

Once the difference is zero, the reconciliation is posted, marking the matched bank ledger entries as closed and writing a posted bank reconciliation record for audit.

Bank reconciliation vs the payment reconciliation journal

BC ships two pages with confusingly similar names, and choosing the right one matters. The Bank Account Reconciliation page (this guide) confirms that posted BC entries agree with the bank — it's a control activity. The Payment Reconciliation Journal does something different: it takes the same imported statement and creates the application of customer and vendor payments — matching incoming payments to open invoices, applying them, and posting the lot. Businesses with high incoming-payment volume live in the payment reconciliation journal daily and run the bank reconciliation as the monthly check on top. Using the bank reconciliation page to discover unapplied customer payments means you're doing AR application a month late; using the payment journal as your only control means nobody has confirmed the bank ledger actually ties out. You want both, in that order — apply daily, reconcile monthly (or weekly).

Multi-currency accounts

A bank account in a foreign currency reconciles in that currency — statement lines and ledger entries both in EUR, say — while the GL carries the LCY equivalent. The reconciliation itself is unaffected, but month-end needs the separate currency revaluation step to restate the LCY balance at the closing rate; see foreign currency revaluation in BC. A reconciled account that still shows a GL difference is almost always an unrevalued FX balance, not a reconciliation error.

Common failure modes

• The stale first reconciliation. An account that has never been reconciled (or was migrated with a lump opening balance) presents years of noise on day one. Do a one-time cleanup reconciliation as part of go-live cutover rather than asking the first month-end to absorb it.
• Direct postings to the GL bank account. If journals post straight to the bank's G/L account instead of through the bank account card, the bank ledger and GL diverge and no amount of reconciling fixes it. Block direct posting on bank-linked G/L accounts.
• Deleting instead of investigating. Unmatched statement lines get deleted to force the difference to zero. The reconciliation posts, and the unexplained transaction resurfaces next month. Every line needs a match, a transfer posting, or a documented reason.
• Trusting Copilot suggestions blind. The AI matching is good at fuzzy references and batched payments, but it proposes — a human accepts. Treat a low-confidence suggestion on a large amount as a prompt to look, not a button to click.

Month-end

A reconciled bank account ledger is what ties bank account balances on the trial balance to actual bank statements. Reconciliation should be done at least monthly; in many businesses it's run daily — daily reconciliation catches fraud, bank errors, and mispostings while they're hours old rather than weeks. The posted reconciliation is also what your auditors will ask for, so the discipline pays for itself at year-end; it slots into the broader month-end close checklist.