Every year-end, the same scene plays out in the Belgian SMEs that run payroll in Odoo: the salary indexation rate comes in, and contracts have to be reviewed one by one, without missing any, and then you must check what has already been calculated. Odoo 20 brings the whole operation into a single wizard, « Salary Increase ». Here is exactly what it does, how to launch it, and what it will never do for you.
1. The problem: it is not the calculation, it is the repetition
Applying a percentage is not complicated. What is costly is doing it twenty or thirty times, on the right contract, on the right date, while keeping a record. And depending on the rules that apply to you, salary indexation is not always a simple percentage: there may be a cap, or a fixed amount added on top.
Then comes the calendar trap. January payslips are sometimes already validated when the increase is entered: you have to find them and correct them, without missing any.
Odoo 19 already offered an indexation action, but it was limited to a percentage applied to the selected contracts. We compared the code of the two versions: the effective date, the cap, the fixed amount and the detection of already validated payslips are specific to Odoo 20.
💡 Key takeaway
The risk of salary indexation is not a calculation error, it is the forgotten contract and the already validated payslip nobody thinks to correct.
2. Step by step in Odoo 20
The wizard is part of the Payroll application of Odoo 20 Enterprise (standard module hr_payroll), with no development.
- Open the Employees list and tick those concerned. A filter by department or contract type helps isolate a group.
- In the Actions menu, choose « Salary Increase ». The action is also available from a single employee's record.
- Fill in the « Date of Salary Increase » and the « Increase Rate ».
- In « Applies on », choose « Full Wage » or « Capped Wage »; in the second case, enter the « Capped Wage Amount ».
- If needed, add a fixed « Extra Amount », then click « Confirm ».
The calculation is the one in the code: new salary = salary + extra amount + (salary, limited to the cap) × rate. With a 2% rate, a cap of 4 500,00 € and an extra amount of 25,00 €, a salary of 5 200,00 € becomes 5 315,00 €, and a salary of 3 800,00 € becomes 3 901,00 €.
Odoo does not overwrite the old salary: it creates a new version of the contract for each employee, dated from the effective day, and also indexes later versions of the same contract. A note in the employee's history records the rate, the cap, the amount and the date.
Then comes the safety net. If there are validated or paid payslips for a period starting on or after the effective date, the wizard switches to « Payslip Correction » mode and shows the number of payslips that « have been affected by this past salary increase and may need to be corrected ». The « Manage Payslips » button opens the list. Odoo spots them; the correction remains your decision.
💡 Key takeaway
One selection, one screen, one confirmation: the contract history is kept and the already validated payslips are flagged to you.
3. Limits and prerequisites
- You enter the rate. Odoo fetches neither the health index nor the rate of your joint committee. Choosing the right rate remains the manager's responsibility.
- One rate per run. If your blue-collar workers and your white-collar employees fall under different joint committees, do one run per group.
- A contract must exist on the effective date. Otherwise, the wizard refuses and lists the employees concerned.
- No decrease and no empty run: a negative rate or amount is refused, and at least a rate or an amount is required.
- Only validated or paid payslips are flagged. Payslips still in draft are not in the list: remember to recompute them.
- Payroll must run in Odoo. If your payroll is entirely handled by a social secretariat, this wizard does not directly concern you.
💡 Key takeaway
The wizard automates applying the rate, not choosing the rate. That is deliberate, and healthy.
4. Who it is useful for
For managers and HR managers of Belgian SMEs who already run payroll in Odoo, or who are hesitating to bring it in-house. The benefit grows with the number of contracts and the complexity of your rules: as soon as a cap or a fixed amount comes into play, contract-by-contract entry becomes a source of errors.
Bonus: an employee without an up-to-date contract blocks the wizard. Better to find that out in December than at payment time.
⚔️ The Match: by hand vs Odoo 20
| Criterion | By hand | Odoo 20 |
|---|---|---|
| Entry | One contract after another | One screen for the whole selection |
| Cap and fixed amount | Separate calculation, to be carried over | Two dedicated fields |
| History | Salary often overwritten | New dated version + note |
| Already validated payslips | To be found yourself | Listed for correction |
| Choice of rate | The manager | The manager |
Functional comparison based on the Odoo 20 Enterprise code (hr_payroll module), with no timing measurement: the duration depends on your number of contracts.
The Verdict: salary indexation becomes an operation, no longer a chore
Odoo 20 does not decide the rate, but it applies it everywhere at once, keeps the history and flags the payslips to redo.
Does your team know how to use it before January? Half a day of
Odoo training
is often enough; and if your payroll still lives outside Odoo, a
process audit
will tell you whether it is worth bringing it in.
Every year-end, the same scene plays out in the Belgian SMEs that run payroll in Odoo: the salary indexation rate comes in, and contracts have to be reviewed one by one, without missing any, and then you must check what has already been calculated. Odoo 20 brings the whole operation into a single wizard, « Salary Increase ». Here is exactly what it does, how to launch it, and what it will never do for you.
1. The problem: it is not the calculation, it is the repetition
Applying a percentage is not complicated. What is costly is doing it twenty or thirty times, on the right contract, on the right date, while keeping a record. And depending on the rules that apply to you, salary indexation is not always a simple percentage: there may be a cap, or a fixed amount added on top.
Then comes the calendar trap. January payslips are sometimes already validated when the increase is entered: you have to find them and correct them, without missing any.
Odoo 19 already offered an indexation action, but it was limited to a percentage applied to the selected contracts. We compared the code of the two versions: the effective date, the cap, the fixed amount and the detection of already validated payslips are specific to Odoo 20.
💡 Key takeaway
The risk of salary indexation is not a calculation error, it is the forgotten contract and the already validated payslip nobody thinks to correct.
2. Step by step in Odoo 20
The wizard is part of the Payroll application of Odoo 20 Enterprise (standard module hr_payroll), with no development.
- Open the Employees list and tick those concerned. A filter by department or contract type helps isolate a group.
- In the Actions menu, choose « Salary Increase ». The action is also available from a single employee's record.
- Fill in the « Date of Salary Increase » and the « Increase Rate ».
- In « Applies on », choose « Full Wage » or « Capped Wage »; in the second case, enter the « Capped Wage Amount ».
- If needed, add a fixed « Extra Amount », then click « Confirm ».
The calculation is the one in the code: new salary = salary + extra amount + (salary, limited to the cap) × rate. With a 2% rate, a cap of 4 500,00 € and an extra amount of 25,00 €, a salary of 5 200,00 € becomes 5 315,00 €, and a salary of 3 800,00 € becomes 3 901,00 €.
Odoo does not overwrite the old salary: it creates a new version of the contract for each employee, dated from the effective day, and also indexes later versions of the same contract. A note in the employee's history records the rate, the cap, the amount and the date.
Then comes the safety net. If there are validated or paid payslips for a period starting on or after the effective date, the wizard switches to « Payslip Correction » mode and shows the number of payslips that « have been affected by this past salary increase and may need to be corrected ». The « Manage Payslips » button opens the list. Odoo spots them; the correction remains your decision.
💡 Key takeaway
One selection, one screen, one confirmation: the contract history is kept and the already validated payslips are flagged to you.
3. Limits and prerequisites
- You enter the rate. Odoo fetches neither the health index nor the rate of your joint committee. Choosing the right rate remains the manager's responsibility.
- One rate per run. If your blue-collar workers and your white-collar employees fall under different joint committees, do one run per group.
- A contract must exist on the effective date. Otherwise, the wizard refuses and lists the employees concerned.
- No decrease and no empty run: a negative rate or amount is refused, and at least a rate or an amount is required.
- Only validated or paid payslips are flagged. Payslips still in draft are not in the list: remember to recompute them.
- Payroll must run in Odoo. If your payroll is entirely handled by a social secretariat, this wizard does not directly concern you.
💡 Key takeaway
The wizard automates applying the rate, not choosing the rate. That is deliberate, and healthy.
4. Who it is useful for
For managers and HR managers of Belgian SMEs who already run payroll in Odoo, or who are hesitating to bring it in-house. The benefit grows with the number of contracts and the complexity of your rules: as soon as a cap or a fixed amount comes into play, contract-by-contract entry becomes a source of errors.
Bonus: an employee without an up-to-date contract blocks the wizard. Better to find that out in December than at payment time.
⚔️ The Match: by hand vs Odoo 20
| Criterion | By hand | Odoo 20 |
|---|---|---|
| Entry | One contract after another | One screen for the whole selection |
| Cap and fixed amount | Separate calculation, to be carried over | Two dedicated fields |
| History | Salary often overwritten | New dated version + note |
| Already validated payslips | To be found yourself | Listed for correction |
| Choice of rate | The manager | The manager |
Functional comparison based on the Odoo 20 Enterprise code (hr_payroll module), with no timing measurement: the duration depends on your number of contracts.
The Verdict: salary indexation becomes an operation, no longer a chore
Odoo 20 does not decide the rate, but it applies it everywhere at once, keeps the history and flags the payslips to redo.
Does your team know how to use it before January? Half a day of
Odoo training
is often enough; and if your payroll still lives outside Odoo, a
process audit
will tell you whether it is worth bringing it in.