Employment Hero New Zealand Pack
New Zealand payroll identifiers on the employee record, wired into the Employment Hero sync.
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 New Zealand Pack
The three identifiers NZ payroll needs
Adds IRD number, PAYE tax code, and KiwiSaver rate to the employee record, grouped on the HR Settings page so they sit with the rest of the employment data.
Mapping lines ready on install
Ships three mapping lines into the shared employee field mapping, pointing at the New Zealand parts of the source payload so values land on the right fields when a sync runs.
Sensitive identifiers kept private
The IRD number and tax code are restricted to HR users through Odoo field groups, so national identifiers do not appear for staff without HR access.
Day in the life
How it shows up in practice
An HR user opens an employee, goes to the HR Settings page, and sees an Employment Hero (New Zealand) group with IRD number, tax code, and KiwiSaver rate. When a sync job pulls employees from Employment Hero, the connector reads the matching values from the source payload and writes them to these fields, skipping any that are empty so existing data is not blanked out. The country profile record confirms the New Zealand pack is installed and active.
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.
Mapping lines write only when the source value is present, so a missing IRD number or tax code in the payload leaves the existing field untouched rather than clearing it.
Source paths ship as defaults (ird_number, tax_code, kiwisaver_rate) and are marked non-updating, so you can adjust them to match your actual Employment Hero payload shape without losing the change on upgrade.
The underlying sync engine keys every record by its external id, so a repeated pull of the same employee updates in place rather than creating duplicates.
These identifiers are read in from Employment Hero and are not pushed back, so a value the platform owns is not overwritten upstream by a local edit.
Because IRD number and tax code carry HR field groups, a user without HR access does not see or read those fields even through the form or exports.
What is inside
Built to do the job, end to end.
- Employee fields. Three Char fields on hr.employee: eh_ird_number and eh_tax_code restricted to the HR user group, and eh_kiwisaver_rate, all added by a clean model inherit.
- Country profile. A single eh.country.profile record for New Zealand with code NZ, the anchor a deployment uses to confirm the localisation is installed and active.
- Mapping lines. Three eh.mapping.line records added to the shared HR employee mapping, each pairing a source path to its target field with empty values skipped by default.
- Form view. An inherited employee form view that adds an Employment Hero (New Zealand) group inside the HR Settings page so the local fields sit alongside core HR data.
Honest about the edges
What this does not do, so nothing surprises you.
- This is a localisation layer, not a standalone integration. It depends on the Employment Hero base and HR connector modules, which provide the connection, OAuth, rate limiting, mapping engine, and sync jobs.
- It adds employee identifier fields and their mapping. It does not compute PAYE, KiwiSaver, or any New Zealand payroll calculation.
- The mapping source paths are shipped as defaults and are not guaranteed to match every Employment Hero payload. Verify and adjust them against your own account before relying on a sync.
- Fields are populated by inbound pull from Employment Hero. This pack does not push New Zealand identifiers back out to the platform.
- Built for Odoo 16 Community. It does not require Enterprise and does not depend on any Enterprise payroll module.
Employment Hero New Zealand, Odoo Employment Hero connector, New Zealand IRD number Odoo, PAYE tax code employee field, KiwiSaver rate Odoo HR, hr.employee New Zealand localisation, Employment Hero field mapping, Odoo 16 HR integration, payroll identifier sync, New Zealand country pack 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.
Sync attendance clock events from the Employment Hero people platform into the stock Odoo Attendances app, keyed...
The United Kingdom country pack for the ERP Heritage Employment Hero integration
Sync Employment Hero employees, departments and payroll bank details into standard Odoo Community HR over the pla...
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...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 4124 |
| Technical Name |
eh_hero_country_nz |
| 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