Employment Hero Malaysia
Adds EPF, SOCSO and MyKad to the Employment Hero connector for Malaysian payroll teams.
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 identifiers MY payroll needs
Adds EPF Number, SOCSO Number and MyKad to hr.employee, with MyKad restricted to HR users. Each lands on the record through the connector's pull mapping when an employee syncs from the people platform.
Malaysia shows up as a country pack
Ships one eh.country.profile record for Malaysia with a stable MY code. A deployment can see the localisation is active and point country specific mapping variants at it without touching the generic configuration.
No bespoke integration code to trust
The pack adds fields and data only. Pull sync, external id dedupe, per record savepoints, webhook idempotency, retry queues and rate limiting all come from the shared connector and are not reimplemented here.
Day in the life
What a Malaysia sync actually does
The connector pulls an employee from the Employment Hero people platform. The shared HR employee mapping resolves first and last name, work email and the rest of the profile, then the three lines this pack adds read the EPF, SOCSO and MyKad values from the payload and write them to the Odoo employee. An external id cross reference ties the two records so the next run updates rather than duplicates, and an unchanged payload is skipped by hash. The HR team opens the employee form and finds the Employment Hero (Malaysia) group populated, with MyKad visible only to HR users.
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.
Each Employment Hero record is cross referenced by external id, so re running a job updates the existing employee instead of creating a duplicate. An unchanged payload is detected by hash and skipped.
The orchestrator wraps each record in its own savepoint. A bad row, for example a value that fails a constraint, is recorded as failed and the run continues, ending in the partial state rather than aborting the whole batch.
The mapping lines keep skip_if_empty behaviour, so an employee without an EPF, SOCSO or MyKad value on the source is left untouched rather than overwritten with a blank.
A uniqueness constraint on connection plus external event id means a redelivered webhook is recognised and not processed twice, and only HMAC verified events are dispatched.
A failed sync job is retried with exponential backoff up to a configured limit, then parked in the dead letter state for manual inspection rather than lost or looped forever.
A cluster wide token bucket meters calls across workers against the database clock, so multiple workers do not multiply the request rate into a 429 storm from the vendor.
The MyKad field is bound to the HR user group, so the national identity number is hidden from non HR users on the form and in exports.
The EPF, SOCSO and MyKad source paths are shipped as editable data (noupdate). If your Employment Hero payload names them differently, an administrator adjusts the mapping line without a code change.
What is inside
Built to do the job, end to end.
- Employee fields. eh_epf_number, eh_socso_number and eh_mykad on hr.employee. MyKad carries groups=hr.group_hr_user so it is restricted to HR users. All three appear in an Employment Hero (Malaysia) group on the employee form under HR Settings.
- Country profile. One eh.country.profile record for Malaysia with country base.my and code MY, loaded with noupdate so a deployment can adjust it. This is the anchor that marks the localisation active.
- Mapping lines. Three eh.mapping.line records appended to the shared HR employee mapping, reading epf_number, socso_number and mykad_number from the source payload into the matching fields. Paths are editable per deployment.
- Form view. An inherited hr.employee form view that adds the Employment Hero (Malaysia) group inside the HR Settings page so the statutory fields sit with the rest of the local configuration.
- Tests. Two tests confirm the Malaysia profile is registered against the correct country with code MY, and that the MyKad field is present on hr.employee after install.
Honest about the edges
What this does not do, so nothing surprises you.
- This is a localisation pack, not a standalone integration. It requires the Employment Hero connector and HR modules it depends on, and does nothing on its own.
- It adds fields and mapping data only. It ships no sync logic, no webhook handler and no queue of its own. Those behaviours are inherited from the connector engine.
- The EPF, SOCSO and MyKad source paths are sensible defaults but are not verified against a live Employment Hero Malaysia payload. Confirm and adjust them to match your tenant.
- The shipped HR employee mapping is pull oriented (Employment Hero to Odoo). These identifiers are read into Odoo by default and are not pushed back upstream unless you configure a push.
- No Malaysian payroll calculation, EPF or SOCSO contribution logic, or statutory reporting is included. The pack stores the identifiers and leaves computation to your payroll system.
- MyKad access control follows Odoo's standard HR user group. It restricts the field to HR users but is not a substitute for a wider data protection review.
Employment Hero Malaysia, Odoo Employment Hero connector, EPF number Odoo, SOCSO number Odoo, MyKad employee field, Malaysia HR integration Odoo, Employment Hero people platform sync, Odoo 17 Malaysia localisation, hr employee statutory fields, Employment Hero country pack, Malaysia payroll integration Odoo, 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 17
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 | 4168 |
| 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