Odoo HR: contract, work entries and payslips without end-of-month surprises

What Odoo 20 HR covers, how to configure it and what to check: contract, work entries, time off, attendances, payslips, recruitment and when custom work is needed.

ProductOdooHRpayrollERP19 November 2026 · 18 min read

Odoo HR is a suite of connected modules that manages the whole employee life cycle, from recruitment to leaving, with Payroll as the financial end point that consumes data from all the other modules. This article describes what the suite covers, how it is configured, which mistakes recur most often and how to decide between standard, configuration, integration and custom development. It refers to Odoo 20 Enterprise; where references are Italian (fixed-term and permanent contracts, collective agreements, the payroll localisation) it says so.

When an implementation is healthy

An HR implementation works when five conditions hold:

  • every employee has an active contract that drives payroll computation automatically;
  • time off, attendances and payroll share a single source of truth, work entries;
  • payslips come from Odoo data, with no manual recalculation in Excel;
  • the recruitment pipeline is tracked in Odoo and becomes the employee record directly at hire;
  • HR reports (headcount, absenteeism, overtime) are available in real time without exports.

The suite covers five areas: employees (the personnel register), payroll (salary computation and payslips), time off (leave, holidays and accruals), attendances (check-in and check-out, overtime) and recruitment (from application to hire).

Suite basics for people working in HR

People in HR move across several apps, but the data is unified.

ViewUse in HR
KanbanRecruitment stages, employee cards by department
ListAll employees, payslips, time off requests: bulk actions
FormA single employee record, payslip or contract
PivotAbsenteeism by department, overtime by month, headcount trends
CalendarTime off overview (who is away on a given day)
GraphTime off analysis, attendance difference, recruitment velocity analysis

Every HR list has predefined and custom filters. On employees: department, job position, coach, company, grouped by contract status. On payslips: period, structure type, state (draft, to pay, done). On time off: type, state (to approve, refused, validated), grouped by employee or department. On attendances: check-in date, grouped by employee, sorted by difference (overtime or absence). Recurring views are saved as favourites: "Pending time off approvals", "Payslips to validate this month", "Employees without a contract".

Every employee record, payslip and time off request has a chatter: the internal note for HR annotations (disciplinary, performance, onboarding steps), visible only to internal users; the message, an email sent from the record (offer letter, contract reminder) and logged automatically; the activity, with which HR follows onboarding tasks, contract renewals and appraisal deadlines. An example: for an employee whose contract is about to expire, HR schedules an "Upload Document" activity thirty days before the end date, which shows in the HR manager's bell and calendar; when the contract is renewed, an internal note mentions the payroll officer.

Access rights. There are three main levels in Employees and Payroll: the employee (self-service, sees their own payslips and sends their own time off and expense requests), the officer or team manager (approves time off for their team and sees team payslips) and the administrator (full access to configuration of salary structures, work entry types and time off types). Payroll data is sensitive: administrator access should be limited to named payroll officers.

Five principles

1. The contract is the single source of truth. Every payroll computation starts from the employee's active contract. The contract defines the wage (monthly, hourly or daily), the salary structure type (the set of rules that computes the payslip), the working schedule (how many hours a week: it affects time off accrual and overtime calculation) and the start and end dates (an expired contract blocks payslip generation). If a payslip is wrong, the cause is almost always wrong contract data, not a payroll defect.

2. Work entries are the bridge. They are the data layer that connects time off, attendances and payroll. The contract's working schedule generates the expected work entries for the period; validated time off overwrites them with the absence type; attendances (check-in and check-out) are the source when the wage type is hourly. Payroll reads the work entries and computes the payslip. They have to be reviewed and conflicts resolved before payslips are generated: an unresolved conflict (overlapping attendance and absence) produces a wrong payslip.

3. Time off types drive payroll behaviour. Each time off type determines how the absence affects the payslip. Paid holiday: no deduction. Sick leave: may trigger a deduction or a replacement. Unpaid leave: deduction proportional to the days. Public holiday: no deduction, managed automatically. A payroll configuration on the time off type that is not consistent (code, rate, structures in which it is unpaid) is the commonest cause of wrong deductions on payslips.

4. Allocations precede time off requests. For time off types that require an allocation (paid holiday, compensatory days) the employee cannot send a request without days allocated. The allocation can be manual (HR allocates one by one or in bulk to a department) or by an accrual plan: days accrue automatically over time (for example 1.83 days a month for 22 days a year). The plan sets whether accrued time not used is carried over or lost, when, and whether the employee moves to the next level at once or after the current period. A frequent mistake is going live without allocating time off: all the employees' requests stay blocked or are bypassed.

