Employment Hero Payroll Bridge
Post finalised Employment Hero pay runs straight into your general ledger, once each, balanced to the cent.
Store price is USD 157 all-in: installing this also pulls the 2 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Payroll Bridge
Payroll lands in the ledger
A finalised pay run becomes a balanced journal entry in your chosen general journal. Wages, tax withheld and superannuation hit the right accounts without anyone retyping figures from a payroll report.
Never the same pay run twice
Each entry remembers its source pay run id, backed by a database uniqueness constraint and a pre-scan before every create. Click import, re-run the job or let the schedule fire, the result is one entry per pay run per company.
Your codes, your accounts
Match an Employment Hero account code to any Odoo account, or let it fall back to the Odoo account code. An unmapped account or an unknown tax code stops only that one pay run with a clear message, never a silent wrong posting.
Day in the life
Friday pay run, Monday ledger
Payroll finalises the weekly run in Employment Hero on Friday. Over the weekend the scheduled job reads it, matches each line to your accounts by its Employment Hero code, and posts a single balanced entry into your general journal. Monday morning the wages, PAYG and super are already in the general ledger, stamped with the pay run id, and nobody opened a spreadsheet. A draft run from the same period is ignored until it is finalised, and last quarter's runs stay untouched because they fall on or before the bridge lock date.
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.
A pay run id already imported for the company is skipped on a pre-scan, re-checked just before create, and blocked at the database by a unique constraint, so concurrent runs still converge on one entry.
One bad pay run, an unmapped account, a non-numeric amount or a locked period, is rolled back inside its own savepoint and skipped with a logged reason, while every other pay run in the batch still imports.
The underlying connection retries transient failures and 429 rate limits with exponential backoff and jitter, honouring a clamped Retry-After header, so a busy payroll API does not lose an import.
Pay run lists are read page by page through the connection's paginator, so a long history of finalised runs is walked completely rather than truncated to the first page.
A pay run in a foreign currency is balanced on its own currency side first, converted to the company currency per line, and any sub-unit rounding drift is absorbed on a configured rounding account rather than failing the post.
Each bridge is scoped to one company through record rules, and the idempotency key is unique per company, so two companies can import their own pay runs side by side without crossing the streams.
A non-numeric or non-ASCII amount raises and skips that pay run rather than silently posting a wrong but balanced-looking entry, because a hard recoverable failure beats a quiet error in the books.
An optional cut-off date keeps historical runs untouched, so you can switch the bridge on mid-year and import only pay runs paid after the date you choose.
What is inside
Built to do the job, end to end.
- Pay run bridge. One bridge per company names the payroll connection to pull from, the general journal to post into, an optional rounding account and an optional lock date. A counter shows how many entries it has imported, with a link straight to them.
- Account and tax mapping fields. Adds an Employment Hero account code to accounts and an Employment Hero tax code to taxes, both indexed. These drive how pay run journal items resolve, with the Odoo account code as a clean fallback when no explicit code is set.
- Pay run stamp. Every imported journal entry carries its Employment Hero pay run id, copy-protected and backed by a per-company unique constraint, so the move tells you exactly which pay run it came from and can never be duplicated.
- Scheduled import. A built-in scheduled job runs the import for every configured bridge, isolating each bridge so one failing connection never aborts the rest. Run it on demand from the bridge form whenever you prefer.
- Employee payslip pull. A separate payslip record holds the per-employee earnings, tax, deductions, super and net breakdown pulled from the platform, for reference and reporting alongside the aggregate accounting entry.
Honest about the edges
What this does not do, so nothing surprises you.
- Import is pull-only and one-directional. It reads finalised pay runs from Employment Hero and writes journal entries into Odoo. It never pushes data back to the payroll platform.
- This module does not run real-time webhooks. Imports happen on the scheduled job or when you trigger them manually. The default schedule is weekly and is adjustable.
- It does not run Odoo payroll or generate payslips itself. It posts the accounting entry from a pay run that was already calculated and finalised in Employment Hero.
- Only finalised pay runs are imported. Draft or in-progress runs are ignored until they are finalised at the source.
- Accounts and taxes must exist in Odoo and carry the matching Employment Hero code, or share the Odoo account code. An unmapped code stops that pay run with a clear message rather than guessing.
- Requires an active Employment Hero Payroll (KeyPay) connection configured in the ERP Heritage Employment Hero connection engine.
- The employee payslip pull ships ready with mapping source paths that follow the standard payload and may need tuning to match your account's exact field names.
Employment Hero Odoo integration, KeyPay Odoo journal import, Employment Hero payroll bridge, pay run journal entry Odoo, payroll to general ledger Odoo, Odoo 18 payroll integration, KeyPay pay run accounting, import payroll journal Odoo, Employment Hero accounting sync, payroll journal automation Odoo Community
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 |
•
Discuss (mail)
• Employees (hr) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4354 |
| Technical Name |
eh_hero_payroll_bridge |
| 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