WHAT WE SEE IN THE FIELD
The bank is connected. The accountant is still matching everything manually.
The transactions are already in Odoo.
Customer payments appear in the bank journal. Supplier payments are there. Bank charges are there.
And yet, every morning, someone still opens each line and decides manually where it belongs.
That is not necessarily a problem during the first days of an implementation.
But if the same transactions are being classified manually month after month, there is usually automation potential being left unused.
Bank reconciliation in Odoo should gradually become less about processing every transaction and more about reviewing the exceptions.
ODOO BANK RECONCILIATION IN PRACTICE
First, bring the bank transactions into Odoo
Odoo can import bank transactions through direct bank synchronization, file imports or manual entry. With bank synchronization, transactions are imported automatically from supported financial institutions. Odoo currently states support for more than 26,000 financial institutions worldwide through third party connectivity providers.
Once the transactions are available, Odoo's Bank Matching view is used to reconcile them with the accounting records.
Typical examples include:
- Customer payment → customer invoice
- Supplier payment → vendor bill
- Bank fee → bank charges account
- Internal transfer → another bank account
- Card settlement → outstanding receipts or payments
When possible, Odoo already applies standard matching logic to suggest the relevant accounting counterpart.
But that is only the starting point.
DEFAULT MATCHING ALREADY DOES PART OF THE WORK
Odoo does not start every transaction from zero
When reconciling a transaction, Odoo looks for existing accounting items that can match it.
For example, it can use information such as the partner, amount and transaction label to identify corresponding invoices, bills or payments. Exact matches are prioritised, and Odoo also supports scenarios such as early payment discounts.
This means a payment with a good reference and the correct amount may already appear with the expected invoice ready to reconcile.
But the quality of those suggestions depends heavily on the quality of the underlying data:
- Customer references matter.
- Payment references matter.
- Partner identification matters.
A good reconciliation process therefore starts earlier than the bank screen.
HOW WE WOULD CONFIGURE IT
Start with the transactions that repeat
The first question we normally ask is not: “How can we automate reconciliation?”
It is: “Which transactions are we reconciling repeatedly in exactly the same way?”
Typical candidates include:
- Monthly bank fees
- Payment provider commissions
- Recurring insurance payments
- Interest charges
- Regular subscriptions
- Cash discounts
- Specific customer or supplier payment flows
Those patterns are where Reconciliation Models become valuable.
RECONCILIATION MODELS
Teach Odoo what to do with predictable transactions
Reconciliation Models are configurable rules that extend Odoo's standard bank matching logic.
They can be configured as manual or automated:
- A manual model gives the accountant a predefined reconciliation action to apply.
- An automated model can be applied automatically when a bank transaction satisfies the configured matching conditions.
Imagine that every month the bank creates a transaction containing: BANK SERVICE FEE
Instead of manually selecting the same expense account twelve times per year, a reconciliation model can recognise the transaction pattern and assign the appropriate counterpart.
The same principle can be applied to many predictable flows - That is where bank reconciliation starts becoming scalable.
MATCHING CONDITIONS MATTER
Automation should be specific enough to be safe
The difficult part is not creating a reconciliation model, but deciding when the rule should be allowed to execute.
Odoo allows reconciliation models to use conditions such as journals, partners and amounts, together with information used to generate the accounting counterpart.
- A model that is too broad may classify the wrong transactions.
- A model that is too narrow may never trigger.
For example:
Every transaction containing “FEE” → Bank Charges
may be convenient.
It may also be unsafe if unrelated bank transactions contain the same text.
A better configuration could combine several conditions:
- Specific bank journal
- Transaction label contains a known reference
- Amount falls within an expected range
- Known partner, where relevant
Automation should reduce repetitive work without reducing accounting control.
THE SUSPENSE ACCOUNT
An imported bank transaction is not automatically fully accounted for
This is an important concept because it is often misunderstood.
When a bank transaction enters Odoo, it is linked to a journal entry involving the bank journal and a temporary suspense account until the transaction is fully reconciled.
The reconciliation process establishes the correct accounting counterpart.
For example: A €5,000 receipt appears in the bank.
Until Odoo knows that it corresponds to customer invoice INV/2026/0427, the accounting treatment is not complete.
Once matched, the reconciliation connects the bank movement with the relevant receivable item.
This is why simply seeing transactions in the bank journal does not mean the accounting process is finished.
PARTIAL PAYMENTS ARE NOT EXCEPTIONS TO THE SYSTEM
€4,800 received against a €5,000 invoice
Real bank transactions are not always clean one-to-one matches.
- A customer might pay only part of an invoice.
- Several invoices may be paid together.
- A payment may include a discount.
- There may be a small remaining balance that requires further investigation.
Odoo allows bank transactions to be matched against existing journal items and, where the amount does not fully settle the item, the remaining balance can stay open.
This is important because reconciliation automation should never assume that every difference is an error.
Sometimes it reflects the actual commercial situation.
BANK SYNCHRONISATION DOES NOT MEAN RECONCILIATION
Importing the transaction and understanding the transaction are two different things
This distinction is essential:
- Bank synchronization answers: What happened in the bank?
- Reconciliation answers: What does this transaction represent in the accounts?
Odoo can automatically import bank transactions from supported institutions.
But importing a €2,300 payment does not automatically tell the system whether that money relates to:
- a customer invoice,
- a loan,
- a capital injection,
- an internal transfer,
- or another accounting event.
Matching rules and reconciliation models provide that second layer.
THE MOST COMMON MISTAKES
Trying to automate everything immediately
When an accounting team sees reconciliation models for the first time, the temptation is often to create a rule for every recurring transaction.
We would usually do the opposite.
- Start with high volume, low ambiguity transactions.
- Observe the results.
- Then expand.
For example, automating a highly recognisable monthly bank fee is low risk.
Automatically classifying incoming payments from customers with inconsistent references may require considerably more caution.
Automation should follow confidence in the transaction pattern.
Not enthusiasm for the feature.
Ignoring the quality of payment references
Good reconciliation often depends on information created before money reaches the bank.
If invoices have clear payment references and customers use them when paying, Odoo has much better information available for matching.
If every bank line arrives as TRANSFER the accounting team is left with very little to work with.
This is why improving bank reconciliation sometimes requires reviewing the invoicing and payment process as well.
Accounting automation rarely exists in isolation.
WHAT GOOD RECONCILIATION LOOKS LIKE
Humans should focus on the transactions that require judgement
The objective is not necessarily 100% automatic reconciliation - that can be the wrong target.
A better target is something like:
- Predictable transactions are handled automatically
- Clear matches are suggested immediately
- Recurring accounting treatments require minimal input
- Ambiguous transactions remain visible for review
Then the accountant spends time investigating unusual transactions instead of processing the same predictable movements every day.
That is a more useful form of automation.
OXALYO'S TAKE
A good reconciliation process becomes quieter over time
At the beginning of an Odoo Accounting implementation, many bank transactions may require manual review.
That is useful.
It allows the accounting team to understand how real banking flows appear inside the system, but recurring patterns should then be identified and translated into matching logic and reconciliation models.
If the accounting team is still manually processing the same bank charge, subscription or predictable payment six months later, the system has learned nothing from the process.
Odoo provides the tools to automate a significant part of that repetitive work.
The implementation work is deciding which transactions are predictable enough to automate, what conditions make the rule safe and which exceptions still deserve human judgement.
That is where configuration becomes accounting design.
FAQ: ODOO BANK RECONCILIATION
What is bank reconciliation in Odoo?
Bank reconciliation is the process of matching imported bank transactions with the corresponding accounting records, such as customer invoices, vendor bills and payments, or assigning another appropriate accounting counterpart.
Can Odoo automatically reconcile bank transactions?
Odoo automatically applies matching logic where possible, and Reconciliation Models can provide additional automated rules for transactions that meet defined conditions.
What is a Reconciliation Model in Odoo?
A Reconciliation Model is a configurable rule used to handle recurring or identifiable bank transactions. Models can be manual or automated depending on how the accountant wants the transaction to be processed.
Does Odoo support direct bank synchronization?
Yes. Odoo Enterprise supports bank synchronization with supported financial institutions through third party connectivity providers. Odoo states that the service covers more than 26,000 financial institutions worldwide.
What happens if the bank payment does not match the invoice amount?
Odoo can reconcile a transaction with an existing accounting item even when the values are not identical. Depending on the situation, the remaining amount can stay open or another accounting counterpart can be added.
Is bank synchronization the same as reconciliation?
No. Bank synchronization imports transactions from the financial institution. Reconciliation determines which accounting records or accounts those transactions correspond to.
Is your accounting team still reconciling the same transactions every month?
If your bank transactions are already in Odoo but reconciliation remains heavily manual, the issue may not be the accounting workload.
It may be how the reconciliation process is configured.
Talk to us about your Odoo Accounting setup.