Account Mass Reconcile
This is a shared work between Akretion and Camptocamp in order to provide:
Reconciliation facilities for big volume of transactions.
Setup different profiles of reconciliation by account.
Each profile can use many methods of reconciliation.
This module is also a base to create others reconciliation methods which can plug in the profiles.
A profile a reconciliation can be run manually or by a cron.
Monitoring of reconciliation runs with an history which keep track of the reconciled Journal items.
2 simple reconciliation methods are integrated in this module, the simple reconciliations works on 2 lines (1 debit / 1 credit) and do not allow partial reconciliation, they also match on 1 key, partner or Journal item name.
Table of contents
Usage
Give the user permissions to view full accounting features, then go to ‘Invoicing / Accounting / Mass Automatic Reconcile’ to start a new mass reconcile.
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 smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Sébastien Beau <sebastien.beau@akretion.com>
Guewen Baconnier <guewen.baconnier@camptocamp.com>
Vincent Renaville <vincent.renaville@camptocamp.com>
Alexandre Fayolle <alexandre.fayolle@camptocamp.com>
Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>
Nicolas Bessi <nicolas.bessi@camptocamp.com>
Pedro M.Baeza <pedro.baeza@gmail.com>
Matthieu Dietrich <matthieu.dietrich@camptocamp.com>
Leonardo Pistone <leonardo.pistone@camptocamp.com>
Ecino <ecino@compassion.ch>
Yannick Vaucher <yannick.vaucher@camptocamp.com>
Rudolf Schnapka <rs@techno-flex.de>
Florian Dacosta <florian.dacosta@akretion.com>
Laetitia Gangloff <laetitia.gangloff@acsone.eu>
Frédéric Clémenti <frederic.clementi@camptocamp.com>
Damien Crier <damien.crier@camptocamp.com>
Akim Juillerat <akim.juillerat@camptocamp.com>
Mykhailo Panarin <m.panarin@mobilunity.com>
Adrià Gil Sorribes <adria.gil@forgeflow.com>
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/account-reconcile 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-mass-reconcile 13.0.1.0.2
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_mass_reconcile-13.0.1.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo13_addon_account_mass_reconcile-13.0.1.0.2-py3-none-any.whl |
Release files / odoo13_addon_account_mass_reconcile-13.0.1.0.2-py3-none-any.whl
| Download URL | odoo13_addon_account_mass_reconcile-13.0.1.0.2-py3-none-any.whl |
|---|---|
| Size | 287.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7787df5a19f75ee1752dcf9b33b00fcee32eeeabd7969ed6df21d1f837fd4fc6
|
|
BLAKE2b-256 checksum How to use checksums |
77cb78c4f7d65918659101e1a514afe9a25ee4d6f793a40435b0d54f2c7b99f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo13-addon-account-mass-reconcile 13.0.1.0.2
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.
