This release is a pre-release and may not be stable for production use.
Account Bank Statement Line Reconciliation
The wizard provides the ability to specify bank statement line when it needed. The only users from security group “Settings” can use it.
Usage
This module is for you if you work with Odoo enterprise and you messed up the bank reconcile report.
The bank reconciliation report is accessible from the hyperlink ‘Difference’ which appears on bank journals cards when the GL balance differs from the bank statement balance.
There are only 2 situation handled from field filter (from bank reconcile view) but there are more in real life:
1 - Blue lines appear if account_move_lines have these values:
statement_id = false
AND payment_id = true
AND account_id = current bank
-> This means that if you post a payment journal entry manually (meaning that you do not use the register payment button) the payment_id will not be populated then the payment_id will not be populated. When this happens, your entry won’t match: you are stuck and you need this module to prevent this situation.
Same issue in case of migration of payment entries with no payment_id
2 - If 1st request is not applicable then Odoo will look up for account_move_lines with:
reconcile_id = false
account_id = flagged as 'Allow reconciliation" = true
excluding the line in the move with the bank account.
-> This means that if you have created entries on a reconciliable account but you never reconcile it (ie: a cut-off entry or a correction) this line will appear forever in the list of possible matches -> so you may need this module to clean it up.
To use this module, you need to:
Go to Accounting > Adviser > Journal Entries
Select one or more Journal Entry items
Press ‘Action > Bank reconcile report change’
Select required value in ‘New value’ field. Leave empty if you want to set empty value.
Press ‘Set value’
By doing this, you will create/delete the link between Journal entry and bank statement lines hence you will make corrections on the bank reconcile report which would be impossible to do through the Odoo interface.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smash it by providing detailed and welcomed feedback.
Credits
Images
Odoo Community Association: Icon.
Contributors
Camptocamp SA
Maintainer
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
To contribute to this module, please visit https://odoo-community.org.
Metadata
Release files for odoo10-addon-account-bank-statement-line-reconciliation 10.0.1.0.0.99.dev4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo10_addon_account_bank_statement_line_reconciliation-10.0.1.0.0.99.dev4-py2-none-any.whl | Python 2 | none | any | Details for odoo10_addon_account_bank_statement_line_reconciliation-10.0.1.0.0.99.dev4-py2-none-any.whl |
Release files / odoo10_addon_account_bank_statement_line_reconciliation-10.0.1.0.0.99.dev4-py2-none-any.whl
| Download URL | odoo10_addon_account_bank_statement_line_reconciliation-10.0.1.0.0.99.dev4-py2-none-any.whl |
|---|---|
| Size | 23.4 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
a91155209dcc8934c1d25236728c20c2fdec354bd3461a99268bbeaf6254b92f
|
|
BLAKE2b-256 checksum How to use checksums |
0c69fe9193f58dad7002995dbfcd86db71bff57334a2779f6d407afd262eb7d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo10-addon-account-bank-statement-line-reconciliation 10.0.1.0.0.99.dev4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.