| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Time Off (hr_holidays)
• Discuss (mail) • Calendar (calendar) • Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 3881 |
| Technical Name |
eh_hero_leave |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au/ |
| Versions | 16.0 17.0 18.0 19.0 |
Employment Hero Leave for Odoo 17
Mirror leave categories, requests and balances from the Employment Hero people platform into stock Odoo Time Off, with mappings and sync jobs you tune from the user interface.
Store price is USD 117 all-in: installing this also pulls the 2 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Leave for Odoo 17
Leave lives in Odoo Time Off
Categories become hr.leave.type and requests become hr.leave, resolved to the right leave type and employee through the external id cross reference, so the Odoo Time Off app reflects the source without manual re-entry.
Mappings you change without code
Endpoints, field mappings and sync jobs ship as data marked no upgrade overwrite, so a deployment adjusts source paths to its own organisation payload from the user interface and keeps those edits across updates.
Run it twice, get one record
Every record is keyed by its Employment Hero id, so a re-sync updates the existing request instead of duplicating it, an unchanged record is skipped by content hash, and a single bad record is isolated in its own savepoint.
Day in the life
A morning leave reconciliation, automated
The leave type job runs first and brings any new categories into hr.leave.type. The leave request job follows, pulling fresh requests and matching each to its Odoo leave type and employee through the cross reference; records already seen are skipped by hash, new ones are created, changed ones updated, and one malformed payload is parked as a failed sync line without blocking the rest. The balance job, driven per employee, refreshes the reference figures so HR can see the authoritative numbers next to the Odoo allocation. Each run records counts, errors and duration for review.
Edge cases
The cases most modules quietly ignore.
In the shipped code today, each one a place where a cheaper module silently does the wrong thing.
Records are keyed by their Employment Hero id through the external id cross reference, so re-running a job updates the matching record rather than creating a duplicate.
A content hash of the mapped values plus a fingerprint of the mapping is stored per record; an unchanged record is skipped, and editing the mapping changes the hash so existing records are rewritten on the next run.
Each record is processed inside its own savepoint, so a single failing leave request rolls back alone and is recorded as a failed sync line while the rest of the batch commits.
Leave types sync at a lower sequence than leave requests, so the request to leave type relation always resolves through the cross reference instead of failing on a missing reference.
When the leave request job runs in delta mode it advances its cursor only to the high water mark of successfully processed records, so a failure mid run causes a re-fetch rather than a silently skipped record.
A leave request whose employee or leave type has no cross reference yet is reported as a failed line with the reason, rather than writing a half mapped record.
The shipped endpoints declare page style pagination with a page size, so large category and balance lists are fetched page by page through the engine.
The leave request job is configured two way with a push create endpoint, but its push domain ships empty so nothing is sent until a deployment narrows the domain and enables the push leg deliberately.
What is inside
Built to do the job, end to end.
- Leave category and request mappings. A leave type mapping into hr.leave.type and a leave request mapping into hr.leave, with employee and leave type resolved by the m2o by external transformer, plus date from, date to and notes fields. All ship as tunable data rows.
- Leave balance reference model. A lightweight eh.hr.leave.balance model carrying the source balance, unit, accrual rate, amount accrued this period, accrual period and as of date next to the Odoo allocation engine, populated by a per employee balance pull job.
- Endpoints and sync jobs as data. Leave category, leave balance and per employee endpoints plus three sync jobs, sequenced so types precede requests, with external id path, delta cursor path and explicit conflict policy declared on each job.
- Rides the shared sync engine. Idempotent upsert, content hash skip, delta cursor, per record savepoint isolation, strategy driven pagination and audited sync runs come from the underlying Employment Hero sync engine this module depends on.
Honest about the edges
What this does not do, so nothing surprises you.
- Targets the standard Odoo Community Time Off app (hr_holidays); it does not replace or re-implement the Odoo allocation and approval engine.
- The leave request push back leg is configured but ships with an empty push domain; a deployment must narrow the domain and enable it before any leave is sent back to the source platform.
- The leave balance job is an employee sub resource: its endpoint path carries the employee id, so a deployment drives it per employee rather than as one organisation wide pull.
- Leave balances are stored as a read only reference model for visibility and reporting; they are not written into the Odoo allocation engine.
- Mapping source paths ship as starter values that must be adjusted to match the shape of your Employment Hero organisation payload.
- Real time webhook delivery and the in database job queue are provided by separate modules in the suite, not bundled in this module's dependencies.
- An unavailabilities endpoint is shipped for reuse but has no mapping or job wired in this module.
Employment Hero Odoo integration, Odoo 17 leave sync, Employment Hero leave connector, Odoo Time Off integration, hr_holidays sync, leave category mapping Odoo, employee leave balance import, Odoo HR data sync, idempotent leave import, Employment Hero people platform connector
Need this fitted to the way you work?
ERP Heritage delivers end to end Odoo work: Odoo Implementation, Customization and Development, Integration, Migration, Consultation, Support and Training. We help teams put this module into production, shape it to their process, and keep it running.
We work with businesses across Australia (Melbourne, Sydney, Brisbane, Perth, Adelaide, Canberra) and the Middle East (Dubai, Abu Dhabi, Riyadh, Jeddah, Doha, Kuwait City, Muscat). Start a conversation at erpheritage.com.au or email info@erpheritage.com.au.
Languages
Available in 19 languages
The interface ships translated out of the box. Switch language in Odoo and the fields, menus, and messages follow.
Modules teams pair with this one.
Premium ERP Heritage modules that extend the same stack, each built to the same engineering bar.
Sync attendance clock events from the Employment Hero people platform into the stock Odoo Attendances app, keyed...
The Singapore country pack for the ERP Heritage Employment Hero integration
The complete ERP Heritage Employment Hero integration in one install
Inbound webhook receiver for the Employment Hero people and payroll platform on Odoo 17 Community
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Time Off (hr_holidays)
• Discuss (mail) • Calendar (calendar) • Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 3881 |
| Technical Name |
eh_hero_leave |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module