For me Human Resources is a completly diferent area than payroll and its not a hard requierment.
We can implement payroll in tryton and manage HR in a separate solution. The long term goal will be to have a complete solution with both features but normally its better to start with a small set of features and add and link together other ones latter.
If you are interested on it. Probably its worth creating a new topic for its design.
Hi Alejandro,
I am very sorry for the late reply, I have been very occupied with other work. I am not a fulltime developer, and I code Tryton on my free time. I have no working code yet, just ideas so if you have a repo, please go ahead. I can contribute with my ideas and coding to your repo.
Regards,
Ricardo V.
I propose implementing a rules-based model for payroll. Users would define the necessary fields to create a liquidation template. When generating an official payroll, the system will use that template as a base to create the final document. In the final document the user can click in a botton like “Compute” to create the final liquidation.
Yes, I have already move in the plan the fields like Numeric to Monetary using the company currency.
For this will be necesary a new model like “payroll.holiday” where the user can define the holidays for your country, and each company could create your own workables days. For example: the user can define that each saturday in the year will be a holiday. is in that way the pruposal of a model for holiday days?
Yes, We can take de analytic accounts for payroll for a separate module as is usual in Tryton account.
In the model payroll.rule_var I was thinking in a way to say to the formula what fields a necesary to compue the payroll rule. With this variables defined the rule could compute the amount for this line. Options are rate will be define in the payroll rule as a field.
I was keeping in mind a strategy to say to the payroll.rule what fields are necesary to compute the amount. But in the last days I have remember that this will be not necesary taking as example the formula in the price list module for example. Maybe I can reuse this strategy too.
We can define a initial requirements for RH module in another thread, maybe?
This is the point that I do not clearly understand.
I guess by liquidation, you mean the account move.
In this case, I do not think it is good to have one move per employee because it will reveal the salary to any accountant.
I think they must be grouped in a single move and the details are kept only on the payroll module part.
So you mean it is never happening that a payroll is computed in a different currency than the company’s. I’m not so sure.
I have opened a new topic with the initial idea for this module at: Commits · topic/default/payroll-module · Tryton / Tryton · GitLab.
This first concept consists of two initial models: payroll.payroll and payroll.line. A payroll is the document that contains the earnings and deductions for an employee during a specific period. It includes a field named amount_to_pay, which is calculated as the sum of all earnings minus the sum of all deductions.
Thank you.
Hi Alejandro,
Could you please create a MR for your topic so we can review and propose changes on it?
Thanks in advance!
I added a Merge Request for the topic.