Employment Hero Malaysia
Malaysia statutory identifiers and country profile for the Employment Hero connector on Odoo 18 Community.
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 Malaysia
The three numbers Malaysia needs
EPF, SOCSO and MyKad as first class employee fields, so a Malaysian workforce records its statutory identifiers in Odoo without custom fields or one off scripts.
MyKad seen only by HR
The MyKad national identity field is restricted to the HR user group, so a sensitive number stays off the form for users who do not need it.
Travels with the employee sync
Three mapping lines extend the suite's shared employee mapping, so the Malaysian numbers flow with the standard sync rather than needing a bespoke job, and the source paths are tunable as data.
Day in the life
What it looks like in use
You install the pack alongside the connector and HR modules. The Malaysia country profile registers itself. On every employee form, an Employment Hero (Malaysia) group appears under HR Settings with EPF Number, SOCSO Number and MyKad, where MyKad is visible only to HR users. When the employee sync runs, the three mapping lines pull the matching values out of the Employment Hero payload into those fields. If your payload uses different key names, you adjust the mapping source paths in place, no code change, and the next sync picks them up.
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 mapping lines ship with update protection, so the source paths epf_number, socso_number and mykad_number are starting points you can edit to match your actual Employment Hero payload keys without a module upgrade overwriting your change.
The Malaysia profile is keyed to the country with a unique per country constraint and cascade delete, so reinstalling or upgrading does not create a duplicate profile.
MyKad is gated to the HR user group at the field level, so a user without HR rights cannot read it even on a form they can otherwise open.
A field with no incoming value is simply left unset; a missing EPF, SOCSO or MyKad number does not block the rest of the employee record from syncing.
Duplicate prevention and upsert against the external id cross reference are handled by the connector and sync engine this pack depends on, so a job that runs twice does not duplicate employees, and this pack inherits that behaviour rather than reimplementing it.
What is inside
Built to do the job, end to end.
- Employee fields. Adds eh_epf_number, eh_socso_number and eh_mykad to hr.employee, with eh_mykad restricted to the hr.group_hr_user group and surfaced in a dedicated group on the HR Settings page of the employee form.
- Country profile. Registers one eh.country.profile record for Malaysia, country code MY, sequence 10, with the unique per country constraint and cascade delete provided by the shared country base.
- Mapping extensions. Adds three eh.mapping.line rows to the suite's shared employee mapping, pointing the source paths epf_number, socso_number and mykad_number to the three new fields, shipped with update protection so they remain operator tunable.
- Tests. Ships an automated test suite that confirms the Malaysia profile is registered against the correct country and that the MyKad field is present on the employee model.
Honest about the edges
What this does not do, so nothing surprises you.
- This pack only adds Malaysian fields, the country profile and mapping rows. The API transport, queue, retries and audited sync runs live in the connector and HR modules it depends on, which must be installed.
- The mapping source paths are sensible defaults, not a guarantee against a specific Employment Hero account shape. You may need to adjust them to match your payload keys.
- It does not validate the format of EPF, SOCSO or MyKad numbers. The fields accept the values delivered by the sync or entered by a user as plain text.
- It does not compute Malaysian payroll, EPF or SOCSO contributions. It records the identifiers, it does not calculate statutory deductions.
- Depends on eh_hero_country_base and eh_hero_hr. It is not a standalone connector and does nothing useful without them.
- Targets Odoo 18 Community. Use the matching version of the suite for your Odoo release.
Employment Hero Malaysia, EPF number Odoo, SOCSO number Odoo, MyKad field, Malaysia HR localisation, Odoo 18 Malaysia employee fields, Employment Hero connector, Malaysia payroll integration, hr.employee statutory fields, country profile Odoo, Malaysia employee identifiers, Odoo Community HR sync
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.
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...
The New Zealand country pack for the ERP Heritage Employment Hero integration
A reusable two way synchronisation engine that keeps Odoo in step with the people and payroll platform, idempoten...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 4152 |
| Technical Name |
eh_hero_country_my |
| 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