| 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 | 3838 |
| 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
Mirror Employment Hero leave categories, requests and balances into Odoo Time Off, tuned as data, no code.
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
Leave lands in stock Time Off
Categories sync into hr.leave.type and requests into hr.leave, with the leave type and employee relations resolved through the external id cross reference. Nothing custom replaces the Odoo Time Off app.
Mapping you change without code
Endpoints, field mappings and sync jobs ship as data marked no update, so you adjust source paths to your own Employment Hero payload shape from the interface and an upgrade never overwrites your changes.
Re-running never duplicates
Every record is keyed by its Employment Hero id through the cross reference, and the upsert hashes the mapped values, so a second run updates in place and an unchanged payload is skipped.
Day in the life
A quiet sync that keeps Time Off honest
Run the leave categories job first so the leave types exist, then run leave requests so each request resolves its type and employee through the cross reference. Balances are an employee sub resource, so you drive that job per employee with the employee id as a path parameter, and the figures land in the EH Leave Balances view under Time Off with the accrual rate, accrued this period and as of date carried straight from Employment Hero. Re-run any job as often as you like: matched records update in place, unchanged records are skipped, and a single bad record is logged as an error line while the rest of the batch completes. Each run records what it created, updated, skipped and failed.
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 Employment Hero id through the cross reference and the upsert compares a hash of the mapped values, so re-running a job updates in place and an unchanged payload is a no op rather than a duplicate.
Each record is processed inside its own savepoint, so a single failing leave request rolls back only itself, is recorded as an error line, and the run ends in the partial state instead of aborting the whole batch.
The transport retries only transient failures and rate limits with exponential backoff plus jitter, honours a Retry-After header, and clamps it so a hostile or buggy header cannot park a worker for hours.
The leave category and balance endpoints page through results using the platform page index and item per page parameters, stopping on a short or empty page, with a page cap that logs a warning rather than silently truncating.
The leave types job runs before leave requests so the request to leave type relation resolves through the external id cross reference, and the employee relation resolves the same way.
The change detection hash folds in a fingerprint of the mapping, so editing a mapping line rewrites existing records on the next run instead of skipping them as unchanged.
The cross reference and the leave balance model carry the connection company, so leave from separate Employment Hero connections stays scoped to its own company.
When the two way leave request push is enabled, a stable idempotency key is sent on each create so a retried push is deduplicated by the vendor instead of creating a second request.
What is inside
Built to do the job, end to end.
- Leave category and request mappings. Starter mappings for hr.leave.type and hr.leave ship as data, including name, leave category, employee, start and end dates and a free text reason, with required fields marked and source paths you can retarget to your payload.
- Leave balance reference model. A lightweight eh.hr.leave.balance model carries the Employment Hero balance, unit, accrual rate, accrued this period, accrual period and as of date per employee and leave type, surfaced in its own list and form under the Time Off menu, without touching the Odoo allocation engine.
- Two way leave request job. The leave request job is configured both ways: a pull from Employment Hero plus a push back through the employee scoped create endpoint, with the employee path placeholder filled per record from the employee external id. The push selection ships empty so you narrow it before enabling the push leg.
- Endpoints and sync jobs as data. Leave categories, leave requests, leave balances and unavailabilities endpoints, plus three sync jobs sequenced so relations resolve in order, all ship as configuration rows you can adjust without a code deployment.
- Security and audit. Access is split between an Employment Hero user group, read only on balances, and a manager group with write, and every run records its counts and per record outcomes for review.
Honest about the edges
What this does not do, so nothing surprises you.
- Targets the Employment Hero people platform leave data through its published API. You supply your own Employment Hero connection and credentials, configured in the connector module.
- The shipped mappings are starter mappings against a typical payload shape. A deployment confirms and adjusts the source paths to match its own Employment Hero organisation before relying on a job in production.
- Two way sync applies to leave requests only, and the push selection ships empty, so you must narrow the push domain and enable the push leg before Odoo requests are sent back. Leave categories and balances are pull only.
- Creating posted hr.leave records depends on your own Time Off allocation and leave type configuration in Odoo, which is outside this module.
- Leave balances are an employee sub resource, so the balance job is driven per employee with the employee id supplied as a path parameter.
- The shipped jobs are not pre-flagged for the scheduled run and ship no webhook detail endpoint for leave, so scheduling and webhook triggered sync are enabled by configuration rather than out of the box.
- This is an integration layer. It does not add new leave approval workflows or accrual rules of its own; it mirrors Employment Hero figures into the standard Odoo Time Off app.
- Requires the Employment Hero connector and sync engine modules and the standard Odoo hr_holidays app.
Employment Hero Odoo integration, Employment Hero leave sync, Odoo Time Off integration, hr_holidays sync, leave category import Odoo, leave request sync Odoo, employee leave balance Odoo, leave accrual mirror, Odoo 16 leave integration, idempotent HR sync, Employment Hero connector, two way leave sync, delta sync Odoo HR, Odoo Community HR integration
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 16 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 | 3838 |
| 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