| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Payroll (hr_payroll) • Discuss (mail) • Employee Contracts (hr_contract) • Employees (hr) |
| Lines of code | 2310 |
| Technical Name |
employee_bonuses_manager |
| License | OPL-1 |
| Versions | 17.0 18.0 |
Employee Bonus Manager
It Helps To Manage The Bonuses Of The Employees and mange multi employees by bonus request batch
Key Highlights
Manage the employee bonuses.
Manage the employees bonuses batch requests.
A beautiful Dashboard to easily detect the state of all bonuses
The user, department head, or managers can create the bonus request for the employees
The bonus will be approved after the two level approvals.
The final approved bonus amount is reimbursed in next payslip of the employee
The bonus can be temporary or permanent so you can control the bonus end date.
Generate PDF reports for both individual bonus requests and batch bonus requests.
The Dashboard
There will be three user groups.
User with Billing access.
Department Head with Billing access.
Manager with Billing access.
Dashboard Colors configuration.
Bonus Request Menus.
First, you can create bonus reasons which has to be provided when creating the bonus request (Configuration Menu).
Second, you can create bonus type that has name , code to use in salary rule , category of salary rule, and structure to be under the employee's salary structure which has to be provided when creating the bonus request (Configuration Menu).
This is the main menu which includes the all menus that refers to the bonuses approval states
Once it is submitted, the state will be changed to SUBMITTED and the name of the submitted person and submitted date will be recorded. Next, it has to be approved by the department head/ manager.
Once the request is approved by the department head, it will move on to the DEPARTMENT APPROVED state. The name of the department head and approved date will be recorded. Next, it has to be approved by the manager.
Once the request is approved by the manager, it will move to the MANAGER APPROVED state. The name of the manager and approved date will be recorded. The changes will also be visible in the chatter.
If rejected, it will go to the REJECTED state. And if needed, it can be reset to the DRAFT state.
If expired, it will go to the EXPIRED state. And if needed, it can be reset to the DRAFT state, there's a field called Bonus State if Temporary will asked an Bonus Expiration Date , i made A scheduled action runs daily to check if the bonus has exceeded the expiration date or not."
If canceled, it will go to the CANCELED state. And if needed, it can be reset to the DRAFT state.
The salary rule for bonus.
When calculating payslip for employee, the bonus amount is loaded as Other Input for those who have the final approved bonus request for the dates of payslip.
A report of bonus request for each employee.
Bonus Batch Menus.
This is the main menu which includes the all menus that refers to the bonuses approval states
Once it is created, the state will be changed to DRAFT and you can submit the request or cancel it.
Once it is submitted, the state will be changed to SUBMITTED and the name of the submitted person and submitted date will be recorded. Next, it has to be approved by the department head/ manager.
Once the request is approved by the department head, it will move on to the DEPARTMENT APPROVED state. The name of the department head and approved date will be recorded. Next, it has to be approved by the manager.
Once the request is approved by the manager, it will move to the MANAGER APPROVED state. The name of the manager and approved date will be recorded. The changes will also be visible in the chatter.
Once the request is approved by the manager, a button called 'Generate Bonus Requests' , Once clicked the it will move to the Done state . and a bonus request was created for each employee in bonus batch with the amount of bonus, and cancel button will be avaliable for group MANAGER APPROVED only.
Once the request done, it will go to the Done state. And if needed, it can be cenceled by manager and move it to the CANCELED state.
If canceled, it will go to the CANCELED state. And if needed, it can be reset to the DRAFT state.
If rejected, it will go to the REJECTED state. And if needed, it can be reset to the DRAFT state.
If expired, it will go to the EXPIRED state. And if needed, it can be reset to the DRAFT state, there's a field called Bonus State if Temporary will asked an Bonus Expiration Date , i made A scheduled action runs daily to check if the bonus has exceeded the expiration date or not."
Our Services
Odoo Customization
Odoo Implementation
Odoo Support
Odoo Integration
Odoo Migration
Support
Need Help?
odoo.lab.info@gmail.com
Got questions or need help? Get in touch.
odoo.lab.info@gmail.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module