Employment Hero HR Sync for Odoo
Bring Employment Hero employees and departments into Odoo HR with mappings and sync jobs you tune as data, no code.
Store price is USD 157 all-in: installing this also pulls the 2 paid ERP Heritage modules it depends on.
Why this module
Employment Hero HR Sync for Odoo
Mappings and jobs ship as data
Endpoints, field mappings and sync jobs install as configuration rows. Adjust which Employment Hero field maps to which Odoo field, or change a transformer, from the user interface. Most changes are configuration, not a code deployment.
Idempotent by external id
Every record is keyed through an external id cross reference, so running a job twice never duplicates. An unchanged payload is a clean skip, and one bad record is isolated to its own savepoint so the rest of the batch still lands.
Bank account number encrypted at rest
Employee bank accounts sync into a dedicated model whose account number is encrypted in the database and restricted to HR users. An upgrade migration encrypts any legacy plaintext column and drops it, so a database dump never leaks the number in clear.
Day in the life
A joiner, a mover and a leaver, handled on the next run
A new starter is added in Employment Hero. On the next scheduled run the employee is created in Odoo HR with name, work email, job title, mobile and primary department resolved to the right team. A mover changes teams in Employment Hero; the same run updates only that record, because its payload hash changed, and leaves every unchanged employee untouched. If one record carries bad data it is logged as an error line and the run finishes in a partial state rather than aborting, so the rest of the workforce still syncs. Re running the job an hour later creates nothing new and rewrites nothing, because each record is matched by its external id.
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 matched by external id through a cross reference with a unique constraint on model, connection and external id, so a rerun never duplicates and an unchanged payload hash is skipped.
Each record applies inside its own database savepoint. A failed write, for example an integrity error, rolls back just that record and the run ends in a partial state instead of poisoning the whole batch.
The employee and team list endpoints page through the HR platform using page index and item per page parameters, stopping on a short or empty page, with a loud warning if a configured page cap truncates results.
When a job runs in delta mode the cursor only advances to the high water mark of successfully processed records and never past a failed one, so a failed or concurrently changed record is re fetched next run rather than skipped forever.
The transport retries only transient failures and rate limit responses with exponential backoff plus jitter, honours and clamps a server Retry After header, and spends one rate token per logical call so a retry does not add to a 429 storm.
Write calls carry a stable Idempotency Key, constant per record for a create and per payload for an update, so a retried create is recognised by the platform and returns the first result instead of making a second record.
The synced bank account number is stored as ciphertext and decrypts only for HR users; an upgrade migration encrypts any legacy plaintext column, drops it, and is idempotent on a second run.
Connections carry a company, and the external id cross reference is scoped per connection, so jobs resolve the correct default connection for their product and company and links never cross companies.
The HR platform connection authenticates with an OAuth2 bearer token that is refreshed lazily and held encrypted at rest, so the sync never deals with token lifetimes in the job itself.
The per record hash folds in a fingerprint of the mapping, so editing a mapping line forces existing records to be rewritten on the next run rather than being skipped as unchanged.
What is inside
Built to do the job, end to end.
- Department and employee pull. Teams and departments sync into hr.department, and employees into hr.employee with name composed from first and last name, work and private email, work and mobile phone, job title, date of birth and the primary team resolved through the external id cross reference.
- Encrypted employee bank accounts. A dedicated eh.hr.bank.account model holds account name, bank, branch or routing code, allocation percentage and primary flag, with the account number encrypted at rest and restricted to HR users, kept separate from the Accounting partner banking.
- Two way ready jobs. The department and employee jobs ship with both directions enabled and an empty push domain, so a deployment narrows the push set, for example to records carrying an external id, before pushing Odoo changes back through the create and update endpoints.
- Endpoint catalogue. Ships read and write endpoints for departments, employees, contractor details, bank accounts, emergency contacts, custom fields, employment and job histories, cost centres, employing entities, positions and kiosk members, so coverage extends through configuration.
- Audited runs. Each run records fetched, created, updated, skipped, deleted and failed counts plus a per record line, so what changed and why is visible without preparing an export.
- Tunable mappings as data. Mappings install with noupdate set so a deployment can adjust source paths to its own Employment Hero payload shape without an upgrade overwriting the changes, and a starter set is shipped for every target.
Honest about the edges
What this does not do, so nothing surprises you.
- This module is configuration over the suite sync engine. It depends on the suite connector and sync engine modules, which install alongside it, and on the standard Odoo hr app.
- The shipped mappings are a starter set. Source paths reflect a typical Employment Hero HR payload and may need adjusting to your organisation's exact field shape, in particular the primary team path used for the employee to department relation.
- The department and employee jobs are two way but ship with an empty push domain, which means the push leg is effectively off until a deployment narrows the domain. Push is a deliberate configuration step, not on by default.
- Employee push updates the employment details surface (work email, job title, team). The display name is not split back into parts on push, and the bank account number is pull only and never pushed back.
- Real time webhook delivery and the asynchronous retry queue are provided by separate modules in the suite. This module ships scheduled sync jobs; install the webhook and queue modules to add push based delivery and queued processing.
- Bank account decryption requires the cryptography Python package. The upgrade migration that encrypts a legacy plaintext column fails cleanly before touching any row if that package is missing.
Employment Hero Odoo integration, Employment Hero HR sync, Odoo employee import, Odoo department sync, HR data integration Odoo, Employment Hero connector, Odoo 17 HR sync, people platform Odoo, employee bank account encryption, idempotent HR sync, field mapping as data, two way HR sync 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.
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.
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
One click install of the full Employment Hero integration for Odoo Community, covering the connector, two way syn...
The Malaysia country pack for the ERP Heritage Employment Hero integration
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4021 |
| Technical Name |
eh_hero_hr |
| 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