Sales commission check deposit
The module allows you to integrate check deposit with agent commissions.
When generating agent settlements, select a payment date until which commissions should be settled.
Invoices with checks payment will be taken into consideration only if the number of days set in the “Safety days for commission” field in journal configuration from due date set in check payment have passed from settlement payment date.
Eg:
Invoice 0001 is paid with check
Check due date: January 1st
“Safety days for commission” set in check journal: 10
- In settlement wizard:
Settle commissions until payment date: January 5th => commission is not settled for check
Settle commissions until payment date: January 15th => commission is settled for check
Table of contents
Usage
For setting journal as Check journal with safety days:
Go to Journal.
Check “Is check Journal” and add safety days.
For pay and register a checks deposit:
Create an invoice and using Checks to pay it.
Add a new checks deposit adding that payment.
For settling the commissions to agents:
Go to Sales > Commissions Management > Settle commissions.
On the window that appears, you should select the date up to which you want to create commissions. It should be at least one day after the last period date. For example, if you settlements are monthly, you have to put at least the first day of the following month.
You can settle only certain agents if you select them on the “Agents” section. Leave it empty for settling all.
Click on “Make settlements” button.
If safety days have passed between settlement payment date and check due date, commission will be settled properly.
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
Nextev Srl
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 maintainers:
This module is part of the OCA/commission 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-sale-commission-check-deposit 14.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 |
|---|---|---|---|---|
| odoo14_addon_sale_commission_check_deposit-14.0.1.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_sale_commission_check_deposit-14.0.1.0.2-py3-none-any.whl |
Release files / odoo14_addon_sale_commission_check_deposit-14.0.1.0.2-py3-none-any.whl
| Download URL | odoo14_addon_sale_commission_check_deposit-14.0.1.0.2-py3-none-any.whl |
|---|---|
| Size | 35.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
210a3b92ad55eb5283ff825259c71017cc1fae94a4b631cf1cf837b586ec3075
|
|
BLAKE2b-256 checksum How to use checksums |
a1106ca0745b752a2826dc0cc54cd42ce62acad9d978d77295f94b5871ca93d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo14-addon-sale-commission-check-deposit 14.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.
