Define EDI Configuration for Bank Statements
auto_awesome What this module does
AI-generated from the code · Odoo 13.0Adds EDI exchange tracking to bank statements, so users can see and open the electronic exchange records linked to a statement and browse all bank statement exchanges from the Accounting configuration menu.
This module connects bank statements with the EDI exchange framework, so the electronic files exchanged for a statement are visible directly in Odoo.
On the bank statement form, a new stat button labelled "EDI" appears in the button box. It shows how many exchange records are linked to that statement and is hidden when the count is zero. Clicking it opens the related exchange records.
A new menu "Exchange records" is added under the Accounting configuration menu, containing a "Bank Statements" entry. This opens a list of all exchange records whose model is account.bank.statement, in list and form views.
When the "Reconcile" action is run on a bank statement (action_bank_reconcile_bank_statements), the module also triggers an event named on_action_bank_reconcile_bank_statements. This lets other EDI components react automatically to the reconciliation, for example to generate or process exchange records.
The module extends the account.bank.statement model with the EDI exchange consumer behaviour, which is what provides the exchange record count and the link to the records. It depends on the Accounting, EDI and component event modules.
Depends on
Menus it adds
Models and fields (1)
- account.bank.statement · new model
Text generated by AI (DeepSeek) from reading the Odoo 13.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-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/edi.
terminal Installation and usage
No verified informationInstallation 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.
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.