Reconcile payment orders
Payment orders that show up as one big transaction can be difficult for the accounting to handle if a transfer account is used. In this case, we need to reconcile this transaction with possibly hundreds of move lines, which can be a bit tiresome. This module tries to recognize transactions deriving from payment orders and propose the unreconciled move lines from this payment order.
Table of contents
Installation
This module requires the module account_payment_order, available in https://github.com/OCA/bank-payment.
Configuration
Go to Settings > Users & Companies > Users.
Give to your user the permission “Show Full Accounting Features”.
Usage
Go to Invoicing > Overview.
Locate the bank kanban card and import or create a new statement on it.
When reconciling, it should just work. What the module does is to search for a finished payment order that has the same amount as the statement line. If any, generated move lines (bank or AR/AP ones) are automatically proposed for the reconciliation.
Known issues / Roadmap
It would be good to check references too, but bank usually change some characters, so this doesn’t seem to be a general solution.
Take into account different currencies (in payment order or in bank statement).
Try to match payment orders resulting entries grouped by due date, instead of a whole, but this will affect performance for sure.
When the reconcile models end with more inheritable code, implement this as a new type of reconciliation in this model.
Develop real UI tests, instead of mimicking the call to the involved method.
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
Holger Brunn
-
Pedro M. Baeza
João Marques
Carlos Roca
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.
Current maintainer:
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 odoo-addon-account-reconcile-payment-order 15.0.1.0.1
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 |
|---|---|---|---|---|
| odoo_addon_account_reconcile_payment_order-15.0.1.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_account_reconcile_payment_order-15.0.1.0.1-py3-none-any.whl |
Release files / odoo_addon_account_reconcile_payment_order-15.0.1.0.1-py3-none-any.whl
| Download URL | odoo_addon_account_reconcile_payment_order-15.0.1.0.1-py3-none-any.whl |
|---|---|
| Size | 33.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f351bc068c00accb9f21288322c9ee738b4444e1bdb686b2392112ee2abb280e
|
|
BLAKE2b-256 checksum How to use checksums |
4d328916dc8b9cc76d07c342a74aa48804c645cff87f28ed71f74dfb8a3d8734
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo-addon-account-reconcile-payment-order 15.0.1.0.1
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.
