Employment Hero United Kingdom
The United Kingdom localisation for the Employment Hero suite: National Insurance number and the country profile the sync engine maps against.
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 United Kingdom
United Kingdom specifics, cleanly
Adds the United Kingdom identifiers and statutory fields the platform sends, access restricted to HR, without forking the standard employee form.
One profile, one anchor
Registers a single United Kingdom profile in the shared registry, the place a deployment sees which localisations are live and routes a sync job to a country mapping.
Part of one suite
Builds on the same connector, queue and sync engine as every other Employment Hero module, so the United Kingdom fields flow through the same audited, retried transport.
Day in the life
Turning on United Kingdom in a multi country roll out
A deployment running several countries installs the United Kingdom pack. The United Kingdom profile appears in the registry, the new United Kingdom fields show on employees in that company, and a sync job for United Kingdom employees is pointed at the country mapping variant so the right payload fields land in the right place. The generic mapping keeps serving the other countries unchanged.
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.
The registry enforces a unique constraint of one profile per country, so installing the pack twice or alongside a clashing pack cannot create a duplicate United Kingdom profile.
Archiving the profile (unchecking active) retires the localisation without deleting its records, so a country can be turned off and back on without data loss.
The National Insurance number is a restricted field on the employee, kept out of self service views, so a national identifier is not casually exposed.
What is inside
Built to do the job, end to end.
- United Kingdom employee fields. Adds the National Insurance number to the employee record, access restricted to HR, contributed through a model inherit rather than a forked employee form.
- Country profile registration. Registers exactly one United Kingdom profile (code UK) in the shared eh.country.profile registry, the anchor a deployment uses to see which localisations are active and to point a sync job at a country specific mapping variant.
- Country scoped mappings. Because the profile carries a country, an eh.mapping tuned to the United Kingdom payload shape can be selected per sync job while the generic mapping serves the rest.
Honest about the edges
What this does not do, so nothing surprises you.
- This pack adds fields and a profile. It does not by itself run a sync; the connector and a sync job from the core suite move the data.
- It localises employee data and mapping selection. It is not a statutory payroll calculator and does not compute United Kingdom tax or contributions.
- Requires the Employment Hero country base and the core connector, which install automatically.
Employment Hero United Kingdom, National Insurance number Odoo, United Kingdom HR fields Odoo, United Kingdom employee localisation, Odoo 19 HR United Kingdom, multi country HR integration, country specific field mapping, Employment Hero country pack
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.
Real-time MRA fiscalisation for Point of Sale receipts in Odoo 19 Community, mapping each paid POS order to the M...
Shared foundation for the ERP Heritage Employment Hero country packs
Imports finalised pay run journals from the Employment Hero payroll platform (KeyPay) into Odoo Community account...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 4170 |
| Technical Name |
eh_hero_country_uk |
| 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