| 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 | 7902 |
| 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 for Odoo 17
One install that keeps people, payroll and HR data in step between the Employment Hero platform and Odoo Community, with idempotent sync, signed webhooks and a retrying job queue.
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 for Odoo 17
Re run a sync, never duplicate
Every record is keyed to its Employment Hero id through a per connection cross reference. Re running a job updates in place, an unchanged payload is skipped, and one bad record is isolated to an error line while the run continues.
New coverage is a record
Endpoints, field mappings and jobs are data, not Python. Mappings read dotted source paths through a transformer registry and resolve relations through the cross reference, so adding an Employment Hero resource is a configuration change.
Built for flaky networks and rate limits
The client retries only transient failures and 429 with exponential backoff and jitter, honours Retry-After within a safe ceiling, meters calls through a token bucket, and sends a stable idempotency key so a retried create is deduplicated by the vendor instead of duplicated.
Day in the life
A working day with the suite running
Overnight, scheduled jobs pull employees, departments, leave, attendance and timesheets in delta mode, fetching only what changed since the last run. During the day an employee record changes in Employment Hero; a signed webhook arrives, is verified in constant time, deduplicated against replays, and queued. The queue runs a targeted pull of just that one record on a per entity ordered channel, so two deliveries for the same employee are never processed out of order. A push job sends Odoo side changes back, skipping records whose outbound payload is byte for byte unchanged. At month end the payroll bridge imports finalised pay run journals into the configured Odoo journal. An administrator opens the Overview dashboard, sees green status cards with created, updated and failed counts, and checks the API log if anything needs attention. Nothing requires touching code.
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 duplicate webhook delivery is caught by a database unique constraint on connection plus external event id, and a concurrent racing create is answered 200 idempotently from a savepoint rather than leaking a 500.
Transient failures, timeouts and 429 are retried with exponential backoff plus jitter; a server Retry-After is honoured but clamped so a hostile header cannot park a worker, and queue jobs retry on a growing delay then dead letter with an admin alert.
Each pulled and pushed record runs inside its own savepoint, so an IntegrityError on one record rolls back only that record, logs an error line, and the run ends partial instead of aborting the whole batch.
A retried create carries a stable idempotency key derived from the connection, model and record, so the vendor returns the first result instead of creating a second copy.
The delta high water mark only advances to the latest success strictly before the earliest failure, and a failure with no readable timestamp holds the cursor, so a failed or out of order record is re fetched next run rather than skipped forever.
OAuth refresh is single flight under a row lock on an autonomous cursor, re checking expiry after the lock, so two workers cannot each spend the same rotating refresh token and overwrite a good token with a dead one.
OData, page number and cursor styles are all supported from data; if a page cap is hit before the natural end the truncation is logged loudly rather than silently dropping records.
A reaper resets jobs left running past a configurable threshold back to failed so the normal retry path recovers work a crashed worker abandoned, while a heartbeat keeps a legitimately long running job from being reclaimed.
Webhook triggered updates are forced to newest wins regardless of the job policy, and an incoming snapshot with no usable timestamp is not allowed to overwrite a newer local record.
What is inside
Built to do the job, end to end.
- Connector core and sync engine. eh.connection owns transport with three auth strategies, rate limiting and an API log with sensitive values masked. The orchestrator fetches paginated, maps through dotted source paths, resolves relations via the external id cross reference, applies the conflict policy and writes a run with one line per record. Push reverses the mapping.
- HR, leave, attendance, timesheets. Domain modules ship endpoints, mappings and sync jobs for employees and departments, leave requests, attendance with kiosk, face and geofence source fields carried as metadata, and timesheets, all targeting stock Community HR models.
- Documents, onboarding and goals. Document, certification, onboarding and goal data flow across with the same data driven jobs, so records entered once in Employment Hero appear in Odoo.
- Payroll journal bridge. A configured bridge links a KeyPay business to an Odoo general journal and imports finalised pay run journals as account entries, stamped with the pay run they came from, respecting the lock date. Community friendly, no Enterprise payroll required.
- Webhooks and async queue. Inbound deliveries are verified with constant time HMAC SHA-256, capped in size, deduplicated against replays and queued. The queue retries with exponential backoff, dead letters poison work with an alert and a To Do activity, and claims jobs with a row lock so concurrent drains never double run.
- Country packs. Country packs for Australia, New Zealand, the United Kingdom, Singapore, Malaysia and Canada add their endpoints, mappings, jobs and local fields such as Australian superannuation, all as installable data.
Honest about the edges
What this does not do, so nothing surprises you.
- This integrates Odoo with the Employment Hero people and payroll platform specifically; it is not a generic connector for arbitrary external systems and you need your own Employment Hero account and API credentials.
- Push and two way sync are real but require a job to declare create and update endpoints and a reverse mapping; a job with only a pull endpoint syncs inbound only.
- Inbound changes are near real time through webhooks that queue async dispatch; this is not a streaming or sub second pipeline, and the async queue runs from a scheduled drain.
- The payroll bridge imports pay run journals into accounting and does not run payroll or post payslips inside Odoo.
- Attendance kiosk, face and geofence values are carried as synced field metadata from Employment Hero; this module does not provide its own kiosk or face recognition capture.
- Coverage of Employment Hero resources is what the shipped endpoint and mapping data defines; extending to other resources is configuration you add, and assumes the vendor API exposes them.
- Endpoint and field shapes follow the Employment Hero APIs at time of build and may need a mapping update if the vendor changes a response.
Employment Hero Odoo integration, Employment Hero connector, Odoo 17 Employment Hero, KeyPay Odoo integration, Employment Hero payroll import, two way employee sync Odoo, HR platform connector Odoo, Odoo Community HR integration, signed webhook integration Odoo, OAuth2 connector Odoo, people data sync Odoo, Employment Hero Australia Odoo, Odoo attendance timesheet sync, idempotent API sync Odoo, Employment Hero country packs
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 17
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 | 7902 |
| 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