SomItCoop ODOO payment return late fee for contracts
This module applies late fee charges on contract returns.
The module activates when a payment return is confirmed and applies additional charges to associated contracts if found or otherwise creates an invoice for the selected partner.
Table of contents
Configuration
To configure this module you will need to go to general settings and inside invoicing tab find the section Manage fees for returned Payments on partners. There, you can set the charge mode along with the fee product that you want to be applied and the accounting journal (the journal is only used by the modes that create invoices).
The charge mode (use_feature_fee_for_returned_payment) accepts the following values:
Contract only: the fee is added as a line to the first active contract of the partner. If the partner has no active contract, no charge is created at all (no invoice is ever generated).
Invoice only: the fee is directly charged as a new invoice, without looking for active contracts of the partner.
Contract or invoice: legacy behavior — the fee is added to the first active contract if found, otherwise an invoice is created.
Product and journal have to be configured before using the features that this module provides.
Usage
To use this module, you will need to make sure that you have set the right configuration to your needs and then you are ready to go! Every time a payment return associated with a partner is confirmed, this module will charge the fee according to the selected mode: it will add a line to the oldest active contract (contract only, contract or invoice), or create an open invoice with only that same fee (invoice only, contract or invoice when no contract is found).
Known issues / Roadmap
There are no issues for the moment.
Bug Tracker
Bugs are tracked on GitLab 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
-
Guillem Alborch <guillem.alborch@somit.coop>
José Robles <jose.robles@somit.coop>
Enrico Stano <enrico.stano@somit.coop>
Juan Manuel Regalado Gómez <juanmanuel.regalado@somit.coop>
-
Gerard Funosas <gerard.funosas@somconnexio.coop>
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.
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-payment-return-contract-late-fee 16.0.2.0.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| odoo_addon_account_payment_return_contract_late_fee-16.0.2.0.0.8.tar.gz | 44.9 kB | Without provenance | Details |
Release files / odoo_addon_account_payment_return_contract_late_fee-16.0.2.0.0.8.tar.gz
| Download URL | odoo_addon_account_payment_return_contract_late_fee-16.0.2.0.0.8.tar.gz |
|---|---|
| Size | 44.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36a1e83879b0f76e38ea333ec2db9b2adcbc2fc2e96c48e7a3b6aa910c798575
|
|
BLAKE2b-256 checksum How to use checksums |
d74aa02cd4c9643fcae50beb3280f16e227855bd56722485a9c276b40a630c09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.2
|
Security for odoo-addon-account-payment-return-contract-late-fee 16.0.2.0.0.8
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.