5. The payslip is a batch process. Monthly payroll is not a payslip-by-payslip job. The correct flow: review and close the period's work entries, generate the payslip batch (Payroll, Payslips, Batches, New), compute the sheet for all, review exceptions (conflicts, missing inputs, negative net), add other inputs if needed (commissions, bonuses, deductions), confirm the batch creating the draft entries, post the entries (accounting integration) and mark as paid registering the payment and the bank reconciliation. Any step done outside this flow (individual payslips for monthly staff, entries created by hand) indicates a broken process.

Configuration

Employee record. It has three tabs that are critical for HR and Payroll. In Work Information: working hours (linked to the resource calendar), timezone (important for multi-country set-ups), work location (office, remote, field), time off approver and expense approver. In Private Information: private address (used for payroll and legal documents), certificate level and field of study (required in some localisations), citizenship and visa details for non-EU employees. In HR Settings: the related user (links the employee to the Odoo login, for self-service), the employee type (employee, student, freelance) and the payroll structure type, which determines which rules apply. Without a related user the employee cannot reach the portal for payslips and time off requests.

Contract. The fields that drive payroll directly: the wage (monthly gross, or hourly if the type is hourly), the contract type (fixed-term, permanent, other), the salary structure ("Employee" for the standard, custom for executives and part-timers), the working schedule (40 hours a week standard, 20 for part-time, flexible for field staff), the start date (mandatory) and end date (fixed-term only) and the HR responsible who manages renewal alerts. The state goes from New to Running with Confirm, then Archived or expired. A contract in the "New" state, not confirmed, does not generate work entries: payroll for that employee will look empty.

Working schedule. A standard full-time schedule of 40 hours: Monday to Friday 08:00 to 12:00 and 13:00 to 17:00 (eight hours a day), Saturday and Sunday with no entry. A part-time schedule of 20 hours: Monday to Friday 08:00 to 12:00 (four hours a day), with the part-time flag set on the contract. For field or flexible staff: a single block with no fixed times, using attendances as the source of work entries and the hourly wage. For split or variable schedules (hotels, tourism, variable demand) a calendar of type Variable is used, with several time blocks a day, possibly recurring. Schedules belong to the company (leave the company field empty to share them across companies) and are also used by Manufacturing work centres. One schedule is used for each physical work pattern: reusing it for different patterns means a change alters all the employees using it at the same moment.

