| 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 | 7881 |
| 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
Connect the Employment Hero people and payroll platform to Odoo Community with a data driven sync engine, signed webhooks, an async queue and six country packs, one install.
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
Integration, not a payroll engine
This connects Odoo to the Employment Hero platform and keeps the two in step. It does not run payroll itself. The pay run bridge imports finalised pay runs from the payroll product into a general journal, so the numbers land in your Community accounts without an Enterprise payroll module.
New coverage is a setting
Endpoints, field mappings and sync jobs are stored as records. Adding an Employment Hero resource or remapping a field is done in the UI, not in a release. Dotted source paths run through a transformer registry, so date, boolean and relation handling is declarative.
Survives flaky calls and replays
Transient failures and 429s back off and retry with jitter and honour Retry-After. Webhooks are signature checked and deduplicated. Failed queue jobs retry with exponential backoff then park in a dead letter state with a notification rather than vanishing.
Day in the life
A change in the people platform reaches Odoo, safely
An employee record changes in the Employment Hero platform. A signed webhook hits your Odoo endpoint, the HMAC is verified in constant time, and the delivery is deduplicated against any replay by its event id. It is queued on a per entity ordered channel so two changes for the same person never run out of order. The dispatch fetches just that one record from the detail endpoint, maps it through the configured field mapping, resolves the external id to the existing Odoo employee and updates it with newest wins protection so an out of order delivery cannot overwrite fresher data. The run is recorded line by line. If the call had failed, the job would have backed off and retried, and only after exhausting retries parked in the dead letter queue for you to inspect and requeue. Nothing silently disappears.
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 external event id and answered 200 duplicate without reprocessing. A concurrent duplicate that races past the check is caught by a unique constraint inside a savepoint and also answered idempotently.
A push that creates a record in the platform carries a stable Idempotency-Key per Odoo record, so a retry after a timeout is deduplicated by the vendor and returns the first result instead of creating a second record.
Each record syncs inside its own savepoint. One bad record is logged as an error line and the run continues, ending in a partial state, rather than poisoning the whole batch transaction.
The delta cursor only advances to the high water mark of records that processed successfully and never past a failed record, so a failed or concurrently changed record is re fetched next run instead of being skipped forever.
Webhook triggered updates are forced to newest wins by source timestamp. A snapshot with no usable timestamp is not allowed to overwrite, because it cannot be proven newer.
A job left running by a worker that died is recovered by a reaper after a configurable threshold, counted as a failed attempt so the retry cap still applies, while a heartbeat keeps genuinely long running jobs from being reclaimed.
A client side token bucket meters calls, with a cross worker database backed bucket so multiple workers share one budget. A server 429 backs off and honours Retry-After, clamped so a hostile header cannot park a worker for hours.
Pagination follows OData skip and top, page index or cursor styles. Hitting the page cap is logged loudly as truncation with advice to narrow the query, never a silent drop of records.
OAuth2 access and refresh tokens are stored encrypted and restricted to system administrators, refreshed lazily before expiry with a leeway window, and a token response missing an access token is rejected rather than written half formed.
A delete event archives the linked Odoo record where the model supports it, otherwise unlinks it, and severs the external id link. A hard delete blocked by a related record is recorded as skipped and kept locally instead of dead lettering on every run.
What is inside
Built to do the job, end to end.
- Connector core and transport. A single client for every call with three auth strategies, OAuth2 Bearer for the HR platform, API key HTTP Basic for the payroll product and a header token for the optional recruitment add on. Rate limiting, retry with backoff, an API log and an endpoint registry sit underneath it.
- Data driven sync engine. Connections, endpoints, field mappings and sync jobs are records. The orchestrator fetches paginated, maps through a transformer registry, resolves relations through an external id cross reference, applies the conflict policy and writes one audit line per record. Pull, push or both per job, with delta mode and dry run.
- Async queue with dead letters. A dependency free job queue with named channels, optional strict ordering per channel, exponential backoff retry, a dead letter state with notification, a reaper for crashed workers and atomic claiming so concurrent drains never double run a job.
- Signed inbound webhooks. A public endpoint that verifies an HMAC SHA-256 signature in constant time, caps the body size, deduplicates replays by event id, records the event and queues a targeted single record sync on a per entity ordered channel.
- HR domains. Employees and departments, leave with balances, attendance with kiosk and face and geofence metadata, timesheets, documents, certifications, onboarding and goals, all syncing into stock Community models.
- Pay run to journal bridge. One bridge per company pulls finalised pay runs from a payroll connection and posts them into a chosen general journal, respecting a lock date. An import path into Community accounting, not a payroll calculator.
- Country packs. Australia, New Zealand, United Kingdom, Singapore, Malaysia and Canada packs add the statutory identifier and contribution fields for each country (for example tax file number and superannuation, NRIC and CPF, EPF and SOCSO) and register the country profile.
- Overview dashboard and runs. An Overview dashboard, scheduled cron runs, per run counts of fetched, created, updated, skipped, deleted and failed, and a line level history so every record movement is traceable.
Honest about the edges
What this does not do, so nothing surprises you.
- This is an integration layer for the Employment Hero people and payroll platform. It does not calculate payroll, tax or statutory contributions inside Odoo. The pay run bridge imports finalised pay runs from the platform into a general journal.
- A live Employment Hero account and API credentials are required. The modules ship with the transport mocked for testing and do not include or provision a platform subscription.
- Field coverage is what the shipped endpoint and mapping records declare. The engine is data driven so mappings can be extended, but out of the box sync covers the resources and fields configured in this suite, not every field the platform exposes.
- Country packs add the statutory identifier and contribution fields for the six listed countries only. They are field and profile additions, not full localisation or compliance reporting.
- Webhook delivery relies on your Odoo instance being reachable by the platform over HTTPS and on configuring the signing secret and subscriptions. Push depends on the related records already carrying an external id, so dependencies should be synced first.
- Authored on Odoo 19. The 16, 17 and 18 series are produced by a backport tool from the same source and pass the same test suite, but you should install the build that matches your Odoo version.
Employment Hero Odoo integration, Employment Hero connector, Odoo HR payroll integration, KeyPay Odoo, two way employee sync Odoo, OAuth2 API connector Odoo, signed webhook receiver Odoo, idempotent sync Odoo, delta sync HR data, async job queue Odoo, pay run journal import, Odoo Community HR sync, Australia New Zealand UK Singapore Malaysia Canada HR, conflict resolution sync, rate limited API client 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 19
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 | 7881 |
| 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