Employment Hero Work Entries
Pull Employment Hero work and roster data straight into Odoo work entries, tuned from the screen with no code.
Store price is USD 206 all-in: installing this also pulls the 3 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Work Entries
Tune the mapping from the screen
Endpoints, field mappings and jobs ship as data. When your Employment Hero organisation returns a different payload shape, you edit source paths, transformers and defaults in the interface instead of waiting for a code change.
Idempotent by external id
Each record is keyed by its Employment Hero id through the external id cross reference, so running the job again never creates duplicates and an unchanged payload is skipped as a no op.
Employee and type wired automatically
Work entries land with the right employee and work entry type because both relations resolve through the external id cross reference, and the type job is sequenced to run before the work entry job.
Day in the life
A roster week lands in Odoo
You run the work entry type job, then the work entry job, from the sync screen. Types arrive first and register their external ids. Work entries follow, each one matched to its employee and type through the cross reference. The pages are walked for you, a flaky response is retried with backoff, and one malformed record is logged and skipped while the rest of the week imports cleanly. Run it again tomorrow and only genuinely changed records move.
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.
Re running a job is safe. Records are matched by Employment Hero external id, so a second run updates in place or skips unchanged records rather than creating duplicates.
Transient failures, timeouts and rate limit responses are retried with exponential backoff and jitter, and a server Retry-After header is honoured and clamped so a worker is never parked indefinitely.
Each record runs in its own savepoint. A single failing record is logged as an error line and isolated, the rest of the batch continues, and the run ends in a partial state instead of aborting everything.
List endpoints are walked page by page, reading items from the data.items envelope at 100 records a page, with a loud warning if a hard page cap is reached so truncated results are never silent.
Mapping lines carry required flags, default values and skip if empty handling, so a missing optional field falls back to a default or is skipped while a missing required field fails just that record.
Employee and work entry type are resolved by external id. If a referenced employee or type has not been synced yet, that work entry fails in isolation and imports cleanly on the next run once the relation exists.
Connections and external id links are scoped per company, so the same Employment Hero ids can be linked independently across companies without collision.
What is inside
Built to do the job, end to end.
- Two endpoints. Work entry types and work entries on the HR platform paths, both reading the data.items envelope with page style pagination at 100 records a page.
- Two mappings. Starter field mappings for hr.work.entry.type and hr.work.entry, shipped non updatable so your edits survive an upgrade. Includes external id relation, date and number transformers.
- Two pull jobs. Sequenced so types import before work entries. Both keyed by external id, with an updated_at path supplied so conflict timestamps and an optional delta mode are available.
- External id cross reference. Every synced record is linked to its Employment Hero id through the shared cross reference, the backbone of idempotent re runs and relation resolution.
- Dry run preview. Run any job in dry run to see exactly what would be created or updated, with nothing written, before committing to a real sync.
- Editable from the screen. Source paths, transformers, required flags, defaults and job settings are all adjustable in the interface, no code required.
Honest about the edges
What this does not do, so nothing surprises you.
- Direction is pull only. This module brings Employment Hero work and roster data into Odoo. It does not push Odoo work entries back to Employment Hero.
- This syncs work entries and work entry types, not payslips or pay runs. Despite the technical module name, the data it moves is work and roster entries into the Odoo Work Entries app.
- Synchronisation runs on demand or on a schedule you configure. This module does not ship webhook or queue handling, so it is not real time.
- As shipped the pull jobs run in full mode each run. An updated_at path is supplied so a deployment can switch a job to delta, but delta is a configuration choice, not the default.
- The shipped source paths assume a typical Employment Hero payload shape. If your organisation returns differently named fields, you adjust the mapping to match before the first clean run.
- Requires a configured Employment Hero connection from the suite base, and the Odoo Work Entries app. Posting work entries against a running contract or employment version is governed by standard Odoo and is deployment specific.
employment hero odoo integration, employment hero work entries, odoo 17 work entry sync, roster import odoo, hr work entry import, employment hero hr sync, external id matching odoo, idempotent api sync odoo, no code field mapping odoo, paginated api import odoo, employment hero connector, odoo human resources 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.
The New Zealand country pack for the ERP Heritage Employment Hero integration
The complete ERP Heritage Employment Hero integration in one install
Sync timesheet entries from the Employment Hero people and payroll platform into the standard Odoo Timesheets app...
Real-time MRA fiscalisation for Point of Sale receipts in Odoo 17 Community, mapping each paid POS order to the M...
Shared foundation for the ERP Heritage Employment Hero country packs
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4152 |
| Technical Name |
eh_hero_ent_payroll |
| 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