Employment Hero Attendance Sync
Pull Employment Hero clock events into the standard Odoo Attendances app, with kiosk, geofence and face-verification metadata kept for audit.
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 Attendance Sync
Lives in the Attendances app you already use
Synced records are ordinary hr.attendance rows with the standard check in and check out, so they show up in the views, reports and kiosks you already use. The Employment Hero capture context rides alongside as extra fields, not a parallel screen.
Every clock event keeps its provenance
Kiosk, source, geofence coordinates, the face-verified flag and the Employment Hero reference are stored on each record so a synced attendance carries the same provenance it had upstream. Useful for audit and reporting, and deliberately kept out of any pay calculation.
Tune the mapping without a developer
Endpoint, field mappings and the sync job ship as editable data on the shared sync engine. Source paths for kiosk, geofence and face verification are starter values you adjust from the UI to match the payload your organisation returns, no module fork required.
Day in the life
A scheduled pull, then attendances you can trust
The attendance job runs against the Employment Hero clock-event feed and walks every page of results. Each record is matched on its Employment Hero id: new events are created as Odoo attendances, ones already seen are updated in place, and an unchanged payload is skipped so a re-run costs nothing. As it writes, it stamps each record with the kiosk, source, geofence latitude and longitude, the face-verified flag and the source reference. One malformed record is logged on its own line and the run carries on, finishing in a partial state rather than aborting the whole batch. By the time the job ends you have a clean attendance ledger in the standard app, each row traceable back to the exact clock event that produced it, and none of it touching your payroll figures.
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 keyed by their Employment Hero id in a cross reference table, so re-running the job updates the same attendance instead of creating a duplicate.
Each record carries a hash of its mapped values plus the mapping definition. If nothing changed since the last sync, the record is skipped, so steady-state runs do almost no writes.
The hash folds in a fingerprint of the mapping itself, so editing a source path or transformer forces existing records to be rewritten on the next run rather than wrongly skipped as unchanged.
Each record is processed inside its own savepoint. A failed write rolls back just that record, is recorded as an error line, and the run continues and ends partial instead of aborting the batch.
The feed is read page by page against the configured page size and stops on a short or empty page, so large attendance histories sync without loading everything at once.
The transport retries transient failures, timeouts and rate-limit responses with exponential backoff and jitter, honouring a server Retry-After header up to a safe clamp, while non-retryable errors raise immediately.
When the job declares an updated-at path, the cursor only advances past records that processed cleanly and never past a failed one, so a failed event is re-fetched next run instead of being lost.
Connections are scoped to a company, so a job resolves the right Employment Hero connection per company in a multi-company database.
HR-platform calls use a bearer token with lazy refresh handled by the connection, so the sync keeps running across token expiry without manual reauthentication.
The source field defaults to a sensible value when the payload omits it, so a record missing the source still lands with usable provenance rather than a blank.
What is inside
Built to do the job, end to end.
- Attendance metadata fields. Adds Kiosk, Capture Source, Latitude, Longitude, Face Verified and Employment Hero Reference to hr.attendance. All descriptive, none read by payroll or rostering logic.
- Pull sync job and mapping. Ships an editable endpoint, a field mapping and a sync job that pull Employment Hero clock events into Odoo attendances, matched by Employment Hero id with idempotent create-or-update.
- Runs on the shared engine. Builds on the suite connector and sync engine for the cross reference table, mapping, retrying transport, paginated fetch, conflict policy and audited run and line records.
- Starter source paths. Kiosk, geofence and face-verification source paths ship as best-guess values you tune from the UI to match the exact shape your Employment Hero organisation returns.
- Audited runs. Every sync produces a run with per-record lines showing created, updated, skipped and errored outcomes, so you can see exactly what each job did.
Honest about the edges
What this does not do, so nothing surprises you.
- The shipped and tested direction is pull, from Employment Hero into Odoo. A push leg is present in the job configuration but ships disabled, with an empty push domain and no update endpoint, and is not exercised by the included test. Treat outbound push as configuration to be completed and verified by your deployment, not an out-of-the-box feature.
- Kiosk, geofence and face-verification metadata is descriptive only. It is stored for audit and reporting and is never interpreted for payroll, pay rules, rostering or compliance decisions inside Odoo.
- The kiosk, geofence and face-verification source paths are best-guess starter values. You will likely need to adjust them in the mapping to match the exact payload your Employment Hero organisation returns.
- This module does not register a webhook or single-record detail endpoint for attendance, so attendance syncs on a scheduled or manual job rather than as a live push from Employment Hero.
- Requires the suite connector and sync engine modules, plus stock Odoo hr_attendance. Employees must already be synced so each attendance resolves to the right employee through the cross reference.
- It records attendance metadata from Employment Hero and does not compute worked hours, overtime, allowances or any pay value from the geofence, kiosk or face-verification data.
Employment Hero attendance, Employment Hero Odoo integration, Odoo attendance sync, clock event sync Odoo, hr.attendance connector, kiosk attendance Odoo, geofence attendance, face verification attendance, Employment Hero connector, Odoo 18 attendance integration, idempotent attendance sync, delta attendance sync, Employment Hero HR platform, attendance audit metadata, multi-company attendance connector
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 18 Community
Real-time fiscalisation of customer invoices and credit notes with the Mauritius Revenue Authority e-Invoicing (E...
The Malaysia 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 |
•
Attendances (hr_attendance)
• Employees (hr) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3683 |
| Technical Name |
eh_hero_attendance |
| 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