Attendance generation for missing days with installed contract
This modules changes the generation of the attendances for the missing days to use the HR contracts accordingly.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0This hidden module makes the automatic creation of missing attendance records follow the employee's HR contract dates and working calendar, so attendances are only generated for periods covered by a contract.
When Odoo generates attendance records for working days that have no attendance, this module changes how the working time is calculated. Instead of using a single general calendar, it looks at the employee's HR contracts that are active or closed during the requested period.
For each contract, it takes the contract's start date and end date and the working schedule (resource calendar) attached to that contract. It then builds the list of working intervals only for the time the contract is valid, using the employee's time zone to convert dates correctly.
As a result, missing attendances are created only for days and hours that fall inside a contract period, and they follow the working hours defined on that contract's calendar. If a contract has no end date, the intervals continue until the end of the requested period.
This module is installed automatically when both HR contracts and the missing attendance generation features are present. It does not add menus, buttons, or reports; it only changes the behaviour of the attendance generation process on the hr.employee model.
Depends on
Models and fields (1)
- hr.employee · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/hr-attendance.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.