Employment Hero AU Payroll
The Australian endpoints and mapping variants the work entry sync needs, shipped as configuration, no new models.
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
Configuration, not code
Two endpoints, two mapping variants and one pull job, all shipped as data rows. No new payroll models are created, so the overlay installs on top of the work entry module without colliding with the base mapping.
Australian shape, isolated
The work entry mapping is scoped to Australia with country_id set to base.au, so the engine selects the Australian variant for Australian companies and a deployment can tune it without an upgrade overwriting the change.
Rides the audited sync engine
Pulls run through the same orchestrator the rest of the suite uses: external id cross reference, idempotent upsert, per record isolation and explicit conflict policy. This overlay supplies the Australian catalogue, the engine does the work.
Day in the life
An Australian deployment wires up its payroll catalogue.
The company country is Australia, so the engine picks the Australian work entry mapping variant the moment the overlay is installed. The STP category pull job runs against the pay category endpoint, paginating through the list and upserting each Single Touch Payroll category onto an Odoo work entry type, keyed by its external id, so a second run never duplicates one. The reporting code is stored on the external code field for later use. A bad row is logged as an error line and the run ends partial rather than aborting the whole batch. The superannuation endpoint sits in the catalogue ready for the deployment to point its own job at when it builds out super reporting. Nothing here invented a new payroll model; the overlay shipped the Australian endpoints and shapes, and the existing engine did the rest.
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 keys every record by its external id through the cross reference table, so re running the job, or replaying it, upserts in place and never creates a duplicate work entry type.
Each record is processed inside its own savepoint. One bad pay category rolls back just that row, is recorded as an error line, and the run ends in the partial state instead of poisoning the whole batch.
The Australian endpoints declare the OData page style at size 100, so the engine walks every page of superannuation payments and pay categories and stops when a short page signals the end of the list.
The mapping variants ship with noupdate set so a later module upgrade ships endpoint corrections but never overwrites the field mapping a deployment has tuned for its own Australian shape.
The STP pull job declares an explicit eh_wins conflict policy, so a category changed on both sides resolves by a rule that was chosen rather than by accident.
The work entry mapping carries country_id base.au, so the Australian variant is selected only for Australian companies and the default mapping stays untouched for everyone else.
What is inside
Built to do the job, end to end.
- Australian payroll endpoints. Two GET endpoints registered as data: superannuation contributions and Single Touch Payroll pay categories, both on the payroll product with OData pagination at page size 100 and a shared payroll rate group.
- Australian work entry mapping. A pull mapping variant for hr.work.entry scoped to Australia, mapping name, employee, date, duration and work entry type, with the employee and type resolved by external id so the Australian shape can diverge from the default.
- STP category mapping and job. A pull mapping onto hr.work.entry.type and a sync job that lands Single Touch Payroll categories on work entry types, storing the STP reporting code on the external code field, keyed by external id with an eh_wins conflict policy.
- No new models. The overlay ships configuration only. It creates no payroll models and adds no fields; it registers endpoints, mappings and one job onto existing models so it installs cleanly on the work entry module.
Honest about the edges
What this does not do, so nothing surprises you.
- Configuration only. This overlay ships endpoints, mapping variants and one pull job as data; it creates no new payroll models and adds no employee fields. It prepares the Australian catalogue a deployment builds its own jobs on, not a finished payroll feature.
- The shipped inbound flows pull from the platform into Odoo. This overlay does not push Australian payroll data back out; the engine supports push, but no push job is configured here.
- Only one job ships ready to run, the Single Touch Payroll category pull. The superannuation endpoint is registered for a deployment to wire into its own job, not run out of the box.
- Requires the work entry module it depends on and, through it, the Odoo Enterprise Payroll work entry models. It targets Odoo 18 and is not a standalone payroll calculation engine.
- The Australian work entry mapping is shipped as a variant for a deployment to tune; it is configuration ready to diverge, not a turnkey Australian payroll import.
Employment Hero Odoo integration, Employment Hero AU payroll, Single Touch Payroll Odoo, STP category sync, superannuation endpoint Odoo, KeyPay API connector, Odoo 18 payroll sync, work entry sync Australia, Australian payroll mapping, idempotent payroll integration, Employment Hero connector, Odoo work entry type import
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 | 4259 |
| 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