Employment Hero AU Payroll
An Australian overlay that teaches the Employment Hero work entry sync the local payroll shape, with superannuation and STP endpoints and a country scoped mapping.
Store price is USD 235 all-in: installing this also pulls the 4 paid ERP Heritage modules it depends on.
Why this module
Employment Hero AU Payroll
An overlay, not a fork
No new payroll models. The module ships endpoints, a country scoped mapping and a job as data, so it installs cleanly on top of the work entry connector and inherits the engine rather than reimplementing it.
Diverge AU without forking the base
The work entry mapping variant is scoped to Australia, so the sync engine picks the Australian shape when the company country is Australia, and a deployment can tune it without disturbing the default mapping for other countries.
Endpoints in the catalogue, jobs in the UI
Super and STP endpoints land in the data driven endpoint registry. The STP category pull runs out of the box, and the super endpoint is ready for a deployment to wire into its own job, all from the user interface.
Day in the life
An Australian deployment goes live on the work entry sync
You install on top of the Employment Hero work entry connector. The Australian work entry mapping is now scoped to base.au, so the engine selects the Australian shape for an Australian company. You point the STP category job at your payroll connection and run it: it pulls KeyPay pay categories onto Odoo work entry types, keyed by external id, with the reporting code landing on the external code field. You open the superannuation endpoint, confirm the KeyPay superpayment path, and wire it into your own job when you are ready to pull contribution data. Every mapping line and the conflict policy are editable from the user interface, so adjusting the Australian shape never touches Python.
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 STP category pull is keyed through the external id cross reference, so re running the job never duplicates a work entry type. An unchanged payload is recorded as a skip rather than a rewrite.
The STP category job ships with Employment Hero wins as the inbound precedence, so a re pull refreshes the local record from the source. The policy is a field you can change to Odoo wins or newest wins from the UI.
Both Australian endpoints declare OData pagination at one hundred records a page, so the engine walks the full superannuation and pay category lists rather than reading only the first page.
The underlying engine wraps each record in a savepoint, so one bad pay category is logged as an error line and the run continues to a partial state instead of aborting the whole pull.
The endpoints ship with noupdate cleared so corrections reach an existing database on upgrade, while the mappings and job ship with noupdate set so a deployment can tune the Australian shape without an upgrade overwriting it.
Because the engine folds a mapping fingerprint into the per record hash, editing an Australian mapping line rewrites existing records on the next run instead of skipping them as unchanged.
What is inside
Built to do the job, end to end.
- Australian endpoints. Two GET endpoints registered as data: superannuation contributions on the KeyPay superpayment path and STP categories on the paycategory path, both payroll product, OData paged at one hundred, on the payroll rate group.
- Country scoped mappings. A work entry pull mapping scoped to base.au that mirrors the base work entry shape with name, employee, date, duration and work entry type lines, plus an STP category mapping that lands name, code and the STP reporting code onto a work entry type.
- STP category job. A ready to run pull job that reads the STP category endpoint through the STP mapping onto hr.work.entry.type, keyed by external id, with Employment Hero wins as the inbound conflict policy.
- Tests. A post install test asserting the two endpoints, the Australia scoped work entry mapping with its lines, and the STP category job with its endpoint and mapping wiring are all present after install.
Honest about the edges
What this does not do, so nothing surprises you.
- This module ships configuration only. It creates no payroll models and computes no superannuation or STP figures; it prepares the endpoints and mappings an Australian deployment builds on.
- The superannuation contributions endpoint is shipped ready for a deployment to wire into its own job. Out of the box only the STP category pull is wired and runnable.
- The shipped jobs and mappings pull from Employment Hero into Odoo. Push and two way operation are engine capabilities you configure per job; this overlay does not ship a push job.
- It requires the Employment Hero work entry module and, through it, the connection, sync and queue engine that own transport, authentication, pagination, retry and webhook handling.
- Mapping source paths reflect the KeyPay payroll API shape and may need tuning in the user interface to match your account before a job is run in production.
- Targeted webhook delivery for these jobs depends on a detail endpoint and subscription configured in the webhook module; the data shipped here is the list pull configuration.
Employment Hero Odoo, Employment Hero Australia payroll, KeyPay Odoo integration, Single Touch Payroll Odoo, STP category sync, superannuation Odoo connector, Odoo work entry sync, hr.work.entry mapping, Australian payroll connector Odoo 16, OData pagination Odoo connector, external id sync Odoo, country scoped mapping 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.
Real-time fiscalisation of customer invoices and credit notes with the Mauritius Revenue Authority e-Invoicing (E...
The Canada country pack for the ERP Heritage Employment Hero integration
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
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4228 |
| Technical Name |
eh_hero_ent_country_au |
| 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