The 2026 End of Financial Year Processing guides are now available.

Process the Australian End of Financial Year

If you have a pay period ending in June but the Payment Date is in July, please read

When a pay period crosses over the End of Financial Year
​

This release (3.29) includes Payday Super compliance features, leave and reporting improvements, and various fixes across the product.

In preparation for Payday Super compliance effective 1 July 2026, Definitiv has updated the Super Guarantee Contribution Base calculation from a quarterly to an annual model. The annual cap is calculated automatically using the ATO formula: Concessional Contributions Cap x 100 / SG Charge Percentage (for FY2026-27, this equals $270,830). Calculations are based on the employee's payment date, and where an employee has separate profiles, the cap applies independently to each.

A new Manage Super Guarantee Capping permission controls access to the organisation-wide MSCB configuration in Organisation Settings, removing the need for a support request to change these settings. Administrators can also configure per-employee overrides for executives or employees with special super arrangements - each employee defaults to the organisation-wide setting but can be set individually. The system tracks Qualifying Earnings accumulation against the annual cap throughout the financial year, with an alert surfaced in the pay run Messages tab as employees approach the threshold.

Existing quarterly cap settings are preserved for historical payroll runs. The annual calculation takes effect from 1 July 2026. For full configuration guidance, see: Maximum Superannuation Contribution Base - Setup and User Guide

Definitiv now supports SuperStream v3 Member Verification Requests (MVR) and Member Verification Outcome Responses (MVOR) for clients using Beam's clearing house, ahead of the Payday Super requirement for verified contributions.

When an employee's super fund details are added or changed in a first-time contribution scenario - whether via the User Interface (UI), Workbook, or API - Definitiv automatically submits an MVR to the nominated fund without any administrator action required. At the point of save, users are clearly informed that an MVR will be sent and that fund details will be locked for up to 24 hours pending a response.

MVR and MVOR status (Verified, Rejected, Pending, Validation Failed, Timed Out) is stored against the employee's super fund record and displayed in the employee's super fund screen with actionable guidance for each outcome. Two new tabs have been added to the Admin - Superannuation screen:

Pay runs that attempt to submit a contribution for an employee with a Rejected MVR status surface an appropriate warning. Duplicate MVR submissions for the same employee and the same fund details within a 24-hour window are prevented.

Definitiv also now correctly handles all new and updated MIG v3 error codes received from Beam. Dynamic variable values - such as specific payment reference numbers - are now extracted from the error response and displayed directly in user-facing messages, rather than showing raw placeholders. For full details, see

Super Fund Member Verification - Setup and User Guide.

A new setting controls how timesheets submitted by project managers against their own projects are routed for approval. Available in Organisation Settings,, Approvals, the Project Manager Timesheet Approval Mode setting offers two options:

Project Clerk permissions have been added to the following reports:

The 2027 Australian national public holidays and the 2026 Friday before AFL Grand Final Holiday have been added to Access Definitiv.

Action Required:

Additional Information:

If employees have already booked leave for the next calendar year, you may to recalculate the current estimated leave calculation on the individual application.

All of the updates below will require configuration to take advantage of these enhancements. Where an Award Rule has been enhanced, the original behaviour has been migrated to the new format and maintains the existing calculation behaviour.

We have taken the upmost care to prevent backpay and supporting of existing behaviour we highly encourage you to open your payrun early and review calculations to ensure correctness.

Add Condition

Day Type Not Public Holiday has been migrated and will now read:
Day Type IS NOT Any Holiday

Else Condition - A new condition type that allows mutually exclusive sub-rule configuration, where further sub-rules are skipped once a preceding rule has succeeded.
For more information, please see: ELSE IF Condition User Guide.

Add Action​

​Add Condition

Add Action​

When an approved timesheet is edited by a user with the Update Locked Timesheet permission, email and push notifications are now sent to the original approver(s) and the employee, ensuring changes are not made silently without the approver's awareness.

Notable customer-reported issues resolved in this release:

