Bank statement extension and profiles
account_statement_ext · OCA/account-reconcile
-
Security25/25No findings
-
Activity0/25Last human commit 121 months ago
-
Required by20/254 modules depend on it
-
Maturity25/25In 5 Odoo series since 6.1
Heuristic over the facts below, not an audit · How it's computed
Migration considerations
AccountMove— Class 'AccountMove' still inherits from the old-style `orm.Model` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · sourcestatement_importer_view_tree— Migrating to 18.0: the `tree` view type was renamed to `list` (`<list>` roots, `view_mode`). migration-view-tree-tag · sourceview_treasury_statement_form— Migrating to 17.0: `attrs=`/`states=` are rejected in views: convert them to Python expressions in `invisible`/`readonly`/`required`, keeping the original AND/OR logic. migration-view-attrs-states · source- Since 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp.osv.orm`) migration-openerp-import · source
- Since 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp.osv`) migration-openerp-import · source
- Since 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp.report`) (4 occurrences in this file) migration-openerp-import · source
Migration review checklist, not a compatibility verdict. "Migrating to X.0" applies once you upgrade to that version; "Since X.0" means this version already ignores or rejects that code. Methodology
Description
Improve the basic bank statement, by adding various new features, and help dealing with huge volume of reconciliation through payment offices such as Paypal, Lazer, Visa, Amazon...
It is mostly used for E-commerce but can be useful for other use cases as it introduces a notion of profile on the bank statement to have more control on the generated entries. It serves as a base for all new features developped to improve the reconciliation process (see our other set of modules:
- account_statement_base_completion
- account_statement_base_import
- account_advanced_reconcile
Features:
- Improve the bank statement: allows to define profiles (for each Office or Bank). The bank statement will then generate the entries based on some criteria chosen in the selected profile. You can setup on the profile:
- the journal to use
- use balance check or not
- account commission and Analytic account for commission
- partner concerned by the profile (used in commission and optionaly on generated credit move)
- use a specific credit account (instead of the receivalble/payable default one)
- force Partner on the counter-part move (e.g. 100.- debit, Partner: M. Martin; 100.- credit, Partner: HSBC)
-
Add a report on bank statement that can be used for checks remittance
-
When an error occurs in a bank statement confirmation, go through all line anyway and summarize all the erronous line in a same popup instead of raising and crashing on every step.
-
Remove the period on the bank statement, and compute it for each line based on their date instead. It also adds this feature in the voucher in order to compute the period correctly.
-
Cancelling a bank statement is much more easy and will cancel all related entries, unreconcile them, and finally delete them.
-
Add the ID in entries view so that you can easily filter on a statement ID to reconcile all related entries at once (e.g. one statement (ID 100) for Paypal on an intermediate account, and then another for the bank on the bank account. You can then manually reconcile all the line from the first one with one line of the second by finding them through the statement ID.)
Dependencies
- Odoo dependencies
- Python dependencies
- None
- System dependencies
- None
- Required by
- account_statement_cancel_line, account_statement_ext_point_of_sale, account_statement_ext_voucher, account_statement_one_move
Code analysis
Extracted from the source by best-effort static analysis (no code is executed); details may be incomplete.
Views touched 6
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
statement_importer_view_form |
account.statement.profile.view | account.statement.profile | form | New |
statement_importer_view_tree |
account.statement.profile.view | account.statement.profile | tree | New |
view_account_move_line_filter_add_statement |
Journal Items add statement | account.move.line | Inherits account.view_account_move_line_filter | |
view_treasury_statement_form |
account.bank.statement.form | account.bank.statement | form | Inherits account.view_bank_statement_form |
view_treasury_statement_search |
account.bank.statement.search | account.bank.statement | search | Inherits account.view_bank_statement_search |
view_treasury_statement_tree |
account.bank.statement.tree | account.bank.statement | tree | Inherits account.view_bank_statement_tree |
HTTP endpoints 0
No HTTP endpoints found for this module.
Models touched 2
No new fields.
Public methods (1)-
unlink(self, cr, uid, ids, context=None)Delete the reconciliation when we delete the moves. This allow an easier way of cancelling the bank statement.
No new fields.
Public methods (1)-
create(self, cr, uid, values, context=None)If no period defined in values, ask it from moves.
Loading…
Loading…
Loading…
Loading…