Employment Hero Canada Pack
Canada statutory employee fields and a registered country profile for the Employment Hero connector.
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 Canada Pack
The identifiers Canadian payroll needs
Adds Social Insurance Number, province of employment and federal TD1 claim code to the employee form, with SIN and TD1 access restricted to HR users so a national id stays private.
Canada registered in the connector
Creates one eh.country.profile record for Canada with a stable CA code, so a deployment can see the localisation is active and point a sync job at the country mapping it wants.
Retune the payload paths without code
The three mapping lines load with noupdate set, so you can adjust the source paths to your organisation's Employment Hero payload from the interface and an upgrade will not overwrite the change.
Day in the life
A new Canadian hire flows in
An employee is created in the Employment Hero platform with a SIN, a province of employment and a TD1 federal code. On the next employee pull, the suite engine maps those payload fields onto the Odoo employee through the mapping lines this pack ships, keying the record by its external id so a re-run never duplicates it. An HR user opens the employee form, sees the Social Insurance Number and TD1 code under the Employment Hero (Canada) group, and ordinary staff never see those fields at all. If the platform later corrects the province, a webhook or the next delta run updates just that field on the existing record.
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 synced employee is keyed by its Employment Hero external id with a payload hash, so re-running the pull never duplicates a record and an unchanged payload is skipped as a no-op.
When the suite webhook receiver is installed, a redelivered event is rejected at the database level by connection and external event id, and a single record is fetched by id rather than re-paginating the whole employee list.
If one employee record fails to map or write, the engine isolates it in a savepoint, logs an error line and continues, ending the run in a partial state instead of aborting the whole batch.
The SIN, province and TD1 source paths load with noupdate set, so a deployment can repoint them to a different payload shape and skip_if_empty keeps a record valid when a value is absent.
A webhook delivery that carries no source timestamp is not allowed to overwrite a newer Odoo record, so a stale, out-of-order update cannot win over fresh data.
The Social Insurance Number and TD1 code are gated to the HR user group at the field level, so they are hidden from users without HR rights even on a shared employee form.
What is inside
Built to do the job, end to end.
- Three statutory employee fields. eh_sin (Social Insurance Number) and eh_td1_federal_code, both restricted to the hr.group_hr_user group, plus eh_province_code for the province of employment, all added to the HR Settings page of the employee form.
- One Canada country profile. A single eh.country.profile record for Canada with code CA and a uniqueness constraint per country, registering the localisation in the suite's country registry.
- Three tunable mapping lines. Mapping lines extending the base Employment Hero employee mapping, binding the payload paths sin, province_of_employment and td1_federal_code to the new fields, all loaded with noupdate so they survive upgrades and stay editable.
- Employee form view. An inherited form view that places an Employment Hero (Canada) group on the existing HR Settings page, with no new menus or screens to learn.
- Test coverage. Tests assert the Canada profile resolves to the correct country with code CA and that the SIN field is present on hr.employee, run on real Odoo.
Honest about the edges
What this does not do, so nothing surprises you.
- This pack adds Canadian fields, one country profile and the mapping lines for them. The fetching, upsert, conflict handling and webhook delivery live in the suite's sync engine, connector and webhook modules, which it depends on and does not replace.
- It carries no API or transport code of its own. It does not call the Employment Hero platform directly.
- The shipped Canadian fields flow inbound on the employee pull. The suite's employee push job sends company email, job title and team, not the SIN, province or TD1 code, so these statutory fields are not written back to the platform out of the box.
- It does not compute Canadian payroll, tax, CPP, EI or T4 figures. It stores identifiers; it is not a payroll engine.
- Source paths are starter values for a typical payload and are meant to be tuned to your own Employment Hero organisation before a production run.
- Requires the Employment Hero country base and HR connector modules from this suite. It is not a standalone connector.
Employment Hero Canada Odoo, Canada payroll integration Odoo 18, Social Insurance Number Odoo employee, SIN field hr.employee, province of employment Odoo, TD1 federal claim code Odoo, Employment Hero connector localisation, Canada country pack Odoo, Odoo 18 Community HR integration, Employment Hero employee sync, Canadian payroll fields Odoo, HR restricted national id 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 18 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 | 4155 |
| Technical Name |
eh_hero_country_ca |
| 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