Paying overtime by hand is where payroll accuracy quietly bleeds out. Spreadsheets tracking who worked late, which day counted as 1.5x versus 2x, and whether a shift crossed into a public holiday are error-prone, slow, and impossible to audit. This ECOSIRE build-to-order module makes overtime a first-class, rule-driven part of your Odoo HR stack — so overtime hours are computed the moment attendance is recorded, priced against the correct rate, routed for approval, and pushed straight into payroll.

This is not an off-the-shelf apps.odoo.com download. ECOSIRE designs, builds, installs and supports a net-new module tailored to your overtime policy, your rate structure, and your working calendars. Typical delivery is one working week depending on the complexity of your rules and integrations.

At the core is a configurable rule engine. We model overtime rules as a dedicated Odoo model (models.Model) with fields for rule type (weekday, weekend, public holiday), the applicable multiplier or fixed rate, the qualifying threshold, and the counting period. A compute field decorated with @api.depends reads each employee's attendance records (hr.attendance) and the relevant working schedule and holiday calendar, then derives overtime hours automatically — no manual data entry, no re-keying between systems.

Public holidays and weekends are handled explicitly. The engine reads your company calendar and resource.calendar working hours so a shift that starts Friday evening and runs into a weekend, or lands on a declared public holiday, is split and priced at the correct rate. Thresholds let you define, for example, that only hours beyond 8 in a day or 40 in a week qualify — and the counting period (daily, weekly, or a custom pay cycle) is yours to set.

Every computed overtime block flows through an approval workflow. Managers see pending overtime in a dedicated view (Odoo list/form views in XML, or OWL components where a richer UX helps), approve or reject with a reason, and the state transition is captured for audit. Access is locked down through ir.model.access.csv and record rules so an employee sees only their own overtime while managers and payroll officers get the scope they need — and nothing more.

Approved overtime integrates with Odoo Payroll (Enterprise) as payslip inputs, or with your existing payroll export if you run Community — mapping overtime hours and amounts to the correct salary rules. QWeb reports give you per-employee and per-period overtime statements for finance and for the employee record. Automated actions and scheduled jobs (ir.cron) can roll up overtime at period close, flag anomalies, and notify approvers. And because it is native Odoo, everything is reachable over XML-RPC and JSON-RPC for downstream systems or a headline dashboard.

Built and tested against Odoo 17, 18 and 19, Community or Enterprise. You get the source, the configuration, documentation, training, and a support window — delivered by an ECOSIRE Odoo engineer, not a black box.