Employment Hero Attendance Sync
Pull Employment Hero clock events into the standard Odoo Attendances app, carrying kiosk, geofence and face verification metadata 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 context, not just times
A synced attendance keeps the kiosk, source, geofence coordinates and face verification flag it carried in Employment Hero, so an audit can see where and how each clock event was captured, not only when.
Idempotent by external id
Every record is keyed by its Employment Hero id through a cross reference with a unique constraint. Running the job twice reconciles the same records instead of creating duplicate attendances, and an unchanged payload is a no op.
Mappings ship as tunable data
The endpoint, the field mapping and the sync job are data records. Source paths for kiosk, geofence and face fields are starting points you adjust to your organisation payload shape from the interface, with no deployment.
Day in the life
A normal sync, start to finish
A scheduled run reads Employment Hero clock events page by page, maps each entry to an Odoo attendance, and resolves the employee through the external id cross reference seeded by the HR sync. New clock events create attendances, repeats are matched and reconciled rather than duplicated, and the kiosk, source, geofence and face verification fields are filled from the payload. A record that fails, for example one whose employee is not yet synced, is rolled back on its own savepoint and recorded as an error line while the rest of the batch completes. The run finishes with counts for fetched, created, updated, skipped and failed, and the operations team reviews the log instead of reconciling a spreadsheet export by hand.
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 Employment Hero id through a cross reference with a unique constraint, so re running a job, or replaying the same feed, reconciles records instead of duplicating attendances.
A mapped payload that hashes to the same value as the last sync is skipped as unchanged, so a steady state run does not rewrite records that did not move. The hash folds in the mapping definition, so editing a mapping line forces a rewrite next run.
Each record is processed inside its own savepoint. A failing record, such as one referencing an employee not yet synced, rolls back alone and is logged as an error line; the rest of the batch still commits and the run ends in a partial state.
The pull walks every page of the clock event feed and stops on a short or empty page, so large date ranges are fetched in full rather than capped at the first page.
The transport retries transient failures and rate limit responses with exponential backoff and jitter, honours a Retry-After header, and clamps it so a hostile or buggy header cannot park a worker for hours.
One rate token is spent per logical call and retries do not re acquire, and an exhausted cluster wide budget raises before a request is sent, so the client backs off rather than adding to a 429 storm.
Where a deployment enables the outbound leg, push writes carry a stable Idempotency-Key so a retried create is deduplicated by the vendor instead of producing a second record.
Connections and external id links carry a company, so attendance cross references are resolved per company and one company sync does not collide with another.
OAuth2 transport reads the access token through a refresh callback on the connection, so an expired token is refreshed transparently without the sync job handling token lifetimes.
A mapping line can carry a default value, so the capture source field falls back to a sensible value when the payload omits it, and geofence and face source paths can be retargeted to your payload shape from the interface.
What is inside
Built to do the job, end to end.
- hr.attendance metadata fields. Adds kiosk, capture source, geofence latitude and longitude, a face verified flag and an Employment Hero source reference to the standard attendance, all descriptive only and never read for payroll.
- Endpoint and mapping data. Ships the clock event endpoint definition, an attendance field mapping with employee, check in, check out, kiosk, geofence, face and reference lines, and the sync job that ties them together, all as data records you can tune.
- Sync job on the engine. A configured pull job that runs on the Employment Hero sync engine: paginated fetch, external id reconciliation, an explicit conflict policy, and a per record sync line written to the run for audit.
- Automated test suite. Ships a test that drives the shipped mapping and job against a simulated API and asserts the attendance and every metadata field land correctly, including geofence coordinates and the face verification flag.
Honest about the edges
What this does not do, so nothing surprises you.
- Depends on eh_hero_sync and the wider Employment Hero connector for the transport, cross reference and run audit, and on the HR sync so that employees already carry an external id link before attendances resolve.
- Capture metadata is descriptive only. The kiosk, geofence and face verification fields are stored for audit and reporting and are never interpreted for payroll, rostering or compliance decisions inside Odoo.
- Geofence, kiosk and face verification source paths ship as best guess starting points and are meant to be tuned to the exact shape your Employment Hero organisation returns.
- The pull leg is the working path out of the box. The job declares an outbound direction with a create endpoint, but no update endpoint and an empty push domain ship by default, so the push back to Employment Hero stays dormant until a deployment configures and scopes it.
- Real time webhook delivery and the asynchronous queue live in separate suite modules and are not part of this package; this module ships the attendance pull job and metadata fields.
- Targets Odoo 17 Community Attendances. No Enterprise dependency.
Employment Hero attendance, Employment Hero attendance sync Odoo, Odoo attendance integration, clock event import Odoo, kiosk attendance Odoo, geofence attendance Odoo, face verification attendance, Employment Hero connector, Odoo 17 attendance sync, hr attendance integration, idempotent attendance sync, timesheet entry import 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 17 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 | 3695 |
| 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