“Nobody has the right leave balance”
The accrual rule is defined once and the balance maintains itself. Employees see it on their own screen instead of asking HR.
PRODUCT · BUILT ON ODOO
Personnel files, leave, attendance and expenses move out of the filing cabinet into something everyone can see.
Most of HR is paperwork chasing: how much leave is left, when a contract expires, whether an expense claim was approved. Odoo moves that chase onto the employee’s own screen. A leave request reaches the manager, and once approved it comes off the balance and appears on the calendar by itself.
These three come up more than anything else in a first conversation.
“Nobody has the right leave balance”
The accrual rule is defined once and the balance maintains itself. Employees see it on their own screen instead of asking HR.
“Contract and document dates slip past”
Contract ends, medical reports, licences and work permits all carry dates. A warning appears before any of them expire.
“Expense slips pile up at month end”
Staff photograph the receipt on their phone, the manager approves, and the amount joins the payment run.
These are Odoo’s own modules. We write whatever is missing, rather than building a program from scratch.
Personnel file, org chart, document archive.
Leave types, accrual rules, approval chain, team calendar.
Clock in by kiosk, badge or phone; overtime calculation.
Receipt photo, approval flow, hand-off to the payment run.
Careers page, application form, staged interview tracking.
Periodic review forms, goal tracking, meeting notes.
Departments, titles, leave types, accruals and the approval chain are written down together.
Employee list, start dates, carried-over leave balances and scanned documents go in.
If you already have a turnstile or fingerprint device we connect to it, and if not we set up a tablet kiosk.
For the first month only the HR team uses the system. Employee logins open once the structure has settled. On the setups where we tried it the other way round, the first week produced hundreds of bad records.
The modules are different screens onto the same data. No bridges to build, no data to shuttle between them.
Start with one module and switch on another six months later. Nothing is rebuilt, the data stays where it is.
Your own server or the cloud, it makes no difference: you can export the entire database whenever you want.
If you want them to. An employee sees only their own leave balance, payslip and expenses, never anyone else’s.
Yes. Different working schedules are defined and overtime is calculated against them. Rules such as a night-shift multiplier need extra development work.
Past about fifteen people, paper tracking starts to hurt. We do set it up for smaller companies, though usually limited to leave and expenses.
Permissions are set per module, so only named people can see salary data. If the server is under your control, the data never leaves it.
How many of you there are, what you track today and how. We talk it through and give you a straight answer. If it does not fit, we say so.
Tell us what you have in mind; within two working days we come back with scope, timeline and a budget.