Way4Tech
Accounting/Accounting Odoo 19.0 On Odoo Apps
Bank Statement Import (OFX, QIF, CAMT.053, CSV) icon

Bank Statement Import (OFX, QIF, CAMT.053, CSV)

Import bank statements from OFX, QIF, CAMT.053 and CSV files, with duplicate protection, journal matching and partner matching, for Odoo Community.

Category
Accounting/Accounting
Odoo version
Odoo 19.0
Price
USDย 79
Odoo Apps Store
Listed

Odoo Community can create a bank statement but it cannot read one. This adds the file import: pick the file the bank gave you, and the statement and its lines are created for you.

Bank Statement Import (OFX, QIF, CAMT.053, CSV) in Odoo

Four formats

  • โœ“ OFX, in both the SGML flavour that most banks still export and the XML flavour of OFX 2. Parsed here, with no external library to install
  • โœ“ QIF, the line prefix format Quicken made and half the smaller banks copied
  • โœ“ CAMT.053, the ISO 20022 end of day statement, read without caring which version of the schema the bank used
  • โœ“ CSV, driven by a column mapping you set up once per bank

Nothing is imported twice

  • โœ“ Every line keeps the reference it was imported under, and that reference is checked against the journal before anything is written
  • โœ“ Files that overlap are the normal case, not the exception: a download of "the last 30 days" run weekly repeats three weeks every time
  • โœ“ Formats that carry no reference of their own, such as QIF and most CSV exports, get a fingerprint derived from the transaction itself, so the same file loaded twice still imports nothing the second time
  • โœ“ The wizard says how many lines were imported and how many were skipped, and the skipped ones are listed by name

The right journal, the right currency

  • โœ“ The account number in the file is matched against the bank account on the journal, including files that print only the last digits
  • โœ“ A file issued in a currency the journal does not keep is refused before anything is written, rather than producing a statement that cannot be reconciled

Partners

  • โœ“ Matched on the counterparty account number first, because a name on a bank line can be anything but an account number belongs to one person
  • โœ“ Then on the name, and only when exactly one partner has it

An audit trail

  • โœ“ Every import is recorded: the file, the journal, what was created, what was skipped and who ran it
  • โœ“ Searchable by the bank's reference, so "why is this payment not in Odoo" has an answer
  • โœ“ Printable as a PDF

The CSV mapping

  • โœ“ Separator, quote character, encoding, header row and lines to skip
  • โœ“ Columns matched by heading or by position
  • โœ“ Date format, decimal separator and thousands separator
  • โœ“ One signed amount column, or a debit column and a credit column
  • โœ“ Save one mapping per bank and attach it to the journals it belongs to
  • โœ“ Unrecognised files are reported in plain language. A PDF statement, a spreadsheet, a camt.052 intraday report: each gets told what it is and what to ask the bank for instead.
  • โœ“ Requires nothing but Odoo Accounting.

What you get

  • โ†’Full module source code: Python, OWL, XML and CSS
  • โ†’Installation on your Odoo instance, or a copy you install yourself
  • โ†’Written documentation and a user guide
  • โ†’A one-hour walkthrough with your team
  • โ†’90 days of bug-fix support

Buy it on the Odoo Apps Store

Bank Statement Import (OFX, QIF, CAMT.053, CSV) is published on apps.odoo.com at USDย 79. Buy there and you get every update we publish for that version.

View on Odoo Apps

Related modules

Need it to work a little differently?

Every module here started as a client request. Tell us what is missing and we will quote the change, or build the thing you actually need.