Odoo Time Off: Requests, Accrual Rules, and Calendar Integration

Introduction

Odoo Time Off centralizes employee data, time off, recruitment, and HR documents so managers and HR work from one file per person instead of parallel folders and tools.

People processes affect every department, yet leave balances, contracts, and hiring status are often unclear until someone escalates a problem.

The Time Off apps connect HR events to the org chart, approvals, and, where relevant, payroll or expense flows, giving leadership a live view of headcount and availability.

HR business partners, office managers, and executives planning workforce changes will find practical patterns to compare with their current setup.

Time Off is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo Time Off: Requests, Accrual Rules, and Calendar Integration states the storyline for stakeholders.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Time Off.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Time Off is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

HR sends a leave approval by email. Payroll finds out late. The manager on site has no idea who is available Tuesday. Everyone trusts HR, but the data is always one step behind reality.

HR processes touch every employee, yet leave, recruitment, and contracts often sit in separate tools. Managers lack a single place to approve requests and see team availability.

Sound familiar? Teams usually hit these walls:

• Leave balances disputed because requests live in email
• Recruitment status unclear across hiring managers
• Contracts signed without a central employee file

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Time Off, and measure what changes.

Top 5 Time Off Use Cases

5 use cases for Odoo Time Off, ranked from Level 1 (easy, do it this afternoon) to Level 5 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy starter. The last level is the ambitious scenario you might dream about but rarely build alone.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Submit your first leave request from the employee portal Level 1 — Easy

Level 1 is the simplest possible Time Off action: one employee, one request, one manager click. No accrual rules, no payroll, no calendar sync, just a clean request that updates the balance.

Here's how you'd do it in Odoo:

1. Install the Time Off app, then open Time Off, My Time Off, New to create a request.
2. Pick a leave type such as Paid Time Off, choose the start and end dates, and tick the Half Day box if needed.
3. Add a short reason in the description so the manager has context, then click Save and Confirm.
4. The manager receives an activity on the clock icon, opens Time Off, To Approve, and clicks Approve.
5. The employee balance is decremented automatically, and the leave appears on their personal Time Off dashboard.

What you get: Zero 'did you ever approve my leave?' email threads, balances stay in sync, and every request is traceable on the employee record from day one.

2. Configure leave types, public holidays, and the approval chain Level 2 — Easy

Level 2 sets the rules every request will follow. Typed leaves, country public holidays, and a clean approver chain are the first compliance layer of any Time Off setup.

Here's how you'd do it in Odoo:

1. Go to Time Off, Configuration, Leave Types, New and create Paid Vacation, Sick Leave, Parental Leave and Unpaid Leave.
2. Per type, set Take Leave In (day or hour), Allocation Requirement, and who approves: Employee's Manager, HR Officer, or Both.
3. Open Time Off, Configuration, Public Holidays and import the country calendar so national days are not counted against balances.
4. On each leave type, decide whether weekends and holidays count and whether the leave can go into negative balance.
5. Set Maximum Allowed Negative Days and a clear color per type so the team calendar stays readable later.
6. Submit a test request from a sandbox employee account and confirm the approval routes to the right person.

What you get: Leave policy is encoded once and applied consistently to every employee, and HR stops being the human firewall that catches missing holidays and wrong approvers.

3. Set up an accrual plan that grants days automatically every month Level 3 — Medium

Level 3 turns Time Off into a self-running balance machine using accrual plans, the feature highlighted in the blog title. No more Excel sheets to recalculate balances on January 1st.

Here's how you'd do it in Odoo:

1. Open Time Off, Configuration, Accrual Plans, New and name the plan Standard Yearly Vacation.
2. Add a level: Accrue 2 days per month, starting on employee start date, with a maximum cap of 25 days per year.
3. Add a second level after one year of tenure: 2.5 days per month, to reward seniority automatically.
4. Set carry-over rules: allow up to 5 unused days to roll over, with an expiry on March 31 of the next year.
5. Go to Time Off, Allocations, New, pick the plan, set Allocation Mode to Multiple Employees and filter by department.
6. Confirm the bulk allocation, then open one employee's Time Off dashboard and watch the balance update at the next cron run.

What you get: Year-start HR admin drops from two full days of spreadsheet work to five minutes of clicks, and every employee can see exactly how many days they have earned at any moment.

4. Sync personal Outlook or Google calendars and plan team availability Level 4 — Hard

Level 4 connects Time Off to the calendars people actually live in. Approved leaves appear in Outlook and Google Calendar, and managers plan around real availability instead of guessing from email threads.

Here's how you'd do it in Odoo:

1. Go to Settings, General Settings, Integrations and enable Google Calendar and Outlook Calendar with the OAuth credentials.
2. Each employee opens Preferences, Calendar tab, and authorizes the sync; approved leaves now mirror automatically to their personal calendar.
3. Open Time Off, Overview, Team to display the shared calendar view, filtered by department or by project.
4. Switch to the Gantt view to spot overlaps in red, and bulk-approve or refuse pending requests without leaving the screen.
5. Enable the Planning integration so a leave automatically frees the employee's shifts and the planner gets reassign suggestions.
6. Open Time Off, Reporting, By Department to forecast the May, August and December peaks and freeze critical weeks ahead of time.

What you get: Project planning finally accounts for who is actually available, and the 'sorry, I forgot to tell you I was off' Monday morning incidents stop happening.

Wiring the OAuth flows for Google and Outlook across the whole company, mapping departments to the right approvers, and tuning the Planning integration is exactly the kind of cross-app setup Dasolo runs as a partner-led engagement.

5. Orchestrate Time Off across Payroll, Planning, Timesheets, AI and a live HR dashboard Level 5 — Expert

Level 5 is the full HR operating system: one approved leave updates pay, capacity, billable hours, IT access and an AI assistant, while a real-time dashboard shows leadership exactly who is off and what it costs.

Here's how you'd do it in Odoo:

1. Enable the Time Off, Payroll integration via the country localization so approved leaves auto-create payslip lines with the right rule.
2. Connect Timesheets: leave days are pre-filled with 0 billable hours and the consultant utilization KPI is recomputed every night.
3. Configure Studio automated actions: any leave longer than 10 consecutive days creates IT and Helpdesk activities (mailbox auto-reply, license review, handover task).
4. Plug an AI HR assistant on Discuss: it answers 'how many days do I have left?', drafts the leave request, and proposes the least disruptive dates per team.
5. Add an anomaly detector that flags suspicious patterns (Fridays only, no leave for 18 months, repeat single-day sick) and creates an HR activity.
6. Build a Spreadsheet 'HR Live' dashboard with absence rate, accrual liability in cash, projected coverage gaps and AI-suggested replanning, refreshed in real time.

What you get: Leave, pay, capacity, billable hours and IT access all agree without a single manual reconciliation, and HR finally has the numbers to defend its decisions in front of the executive committee.

Designing the payroll mappings, the Studio automations, the AI prompt library, the anomaly rules and the live HR dashboard is the architecture Dasolo designs as a partner-led growth engagement. Most teams need an outside team to assemble these pieces correctly the first time.

When Expert Help Makes Sense

If levels 1 to 3 fit your world, you can often succeed with standard Odoo Time Off, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 4 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Time Off includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo