| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Discuss (mail) • Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 2415 |
| Technical Name |
eh_hr_attendance_award_au |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Versions | 16.0 17.0 18.0 19.0 |
AU Modern Award Engine
Interpret every attendance into ordinary, penalty, and overtime hours against your Australian Modern Award, automatically, on Community.
Why this module
AU Modern Award Engine
Segment by segment, not one rate per shift
A shift from Friday 22:00 to Saturday 02:00 is not billed entirely as Friday ordinary. The engine cuts the interval at every midnight and penalty band edge, classifies each segment by its own date and clock, and applies public holiday over Sunday over Saturday over band over ordinary. The hard part of award work, done in code.
Writes straight onto the attendance row
Ordinary, penalty, overtime tier 1, overtime tier 2, and effective pay hours are stored computes on hr.attendance with the right dependencies. Close a shift, change an employee award, or add a public holiday, and the buckets recompute. The payroll exporter, list, and form all read the awarded values with no extra step.
Your rates, your award, yours to keep
Rates are data on a per company award record, never hard coded. A General Retail baseline ships configured so loadings apply on day one. LGPL-3 source on disk, no activation key, no phone home. Copy the baseline, edit the multipliers, and model whatever award your workforce sits under.
Day in the life
A retail manager runs a week of mixed shifts.
An employee works four weekday day shifts and one Friday late that runs past 6:00 pm and on into Saturday morning. The engine fills the daily ordinary cap, then tips the Friday excess into overtime tier 1; the post 6:00 pm segment picks up the configured evening band, and the segment after midnight is classified as Saturday penalty at the Saturday rate. Across the week, the ordinary hours that cross the 38 hour cap on the last shift move into the overtime tiers, and adding that Friday shift recomputes the rest of the week so the overtime lands on the right row regardless of entry order. A casual flag adds the award loading to every hour. Each attendance ends up carrying its ordinary, penalty, two overtime tiers, and effective pay hours, ready for the payroll exporter.
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 shift that spans midnight is split at the boundary and each side is classified by its own date. Friday 22:00 to Saturday 02:00 is two ordinary hours on Friday and two Saturday penalty hours, not four Friday ordinary hours.
When a day is both a weekend and a public holiday, the public holiday rate wins. The classifier ranks public holiday over Sunday over Saturday over an explicit penalty band over ordinary, segment by segment, so a holiday never silently gets paid as a normal weekend.
Weekly overtime over the 38 hour cap and broken shift detection are cross record. Adding or editing one shift recomputes the employee's other attendances in the same Monday to Monday work week, so the overtime excess and the once per day broken shift allowance stay correct no matter what order shifts are entered.
Two or more periods on one day split by an unpaid gap of an hour or more mark a broken shift, and the flat allowance is paid exactly once, on the last period worked that day, never doubled across the periods.
A shift shorter than the award minimum engagement is topped up to the floor in a separate field, kept out of the rate weighted pay hours so it does not distort the multiplier maths; the payroll exporter sums it in.
Awards and public holidays are scoped by a global per company record rule, with a company empty value meaning all companies. When the leave suite is installed, the award reads the canonical public holiday calendar unioned with its own rows, so a holiday entered once is honoured in both places.
An attendance with no check out, a zero or inverted duration, or an employee with no assigned award resolves to all zero buckets rather than a half computed or negative result. Award rates are constrained positive at write time.
What is inside
Built to do the job, end to end.
- Per company award records. Each award carries the daily ordinary cap, weekly cap, two overtime tier multipliers and the tier 1 hour cap, Saturday, Sunday and public holiday rates, casual loading percent, minimum engagement floor, and broken shift allowance. A General Retail Industry Award MA000004 baseline ships configured. Rates are tracked on the chatter for an audit trail.
- Configurable penalty bands. Add time of day penalty bands per award, each with a day type (weekday, Saturday, Sunday, or any day), a start and end hour, and a multiplier. The interval engine applies a band only to the part of the shift that falls inside it, layered under overtime and casual loading.
- Allowances. Define award allowances with a code, an amount, and a per shift, per hour, or per day unit. Mark an allowance auto apply to add it to every attendance under that award, or leave it for the payroll operator to attach case by case. Amounts are summed into an allowances field on each attendance.
- Stored buckets on every attendance. Ordinary hours, penalty hours, overtime tier 1 and tier 2 hours, effective pay hours, the award that was applied, the minimum engagement top up, a broken shift flag, and the allowance amount are all stored fields, surfaced on the attendance list and form and ready for export.
- Public holiday calendar. A public holiday model with a date, an optional company, and a state or territory region. National holidays apply everywhere; the calendar unions with the suite wide leave calendar when that suite is installed so holidays are entered once.
- Re-flush cron, off by default. Buckets recompute automatically through stored compute dependencies, so no periodic sweep is needed in normal flow. An off by default cron is included to re-flush attendances closed in the last seven days for the rare case where a bulk SQL update or mass import bypassed the recompute.
Honest about the edges
What this does not do, so nothing surprises you.
- This is an attendance interpretation engine, not a full payroll run. It assumes an hourly rate and produces hours and allowance amounts as inputs; pay slips, tax, and superannuation are out of scope. Annualised salary employees should be left without an award assigned.
- The shipped General Retail baseline is a cited, working starting point as at FY2024-25, not a substitute for the current determination. Award rates change with each annual Fair Work determination and vary by employment type, so the operator must verify every rate before running payroll.
- The public holiday model carries a state or territory region, but the attendance compute path does not yet filter holidays by employee region; a public holiday row affects every attendance in its company. Use the company field to scope holidays where regional variation matters.
- Penalty bands cover time of day and day type. Award rules that depend on consecutive days, rostered day off interactions, shift length thresholds beyond the daily cap, or annual leave loading are not modelled and would need a follow up.
- The engine reads naive shift datetimes and uses a Monday to Monday work week; configure shifts so they do not straddle a week boundary in a way your award treats specially.
Australian Modern Award Odoo, Fair Work penalty rates Odoo 19, attendance overtime calculation, casual loading award engine, public holiday loading attendance, weekend penalty rate Odoo, minimum engagement broken shift, hr_attendance award interpretation, Odoo 19 Community payroll input, span of hours penalty band, weekly overtime 38 hour cap, ordinary penalty overtime split
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.
Please log in to comment on this module