This release is a pre-release and may not be stable for production use.
Reconcile entries from pseudo bank statements
This is a technical modules that you can use to improve the processing of statement files from payment providers. These statements usually consist of lines that to be reconciled by customer debts, offset by lines that are to be reconciled by the imbursements from the payment provider, corrected for customer credits and the costs of the payment provider. Typically, the balance of such a statement is zero. Effectively, the counterpart of each statement line is made on a clearing account and you should keep track of the balance of the clearing account to see if the payment provider still owes you money. You can keep track of the account by reconciling each entry on it.
That is where this module comes in. When importing such a statement, this module reconciles all the counterparts on the clearing account with one another. Reconciliation is executed when validating the statement. When reopening the statement, the reconcilation is undone.
Known issues
This module does not come with its own tests because it depends on a statement filter being installed. Instead, it is tested in account_bank_statement_import_adyen
Table of contents
Configuration
In order to enable the reconcilation of the counterparts of zero-balance statement files from payment providers, you need to make sure that the journal that is used for these statements have the same default debit account as their default credit account, and this account is configured for reconciliation.
Usage
After installing this module, any statement where the sum of all debit and credit lines match, and where the default journal account is reconcilable, will reconcile all posted moved when the statement is confirmed.
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 to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Stefan Rijnhart <stefan@opener.amsterdam> (https://opener.amsterdam)
Martin Pishpecki <pishpecki@gmail.com> (https://www.vanmoof.com)
Ronald Portier <ronald@therp.nl> (https://therp.nl)
Maintainers
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.
This module is part of the OCA/bank-statement-import project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo13-addon-account-bank-statement-clearing-account 13.0.1.0.1.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 |
|---|---|---|---|---|
| odoo13_addon_account_bank_statement_clearing_account-13.0.1.0.1.dev4-py3-none-any.whl | Python 3 | none | any | Details for odoo13_addon_account_bank_statement_clearing_account-13.0.1.0.1.dev4-py3-none-any.whl |
Release files / odoo13_addon_account_bank_statement_clearing_account-13.0.1.0.1.dev4-py3-none-any.whl
| Download URL | odoo13_addon_account_bank_statement_clearing_account-13.0.1.0.1.dev4-py3-none-any.whl |
|---|---|
| Size | 27.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4cfc93f21864b049a4084be7a8e3b83abc71afbd60030eeea5acec1db1c15e07
|
|
BLAKE2b-256 checksum How to use checksums |
87d02834e63234cd4a25c3f53cf84f922d339c41c6d18f49a027ba5c637c04e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo13-addon-account-bank-statement-clearing-account 13.0.1.0.1.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.
