OdooWiki OCA HUB

Bank Account Camt54 Import

account_statement_import_camt54 folder_open OCA/bank-statement-import open_in_new
Account License: AGPL-3

> This module allows you to import CAMT.054 file (details of customers > payments batch) into a dedicated journal taking care of the start/end > balance and the remittance reference number.

Customer invoices will be reconciled/Paid. Payment entries will be posted into an internal transfer account (that you have to create with a type current asset and set on the journal)

After this first step, import normally your CAMT.053 (full bank statement) into the bank journal. You will be able to clear the internal transfer account to end up the accounting flow.

Optionally we can activate add generation of additional line in bank statement which will balance your bank statement total to 0. This line can be consolidated later with different account. To enable option of final statement line you need properly set flag on Account Journal Configuration -\> Journals -\> tab Advanced Settings -\> Bank statement configuration

Switzerland localisation

For QRR containing a partner reference, uses the config parameter key qrr_partner_ref. Doing so will fill the partners on bank statement lines and speed up the matches in the reconciliation process.

Value to set in qrr_partner_ref defines the position of the partner reference inside the QRR. The format is i[,n] For instance 13,6 to start on position 13 with a 6 digit long reference. n is optional and it's default value is 6.

auto_awesome What this module does

AI-generated from the code · Odoo 19.0

Import CAMT.054 payment batch files into a dedicated journal, automatically matching customer payments to invoices and optionally adding a balancing line so the statement totals zero.

This module extends the CAMT bank statement import to handle CAMT.054 files, which contain the details of a batch of customer payments. When you import such a file, Odoo creates a bank statement in the journal you choose and tries to match each payment to a customer invoice using the payment reference.

  • The payment reference (often a structured QRR/ESR number) is read from the file and used to find the customer by their reference number. A system setting called qrr_partner_ref defines where the customer number sits inside that reference; if it is missing or wrongly formatted, an error message explains the expected format.
  • If no structured reference is found, the module falls back to other text fields in the file to build the payment label, and it can append the bank's transaction ID for easier tracing.
  • On the journal configuration form (Accounting > Configuration > Journals, Advanced Settings tab), a new option "Add balance Line" appears. When enabled, after import Odoo adds an extra line to the statement so that the total of all lines is zero, and sets the ending balance equal to the starting balance. When disabled, the ending balance is simply the starting balance plus the sum of the imported lines.
  • The module works together with the standard CAMT import and touches the journal settings, the import wizard, and the CAMT parser. It does not create new menus; the option is added inside the existing journal form.

Depends on

account_statement_import_camt
Models and fields (3)
  • account.journal · extends an existing modeltransfer_line (Add balance Line)
  • account.statement.import · extends an existing model
  • account.statement.import.camt.parser · extends an existing model

Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 6 confirmed, 3 with no information of 9 versions.

Sources · Odoo 18.0

Confirmed on 2026-11-03 in branch 18.0 of OCA/bank-statement-import.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.