Employment Hero Country Base
The shared registry every Employment Hero country pack anchors to, one profile per country.
Store price is USD 107 all-in: installing this also pulls the 2 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Country Base
One profile per country
Each country pack registers exactly one eh.country.profile. A unique constraint on the country guarantees two packs can never claim the same country, so the registry stays clean as you add localisations.
A stable seam to build on
The profile is the fixed point the country packs and their mappings reference. Packs add national id fields and ship eh.mapping variants in their own modules; this base just holds the profile they anchor to.
Tracked and access scoped
Every profile carries Odoo chatter, so a change to a country code or its active flag is recorded. Employment Hero users read the registry; only managers create, edit or archive entries.
Day in the life
What this looks like in practice
You install a country pack for a region you operate in. On install it creates its profile in this registry, and you see it listed under the Employment Hero configuration menu with its country, code and active state. You reorder the list by dragging the handle, archive a country you no longer run without deleting its records, and read the chatter to see who last changed a code. The national id fields and field mappings you actually sync live in the country pack itself; this module is the shared list that keeps every localisation accounted for in one place.
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.
A database unique constraint on the country rejects a second profile for the same country, so two packs installed together cannot register the same country twice. The error surfaces at the database level, not as a silent overwrite.
Setting a profile inactive archives it without removing records. The Country Profiles view runs with active_test off, so archived localisations stay visible to managers rather than disappearing.
The profile links to its country with ondelete cascade, so if a country record is removed the orphaned profile is cleaned up with it rather than left dangling.
Employment Hero users get read only access to the registry. Create, edit and archive are restricted to the manager group, so a regular user cannot register or retire a country pack by accident.
A sequence field with a handle widget controls list order, and the model orders by sequence then code, so the registry presents predictably even as packs are added over time.
What is inside
Built to do the job, end to end.
- eh.country.profile model. One thin model: a required country, a stable short code, an active flag, an order sequence and an operator note. One record per country, enforced by a unique constraint. The value is in what each country pack layers on top, not in the base itself.
- List and form views. A list view with a drag handle for sequence and a boolean toggle for active, plus a form with the country, code, ordering and an operator notes box. Reached from a Country Profiles menu under the Employment Hero configuration section.
- Chatter and tracking. The model inherits mail.thread and mail.activity.mixin, so the country, code, active flag and sequence are change tracked and the form carries a full message and activity history.
- Access control. Two access rules: the Employment Hero user group reads the registry, the manager group has full create, edit and unlink rights. No new security groups are defined here; it reuses the suite groups.
- Tested behaviour. Ships a test suite covering profile creation with its defaults and the one profile per country constraint, run on Odoo 16 Community.
Honest about the edges
What this does not do, so nothing surprises you.
- This module is a registry only. It does not add any fields to the employee record. National id and payroll fields are added by the individual country packs, not here.
- It ships no eh.mapping records and no field mappings. The country_id variant lives on the mapping model in the sync module, and the actual mapping data ships in each country pack.
- It performs no validation or format checking of national identifiers. Any format rules belong to the country pack that defines the field.
- It contains no sync, queue, webhook or authentication logic. Those capabilities live in the connector, sync engine, queue and webhook modules this suite depends on.
- It is a dependency for the country packs rather than a standalone feature. On its own it adds the registry and its menu but no country specific behaviour.
- Requires the Employment Hero sync engine module, which in turn requires the connector base. It is not intended to be installed alone.
Employment Hero Odoo integration, Odoo country profile registry, Employment Hero country pack base, Odoo 16 HR localisation foundation, eh.country.profile model, multi country payroll sync Odoo, Employment Hero connector suite, Odoo Community HR no Enterprise, country specific employee fields Odoo, eh.mapping country variant
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.
A dependency free asynchronous job queue that runs long running and fan out work out of band of the request that...
Post Irish payslips to the general ledger on the Irish chart of accounts
Interactive drag and drop Gantt planner for Odoo 16 Community project tasks with a deterministic server side sche...
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...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 3583 |
| Technical Name |
eh_hero_country_base |
| 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