Employment Hero Australia Pack
Australian payroll identifiers for Employment Hero, pulled into Odoo with the TFN and super member number encrypted at rest.
Store price is USD 175 all-in: installing this also pulls the 4 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Australia Pack
The AU identifiers, wired in
Registers the Australian country profile and adds Tax File Number, superannuation fund name and member number, and ABN to the employee form, plus a separate superannuation fund record for employees who split across funds.
Sensitive numbers stay sensitive
The TFN and super member numbers are encrypted at rest and shown masked. The clear TFN is returned only by an audited Reveal action that logs who accessed it and when, matching the statutory handling these numbers expect.
Rides a hardened connector
Data movement runs on the shared connector engine: external-id matching so a record is never duplicated, per-record savepoint isolation, exponential backoff on transient failures, and a configurable conflict policy that defaults to letting Employment Hero win.
Day in the life
What this looks like in practice
An HR user opens an employee in Odoo Community. Under HR Settings sits an Employment Hero (Australia) group showing the masked Tax File Number, the super fund name and member number, and the ABN. Clicking Reveal surfaces the real TFN in a transient notification and quietly writes a PII access log row. Meanwhile the superannuation pull job loads each employee's fund detail from the platform into its own list under the Employment Hero menu, matched back to the right employee by external id. The clear TFN never reaches the browser except through that one audited path.
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.
Pulled superannuation records resolve to the right employee and the right local row through the engine's external-id cross reference, which carries a unique constraint per connection, so a re-run updates rather than duplicates.
Each record is written inside its own savepoint. One malformed fund row is logged as an error line and the run continues to completion in a partial state rather than aborting the whole batch.
The engine retries only transient failures and rate-limit responses with exponential backoff plus jitter, honouring a server Retry-After header but clamping it so a hostile or buggy value cannot stall the run.
Write requests carry an idempotency key reused across retries, so a call the platform already accepted is not applied twice when a retry resends it.
The TFN field loads as a mask. Saving the form without changing it detects the mask and leaves the stored ciphertext untouched, so a routine save can never blank or corrupt the real number.
Upgrading from an earlier version runs a migration that reads any plaintext TFN and member-number columns, encrypts them into the ciphertext columns, and drops the orphaned plaintext.
Superannuation fund records carry a company field defaulting to the active company, and the PII access log records the company against each reveal.
Field source paths ship as a starting point and are marked non-updating, so you can point the TFN, super and ABN mappings at wherever they sit in your own Employment Hero payload without losing your changes on upgrade.
What is inside
Built to do the job, end to end.
- Employee fields. Tax File Number (encrypted, masked, audited reveal), super fund name, super member number (encrypted), and ABN, added under HR Settings on the employee form and restricted to HR users.
- Superannuation fund model. A dedicated eh.hr.super.fund record with fund name, fund type, USI, fund ABN, encrypted member number and contribution rate, with its own list, form and menu, allowing multiple memberships per employee.
- Connector wiring. An Australian country profile, the superannuation endpoint, mapping lines for the AU identifiers and the fund sub-resource, and a pull sync job that loads fund detail per employee with an Employment Hero wins conflict policy.
- Security and migration. Model access rules, a PII access log entry on every TFN reveal, and an upgrade migration that encrypts and removes any legacy plaintext columns.
Honest about the edges
What this does not do, so nothing surprises you.
- This is a country pack, not a standalone integration. It depends on the Employment Hero connector base and HR modules, which carry the connection, authentication and sync engine.
- The Australian identifiers are loaded inbound from Employment Hero. The Tax File Number and super member number are pull only by design, so changes you make in Odoo are not pushed back to the platform.
- This pack ships a scheduled and on-demand pull job. It does not register a real-time webhook subscription for the Australian data, so updates arrive when a sync runs rather than the instant they change upstream.
- Conflict handling is policy based and defaults to letting Employment Hero win. It is not a field-by-field merge or interactive conflict resolver.
- The superannuation endpoint is an employee sub-resource, so a deployment drives it per employee by supplying the employee id; it does not bulk-list every fund in one call.
- Field source paths are starting points tuned to a common payload shape. They may need adjusting to match how your organisation structures its Employment Hero data, and some tax and super detail may need a payroll-sourced job.
- Encryption at rest protects the database contents. It relies on the key handling provided by the connector base module.
Employment Hero Odoo integration, Odoo 18 Australia payroll, Tax File Number Odoo, superannuation Odoo, Odoo TFN encryption, Australian Business Number Odoo, Employment Hero connector, Odoo HR payroll sync, ABN employee field, super fund USI Odoo, Odoo Community HR Australia, PII access log Odoo, employee data sync Australia, Odoo payroll localisation, Employment Hero Australia
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.
Employment Hero Connector is the integration core of the ERP Heritage Employment Hero suite, providing per compan...
Sync certifications, qualifications and employee document metadata from the Employment Hero people platform into...
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 18
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...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 4388 |
| Technical Name |
eh_hero_country_au |
| 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