| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Employees (hr) • Discuss (mail) • Time Off (hr_holidays) • Calendar (calendar) • Invoicing (account) • Project (project) |
| Community Apps Dependencies |
Show
•
Employment Hero Attendance
• Employment Hero Australia • Employment Hero Canada • Employment Hero Connector • Employment Hero Country Base • Employment Hero Documents • Employment Hero HR • Employment Hero Leave • Employment Hero Malaysia • Employment Hero New Zealand • Employment Hero Onboarding • Employment Hero Payroll Bridge • Employment Hero Queue • Employment Hero Singapore • Employment Hero Sync Engine • Employment Hero Timesheet • Employment Hero UK • Employment Hero Webhook |
| Lines of code | 7862 |
| Technical Name |
eh_hero |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au/ |
| Versions | 16.0 17.0 18.0 19.0 |
Employment Hero Suite
One install connects the Employment Hero people platform to stock Odoo 18 Community, with a data driven sync engine that keeps employees, leave, attendance, timesheets and documents in step both ways.
Store price is USD 427 all-in: installing this also pulls the 18 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Suite
New coverage is a setting, not a release
Endpoints, field mappings and sync jobs are records you edit in the interface. Adding an Employment Hero resource or remapping a field needs no Python and no module update, so your integration grows with your setup.
Re running a sync never duplicates
Each record remembers its Employment Hero id through a cross reference. Run a job twice and unchanged records are skipped, changed records are updated, and nothing is duplicated. Push back is gated so you cannot send everything by accident.
Failures retry, they do not vanish
Transient errors and rate limits back off and retry, one bad record is isolated so the rest of the batch still lands, and a job that exhausts its retries parks in a dead letter state you can inspect and requeue.
Day in the life
A morning of people data, kept in step
Overnight a scheduled run pulls the latest employees, departments and leave from Employment Hero into Odoo. Each card on the Overview shows green with counts of records created and updated. A new starter signs their contract in Employment Hero, and a webhook delivery arrives within seconds, is signature verified, queued and applied to the one record it names without re pulling the whole list. At ten you preview a push of an updated cost centre, see exactly which records would change, then run it for real. When a finalised pay run closes, the payroll bridge imports its journal into accounting as a draft entry, and because that run was already imported last cycle it is recognised and skipped. Anything that failed is one click away on its run, with the exact error on the line.
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.
A redelivered webhook is recognised by its event id and acknowledged as a duplicate, and a concurrent duplicate that races to create is caught by a unique constraint, so the same event is never processed twice.
Webhook deliveries for one entity are queued on an ordered per entity channel so an older snapshot can never overwrite a newer one, and a delivery with no usable timestamp is skipped rather than allowed to win.
Every push carries a stable idempotency key, so a create that is retried after a timeout is deduplicated by the platform and returns the first result instead of producing a second record.
Each record runs inside its own savepoint. A single bad record is rolled back and logged as an error line, the run ends in a partial state, and every other record in the batch still commits.
The delta cursor only advances to the latest record that processed cleanly and never past a record that failed, so a failed or concurrently changed record is re fetched next run rather than skipped forever.
OAuth access tokens are stored encrypted and refreshed lazily before they expire, so a long running sync never stalls on a stale token and a missing access token raises instead of writing a half token.
A client side token bucket meters calls before they are sent, a server 429 is honoured with its Retry-After header clamped to a safe ceiling, and a cross worker bucket keeps a multi worker deployment under one shared budget.
A delete signalled by a webhook archives the linked Odoo record where the model supports it, falls back to unlink, and quietly keeps the record when a foreign key blocks the delete instead of dead lettering forever.
Pagination across odata, page number and cursor styles stops on a short page, and if a hard page cap is reached it logs a loud truncation warning rather than silently dropping records.
What is inside
Built to do the job, end to end.
- Connector core and sync engine. Connections with dual authentication, a data driven endpoint registry, encrypted OAuth tokens, rate limiting, a masked API log, configurable field mappings with a transformer library, and an orchestrator that runs pull, push or both per job with idempotent cross references.
- HR, leave, attendance and timesheets. Sync jobs and mappings for employees and departments, bank accounts, leave types, leave requests and balances, attendance with kiosk, face and geofence metadata, and timesheets into analytic lines, all targeting stock Community HR models.
- Documents, onboarding and goals. Sync of documents, certifications, employee onboarding and goals, so the people records that live in Employment Hero are visible and queryable inside Odoo.
- Payroll bridge. Imports finalised Employment Hero and KeyPay pay run journals into Odoo accounting as journal entries, mapping account and tax codes, running on a schedule, and never importing the same pay run twice. Community friendly, it depends only on the accounting and HR apps.
- Webhooks and async queue. A public webhook endpoint with constant time HMAC SHA-256 verification and replay protection, feeding an asynchronous queue with exponential backoff retries, ordered channels, a crash reaper and a dead letter state for jobs that exhaust their retries.
- Overview, runs and country packs. An Overview dashboard with per data type status, last run counts and Run Now and Preview buttons, full sync run history with graph and pivot views, and country packs for Australia, New Zealand, the United Kingdom, Singapore, Malaysia and Canada.
Honest about the edges
What this does not do, so nothing surprises you.
- This bundle is the Community edition and installs the Community modules only. Enterprise overlays for work entries, Planning shifts and the Documents app are separate installs and need the matching Enterprise apps; the optional recruitment connector is also installed on its own.
- You supply your own Employment Hero API credentials. The suite connects to your account, it does not provide one, and you need the relevant access to read or write the resources you sync.
- Default endpoints, mappings and jobs cover the common people and payroll resources. Coverage outside what ships is added through the configuration screens, which is the design intent, not by the publisher on your behalf.
- A sync never deletes Odoo records on its own; an upstream deletion archives or, where archiving is unavailable, unlinks the linked record. Push back to Employment Hero is off until you select the records to send.
- The payroll bridge imports pay run journals into accounting as draft entries for review; it is a journal import, not a full payroll engine, and it leaves posting to you.
- Built and tested against Odoo 18 Community. The same source is maintained for Odoo 16, 17 and 19 as separate version streams.
Employment Hero Odoo integration, Employment Hero connector Odoo, Odoo 18 Employment Hero sync, KeyPay Odoo integration, Employment Hero payroll Odoo, HR sync Odoo Community, Odoo employee sync, Employment Hero webhooks Odoo, two way HR sync Odoo, Odoo leave attendance sync, Employment Hero API Odoo, Odoo Community HR integration, payroll journal import Odoo, Employment Hero Australia Odoo
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.
Modules teams pair with this one.
Premium ERP Heritage modules that extend the same stack, each built to the same engineering bar.
Sync Employment Hero leave categories, leave requests and leave balances into the standard Odoo Time Off app, wit...
Show the Hijri (Umm al-Qura) date alongside Gregorian dates across Odoo 18
Connect Odoo partner records to the Saudi SPL National Address service and the Wathq commercial registry
Sync Employment Hero ATS recruitment job openings into the standard Odoo Recruitment app, mapping each opening on...
The New Zealand country pack for the ERP Heritage Employment Hero integration
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Employees (hr) • Discuss (mail) • Time Off (hr_holidays) • Calendar (calendar) • Invoicing (account) • Project (project) |
| Community Apps Dependencies |
Show
•
Employment Hero Attendance
• Employment Hero Australia • Employment Hero Canada • Employment Hero Connector • Employment Hero Country Base • Employment Hero Documents • Employment Hero HR • Employment Hero Leave • Employment Hero Malaysia • Employment Hero New Zealand • Employment Hero Onboarding • Employment Hero Payroll Bridge • Employment Hero Queue • Employment Hero Singapore • Employment Hero Sync Engine • Employment Hero Timesheet • Employment Hero UK • Employment Hero Webhook |
| Lines of code | 7862 |
| Technical Name |
eh_hero |
| 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