Banking & reconciliation

Ticking off payments by hand is the most thankless task of the month, and the one that produces the most dunning mistakes. This module does it for you, and leaves you to arbitrate what remains.

What comes in

• CODA , the Belgian banking format.
• CAMT.053 , the ISO 20022 statement.
• Manual entry for whatever fits neither.

Matching, in cascade

Each entry is compared with open invoices, in an order that runs from certain to likely:

1. Structured communication — the +++…+++ the invoice carried. No ambiguity possible.
2. Invoice number and amount — when the customer typed the reference in the description.
3. Sender IBAN — you know where the money came from, you look for what they owe.
4. Amount alone — proposed, never applied silently.

What is matched updates the invoice and publishes the fact to the rest of the software: receivables, aged balance and dunning follow on their own.

What it changes

A payment received on Tuesday is no longer a reminder sent on Thursday. It is the most visible flaw of a small company seen from outside, and it almost always comes from late reconciliation rather than bad faith.

What is coming

Direct bank connectivity (PSD2) is prepared but deliberately deferred : it adds a dependency on an aggregator, a consent renewal every ninety days, and a cost per account. Statement import has none of those three flaws.