Account Invoice Payment Retention
This module provide a feature to plan for retention during invoice / payment. And return it at later time.
At Vendor Bill (or Customer Invoice), user can plan the retention by percent/amount
At Payment, to retain the amount as planned (enforce / not enforce)
At a later time, with another Vendor Bill (or Customer Invoice), user can select the retained payment in order to return it
Note: This feature works on both customer invoice and vendor bill alike.
Table of contents
Configuration
Go to menu > Invoicing > Configurations > Settings
Enable Invoice’s Retention on Payment
Select the Retention Account, make sure this account allow reconciliation
Once setup, user will see new Retention fields in Customer Invoice / Vendor Bill.
Usage
To plan for retention during invoice
Create new Vendor Bill (or Customer Invoice).
Specify amount to retain, by percent or amount.
Validate invoice as per normal.
To make payment retention
From the invoice, click Register Payment.
On the payment window, system suggest the retention amount, click on helper toggle to apply it.
By default, enforce retention is checked to ensure that, a valid retention amount and retention account is applied.
Once ready, make payment as per normal. Journal Entry created with a retention account move line (to be cleared at later time).
Note: System just help to validate retention. At the end, user can ignore the retention.
To return the retained amount
As time arrived to return the retained amount. Create the new Vendor Bill (or Customer Invoice).
Select the partner. Return Retention field will list only uncleared retained amount for this partner.
Select one or multiple payments (journal entry), system will auto populate the retained amount.
Validate invoice as per normal, system will now clear (reconcile) that retention.
Proceed to payment as per normal.
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
-
Kitti U. <kittiu@ecosoft.co.th>
Saran Lim. <saranl@ecosoft.co.th>
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-invoicing 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 odoo14-addon-account-invoice-payment-retention 14.0.1.2.0
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 |
|---|---|---|---|---|
| odoo14_addon_account_invoice_payment_retention-14.0.1.2.0-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_account_invoice_payment_retention-14.0.1.2.0-py3-none-any.whl |
Release files / odoo14_addon_account_invoice_payment_retention-14.0.1.2.0-py3-none-any.whl
| Download URL | odoo14_addon_account_invoice_payment_retention-14.0.1.2.0-py3-none-any.whl |
|---|---|
| Size | 38.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2883ab6fc1648a4fca7f632a842b4d15fe0f00f0d1c2980d3a916cfeedaad7f3
|
|
BLAKE2b-256 checksum How to use checksums |
eaee429fe766767c01657d3336cefdfae5af6095948e1b4790a726229da6d5c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo14-addon-account-invoice-payment-retention 14.0.1.2.0
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.
