Employment Hero Onboarding Sync
Pull onboarding workflows, employee goals and contractor details from the people platform into Odoo, with field mappings and sync jobs you tune from the screen, not the 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 Onboarding Sync
Records Community does not ship
Stock Odoo Community has no onboarding or goal model. This adds eh.hr.onboarding and eh.hr.goal as proper records with list, form, search, grouping and chatter, so onboarding status and objectives live in Odoo instead of only in the people platform.
Tune the mapping from the screen
Endpoints, field mappings and sync jobs ship as data marked no update, so editing a source path or adding a field to match your organisation's payload is a user interface change, not a patch. The starter mappings are a known shape you adjust, not a black box.
Imports that do not duplicate or stall
Each record is keyed by its Employment Hero external id, so re running a pull never creates a second copy and an unchanged payload is a no op. One bad record is isolated and logged while the rest of the batch continues.
Day in the life
From people platform to Odoo, on demand
Run the employee sync first so the external id cross reference exists, then run the onboarding and goals pull jobs. Each fetch is paginated, mapped through the shipped field mappings, and matched to the right Odoo employee by external id. New workflows and goals are created, changed ones are updated, unchanged ones are skipped, and a per record sync line records exactly what happened. Contractor flags ride in on the employee sync and show on the standard employee form, hiding the business number field until someone is marked a contractor. Nothing here writes back to Employment Hero, so the people platform stays the system of record.
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 deduplicated by Employment Hero external id through the cross reference, so re running a job, or running it after a partial failure, updates in place and never creates duplicates.
Each mapped payload is hashed together with a fingerprint of the mapping. An identical record is skipped as unchanged, and editing a mapping line forces a rewrite on the next run instead of a silent stale record.
Every record is processed in its own savepoint. A bad row (a missing required field, an unresolved employee) is logged as an error line and the run ends partial, rather than aborting the whole batch.
Transient failures (5xx, timeouts) and rate limit responses are retried with exponential backoff and jitter, honouring a server Retry-After header and clamping it so a hostile value cannot park a worker for hours.
The onboarding and goals endpoints are read page by page (page index and item per page, 100 at a time) until a short page ends the scan, with a page cap that warns loudly rather than silently truncating.
The employee link resolves through the external id cross reference scoped to the connection, so two connections holding the same id never cross bind. An onboarding or goal whose employee has not been synced yet fails that one record cleanly for a re run once the employee exists.
Started, completed and due dates are parsed through UTC before being stored, so an offset near midnight does not shift the calendar date.
Onboarding and goal records carry a company and are filtered by a global record rule, so each company sees only its own (and shared company-less) records.
The contractor business number field is hidden on the employee form until the contractor flag is set, keeping the form clean for ordinary employees.
What is inside
Built to do the job, end to end.
- Two new HR records. eh.hr.onboarding (workflow name, status, started and completed dates) and eh.hr.goal (title, description, status, due date), each linked to the Odoo employee, with list, form, search views, group by employee and status, and chatter tracking.
- Contractor flags on the employee. A contractor marker and a contractor business number field (for example an ABN) added to the standard hr.employee and surfaced in the HR Settings area of the employee form.
- Configurable pull jobs and mappings. Onboarding and goals sync jobs with starter field mappings, shipped as data you can tune in place. Both run in the pull direction with an Employment Hero wins conflict policy, driven by the shared sync engine.
- HR endpoint declarations. Endpoint records for onboarding and goals, plus read endpoints for policies, forms, form categories and form templates, ready for the engine to call once a mapping and job are pointed at them.
- Sync run and line history. Every run records counts and a per record line (created, updated, skipped, error) through the sync engine, so you can see exactly what each pull did and why a record was skipped or failed.
Honest about the edges
What this does not do, so nothing surprises you.
- Pull only. The shipped onboarding and goals jobs import from Employment Hero into Odoo and do not write changes back to the people platform.
- Not real time out of the box. The shipped jobs run on demand or, once you tick the scheduled flag, on the engine's schedule. Single record webhook delivery is handled by a separate webhook module and is not configured for these jobs by default.
- Goals and onboarding are stored as lightweight standalone records, not wired into any Odoo appraisal, survey or recruitment workflow.
- The shipped mappings assume a particular payload shape. If your Employment Hero organisation returns different field names or nesting, adjust the source paths on the mapping lines before the first run.
- Employees must be synced first (via the employee sync) so the external id cross reference exists, otherwise onboarding and goal records cannot match their employee.
- The policies, forms and form template endpoints are declared for the engine but are not synced into Odoo models by this module on their own; they are scaffolding for a mapping you add.
- Requires a configured Employment Hero connection from the base module. This module does not handle credentials or authentication itself.
Employment Hero Odoo integration, Employment Hero onboarding sync, employee goals Odoo, contractor ABN Odoo, Odoo HR data import, people platform connector Odoo, Odoo 19 HR sync, external id matching, configurable field mapping Odoo, idempotent HR sync, Odoo Community onboarding, HR pull sync job
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.
A dependency free asynchronous job queue that runs long running and fan out work out of band of the request that...
Post Irish payslips to the general ledger on the Irish chart of accounts
Interactive drag and drop Gantt planner for Odoo 19 Community project tasks with a deterministic server side sche...
Employment Hero Connector is the integration core of the ERP Heritage Employment Hero suite, providing per compan...
The United Kingdom country pack for the ERP Heritage Employment Hero integration
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 3943 |
| Technical Name |
eh_hero_onboarding |
| 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