Odoo Bank Statement Import Format: Convert PDF Bank Statements to OFX, QIF and CSV for Odoo Accounting

What file formats does Odoo accept for bank statements?

Odoo Accounting imports bank transactions from five formats: CAMT.053, CSV, OFX, QIF and CODA. That is a wider list than most accounting systems offer, and notably it includes both of the formats a converted bank statement is most naturally exported as. PDF is not on the list, which is the one detail that catches people out, since a PDF is what online banking actually hands you.

Which of the five makes sense depends almost entirely on where you are. The table below is the short version for a US account.

Can Odoo import an OFX file?

Yes. Open Financial Exchange is one of the formats Odoo Accounting reads directly, alongside CAMT.053, CSV, QIF and CODA. Because OFX describes its own structure, the import does not depend on you correctly mapping a spreadsheet column to an Odoo field, which removes the step where most CSV imports go wrong.

It also removes a subtler risk. An OFX file assigns every transaction a unique identifier, so an overlapping statement period has something in it that can be recognized as already seen. A CSV row and a QIF entry carry no such identity, which is why re-importing a spreadsheet is the classic way to end up with a bank journal holding two copies of March. There is more on that structure on the OFX file format page.

How do I import a bank statement into Odoo?

Go to the Accounting Dashboard, find the bank journal for the account the statement belongs to, and click Import File. The same import is reachable from the ellipsis icon on the journal card, and from the transaction list through the gear icon and Import records. Upload the converted file, set the formatting options the wizard asks for, and where the format needs it, map each column in the file to its related Odoo field.

Then use Test before you import. The wizard offers it specifically so a wrong mapping or a misread date format can be caught while it is still a preview rather than a set of journal entries you have to unwind. Check that the transaction count matches the statement and that the dates fall in the period you expect, and only then run the import.

Why the CSV route is the fussiest of the three

CSV feels flexible and behaves like the opposite. Every import runs through formatting options and a column mapping step, and both have to be right for the file in front of you. When a bank changes its export layout, or a spreadsheet gets an extra column somewhere along the way, the mapping you saved last month no longer describes this month's file.

Dates are the specific hazard, because they fail quietly rather than loudly. A file where the day and month can be read either way will import without complaint and put transactions in the wrong period, and the only signal is that reconciliation stops tying out. OFX avoids the whole category of problem by stating its dates unambiguously inside the file. If a spreadsheet is genuinely the destination rather than a step on the way, the PDF bank statement to CSV converter covers that output directly.

Loading history a bank feed cannot reach

This is what drives most manual imports. Bank download screens typically serve about 90 days of activity while the statement archive runs for years, so any Odoo migration, any account that was never connected, and any auditor asking about a prior period lands outside what a feed can supply. The statements are the complete record, and they are always available.

For that kind of catch-up, convert the monthly PDFs as one batch rather than one at a time. Up to 50 files go into a single upload, and when they all belong to the same account they can be merged before extraction, so twelve monthly statements come back as one continuous file and one import into the bank journal instead of twelve. The bulk bank statement converter page covers how batching and merging behave.

Checking the import before you reconcile

Two checks catch nearly everything. Compare the transaction count and the closing balance of each converted statement against the printed document, because a matching closing balance is strong evidence that every line between the opening and closing figures came through correctly. Then run the wizard's Test step and read what it is about to create before committing it.

If a period does end up imported twice, deal with it before reconciling rather than after, and prefer OFX for anything you might reload. Odoo will happily accept the same QIF or CSV file twice, because nothing in those formats says the transactions are the same ones. The same problem shows up in every accounting system that accepts spreadsheets, and it is covered in more depth for a different one on the QuickBooks bank statement import page.