Maria's case: when payroll doesn't add up
Maria is the HR manager at a mid-sized company that had just migrated to Odoo. Everything was fine until month-end closing: the payroll for its 50 employees showed strange differences in the AFP and health deductions. Some employees had incorrect amounts, others simply did not appear in the payment report. Maria spent two nights reviewing contracts and salary rules, without success. She called her implementer's support, but the problem persisted. Desperate, she started searching on her own and found that the solution lay in configuration details that had been overlooked. If you work with Odoo and face similar problems, this article will guide you to solve them quickly and efficiently, and along the way, we'll tell you how Ganemo can help you implement best practices.
Error in the base salary calculation
One of the most common errors is that the base salary is not calculated correctly. This happens when the salary structure is not linked to the contract type or when the Base Salary field in the contract is left at zero. Check that every contract has a base salary assigned and that the selected salary structure is the correct one. For example, if you have part-time employees, make sure the salary rule that calculates the base salary is configured to multiply the amount by the work-hours percentage.
In Maria's case, one of the employees had a part-time contract, but the salary rule used the full base salary. After correcting the rule and assigning the work-hours percentage, the calculation was exact. If you need help configuring these rules, teams like Ganemo offer specialized consulting so you don't waste time on trial and error.
Problems with statutory deductions (AFP, Health, ONP)
Mandatory deductions usually fail for two reasons: the withholding table is outdated or the employee doesn't have the correct regime assigned. First, check that the AFP and ONP withholding tables are up to date according to the latest legal provisions. In Odoo, these tables are loaded via fiscal data. Second, make sure the pension regime (for example, AFP or ONP) is selected in the employee's contract. If the regime is empty, no deduction will be applied.
At Maria's company, a group of employees had no regime assigned because the contract was created without that field. After updating the contracts, the deductions appeared correctly. To avoid these oversights, you can set up automatic alerts or periodic reviews. Ganemo implements validation workflows that ensure no field is left empty before a payroll is approved.
Errors in overtime or bonus calculations
When employees have overtime or variable bonuses, the calculation can fail if the rules are not configured correctly. Check that the overtime salary rules use the correct attendance category and that the calculation method is appropriate (for example, a percentage of the base salary or an hourly rate).
Maria had an employee with a productivity bonus that was not included in the payroll. The rule was set to add a fixed amount, but the contract did not define the bonus amount. By adding the custom field to the contract, the rule could read it and the bonus was calculated automatically. If your case is more complex, Ganemo designs custom salary rules so that each bonus or concept is calculated without errors.
Problems with the settlement report (CTS, Gratification, Vacation)
Settlement reports require that the concepts have been correctly accrued in previous periods. If an employee has no base salary records in prior months, the settlement will be zero. Make sure all employees have had at least one month of base salary recorded. Also, check that the hire date in the contract is correct, since calculations such as CTS depend on it.
Maria had an employee whose settlement showed zero CTS. It turned out the hire date in the contract was wrong (it showed 2023 instead of 2021). Correcting the date was enough for the system to calculate the CTS for the two prior periods. To avoid these errors, we recommend periodic audits of master data. Ganemo offers monthly review services to ensure all base information is correct.
Errors when processing payroll (Worked Days vs. Payslip)
Sometimes the system shows an inconsistency between the days worked and the salary calculation. This is usually because the attendance entries (Worked Days) were not generated or are duplicated. Check that the corresponding work entries were created for the payroll period. If you use the Attendance module, verify that the records are approved.
Maria had an employee who showed zero hours worked on the payslip, even though attendance had been recorded. The reason was that the attendance records had not been transferred to the Payroll module because the sync option was disabled. Once enabled, the data was updated. If this process seems complicated to you, Ganemo sets up the automatic integration between Attendance and Payroll so it always keeps working.
Ganemo's solution for implementing Odoo without headaches
As you've seen, many payroll problems in Odoo are solved with basic configuration, but when the company grows or cases become complex, it's easy to make mistakes that affect dozens of employees. That's why having a partner like Ganemo makes a difference: we offer Odoo implementations that include payroll configuration, salary rules, attendance integration and periodic data review. Don't let a payroll error damage your relationship with your employees. Contact us for a free assessment of your payroll module.