Bank Statement Import (MT940/CSV/OFX)

This is a build-to-order module, not an instant download. Typical delivery is 2–4 weeks from the point we receive your sample statement files and confirm which banks, formats and Odoo edition you're on. A single bank in one format lands toward the 2-week end; several banks with mixed MT940/CAMT/CSV layouts and multi-currency handling sit toward 4 weeks. We share a scoped timeline before we start and install it on your server or Odoo.sh when it's tested.

Every build includes a defined post-delivery support window to fix any bugs in the delivered scope at no extra cost. Beyond that, we offer a paid maintenance option that covers adding new banks or file formats, adapting when a bank changes its export layout, and porting the module forward when you upgrade Odoo (e.g. 17 to 18 to 19). You own the source code, so you're never locked in.

Yes — that's exactly the case this module is built for. We create a saved mapping template per bank that records which column is the transaction date, which is the value date, whether the amount is one signed column or split debit/credit, the sign convention, the date format, and the decimal and thousand separators. Once built, your team just selects the bank and uploads the file; no re-mapping each time.

No. Duplicate-line detection compares each incoming line against already-imported lines using the bank's unique end-to-end reference where available, and otherwise a computed hash of date, amount and reference (an Odoo compute field with @api.depends). Overlapping or accidentally re-uploaded files skip the lines already present and only import genuinely new ones — the import summary tells you exactly how many were skipped as duplicates.

Odoo core imports OFX, QIF, CAMT and generic CSV but has no MT940 parser and no per-bank saved column mapping, so real-world bank CSVs and German MT940 exports fail or need manual clean-up. A live bank feed (Enterprise) is great when your bank is supported — but many regional banks aren't, feeds cost per connection, and they don't cover historical back-loading. This module fills that gap: it imports whatever file your bank gives you, mapped to the right journal, deduplicated, in your Odoo edition.

Yes. Statements are parsed with their own currency preserved and converted at the transaction-date rate against the journal currency using Odoo's currency rates. For multi-company groups we add company_id record rules so each company only sees and imports against its own bank journals and templates, and access to the import wizard is governed through ir.model.access.csv tied to your existing accounting roles.

They can. On top of the manual upload wizard, we can wire an automated action and expose the importer over Odoo's XML-RPC / JSON-RPC API so an upstream system, script, or a scheduled pull from a bank SFTP drop can push files in automatically — with an email alert to finance if a file fails to parse. We scope this as an add-on since it depends on how your bank delivers files.