Odoo Bank Feeds in Australia: Sync, Manual Imports, and Which to Choose
How Odoo bank feeds work in Australia: the free Basiq connector, OFX and CSV imports, sync frequency, and which setup keeps reconciliation and BAS tidy.
By Auboros ·
Bank reconciliation is only ever as good as the transaction data flowing into it. Get the feed setup right and reconciliation becomes a ten minute daily habit. Get it wrong and you’re exporting spreadsheets from internet banking every Friday, wondering why the bank balance in Odoo never matches the real one.
Odoo gives Australian businesses two ways to bring bank transactions in: automatic synchronisation through a bank feed, or manual statement imports. This post covers how each works, what the Australian connector actually supports, and how to decide which setup fits your business.
How Odoo bank feeds work in Australia
Odoo Enterprise includes online bank synchronisation, which connects your bank accounts to Odoo through a third-party data provider. For Australia, that provider is Basiq. The Odoo documentation on Basiq confirms the connector is free for Odoo users and available only for Australian banks, which is exactly what you want: a connector built for this market rather than a global service with patchy local coverage.
Once connected, Odoo checks for new transactions automatically every 12 hours. You can also trigger a fetch manually from the accounting dashboard whenever you need up to the minute data, such as before a payment run or at month end.
The connection process runs through Basiq’s consent flow. You authorise access to the specific accounts you want in Odoo, and only transaction data comes across. Odoo never stores your banking credentials. If your bank doesn’t appear in the connection flow, that’s your answer on coverage, and manual imports become the fallback.
One thing worth being clear about: bank synchronisation is a feature of Odoo Enterprise. If you’re weighing up editions, feeds belong on the Enterprise side of the ledger along with the Australian localisation features like BAS reporting.
Manual statement imports: OFX, QIF, CSV and CAMT
Not every business wants a live feed, and not every account can have one. Odoo Enterprise ships with import support for the four common statement formats: OFX, QIF, CSV and CAMT.053. Most Australian banks export at least OFX or CSV from internet banking.
CSV is the most flexible and the most work. On first import you map your bank’s columns (date, description, amount) to Odoo’s fields, and Odoo remembers the mapping for next time. OFX and QIF carry more structure, so they import with less setup.
Manual imports make sense in a few situations:
- Low transaction volume. If an account sees a dozen transactions a month, a weekly import takes two minutes and a feed adds little.
- Unsupported accounts. Some credit union accounts, term deposits and specialty facilities don’t appear in feed coverage.
- Policy reasons. Some boards and finance committees are not yet comfortable authorising third-party data access, common in clubs and not-for-profits. Imports keep everything in-house.
A quick clarification that trips people up: ABA files are for sending payments out of Odoo to your bank, not for bringing statement data in. If you’re setting up supplier payment runs, that’s covered in our guide to Odoo accounts payable and ABA payments.
Feed or import: how to choose
For most trading businesses, the feed wins. The MYOB ERP Trends report found 45% of Australian decision-makers say disconnected systems limit their growth, and a bank account that only talks to your ERP when someone remembers to export a file is a disconnected system.
The practical difference shows up in reconciliation behaviour. With a feed, transactions appear twice a day and someone can clear them in minutes while the transactions are still fresh in memory. With imports, reconciliation tends to drift into a batch job, and batch reconciliation is where errors hide.
“The businesses with clean books are never the ones with the fanciest setup. They’re the ones where transactions arrive automatically and someone spends ten minutes a day clearing them. The feed is what makes that habit possible.”
Josh Craig, Director, Auboros
There are legitimate mixed setups too. We regularly configure the main trading account on a Basiq feed and leave a rarely used foreign currency account or term deposit on quarterly CSV imports. Odoo handles per-journal configuration without fuss.
Setup details that matter for Australian books
Whichever path you choose, a few configuration decisions determine whether your feed helps or hurts at BAS time.
- Reconciliation models do the heavy lifting. Bank fees, merchant charges and interest can be matched and coded automatically, including the right GST treatment. We covered this in detail in our Odoo bank reconciliation guide.
- GST coding at the point of reconciliation. Every transaction cleared with the wrong tax code is a future BAS adjustment. Set your models up so the common cases code themselves and the odd ones get flagged, not guessed. The ATO’s guidance on business activity statements is the reference point for what you’re reconciling toward.
- Keep the source records. The ATO’s record keeping rules require most business records to be kept for five years. A feed doesn’t replace statements; download and store the PDFs, or attach them to the statement records in Odoo.
When feeds misbehave
Feeds are reliable but not perfect, and it pays to know the failure modes. Connections occasionally need re-authorising after a bank-side security change. Pending transactions can shift dates when they settle, which is why Odoo’s matching works on posted transactions. And if you disconnect and reconnect an account, watch the first fetch for duplicates before you reconcile it.
None of these are reasons to avoid feeds. They’re reasons to have someone who knows what a healthy feed looks like glance at the journal weekly, which is a far smaller job than manually importing everything forever.
Getting bank feeds flowing into Odoo
We set up Basiq feeds, statement imports and reconciliation models as part of every Odoo implementation we deliver from Brisbane, for businesses across Queensland and beyond. If your reconciliation still starts with a CSV export, book a free consultation and we’ll show you what the daily habit version looks like. No pressure, just a look at how your current setup compares.
FAQ
Frequently asked questions
Does Odoo connect to Australian banks?
Yes. Odoo Enterprise connects to Australian banks through Basiq, a connector that is free for Odoo users and available only in Australia. You authorise the specific accounts, and transactions flow into your bank journals automatically.
How often does Odoo sync bank transactions?
Odoo fetches new transactions automatically every 12 hours once a feed is connected. You can also trigger a manual fetch from the accounting dashboard at any time, which is useful before payment runs or at month end.
Can I import bank statements into Odoo manually?
Yes. Odoo Enterprise imports OFX, QIF, CSV and CAMT.053 statement files. CSV needs a one-off column mapping on first import; most Australian banks export at least one of these formats from internet banking.
Does Odoo bank synchronisation cost extra in Australia?
No. The Basiq connector is free for Odoo users. Bank synchronisation is an Odoo Enterprise feature, so you need an Enterprise subscription, but there is no additional per-feed charge.