Employment Hero Attendance Sync
Pull Employment Hero clock events into the standard Odoo Attendances app, with kiosk, geofence and face verification metadata carried along 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
Clock data lands in Odoo without a manual import
Attendance records flow from Employment Hero into the standard Attendances app, mapped onto the native check in and check out. The manual clock export and copy paste step is gone.
Every record keeps the context it was captured with
Kiosk, capture source, geofence latitude and longitude, and face verification status ride along on each attendance, so a synced record carries the same provenance it had upstream for audit and reporting.
Re run a job without fear of duplicates
Each record is keyed by its Employment Hero id through a cross reference. An unchanged record is skipped, a changed one is updated in place, and one bad record is logged without stopping the rest of the batch.
Day in the life
A morning attendance reconciliation, without the spreadsheet
Overnight the scheduled run pulls the previous day of clock events from Employment Hero. Each entry is matched to its employee through the cross reference, the start and end times become a check in and check out, and the kiosk, source, geofence coordinates and face verification flag are written alongside. Records already in Odoo are left untouched unless they changed upstream. In the morning the operations team opens the Attendances app and the day is already there, with a sync run logging exactly what was created, updated, skipped and why. Nothing was exported by hand, nothing was pasted, and the audit trail is the run itself.
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 Employment Hero id through a cross reference. Running a job twice finds the existing row and updates in place rather than creating a second attendance. An unchanged payload, detected by a content hash, is skipped as a no op.
Each record is processed inside its own savepoint. A single record that fails to write, for example an integrity error, rolls back only itself and is recorded as an error line. The run continues and ends in a partial state instead of aborting the whole batch.
Transient transport failures, server 5xx responses and rate limit 429s are retried with exponential backoff and jitter. A server supplied Retry-After header is honoured and clamped so a bad header cannot park a worker. Non retryable errors raise immediately.
Calls draw from a shared token bucket per rate group, so multiple workers and jobs hitting the same Employment Hero product stay within one budget rather than multiplying it. One logical call spends one token, retries included.
The attendance feed is read page by page using the HR platform page index and item per page scheme, stopping on a short or empty page. A page cap guards against an endless loop and warns loudly when results would be truncated, so a large window is narrowed rather than silently cut.
When a record changed in both places the inbound precedence is an explicit rule you choose. Out of the box Employment Hero is authoritative for attendance. Most recently changed and Odoo wins are available per job, so a record is never overwritten by accident.
Each mapping line has a source path, an optional transformer and an optional default. The capture source defaults to a known value when the payload omits it, and times and coordinates are coerced through datetime and float transformers so a slightly different payload shape still lands cleanly.
Connections and cross references are scoped per company, and a sync job runs for a specific company against its own connection, so attendance from separate Employment Hero organisations stays isolated.
Against the HR platform the connector authenticates with a bearer token and refreshes it lazily through the connection, so a long lived scheduled job keeps running without a manual credential rotation.
What is inside
Built to do the job, end to end.
- Attendance fields on hr.attendance. The standard attendance is extended with kiosk, capture source, geofence latitude and longitude, face verification and an Employment Hero reference. All are descriptive, stored for audit and reporting, and never used for payroll.
- Endpoint, mapping and sync job as data. The timesheet entries endpoint, the field mapping that translates a clock event into an attendance, and the sync job that ties them together all ship as data records and can be tuned in the user interface without code.
- Idempotent pull through a cross reference. A dedicated external id model links each Odoo attendance to its Employment Hero id, holding the source timestamp and a payload hash so re runs upsert cleanly and unchanged records are skipped.
- Audited sync runs. Every run records counts for created, updated, skipped, deleted and failed, with a per record line carrying the outcome and message, and an API log of the underlying calls.
- Scheduled or on demand. A daily scheduled run is available behind a master switch and a per job flag, and any job can also be run manually or as a dry run preview from its form.
- Built on the shared sync engine. Pagination, retry with backoff, cluster wide rate limiting, conflict policy and multi company scoping come from the Employment Hero connector and sync engine this module depends on, not from bespoke per module code.
Honest about the edges
What this does not do, so nothing surprises you.
- The kiosk, geofence and face verification metadata is descriptive only. It is stored for audit and reporting and is never interpreted for payroll, rostering or compliance decisions inside Odoo.
- There is no real time webhook listener in this module. Attendance is brought in by a scheduled or manually triggered pull, not by a push from Employment Hero the instant a clock event happens.
- The job ships configured for a pull. A push of Odoo attendances back to Employment Hero is wired as an optional create only path, but it ships disabled with an empty record selection and must be narrowed and enabled deliberately before use.
- The shipped job uses a full read rather than a changed since delta out of the box. Delta mode is supported by the engine but requires setting the source timestamp path and delta parameter for this feed.
- The geofence, kiosk and face verification source paths are sensible defaults based on the published payload shape and may need adjusting to match the exact fields your Employment Hero organisation returns.
- Employees must already exist in Odoo and be linked to Employment Hero, normally through the suite HR module, so each attendance can resolve to the right employee through the cross reference.
- This is an integration for the Employment Hero people platform. It does not replace Employment Hero itself and does not compute pay.
Employment Hero Odoo integration, Employment Hero attendance sync, Odoo attendance connector, clock in clock out import Odoo, hr.attendance Employment Hero, kiosk attendance Odoo, geofence attendance Odoo, face verification attendance, idempotent sync Odoo, scheduled attendance sync, Odoo 16 Community attendance, Employment Hero timesheet entries, no Enterprise attendance connector, people platform integration Odoo, audited sync runs 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.
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 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 | 3656 |
| 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