Time off types. The key settings of each type: whether it requires allocation (yes for holiday and compensatory days, no for sick and unpaid), the approval (none, by the time off officer, by the employee's approver, both), the duration type (full day, half day, custom hours), the payroll configuration (code, rate, structures in which it is unpaid), the accrual plan for types that accrue over time, the carry-over of unused days to next year (none, all, up to N days) and the negative balance (allowing requests beyond the allocation, risky).

Salary structures. The structure type (parent) follows the employee category: "Employee" for standard monthly staff, "Worker" for hourly, "Executive" with custom rules. The structure (child) follows the payslip type: "Employee Monthly Pay" recurring, "13th Month Bonus" occasional and separate, "Termination Pay" only at the end of the contract. Inside each structure are the salary rules: BASIC (gross wage from the contract), GROSS (BASIC plus allowances), TAXABLE (GROSS minus exemptions), INCOME_TAX (computed on the taxable amount with the tax table) and NET (GROSS minus all deductions). Adding a rule to a structure affects all the employees who use it: test first on a staging database.

Recruitment. The default stages: New, Initial Qualification, First Interview, Second Interview, Contract Proposed, Contract Signed. Each stage can trigger an automatic email to the applicant (template configurable per stage), a Kanban colour change and an automatic activity for the recruiter. Conversion into an employee: at Contract Signed you use Create Employee, the record is pre-filled from the application and department, job position and interviewer carry over. Still to do: add the contract, set the working schedule and create the related user. A recruitment pipeline not connected to employee creation means data is re-entered by hand at hire, an integration failure.

The flows

Monthly payroll cycle. Between the 1st and the 5th of the month HR reviews work entries (Payroll, Work Entries), resolves conflicts between attendances and time off, validates pending time off requests that fall in the period and checks employees with expired contracts. Between the 5th and the 10th the period's payslip batch is generated, other inputs are added (commissions, bonuses, salary attachments), the sheet is computed in bulk and payslips with negative net or anomalous amounts are reviewed. Between the 10th and the 15th, HR and Finance review and sign off: batch confirmation and creation of the draft entries, which pass to the Accounting module. On the pay date: mark as paid, register the bank payment and reconcile.

Time off request. The employee sends the request (self-service, or HR creates it on their behalf). The system checks whether there is an allocation balance and whether the dates overlap other time off. The approver is notified by activity and email. If they validate, the work entry is created by itself for the period; if they refuse, the employee is notified and the balance restored. Validated time off appears in the employee's calendar, the team calendar and the work entries of the pay period, and so affects the payslip.

Attendances and overtime. Check-in and check-out are recorded in kiosk mode (a dedicated device at the entrance), by hand from the Attendances app, from the punches of a ZKTeco BioTime server (Attendances ZKTeco BioTime module) or with entry or correction by HR. Attendance hours above those expected by the schedule give a positive difference (overtime), lower hours a negative difference (absence). Overtime is handled with an allocation of compensatory days (the extra hours become days off), with an extra-pay rule on the payslip (it requires configuring a salary rule) or with management approval before compensation.

Onboarding of a new hire, with activities. When the employee is created HR schedules activities: on day zero "Upload the signed contract" for the HR officer; on day one "Create IT access" for the IT manager and "Deliver equipment" for facilities; on day seven "Complete the onboarding form" for the employee in self-service; on day thirty "First month check-in" for the line manager. Odoo has no native onboarding checklist module: activities on the employee record are the right tool. If the team tracks onboarding on a spreadsheet, it is a missed implementation opportunity.

What changes with Odoo 20

Odoo 20 Enterprise is the baseline. Before classifying a need as development (Studio or custom), it is worth testing it against these features.

  • Time off. Approval "by the time off officer" applies to any officer; the Notify HR field is no longer on the time off type. There is a new option Display Time Off in Calendar and the negative cap can be expressed in hours or days. Missing or retroactive requests can be created from the All Time Off dashboard or the Overview by selecting cells; there is a new request form and a Gantt view, and the validity period of allocations is visible in My Allocations.
  • Accrual plans. What happens to unused accrued time (carried over or lost) and when it is reset or carried over are chosen separately; the employee can move to the next level at once or after the current accrual period.
  • Working hours. They can be Fixed or Variable: variable calendars allow several time blocks a day with recurrence, suited to split schedules (hotels, tourism, variable demand). The working schedule is now mandatory on the employee.
  • ZKTeco BioTime integration (BioTime 8.5 and 9.0 APIs): punches from a BioTime server become Attendances records; employees carry a ZKTeco Employee ID field.
  • Employee departures. An End of Collaboration action (reason: fired, resigned, resigned for retirement; dismissal date and departure date) with Planned Actions that archive the employee, set the contract end and delete future versions, unassign company car and equipment, delete future appraisals. Archiving is no longer a standalone path for leavers.
  • Payroll. New documentation on Salary Rules (code, category, structure, sequence, Appears on Payslip, Contributes to Employer Cost, conditions and computation: edit only if necessary, because the rules come from the localisation); the pages on salary, payslip and salary attachments are updated; new Headcount report (employees on payroll with employer cost and wage); the Payroll Analysis report has been removed.
  • Recruitment. The Hiring Velocity report is now Velocity analysis; new Offer Analysis report (offers by job position and stage, by default the last 365 days).
  • Approvals. Its own documentation, with preconfigured types (business trip, borrow items, general approval, contract approval, payment application, car rental, job referral award, procurement, create RFQs). Payment Application is for prior approval of company-paid costs, not reimbursements, which go through Expenses.
  • Users. Beside User and Administrator there is the Light internal role (limited access, linkable to an employee without login, upgraded automatically if it receives wider access).
  • Lunch and Frontdesk. The documentation of Lunch and Frontdesk is updated to 20.0.

For development requests the guidance is this: custom HR registries, spreadsheet skill matrices, manual handoffs between expenses and payroll, bespoke training trackers and separate time-clock systems are first tested against the standard and configuration of Odoo 20 HR, Expenses, Payroll, Attendances (including BioTime), Planning and eLearning.

The rationalisations you hear

In the company they sayWhat it really is
"We compute payroll in Excel and just import the journal entry"Payroll sits entirely outside Odoo. The integration gives no value beyond an entry that any accountant could create.
"We create payslips one by one every month"Batch processing exists precisely to avoid that. Creating payslips by hand at scale is error-prone and unauditable.
"We approve time off by email or WhatsApp and update Odoo afterwards"Balances are wrong until updated by hand. The period's work entries are incomplete and payslip deductions unreliable.
"We do not use contracts because salaries are confidential"No contract means no work entries and no payslips. Confidentiality is managed with access rights, not by skipping contracts.
"We will configure working schedules later, for now we use the default"Every employee on the wrong schedule has wrong overtime, wrong time off allocations and wrong payslips. It is fixed at go-live, not later.
"We manage attendance in another system and sync monthly"The sync is manual, late and breaks the work entry chain. Overtime and absences arrive too late to correct payslips before pay day.
"HR does not use Odoo for recruitment, we use LinkedIn"LinkedIn for sourcing is fine. Not tracking stages and outcomes in Odoo means no hiring funnel data and manual re-entry at hire.
"Employees check their payslips on paper"Self-service access to payslips from the portal costs nothing and removes a recurring HR administration task.

Warning signs

  • Employees without an active, confirmed contract.
  • Payslips computed outside Odoo (Excel, external payroll software) with only the journal entry imported.
  • Work entries not reviewed before payslip generation: batch created with conflicts present.
  • Time off approved outside Odoo (email, chat) and Odoo updated afterwards, or never.
  • A single working schedule for all employees, whatever the real hours.
  • Time off types with no payroll configuration (code, rate, unpaid structures): the absence has no payroll effect or the wrong one.
  • Allocations never created: employees send requests that are all in "negative balance".
  • No accrual plan for paid holiday: allocations created by hand every January.
  • Attendances tracked in a separate system, with the Odoo Attendances module unused or duplicated.
  • Recruitment pipeline in Odoo but the Create Employee button never used: every hire re-entered by hand.
  • Employee records with no related user: no self-service, and HR handles everything by hand.
  • Payroll officers with administrator access to all modules: no separation of duties.
  • Fixed-term contracts with no end-date monitoring: renewals missed, legal exposure.

How to verify a configuration

After configuring or assessing HR, verification goes through these checks:

  • every active employee has a confirmed contract with correct wage, working schedule and salary structure;
  • working schedules reflect the real patterns (full-time, part-time, shift, hourly) and not all employees are on the default 40 hours;
  • all time off types have their payroll configuration and validating time off creates work entries automatically;
  • allocations exist for all employees on the time off types that require them (paid holiday, compensatory);
  • there is at least one accrual plan for paid holiday if company policy is monthly accrual;
  • payslip generation uses the batch flow and not individual payslip creation;
  • work entries are reviewed and conflicts resolved before each batch is computed;
  • payroll accounting entries pass to the Accounting module and are not created by hand;
  • check-in and check-out come from Odoo (kiosk, app or integration) and not from a parallel system;
  • the recruitment pipeline in Odoo ends with Create Employee, with no re-entry at hire;
  • every employee has a related Odoo user, for self-service on payslips and time off requests;
  • fixed-term contracts have end dates and renewal activities scheduled;
  • payroll access is restricted: payroll officers see payroll data, other employees see only their own payslips.

Standard, configuration, integration or custom development

To compare the current process with what Odoo covers without customisation, the starting point is knowing what is standard: employee master data with organisation structure (department, manager, job position); time off management with approval flows and balance accrual; timesheet capture linked to projects and work orders; expense reports with approval, reimbursement and accounting integration; appraisal cycles with structured forms and goal tracking; the recruitment pipeline (job positions, applications, interviews, offers); fleet management (vehicles, contracts, fuel); payroll (it needs the country localisation: for Italy l10n_it_hr_payroll).

Six questions help classify each gap before asking for development:

  1. How is employee data managed today? Spreadsheet, HRIS, payroll system? Who is the master? A spreadsheet is standard. An external HRIS to keep is an integration. With the payroll system as master the direction of synchronisation has to be assessed.
  2. How are time off requests sent and approved? Email, paper, a tool? How are balances kept? Email or paper are standard plus process change. Time off types with several complex policies are configuration.
  3. How are timesheets captured, if at all? For billing, payroll, project control or not at all? If not captured, assess whether they are needed before go-live. Excel is standard. An external tool is an integration.
  4. How are expense reports sent and reimbursed? Paper receipts, scanned PDFs, an app? How long does reimbursement take? Paper is standard plus process change. If corporate credit card integration is needed, it is an integration.
  5. How is payroll processed? In-house, outsourced or hybrid? What data goes to the payroll system? Outsourced is an integration (file export to the payroll bureau). In-house with Italian payroll is configuration (l10n_it_hr_payroll). Complex union agreements may be custom development.
  6. Which HR data is confidential and who can see what? The absence of access control is a configuration gap. An access audit is needed: it is a security finding as much as an HR one.

The typical classification of the commonest cases is this:

Common gapTypical pathSignals that push towards custom
Employee data in ExcelStandardAn external HRIS with complex HR processes the company will not abandon
Email-based time off requestsStandard and process changeComplex leave policies (multi-country, union-specific accrual rules)
No timesheet captureProcess change and configurationNone
Paper expense reportsStandard and process changeCorporate card integration through a bank or provider API
Time clock in a separate systemStandard if ZKTeco BioTime, otherwise integrationProprietary terminals with no export or API
Payroll outsourcedIntegration (file export)Italian payroll with complex collective-agreement rules: assess the coverage of l10n_it_hr_payroll
This article is an OIAR skill

What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.

odoo-hrGuide to designing and assessing the Odoo 20 Enterprise HR suite: employee records, contracts, work entries as the bridge between time off, attendances and payroll, time off and accruals, batch payslips, attendances and overtime, recruitment. It includes warning signs, the rationalisations heard in companies and the questions that decide between standard, configuration, integration and custom development. Use it when setting up or checking the HR area in Odoo, with or without interviews with HR managers and payroll officers.