When creating an account_payment_line, chose by default an employee’s bank account if two conditions are met:
The selected partner is also an employee
The payment is part of a wage retribution.
Otherwise, keep the first partner’s active bank account (as default).
This us usefull when an employee has a different bank account for wage payments.
Table of contents
Configuration
We use the l10n_es module for their account_group_46 account payment group which is used for wage payments.
To use this module we also need employees related to partners by their address_home_id field.
Usage
Prepare a partner with an employee associated (from now on “partner employee”) with a bank accounts that it is not the first active one from its related partner.
For a partner employee, generate one ore more account_move with the account of its journal items belonging to the l10n_es.account_group_46 group.
[Invoicing > Accounting > Accounting Entries > Journal Entries]
Create a payment order from the generated journal items
[Invoicing > Payments > Payment Orders > Create > Create Payment Lines from Journal Items]
Select the partner employee as the partner for the payment order and add the move lines.
Check that the employee bank account is selected by default in the payment line form
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
-
Álvaro García <alvaro.garcia@somit.coop>
José Robles <jose.robles@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 odoo12-addon-account-payment-line-employee-wages 12.0.1.0.0
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 | |
|---|---|---|---|---|
| odoo12-addon-account_payment_line_employee_wages-12.0.1.0.0.tar.gz | 25.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo12_addon_account_payment_line_employee_wages-12.0.1.0.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 50.7 kB
Release files / odoo12-addon-account_payment_line_employee_wages-12.0.1.0.0.tar.gz
| Download URL | odoo12-addon-account_payment_line_employee_wages-12.0.1.0.0.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4dc1a449290ce87feabed457673eb5386451f141291a7e0be7948a97cedbc769
|
|
BLAKE2b-256 checksum How to use checksums |
790425a9118f4c26544556fe9e4240a3a933553a9fe75f603d3cd3c2d6189673
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.2
|
Release files / odoo12_addon_account_payment_line_employee_wages-12.0.1.0.0-py2.py3-none-any.whl
| Download URL | odoo12_addon_account_payment_line_employee_wages-12.0.1.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 25.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f20e090defa2ed2980ebd7fa1c4df9775656581edb623edde89931a228777c35
|
|
BLAKE2b-256 checksum How to use checksums |
1f33ee22a27372ba71cbc93deb7e51422ad04d8d87f7da915d91a602b9a77ad7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.2
|
Security for odoo12-addon-account-payment-line-employee-wages 12.0.1.0.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.
