Odoo 20 · Workforce and service delivery · Part 4 of 8
What is confirmed about HR, payroll and service delivery in Odoo 20?
This part of the release contains the best-evidenced structural change in the whole version, because two independent sources point at the same thing without referencing each other.
Odoo 20 is released at Odoo Experience Americas in San Francisco on 2 and 3 September 2026, where Odoo says the new version “will be released during the event”. The European launch follows at Odoo Experience in Brussels on 24 to 26 September 2026, where Fabien Pinckaers unveils it in the opening keynote.
The Brussels agenda confirms sessions for Projects, Timesheets, Helpdesk and Field Service or Planning. The April Partner Day briefing, as reported, adds an AI timesheet assistant and a “Pay from Odoo” payroll capability.
It also reports something structural: Field Service being merged into Planning. That claim is worth more than most, for a reason we explain below.
This is part four of an eight part series on Odoo 20 by business function.
We label every claim by how well sourced it is. Confirmed means Odoo has published it, on its release notes, its event pages or its conference agenda. Partner Day means Odoo briefed its partner network on it in April 2026 and it has been reported, but Odoo has not published it directly. Unverified means it is circulating without a traceable source. Nothing here is presented as fact unless we can point you at where it came from.
Is Field Service really merging into Planning?
Partner Day reported, and independently corroborated by Odoo’s own agenda. This is the best-evidenced structural claim about Odoo 20 we have found.
The April briefing reported that the Field Service module is being merged into Planning. On its own that would be a single-source claim and we would label it accordingly.
But look at Odoo’s published agenda. Every other module has its own session: “What is new in Sales?”, “What is new in Inventory?”, “What is new in Helpdesk?”. Field Service does not. It appears as a single combined session titled What is new in Field Service/Planning?, presented jointly by two people.
Neither source references the other. A partner briefing in April said the modules were merging; a conference agenda published separately lists them as one session with joint presenters. That is corroboration, and it is the kind of evidence worth acting on rather than merely noting.
If you run field service on Odoo, this is the item in the entire release most likely to affect how you work. A module merge is not a feature addition. It changes data structures, views, access rights and very possibly any customisation you have built on top.
A maintenance contractor in Dubai runs annual maintenance contracts across roughly 600 sites with 40 technicians. They use Field Service for interventions and Planning for shift rostering. A merge touches all of it.
- Contract entitlements drive scheduled visits. Those generate tasks that must be assigned by skill, geography and availability, which currently spans both modules.
- Technician rosters and leave live in Planning. Intervention records live in Field Service. Today reconciling the two is a known friction point, which is presumably the reason for the merge.
- Timesheets flow from interventions into both payroll and contract profitability. Any change to where intervention data lives affects both downstream.
- Any custom fields or automations built across the two modules must be re-tested. This is where a merge costs real money.
If this merge is real, do not upgrade field service operations without a full rehearsal on a copy. Module merges are the single most disruptive kind of change in an Odoo major version.
This is a worked example of how to read release evidence. One source is a claim. Two independent sources pointing at the same thing, without citing each other, is close to fact. Apply that test to everything else you read about Odoo 20.
What is the Partena payroll partnership?
Confirmed. Three sessions cover a partnership with Partena Professional, one co-presented by Fabien Pinckaers himself.
The session titles are unusually promotional for a conference agenda: the story behind a groundbreaking partnership, revolutionising payroll management, and a preview of what is coming for accountants. Founders do not normally present integration sessions, and that alone marks it as strategic.
Payroll has always been Odoo’s hardest localisation problem. Rules differ by country, change annually, and getting them wrong carries legal rather than merely inconvenient consequences. Partnering rather than building is a rational response.
The honest caveat for readers in India and the Gulf: Partena is a Belgian provider and the confirmed sessions concern Belgian and French payroll. This does not obviously extend to Indian PF, ESI, professional tax and TDS, or to GCC wage protection requirements. Odoo has not said it does.
The reported “Pay from Odoo” capability sits alongside this. Also worth regional caution, because the UAE Wage Protection System mandates a specific salary file format through approved channels, and Indian disbursement runs through bank-specific bulk formats. A generic payment capability does not automatically satisfy either.
What is confirmed for HR and recruitment?
Confirmed. “From Paperwork to People: How Odoo Reimagined HR” is on the agenda, alongside a session on recruitment to onboarding.
“Reimagined” is marketing language and we are not going to pretend it tells us what changed. What it indicates is that HR is being presented as a rethink rather than a set of incremental fixes.
The supporting agenda is substantial and more informative than the headline: skills matrix mapping for continuity and coverage, biometrics in a real deployment, an implementation across four thousand users, and a session on attendance and daily wages for three thousand plantation workers across twelve remote sites.
That last one describes exactly the shape of problem many Indian and Gulf employers face. Distributed workforce, daily wage calculation, attendance capture where connectivity is unreliable, and labour law compliance varying by site.
What is reported about timesheets?
Partner Day, not confirmed. An AI timesheet assistant using ActivityWatch for automatic hour tracking, with local storage and supervisor privacy protections.
ActivityWatch is an open source time tracking tool that records application and window activity locally. Using it to propose timesheet entries is a sensible engineering choice, and the reported emphasis on local storage and privacy protection suggests Odoo is aware of how badly this can be received.
It should be said plainly: automatic activity tracking is a sensitive capability. Deployed well, it removes the Friday afternoon ritual of reconstructing a week from memory. Deployed badly, it is surveillance, and it will be received as such by your team.
For a services business, timesheets are not administrative overhead, they are the revenue record. If time is captured late, billing is wrong, utilisation reporting is fiction and project margin cannot be calculated. Anything that improves capture accuracy has direct financial value.
How should a services business prepare?
Document which payroll rules are standard and which are custom, and rehearse a parallel payroll run before going anywhere near production.
Payroll is the most common reason an Odoo upgrade stalls. If your salary rules were custom built to handle local statutory requirements, every upgrade means revalidating them, and a payroll that computes slightly differently after an upgrade is a serious problem rather than a cosmetic one.
The step to take before September is to list every payroll rule and mark it standard or custom. Then, after upgrading a copy, run a full parallel payroll and compare payslip by payslip, not total by total. Totals can match while individual employees are wrong in offsetting directions.
If field service is in scope, add the module merge to your test plan explicitly. Do not assume your customisations survive it.
Work out what a rollout or upgrade costs for your team, size the infrastructure it runs on, and see which add-ons cover the gaps in standard Odoo.
For the current state of Odoo payroll in India, we have written in detail about recruitment, payroll, appraisals and ESG for the mid-market.
Part five covers website, marketing and eCommerce.
Frequently asked questions
Is Field Service merging into Planning in Odoo 20?
Reported from the April 2026 Partner Day briefing and independently corroborated by Odoo’s own conference agenda, which lists a single combined “What is new in Field Service/Planning?” session with joint presenters while every other module has its own. This is the best-evidenced structural change in the release.
What has Odoo confirmed about payroll in version 20?
Three confirmed sessions cover a partnership with Partena Professional, a Belgian payroll provider, one co-presented by founder Fabien Pinckaers.
Does the Partena partnership cover Indian or UAE payroll?
Odoo has not said so. Partena is Belgian and the confirmed sessions concern Belgian and French payroll. Treat it as an indication of direction rather than locally available functionality.
Is Odoo adding automatic time tracking?
Reported from Partner Day rather than confirmed: an AI timesheet assistant using ActivityWatch for automatic hour tracking, with local data storage and supervisor privacy protections.
When is Odoo 20 released?
At Odoo Experience Americas in San Francisco on 2 and 3 September 2026, with the European launch in Brussels from 24 to 26 September 2026.
Eight parts covering Odoo 20 by business function. Parts one to six use confirmed and Partner Day sources. Part seven examines unsourced claims. Part eight tracks what Odoo’s founder is publishing directly.
- Part 1: Accounting and finance
- Part 2: Sales, CRM and POS
- Part 3: Manufacturing, inventory and quality
- Part 4: HR, payroll and service delivery (you are here)
- Part 5: Website, marketing and eCommerce
- Part 6: AI, Studio and automation
- Part 7: Rumours and unconfirmed features
- Part 8: What the founder is showing
Plan your Odoo 20 move with people who read the source
We scope, implement and support Odoo for mid-market businesses across India and the GCC on a fixed-cost basis. If you are weighing an upgrade against a fresh implementation, we will tell you which one actually fits, and why.