Employment Hero Documents Sync
Bring Employment Hero certifications and employee document metadata into Odoo, with certifications kept in two-way step.
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 Documents Sync
Models Community does not ship
Stock Odoo Community has no HR certification or employee document model. This connector adds eh.hr.certification and eh.hr.document and populates them from your Employment Hero organisation.
Certifications sync both directions
The certification job pulls the list and pushes new and changed records back through the create and update endpoints, with a conflict policy you set so an edit in Odoo or in Employment Hero is handled predictably.
Mappings ship as editable data
Endpoints, field mappings and sync jobs are data records you adjust in the user interface. Point a source path at your own organisation payload shape without touching Python or waiting on an upgrade.
Day in the life
A sync run, end to end
The certification job runs and paginates the Employment Hero certification list. Each record is keyed by its external id, so a record already in Odoo updates in place rather than duplicating, and each employee link resolves through the external id cross reference onto the right employee. Changed certifications are pushed back through the update endpoint with an idempotency key, so a retried write is deduplicated upstream instead of doubled. A row that fails to write is isolated in its own savepoint, the rest of the batch still lands, and the run records what happened. Documents are pulled per employee, storing each title, type, upload date and source URL for staff to open directly in Employment Hero.
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.
Every record is keyed by its external id through the cross reference, so a re-run updates the existing certification or document in place instead of creating a duplicate.
Transient failures, timeouts and 429 responses are retried with exponential backoff and jitter, honouring a server Retry-After header and clamping it so a hostile or buggy value cannot stall the run.
Each record is written inside its own savepoint, so one bad row, for example a value an Odoo constraint rejects, is skipped and reported while the rest of the batch still commits.
Certification create and update calls carry a stable idempotency key, so a write that a retry resends is deduplicated by the vendor rather than applied twice.
A webhook triggered run is forced to newest wins and a timestamp-less delivery cannot overwrite a newer record, so a delivery that arrives late does not roll a certification back.
A webhook fetches just the one changed record by external id rather than paginating the whole list, so a delivery and each retry of it cost one request.
OAuth2 access tokens refresh lazily through the connection, with the expiry always rewritten, so a sync does not stall on an expired token or storm the refresh path.
Certifications and documents are isolated per company by record rule, while records with no company stay visible to all, so one company cannot read another's HR records.
Mappings ship with noupdate set so your tuned source paths survive upgrades, and a non required field that is missing in the payload is simply left empty rather than failing the row.
What is inside
Built to do the job, end to end.
- Two synced models. eh.hr.certification holds the name, reference, issued and expiry dates and status. eh.hr.document holds the title, type, upload date and source URL. Both carry a chatter and an employee link, with list, form and search views and a grouped HR Records menu.
- Shipped endpoints and jobs. Endpoints for the certification and document lists and for certification create and update ship as data, alongside a two-way certification job and a per-employee document pull job, all editable in the user interface.
- Field mappings as data. Each model has an editable mapping with one line per field, including date transformers and the employee resolver that matches by external id. Adjust a source path to fit your organisation payload without code.
- Engine it runs on. Sits on the shared Employment Hero sync engine for pagination, external id keying, retry with backoff, idempotent writes, conflict policies and the webhook targeted pull path, so this connector stays a thin, honest layer.
Honest about the edges
What this does not do, so nothing surprises you.
- Document sync stores metadata and the source URL only. It does not download or store the binary file in this version; staff open documents in Employment Hero through the stored link.
- Document pull is a per-employee operation because the documents path carries an employee id. A deployment drives it per employee, one call per employee, or via a webhook, rather than a single org wide pull.
- Certification sync is two way. Document sync is pull only into Odoo; there is no document push back to Employment Hero.
- Field names and payload shapes vary by organisation, so the shipped mapping source paths are a starting point you confirm and tune against your own Employment Hero data.
- Employees must already exist in Odoo with an external id cross reference, normally from the employee sync, so certifications and documents resolve onto the right person.
- This is a connector to the Employment Hero people platform and requires a valid Employment Hero subscription and API credentials. It does not replace Employment Hero.
- Built for Odoo 16 Community and depends on the Employment Hero base and sync modules and the standard HR app.
Employment Hero Odoo integration, Employment Hero documents sync, Odoo HR certifications, employee document sync Odoo, qualification tracking Odoo, certification expiry Odoo, Employment Hero connector Odoo 16, Odoo HR records sync, two-way certification sync, Odoo Community HR 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.
Inbound webhook receiver for the Employment Hero people and payroll platform on Odoo 16 Community
Real-time fiscalisation of customer invoices and credit notes with the Mauritius Revenue Authority e-Invoicing (E...
The Canada country pack for the ERP Heritage Employment Hero integration
A dependency free asynchronous job queue that runs long running and fan out work out of band of the request that...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 3884 |
| Technical Name |
eh_hero_documents |
| 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