Key takeaways
- Bank reconciliation matches every payment received or sent to the invoice and entry it settles; done by hand, it is slow and error-prone.
- Three levers automate it in Belgium: structured communication, the CODA file, and open banking.
- Structured communication is a twelve-digit reference whose last two digits form a modulo 97 check key, which makes automatic matching reliable.
- Software connected to your bank reconciles payments continuously and leaves you only the real exceptions to handle.
Bank reconciliation, from statement to invoice
Bank reconciliation means matching every movement on your account to the invoices and entries it settles. In concrete terms: a transfer arrives, and you need to know which invoice it pays, or why it matches nothing you expected. Until that link is made, an invoice can stay marked unpaid even though it has been settled, and your cash position stays approximate.
The stake is not cosmetic. Up-to-date bookkeeping drives your follow-up on unpaid invoices, your reminders, your VAT return and, in an audit, the justification of every entry. The more your invoice volume grows, the more manual reconciliation becomes a bottleneck.
This article explains what bank reconciliation covers, why doing it by hand is costly, and which Belgian mechanisms let you automate it almost entirely.
Why manual reconciliation is costly
Reconciling by hand means opening the statement, reading each line and finding the matching invoice from a label that is often vague. When the customer wrote "June invoice" or only their name, you have to guess. When they settle two invoices in a single transfer, or pay only part of one, you split the amount by hand.
Every untreated exception is paid for later: a reminder sent to a customer who has already paid, an unpaid invoice that slips through, a VAT figure calculated on incomplete data. These are not spectacular mistakes, but they accumulate and end up distorting your view of cash.
Manual reconciliation never really disappears: it gets pushed to month-end, when the volume makes the task even more painful. Automating it means handling the flow as it comes rather than in bursts.
The three levers of automatic reconciliation
In Belgium, three mechanisms combine to automate matching. None is proprietary: they are market standards that any serious software uses.
What makes reconciliation automatic
Structured communication
A standardised payment reference that links a transfer unambiguously to the invoice it pays.
The CODA file
The standard electronic bank statement of Belgian banks, readable directly by accounting software.
Open banking
Secure access to your accounts, framed by the European payment services directive, through aggregators such as Ponto or Powens.
digits
the length of a structured communication
check modulo
the key that catches entry errors
Belgian standard statement
format maintained by Febelfin
Structured communication, the key to automatic matching
Structured communication is the simplest lever to put in place, because it happens when the invoice is issued. It is a Belgian twelve-digit reference, shown between symbols as +++XXX/XXXX/XXXXX+++. Its last two digits are not arbitrary: they form a check key calculated as the remainder of the first ten digits divided by 97. This mechanism, framed by Febelfin, immediately catches a mistyped reference.
The effect is direct. When your invoice carries a structured communication and the customer copies it into their transfer, the software links the payment to the invoice without interpreting any free text. There is no "June invoice" to guess: the reference is unique and verifiable. The condition is still that the customer enters it correctly, which is exactly what the check key helps to guarantee.
The second pillar is the CODA file, the standardised electronic bank statement of Belgian banks. Where a PDF statement has to be read by a human, the CODA codes each operation in a structured way, so software imports and posts it automatically. Structured communication and CODA reinforce each other: one carries the reference, the other transports it in a machine-readable form.
| Manual reconciliation | Automatic reconciliation | |
|---|---|---|
| Reading the statement | Line by line | Imported (CODA / open banking) |
| Identifying the invoice | From a free-text label | By structured communication |
| Partial or grouped payments | Split by hand | Proposed by the software |
| Work left to do | Every line | Only the exceptions to arbitrate |
Setting up automatic reconciliation
Moving to automatic reconciliation does not require rebuilding your accounting. The approach comes down to a few steps, from invoice settings to the bank connection.
- 1
Enable structured communication
Step 1Configure your software to generate a structured communication on every invoice issued.
- 2
Connect the bank account
Step 2Link your account through a CODA feed or an open-banking aggregator, so movements flow in automatically.
- 3
Let the software propose matches
Step 3Payments carrying a reference match themselves; the rest are proposed for validation.
- 4
Arbitrate the exceptions
OngoingYou only handle the ambiguous cases left: partial payments, grouped transfers, movements with no invoice.
Match your payments without re-keying
YouInv generates invoices with structured communication, connects to your bank and reconciles your payments automatically.
What it changes for your bookkeeping
Automated reconciliation does not remove the accountant: it takes them out of the mechanical sorting. The time spent reading statements and guessing labels shifts to checking exceptions and chasing unpaid invoices, where judgement actually counts. Cash becomes legible in real time, because payments are reconciled day by day rather than at month-end.
It is also a foundation for what comes next. As invoicing becomes more structured, notably with the arrival of B2B e-invoicing, having payments correctly referenced and reconciled makes every later step simpler. The first concrete habit to adopt: put a structured communication on every invoice, and connect the account that collects them.
Further reading
- Automating SME accounting: the accounting tasks that benefit most from automation.
- Mandatory invoice details in Belgium: what a compliant invoice must contain.
- Peppol in Belgium: the B2B mandate on 1 January 2026: the context of structured e-invoicing.
For the statement format, the reference is the Febelfin CODA documentation.
What is bank reconciliation?
Bank reconciliation means matching every movement on your account to the invoices and entries it settles. It confirms that incoming and outgoing payments line up with your bookkeeping, and flags what is left to handle: unpaid invoices, partial amounts, or transactions with no supporting document.
What is the difference between bank reconciliation and payment matching?
Bank reconciliation compares the bank's statement to the financial account in your bookkeeping, to confirm the two agree. Payment matching links a specific payment to the invoice or invoices it pays. They are complementary: you reconcile the statement first, then match each payment to the right invoice.
How do you automate bank reconciliation in Belgium?
Three levers make it automatic in Belgium: the structured communication, which carries a unique reference linking a payment to its invoice; the CODA file, the standard electronic statement format of Belgian banks; and open banking, which lets software read your movements continuously. Combined, they match most payments without manual entry.
What is structured communication used for?
Structured communication is a Belgian twelve-digit payment reference, shown as +++XXX/XXXX/XXXXX+++. Its last two digits are a check key calculated modulo 97. When the customer copies it exactly, the software links the payment to the matching invoice automatically, with no free-text interpretation.
What is a CODA file?
The CODA (Coded statement of account) is the standardised electronic bank statement format of Belgian banks, maintained by Febelfin. It codes each account movement in a structured way, so accounting software can recognise and post it automatically, without re-keying the paper statement.




