TIP: You can type at any time to perform a new search.
Bank statement completion from transaction ID
account_statement_transactionid_completion · OCA/account-reconcile
Security findings
Migration considerations
- Imports from the old `openerp.tools.translate` namespace: renamed to `odoo` since Odoo 10.0. migration-openerp-import · source
- Imports from the old `openerp.osv.orm` namespace: renamed to `odoo` since Odoo 10.0. migration-openerp-import · source
- Imports from the old `openerp.osv` namespace: renamed to `odoo` since Odoo 10.0. migration-openerp-import · source
- Imports from the old `openerp.addons.account_statement_base_completion.statement` namespace: renamed to `odoo` since Odoo 10.0. migration-openerp-import · source
- For a target of Odoo 10.0+: use the `__manifest__.py` manifest name instead of `__openerp__.py`. The filename alone does not establish module age or compatibility. migration-openerp-manifest · source
AccountStatementLine— Class 'AccountStatementLine' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · source
Migration review checklist, not a compatibility verdict. No target version is selected: apply version-specific advice only when migrating to that version or later.
- Repository
- OCA/account-reconcile · module folder · Try on Runboat
- Module version
- 1.0
- Category
- Finance
- Folder size
- 0.02 MB
- License
- AGPL-3
- Application
- No
- Auto-installable
- Yes
- Website
- http://www.camptocamp.com
- Last tracking update
- 2026-08-07 07:03:11
- Authors
- Camptocamp, Odoo Community Association (OCA)
- Maintainers
- Camptocamp
- Committers
- Stéphane Bidoul, Pedro M. Baeza, Stéphane Bidoul (ACSONE)
- Odoo dependencies
- Python dependencies
- None
- System dependencies
- None
- Required by
- account_statement_transactionid_import
- Description
Add a completion method based on transaction ID providen by the bank/office. This transaction ID has been recorded on the SO (by a mapping through the e-commerce connector, or manually). Completion will look in the SO with that transaction ID to match the partner, then it will fill in the bank statement line with it, as well as the reference with the found SO name to ease the reconciliation. This way, the reconciliation always happen on the SO name stored in ref.
Code Analysis
Views touched (1)
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
bank_statement_view_form |
account_bank_statement_import_base.bank_statement.view_form | account.bank.statement | form | Inherits account.view_bank_statement_form |
HTTP endpoints (0)
No HTTP endpoints found for this module.
Models touched (3)
New fields (0)
No new fields.
Public methods (0)No public methods.
New fields (0)
No new fields.
Public methods (0)No public methods.
New fields (0)
No new fields.
Public methods (2)-
get_from_transaction_id_and_invoice(self, cr, uid, st_line, context=None)Match the partner based on the transaction ID field of the invoice. Then, call the generic st_line method to complete other values. In that case, we always fullfill the reference of the line with the invoice name. :param dict st_line: read of the concerned account.bank.statement.line :return: A dict of value that can be passed directly to the write method of the statement line or {} {'partner_id': value, 'account_id' : value, ...} -
get_from_transaction_id_and_so(self, cr, uid, st_line, context=None)Match the partner based on the transaction ID field of the SO. Then, call the generic st_line method to complete other values. In that case, we always fullfill the reference of the line with the SO name. :param dict st_line: read of the concerned account.bank.statement.line :return: A dict of value that can be passed directly to the write method of the statement line or {} {'partner_id': value, 'account_id' : value, ...}
Loading…
Loading…