Start with why, not with features
HR software is easy to buy for the wrong reason.
A small company does not need an HR system because HR systems exist. It needs one when specific things have started going wrong: nobody knows how much leave someone has left, contract details live in a drawer, and the answer to “how many people do we have” depends on who you ask.
If none of that is happening, you can wait.
If it is, here is what Odoo offers and in what order to use it.
Employees — the foundation
The Employees app is the record of who works for you.
Each employee record holds personal details, job position, department, manager, contract information, work schedule and documents.
Two things make this worth doing properly.
It is the base for everything else. Time Off, Timesheets, Appraisals and Recruitment all read from it. A messy employee list makes every other HR app messy.
The org structure becomes real. Departments and managers are not decoration — they drive who approves what. Leave requests go to the manager on the record. Get the reporting lines right and approvals route themselves.
FIGURE 1: EMPLOYEE RECORDS ARE THE FOUNDATION
Employees
- Job, department, manager, contract, work schedule. Everything else reads this.
Time Off
- Balances, approvals and calendars, driven by the schedule on the record.
Timesheets
- Hours against projects, which can feed customer invoices.
Expenses and Appraisals
- Claims and reviews, kept against the same employee record.
Work schedules
Define the working hours for each employee — days, hours, breaks.
This matters more than it looks. Schedules drive leave calculations, timesheet expectations and availability planning. An employee on the wrong schedule will have their leave calculated wrongly.
Time Off
For most companies this is the app that pays for itself first.
How it works
You define leave types — annual, sick, unpaid, and whatever else applies where you operate. Each has its own rules on allocation, approval and whether it needs a document.
Employees request leave. Odoo checks their balance, routes it to their manager, and updates the calendar when approved.
What to set up carefully
Allocation. How leave is granted — a fixed amount per year, accrued monthly, or manually assigned.
Carry-over rules. What happens to unused leave at year end. This is the setting people get wrong most often, and it produces balance arguments a year later.
Approval chain. Who approves. Usually the manager, sometimes HR as well for certain types.
Public holidays. Enter these per country. Employees in different locations need different calendars.
The benefit
The value is not the app. It is that everyone can see their own balance without asking anyone.
Most leave friction comes from disagreement about the number. Remove the disagreement and the friction goes with it.
Recruitment (Enterprise)
A hiring pipeline that works like the CRM pipeline.
Job positions are published, applications arrive by email or through your website, and candidates move through stages — screening, interview, offer.
Useful features: applications from your careers page create candidate records directly, interview scheduling, scorecards, and one-click conversion of a hired candidate into an employee record.
Worth it when: you hire regularly enough that a spreadsheet has become painful.
Timesheets
Employees log hours against projects and tasks.
Two reasons to use it.
Billing. For services businesses, timesheets feed directly into customer invoices. Log the hours, invoice the hours.
Understanding cost. Even when you do not bill by time, knowing where hours actually go is valuable. Most companies are surprised by their first honest timesheet report.
The catch: timesheets only work if people fill them in. That is a management commitment, not a software feature. Make it a habit or do not start.
Appraisals (Enterprise)
Structured performance reviews on a schedule, with employee self-assessment and manager review, kept against the employee record.
Useful when: you have enough people that review conversations are getting missed.
Not useful when: you are ten people who talk every day. It becomes a form-filling exercise nobody values.
Expenses
Employees submit expense claims with receipts attached. Managers approve. Approved expenses post to accounting and can be reimbursed with payroll or separately.
Odoo can also read receipt photos and extract the amount and date automatically. Check the extraction before posting — it is good, not perfect.
Worth it when: expense claims are currently arriving as photos in a chat group.
Payroll — read this carefully
Odoo has a Payroll module, but its usefulness depends entirely on your country.
Payroll is heavily localised. Tax rules, social contributions, statutory deductions and filing formats differ everywhere, and they change.
Odoo provides full localisation for some countries and not others. In some places, Odoo Payroll will work out of the box. In others it needs significant custom work, and in some it is genuinely better to use dedicated local payroll software and post the summary into Odoo accounting.
Check your country’s localisation before assuming Odoo Payroll will work for you. This is not a place for optimism.
FIGURE 2: WHAT TO SET UP AND WHAT TO LEAVE
Worth doing first
- Complete employee records
- Time Off with agreed carry-over rules
- Expenses, if claims are chaotic today
Worth delaying
- Timesheets without a commitment to enforce them
- Appraisals in a small team
- Payroll before checking your localisation
What usually goes wrong
Employee data half-entered. Missing managers, wrong departments, no work schedules. Every other HR app then behaves oddly and nobody knows why.
Leave rules unclear. Carry-over and accrual rules that were never properly decided produce balance disputes twelve months later, when they are hardest to fix.
Timesheets started without commitment. Half the team fills them in. The data is worse than useless because it looks complete and is not.
Appraisals for the sake of it. Adds process without adding value in a small team.
Assuming payroll will work. Check the localisation first.
Getting started
Do these in order and stop when your problems are solved.
- Employees — complete records, correct managers, correct work schedules
- Time Off — leave types, allocation and carry-over rules agreed in writing before configuring
- Expenses — if claims are currently chaotic
- Timesheets — only if you will enforce them
- Recruitment — if you hire regularly
- Appraisals — only when you have the headcount to need them
- Payroll — only after checking your country’s localisation carefully
Most small companies should do the first two and stop there for a year. That alone removes the majority of everyday HR friction.
Setting up HR in Odoo?
Get in touch. We start with employee data and leave rules, because every other HR app depends on them.
