Applying payments by hand is the most visible routine in any finance team. Business Central handles it with two tools — and confusing them is the costliest mistake.
Short answer. Business Central has two distinct mechanisms for working with bank statements, solving different problems. The Payment Reconciliation Journal applies payments to documents: it identifies which invoice was paid and closes the balance. Bank Account Reconciliation compares the bank account balance in the system with the balance at the bank. The first is daily work, the second is a period-end control.
| Payment Reconciliation Journal | Bank Account Reconciliation | |
|---|---|---|
| Question answered | who paid and for what | does our balance match the bank |
| Effect on documents | applies the payment and closes the balance | marks bank entries as reconciled |
| Frequency | daily or weekly | at month end |
| Who runs it | accounts staff | chief accountant / controller |
Both accept the same statement file. The complaint "we imported the statement but the invoices are still open" almost always means the file went into the wrong journal.
Out of the box Business Central expects the European standard for bank files — the CAMT family of ISO 20022. Many banks outside that ecosystem, including Ukrainian ones, export their own formats: CSV with a proprietary column set, non-standard XML, sometimes legacy binary formats. There is no direct import.
Three ways out, in ascending order of reliability:
In practice the second option covers most companies: one exchange definition per bank, configured during implementation.
-->Once the statement is imported you run the automatic matching action. The system compares every statement line with open documents and proposes a match, scoring its confidence from high down to none.
What it looks at:
INV-2026-00147 is recognised, "payment as per contract" is not.High-confidence lines can be accepted in bulk; the rest are handled manually. The real driver of automation here is not the software but discipline in payment references — when customers quote invoice numbers, most receipts apply themselves.
The cheapest improvement available: put the invoice number where the customer sees it first on the printed document, and ask them to quote it in the payment reference. It beats any customization on return per hour spent.
Bank charges, card acquiring fees, interest on balances — statement lines with no invoice attached. Posting them by hand every month makes no sense.
That is what Text-to-Account Mapping is for: you define a fragment of the payment text and the account it should post to. Next time, "monthly account servicing fee" lands on your bank charges account automatically.
One hygiene rule: keep the mapping list short and review it quarterly. A text fragment that is too generic will start capturing the wrong payments.
Recent Business Central versions include a Copilot reconciliation assistant: it proposes matches for lines that did not match automatically and explains why it considers them similar. It runs as a second pass after standard matching — a human still decides.
Our assessment is measured: the assistant removes real drudgery on repetitive payments and helps very little where payment references are filled in carelessly. It amplifies order in your data rather than replacing it.
If you want to size what this automation is worth in your case, run the numbers in our cost calculator or get in touch.
Leave your details and we'll send the details of a free process audit. We reply within one business day.
or write directly: nbcs365@zohomail.eu · +380 98 107 5878