Bank reconciliation is the part of an Odoo accounting implementation that quietly decides whether the finance team trusts the system. Get it right and the month-end close runs in days. Get it wrong and you're chasing unmatched transactions for weeks, your BAS won't tie back to the bank statement, and someone ends up reconciling by hand in a spreadsheet anyway. Australian businesses have a few specific moving parts here, ABA batch payments, GST cash versus accruals reporting, and the quirks of how Australian banks publish statement data, so the setup needs more attention than the standard Odoo accounting guide suggests.
This post covers how Odoo bank reconciliation actually works in v19, the realistic options for connecting to Australian banks, how to reconcile ABA batches without manual line-by-line matching, and where most implementations go wrong. It's written for finance managers, controllers, and business owners deciding whether to commit Odoo as the source of truth for the bank.
How Odoo bank reconciliation actually works
Odoo reconciles bank statements against three things: vendor and customer payments that already exist in the system, open invoices and bills that haven't been matched to a payment yet, and direct journal entries you create on the fly (interest, fees, transfers). The reconciliation view groups these together and lets you match each statement line to one or more counterparts. When a match locks in, Odoo posts the bank journal entry and closes the statement line.
The mechanics are the same whether you're running Community or Enterprise. What Enterprise adds is automatic bank synchronisation, the BAS report, and the reconciliation models that learn from your matches over time. Per Odoo's v19 bank synchronisation documentation, the automatic sync service is only available with a valid Enterprise subscription. Community users can still reconcile, they just have to import files manually.
Bank statement feeds for Australian banks
You have three options for getting statement data into Odoo, and the right choice depends on which bank you use, how often you reconcile, and what's actually supported.
Automatic bank synchronisation
Odoo connects to Australian banks through third-party aggregators, primarily Yodlee and Salt Edge depending on the bank, with coverage of over 26,000 financial institutions worldwide. In practice for Australian businesses, the big four (CBA, Westpac, ANZ, NAB) and most of the mid-tier banks (Bendigo, BOQ, Macquarie, Suncorp) are supported through one or the other. Before you commit to automatic sync as the production approach, log into Odoo's Accounting Features panel, click "See list of supported institutions," and verify your specific bank and account type appear. We've seen edge cases with business savings accounts and certain merchant-facilitated accounts where the feed is read-only or unavailable.
Once connected, statements pull in daily. The catch is the connection occasionally drops and requires re-authentication, which finance teams forget to monitor. Build a weekly "is the sync healthy?" check into the close process, otherwise you'll discover a missing fortnight at month-end.
Manual file import (CSV, OFX, CAMT.053)
Per the v19 bank transactions documentation, Odoo accepts CAMT.053 (the SEPA cash management format), OFX, QIF, and CSV file imports. For Australian banks, OFX is the most reliable manual format because every major bank exports it directly from their business banking portal. CAMT.053 is rare outside European multinational subsidiaries operating here. CSV works but you have to map the columns yourself the first time, and Australian bank CSVs put the date, description, and amount in different places depending on the bank.
The opening balance trap catches new implementations frequently. Odoo expects the first statement line to start from a known opening balance. If you start importing statements halfway through a financial year without entering the opening balance correctly, the running balance in Odoo will never agree with the bank, even if every individual line reconciles.
Manual entry (when you'd use it)
For low-volume accounts (a petty cash float, a foreign currency holding account that sees three transactions a quarter), manual entry into a bank journal is fine. We don't recommend it as the default for an operating account. The risk of typos and missed lines outweighs the cost of either the sync subscription or the five minutes it takes to import an OFX file.
Matching rules and how Odoo learns
Odoo's reconciliation engine uses what it calls "reconciliation models," which are essentially rules that auto-match common statement lines without human intervention. The default models handle exact-amount matches against open invoices and bills. Custom models let you handle the lines that repeat every month: bank fees, interest, EFTPOS settlement fees, FX margin charges, BAS refunds, and ATO PAYG payments.
A model that books a $15 monthly bank fee directly to "Bank Fees" expense as soon as it appears will save a finance team an hour a month. Set up six or seven of these in the first week of the implementation. After that, Odoo's machine-matching also learns from manual choices and will start suggesting the right account for recurring lines automatically.
Reconciling ABA batch payments
ABA (Australian Bankers' Association) files are how Australian businesses pay multiple suppliers in a single bank transaction. The bank's statement shows one consolidated debit, but the underlying payments inside Odoo are individual vendor bill payments. This is the moment most accounting platforms fall apart in Australia, and Odoo handles it correctly if configured properly.
Per the Odoo v19 Australia fiscal localisation documentation, you enable batch payments in Accounting > Configuration > Settings, then configure each bank journal with the BSB code, Financial Institution Code (the 3-letter abbreviation your bank uses), and your Supplying User Number (the 6-digit identifier the bank issues). Once that's in place, the workflow is: register vendor bill payments using "ABA Credit Transfer" as the payment method, tick the bills to include, click Create Batch, then Verify and Validate. Odoo generates the ABA file and attaches it to the batch.
You upload the file to your bank's business banking portal. The next time the bank statement syncs or imports, the statement line shows a single debit for the batch total. In the reconciliation view, you select the Batch Payment tab and match the statement line to the batch in one click. No line-by-line matching, no manual journal entries, just one match.
Our guide to Odoo accounts payable and ABA payments covers the upstream side of this workflow in more detail, including the three-way matching that should happen before any payment ever gets to a batch.
Multi-currency and FX revaluation
If you hold a USD or EUR bank account (importers and exporters often do), Odoo records each transaction at the daily rate and revalues the balance to AUD at period end. The revaluation creates an unrealised FX gain or loss journal entry. This is correct accounting, but it adds one more reconciliation step: the bank balance in AUD shifts at month-end based on the closing exchange rate, and the unrealised entry has to reverse on day one of the next period.
Two settings to check before you go live. First, the bank account currency must be set at the journal level (not just on the company). Second, the exchange rate source needs to be either the RBA daily rate or a manual override that matches whatever the auditors expect. If those don't match, the FX position on the balance sheet will be a few hundred dollars off every month, which finance teams find harder to ignore the longer it persists.
"The biggest reconciliation problem we fix on inherited implementations isn't matching, it's the opening balance. People start importing statements without setting a clean opening figure, and from that point forward the bank balance in Odoo drifts a few hundred dollars off the actual bank. Two months in, no one trusts the system. Fix the opening balance, set up four or five reconciliation models for recurring lines, and the close goes from days to hours."
Josh Craig, Director, Auboros
Where bank reconciliation goes wrong
Three patterns account for most of the implementation problems we see, and all three are avoidable.
Reconciling too infrequently. Some teams batch the whole month into the last week. By the time you're matching a transaction from 28 days ago, the context is gone and matching becomes guesswork. Reconcile weekly at minimum, daily if you're doing meaningful volume. The MYOB 2025 ERP Trends report found 45% of Australian decision-makers say disconnected systems limit their ability to grow, and stale bank reconciliation is one of the practical ways that surfaces.
Treating the bank as the source of truth for GST. The bank tells you cash moved. It doesn't tell you what GST applied. For accruals-basis BAS reporters, the tax invoice is the source, not the bank line. Per the ATO's guidance on choosing an accounting method for GST, accruals reporters include GST in the period the invoice was issued or received, not when payment cleared. If you're auto-coding bank lines to GST-inclusive accounts without the invoice already in the system, BAS will be wrong.
Skipping the bank reconciliation step before lodging BAS. The ATO's BAS and GST tips explicitly recommend reconciling all bank accounts before lodging. Odoo's BAS report draws from the GL, and if the GL doesn't agree with the bank, the BAS will have gaps. We've seen businesses lodge a BAS that the ATO later corrects when bank transactions were missed.
How bank reconciliation feeds the BAS report
The Australian Enterprise localisation includes a native BAS report that draws GST data straight from the GL. Once the bank is reconciled and the underlying invoices and bills are matched to payments, the BAS figures populate automatically. You preview the report from Accounting > Reports > BAS Report (AU), confirm the figures, and either lodge directly or export for the tax agent. Our guide to Odoo Australian localisation for BAS and STP covers the BAS workflow end-to-end.
The integrity of that report depends on the reconciliation finishing cleanly. Skipped reconciliation is the single most common reason a BAS draft looks wrong in Odoo. If the bank balance ties out and every invoice that's been paid is matched to a payment line, the BAS will agree with reality. If not, it won't.
If you're running Xero alongside Odoo
Plenty of Australian businesses run Xero and Odoo in parallel during a transition. The temptation is to reconcile in both systems. Don't. Pick one as the source of truth for the bank, and let the other receive a journal summary. Our post on running Odoo and Xero at the same time covers the trade-offs, and our Odoo Xero integration guide walks through what syncs and what doesn't if you're committing to both systems for the medium term.
Frequently asked questions
Does Odoo connect directly to Australian banks?
Yes, through third-party aggregators (Yodlee and Salt Edge) bundled with the Odoo Enterprise subscription. All four major Australian banks and most mid-tier banks are supported. Verify your specific account type in Odoo's bank list before go-live, as some business savings and merchant-facilitated accounts have limited support.
What file formats does Odoo accept for bank statements?
Odoo v19 accepts CAMT.053, OFX, QIF, and CSV imports. For Australian businesses, OFX is the most reliable because every major bank exports it from their business banking portal. CSV works but requires column mapping the first time you use it.
Can Odoo auto-reconcile ABA batch payments?
Yes. Configure your bank journal with BSB, Financial Institution Code, and Supplying User Number, then create batch payments using the ABA Credit Transfer payment method. When the bank statement shows the consolidated debit, you match it to the batch in a single click from the reconciliation view.
Does Odoo handle multi-currency bank accounts?
Yes. Set the currency at the journal level, configure the exchange rate source (RBA daily is the standard in Australia), and Odoo will revalue the balance at period-end and post unrealised FX gains or losses. Confirm the rate source matches what your auditor expects before going live.
Should I reconcile daily or weekly?
Weekly at minimum. Daily if you process more than 50 bank transactions a week or if you rely on real-time cash position reporting. Monthly reconciliation makes matching harder because context is lost, and it pushes risk into BAS lodgement.
Considering Odoo for your finance team?
We're a certified Odoo Silver Partner in Brisbane and we implement Odoo for Australian mid-market businesses across QLD, NSW, and Victoria. Bank reconciliation, ABA payments, BAS, and STP all sit inside our standard scope.
If you want to talk through whether Odoo fits your business and what implementation would look like, book a free consultation. No obligation, just a conversation about your current setup.
Bank reconciliation is the part of an Odoo accounting implementation that quietly decides whether the finance team trusts the system. Get it right and the month-end close runs in days. Get it wrong and you're chasing unmatched transactions for weeks, your BAS won't tie back to the bank statement, and someone ends up reconciling by hand in a spreadsheet anyway. Australian businesses have a few specific moving parts here, ABA batch payments, GST cash versus accruals reporting, and the quirks of how Australian banks publish statement data, so the setup needs more attention than the standard Odoo accounting guide suggests.
This post covers how Odoo bank reconciliation actually works in v19, the realistic options for connecting to Australian banks, how to reconcile ABA batches without manual line-by-line matching, and where most implementations go wrong. It's written for finance managers, controllers, and business owners deciding whether to commit Odoo as the source of truth for the bank.
How Odoo bank reconciliation actually works
Odoo reconciles bank statements against three things: vendor and customer payments that already exist in the system, open invoices and bills that haven't been matched to a payment yet, and direct journal entries you create on the fly (interest, fees, transfers). The reconciliation view groups these together and lets you match each statement line to one or more counterparts. When a match locks in, Odoo posts the bank journal entry and closes the statement line.
The mechanics are the same whether you're running Community or Enterprise. What Enterprise adds is automatic bank synchronisation, the BAS report, and the reconciliation models that learn from your matches over time. Per Odoo's v19 bank synchronisation documentation, the automatic sync service is only available with a valid Enterprise subscription. Community users can still reconcile, they just have to import files manually.
Bank statement feeds for Australian banks
You have three options for getting statement data into Odoo, and the right choice depends on which bank you use, how often you reconcile, and what's actually supported.
Automatic bank synchronisation
Odoo connects to Australian banks through third-party aggregators, primarily Yodlee and Salt Edge depending on the bank, with coverage of over 26,000 financial institutions worldwide. In practice for Australian businesses, the big four (CBA, Westpac, ANZ, NAB) and most of the mid-tier banks (Bendigo, BOQ, Macquarie, Suncorp) are supported through one or the other. Before you commit to automatic sync as the production approach, log into Odoo's Accounting Features panel, click "See list of supported institutions," and verify your specific bank and account type appear. We've seen edge cases with business savings accounts and certain merchant-facilitated accounts where the feed is read-only or unavailable.
Once connected, statements pull in daily. The catch is the connection occasionally drops and requires re-authentication, which finance teams forget to monitor. Build a weekly "is the sync healthy?" check into the close process, otherwise you'll discover a missing fortnight at month-end.
Manual file import (CSV, OFX, CAMT.053)
Per the v19 bank transactions documentation, Odoo accepts CAMT.053 (the SEPA cash management format), OFX, QIF, and CSV file imports. For Australian banks, OFX is the most reliable manual format because every major bank exports it directly from their business banking portal. CAMT.053 is rare outside European multinational subsidiaries operating here. CSV works but you have to map the columns yourself the first time, and Australian bank CSVs put the date, description, and amount in different places depending on the bank.
The opening balance trap catches new implementations frequently. Odoo expects the first statement line to start from a known opening balance. If you start importing statements halfway through a financial year without entering the opening balance correctly, the running balance in Odoo will never agree with the bank, even if every individual line reconciles.
Manual entry (when you'd use it)
For low-volume accounts (a petty cash float, a foreign currency holding account that sees three transactions a quarter), manual entry into a bank journal is fine. We don't recommend it as the default for an operating account. The risk of typos and missed lines outweighs the cost of either the sync subscription or the five minutes it takes to import an OFX file.
Matching rules and how Odoo learns
Odoo's reconciliation engine uses what it calls "reconciliation models," which are essentially rules that auto-match common statement lines without human intervention. The default models handle exact-amount matches against open invoices and bills. Custom models let you handle the lines that repeat every month: bank fees, interest, EFTPOS settlement fees, FX margin charges, BAS refunds, and ATO PAYG payments.
A model that books a $15 monthly bank fee directly to "Bank Fees" expense as soon as it appears will save a finance team an hour a month. Set up six or seven of these in the first week of the implementation. After that, Odoo's machine-matching also learns from manual choices and will start suggesting the right account for recurring lines automatically.
Reconciling ABA batch payments
ABA (Australian Bankers' Association) files are how Australian businesses pay multiple suppliers in a single bank transaction. The bank's statement shows one consolidated debit, but the underlying payments inside Odoo are individual vendor bill payments. This is the moment most accounting platforms fall apart in Australia, and Odoo handles it correctly if configured properly.
Per the Odoo v19 Australia fiscal localisation documentation, you enable batch payments in Accounting > Configuration > Settings, then configure each bank journal with the BSB code, Financial Institution Code (the 3-letter abbreviation your bank uses), and your Supplying User Number (the 6-digit identifier the bank issues). Once that's in place, the workflow is: register vendor bill payments using "ABA Credit Transfer" as the payment method, tick the bills to include, click Create Batch, then Verify and Validate. Odoo generates the ABA file and attaches it to the batch.
You upload the file to your bank's business banking portal. The next time the bank statement syncs or imports, the statement line shows a single debit for the batch total. In the reconciliation view, you select the Batch Payment tab and match the statement line to the batch in one click. No line-by-line matching, no manual journal entries, just one match.
Our guide to Odoo accounts payable and ABA payments covers the upstream side of this workflow in more detail, including the three-way matching that should happen before any payment ever gets to a batch.
Multi-currency and FX revaluation
If you hold a USD or EUR bank account (importers and exporters often do), Odoo records each transaction at the daily rate and revalues the balance to AUD at period end. The revaluation creates an unrealised FX gain or loss journal entry. This is correct accounting, but it adds one more reconciliation step: the bank balance in AUD shifts at month-end based on the closing exchange rate, and the unrealised entry has to reverse on day one of the next period.
Two settings to check before you go live. First, the bank account currency must be set at the journal level (not just on the company). Second, the exchange rate source needs to be either the RBA daily rate or a manual override that matches whatever the auditors expect. If those don't match, the FX position on the balance sheet will be a few hundred dollars off every month, which finance teams find harder to ignore the longer it persists.
"The biggest reconciliation problem we fix on inherited implementations isn't matching, it's the opening balance. People start importing statements without setting a clean opening figure, and from that point forward the bank balance in Odoo drifts a few hundred dollars off the actual bank. Two months in, no one trusts the system. Fix the opening balance, set up four or five reconciliation models for recurring lines, and the close goes from days to hours."
Josh Craig, Director, Auboros
Where bank reconciliation goes wrong
Three patterns account for most of the implementation problems we see, and all three are avoidable.
Reconciling too infrequently. Some teams batch the whole month into the last week. By the time you're matching a transaction from 28 days ago, the context is gone and matching becomes guesswork. Reconcile weekly at minimum, daily if you're doing meaningful volume. The MYOB 2025 ERP Trends report found 45% of Australian decision-makers say disconnected systems limit their ability to grow, and stale bank reconciliation is one of the practical ways that surfaces.
Treating the bank as the source of truth for GST. The bank tells you cash moved. It doesn't tell you what GST applied. For accruals-basis BAS reporters, the tax invoice is the source, not the bank line. Per the ATO's guidance on choosing an accounting method for GST, accruals reporters include GST in the period the invoice was issued or received, not when payment cleared. If you're auto-coding bank lines to GST-inclusive accounts without the invoice already in the system, BAS will be wrong.
Skipping the bank reconciliation step before lodging BAS. The ATO's BAS and GST tips explicitly recommend reconciling all bank accounts before lodging. Odoo's BAS report draws from the GL, and if the GL doesn't agree with the bank, the BAS will have gaps. We've seen businesses lodge a BAS that the ATO later corrects when bank transactions were missed.
How bank reconciliation feeds the BAS report
The Australian Enterprise localisation includes a native BAS report that draws GST data straight from the GL. Once the bank is reconciled and the underlying invoices and bills are matched to payments, the BAS figures populate automatically. You preview the report from Accounting > Reports > BAS Report (AU), confirm the figures, and either lodge directly or export for the tax agent. Our guide to Odoo Australian localisation for BAS and STP covers the BAS workflow end-to-end.
The integrity of that report depends on the reconciliation finishing cleanly. Skipped reconciliation is the single most common reason a BAS draft looks wrong in Odoo. If the bank balance ties out and every invoice that's been paid is matched to a payment line, the BAS will agree with reality. If not, it won't.
If you're running Xero alongside Odoo
Plenty of Australian businesses run Xero and Odoo in parallel during a transition. The temptation is to reconcile in both systems. Don't. Pick one as the source of truth for the bank, and let the other receive a journal summary. Our post on running Odoo and Xero at the same time covers the trade-offs, and our Odoo Xero integration guide walks through what syncs and what doesn't if you're committing to both systems for the medium term.
Frequently asked questions
Does Odoo connect directly to Australian banks?
Yes, through third-party aggregators (Yodlee and Salt Edge) bundled with the Odoo Enterprise subscription. All four major Australian banks and most mid-tier banks are supported. Verify your specific account type in Odoo's bank list before go-live, as some business savings and merchant-facilitated accounts have limited support.
What file formats does Odoo accept for bank statements?
Odoo v19 accepts CAMT.053, OFX, QIF, and CSV imports. For Australian businesses, OFX is the most reliable because every major bank exports it from their business banking portal. CSV works but requires column mapping the first time you use it.
Can Odoo auto-reconcile ABA batch payments?
Yes. Configure your bank journal with BSB, Financial Institution Code, and Supplying User Number, then create batch payments using the ABA Credit Transfer payment method. When the bank statement shows the consolidated debit, you match it to the batch in a single click from the reconciliation view.
Does Odoo handle multi-currency bank accounts?
Yes. Set the currency at the journal level, configure the exchange rate source (RBA daily is the standard in Australia), and Odoo will revalue the balance at period-end and post unrealised FX gains or losses. Confirm the rate source matches what your auditor expects before going live.
Should I reconcile daily or weekly?
Weekly at minimum. Daily if you process more than 50 bank transactions a week or if you rely on real-time cash position reporting. Monthly reconciliation makes matching harder because context is lost, and it pushes risk into BAS lodgement.
Considering Odoo for your finance team?
We're a certified Odoo Silver Partner in Brisbane and we implement Odoo for Australian mid-market businesses across QLD, NSW, and Victoria. Bank reconciliation, ABA payments, BAS, and STP all sit inside our standard scope.
If you want to talk through whether Odoo fits your business and what implementation would look like, book a free consultation. No obligation, just a conversation about your current setup.