Fixed an issue where partial day leave hours were calculated incorrectly for employees where the costing mode (Chronological vs Proportional) was being lost during the ScheduledHours processing path, resulting in incorrect leave hour calculations.
​Please be mindful for backpay calculations which may occur on this fix

Fixed an issue where pay runs were calculating incorrect hours for employees using start/end time timesheets when the Apply Max option was not enabled on the award tag configuration, resulting in hours not matching the expected output.

Please be mindful for backpay calculations which may occur on this fix

Fixed an issue where duplicate version numbers were displayed under an Award Policy after importing an award policy with multiple drafts in progress.

Fixed an issue where, when a line manager submitted a leave application on behalf of an employee and the line manager's own approval step was auto-approved, subsequent approval steps remained in Waiting status and did not progress to Pending. The leave request therefore never appeared in the next approver's Pending Requests list.

Resolved a timing issue where refreshing the Team Leave page caused the Leave Application History panel to display the logged-in manager's own leave applications rather than the selected employee's.

Fixed an issue where partial leave applications for night shift employees spanning a break that occurs after midnight (e.g. 2:00 AM - 2:20 AM) did not deduct the break, resulting in incorrect leave hours and potential overpayment.
​This update is feature flagged to resolve calculation from pay period on or after 01/06/2026.

Resolved an issue in the Team Leave Calendar where only one full-day leave application was displayed when multiple full-day leave records existed for the same employee on the same date (e.g. a withdrawn leave and an approved leave). In some cases, the withdrawn entry was displayed instead of the approved one.

Fixed an issue where compliance record approvals submitted by employees were not appearing in the Pending Requests list for approvers with limited permissions. Approvers with an Employee-only role can now view and action pending approvals as expected.

Resolved an issue where the normal gross earnings value used in Termination marginal calculations were being subtracted twice.
​This only impacts new Normal Gross values calculated since the release

When submitting an overlapping manual timesheet, a generic error was displayed rather than a clear validation message explaining the conflict. This has been resolved.

The daily recurring roster notification job was sending "Rostered Shifts - please accept to confirm your availability" emails for work schedule entries with a Not Required status has been fixed to no longer send.

In the new onboarding flow, selecting "Create a new employee record" and then searching for an existing employee was incorrectly triggering the rehire process. This has been resolved.

The Effective Date field was overlapping the Disabled checkbox on the new onboarding Custom Fields page at narrower browser widths. This has been resolved.

Fixed the system showing an error "Failed to load Work schedule assignments" message to appear when loading an employee profile where no active work schedule was assigned.

Fixed a cosmetic issue where new users clicking an invitation link to set their password saw a red toast error reading "Your session has expired due to inactivity" despite successfully completing account setup.

Updating an employee number via the Employee Workbook Import was causing custom fields and other worksheet data in the same import to fail, as the remaining sheets still referenced the old employee number. This has been resolved.

Resolved an issue where the Swagger API documentation page (/api-docs) was taking up to 5 minutes to load, particularly the Admin and Employees tabs.

Resolved an issue where the close button was hidden on smaller screens on the Feature Sentiment popup.

Fixed an issue where the TimeClock Approval Workflow recurring background job blocked indefinitely when a new scheduled execution was triggered.

Resolved an issue where certain record deletions and bulk updates performed through code paths caused audit log entries to record the acting user as "Database" rather than the actual logged-in user who performed the action.

Fixed two related issues where the Evo / Access button was not visible or disappeared during a session for organisations using Access Identity SSO:

Fixed two related issues where the Evo / Access button was not visible or disappeared during a session for organisations using Access Identity SSO:

Resolved an issue where, after successfully registering an Evo client via Admin > Integration > Access Identity Client Registration, the registration status reverted to "Unregistered" on page refresh. This caused administrators to attempt re-registration, which failed with a BadRequest error because the client already existed at the identity provider. The fix ensures the in-memory configuration is updated immediately after successful registration.