This release is a pre-release and may not be stable for production use.
Bank Statement Operation Rules with Dunning Fees
Extends the Bank Statement Operation Rules with a new rule, the Dunning Fees rule. It allows to automatically create a write-off entry for the amount paid by the customers when they received dunning fees (using the Account Credit Control module).
Configuration
As this module aims to automatize the Statement Operation Templates, you first want to ensure that you have an operation configured for the dunning fees. You can find them in Invoicing > Configuration > Miscellaneous > Statement Operation Templates. An example of operation is (the account is where the amount received for the dunning fees will be input):
Account |
Amount Type |
Amount |
Label |
|---|---|---|---|
Depends of the l10n |
Percentage of open balance |
100.0 % |
Dunning Fees |
The configuration of the rules themselves happens in Invoicing > Configuration > Miscellaneous > Statement Operation Rules.
There is no conditions to setup on this rule. It will be applied if the amount in the bank statement line is above the journal entries amount and if the difference is comprised in the amount of the dunning fees for the journal entries.
Example:
Document |
Amount |
|---|---|
Journal Entry (invoice) |
100.- |
Dunning Fees no1 |
5.- |
Dunning Fees no2 |
10.- |
Dunning Fees no3 |
15.- |
The customer received 3 times dunning fees, with a increasing amount. The customer might pay from 100.- to 115.-. The difference between 100.- and what the customer paid above goes to the write-off account configured on the operation. If the customer pays 99.- or 116.-, the Dunning Fees rule is not valid and the other rules will be evaluated.
Dependencies
This module only works with the account_credit_control_dunning_fees module in the project: https://github.com/OCA/account-financial-tools
Credits
Contributors
Guewen Baconnier <guewen.baconnier@camptocamp.com>
Maintainer
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.
To contribute to this module, please visit http://odoo-community.org.
Metadata
Release files for odoo8-addon-account-statement-operation-rule-dunning-fees 8.0.1.0.0.99.dev8
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 |
|---|---|---|---|---|
| odoo8_addon_account_statement_operation_rule_dunning_fees-8.0.1.0.0.99.dev8-py2-none-any.whl | Python 2 | none | any | Details for odoo8_addon_account_statement_operation_rule_dunning_fees-8.0.1.0.0.99.dev8-py2-none-any.whl |
Release files / odoo8_addon_account_statement_operation_rule_dunning_fees-8.0.1.0.0.99.dev8-py2-none-any.whl
| Download URL | odoo8_addon_account_statement_operation_rule_dunning_fees-8.0.1.0.0.99.dev8-py2-none-any.whl |
|---|---|
| Size | 26.0 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
b27ddc0d732c88ac89a02e8b35781ca90101fb3b93d5a63eb78a76da4e1f80e3
|
|
BLAKE2b-256 checksum How to use checksums |
28fcb44e5f8e96fc4511ab6bda8ff3194d00e66b369a067e004e8aa53b7b1e4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo8-addon-account-statement-operation-rule-dunning-fees 8.0.1.0.0.99.dev8
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.