Versions 31.2 to 31.4
Version: Jem 31.4 - 13 Dec 2024
What’s new in Pay?
New feature: Business Leave
Check out our in-depth guide in Knowledge Jems:
Create leave events that allows employees to take paid leave on a day (or days) of your choosing, without affecting their leave balances
Business Leave is perfect for business shutdown periods like the days between Christmas and New Year’s. It can be set up in the Holidays bubble (previously called Public Holidays) found in Pay.
There are multiple ways to configure Business Leave. Apply it across the whole organisation, specific locations, or individual organisation components.
Employees don’t need to submit leave requests for these days, making it easier to manage business shutdowns and special events. It also enhances employee wellbeing and job satisfaction by giving them greater flexibility in choosing when to take their annual leave.
(JEM-21316)
ADP Calculation Enhancements
You can now add backdated transactions that count towards Average Daily Pay (ADP) days into current or future unpaid pay periods
These backdated transactions will be counted if not already counted previously, and the ADP Days quantity will increase as expected.
(JEM-19567)
Costing Code Enhancement
The Costing Component Code now shows on the General Ledger (GL) Code record when selecting a Debit or Credit component
You no longer need to open the GL Code record to retrieve the code from the Costing Code panel.
(JEM-22072)
What’s new in People?
Pay Mode Enhancement
We’ve enhanced the scrolling functionality of the Pay Period drop-down list in Pay Mode
It’s now easier to find the specific pay period you need. This is especially useful if you have over five years of pay periods where the list gets very long.
(JEM-21667)
What else is new?
Payslip Enhancement
You can now add your company logo to payslips
If you’d like to set this up, please raise an iHelp. There’s a $500 fee to add a logo to payslips.
(JEM-22123)
What's fixed?
Here’s an issue we've fixed since the last release
Since the 31.3 release on 8 November, continuous leave payments for employees set to be paid at the greater of and were incorrectly paid solely at RDP. This issue has now been fixed, and payments will be correctly calculated at the greater of ADP and RDP moving forward (JEM-22491)
Application Programming Interface (API) Updates
This section is for developers and consultants managing APIs
We’ve added and updated REST APIs in these areas:
Entitlement to Work
Leave Plans
Public Holidays
For detailed information on these changes, refer to the Swagger documentation, which is contained within the Jemini application to select users. If you need access or have any questions regarding the APIs, please raise an iHelp.
(JEM-21605, JEM-21606, JEM-21984)
Version: Jem 31.3 - 8 Nov 2024
What’s new in Pay?
ADP Calculation Enhancements
We’ve refined the Average Daily Pay (ADP) calculation to ensure that leave payments better reflect irregular work patterns
Bereavement, Alternative, Public Holiday and Sick (BAPS) Leave payments are now calculated using employee work patterns, basing the payment on actual hours worked each day.
(JEM-20333)
What’s new in People?
Leave and Core Table Enhancement
Create your own leave types to add leave plans
You can create custom leave types in People Core Tables, using the new ‘Leave Type’ core table. Only new leave types can be updated or deleted, while system-generated ones are locked.
(JEM-21486)
What’s new in System?
Application Setting Enhancement
You can now choose whether an error or warning should appear when future dated leave exists and an employee’s leave request will reduce their balance below the minimum required
This setting, ‘Show leave warning when future dated leave exists’, is in the Application Settings under the Leave section.
When set to Yes:
If an employee or manager attempts to submit a leave request that reduces the balance below the minimum, a warning message appears. After acknowledgement, Jemini creates the request.When set to No:
If an employee attempts to submit a leave request that reduces the balance below the minimum, an error message appears, and the employee can’t continue. A manager will still receive a warning and can proceed.
(JEM-21891)
What else is new?
What's fixed?
Here’s an issue we've fixed since the last release
You can now add Super Fund records again by setting the ‘Employee has a non-KiwiSaver superannuation scheme’ toggle in the KiwiSaver bubble to Yes. The Super Fund bubble will then appear as expected (JEM-21955)
Managers can now view direct reports with a fixed term end date, as expected (JEM-22141)
Application Programming Interface (API) updates
This section is for developers and consultants managing APIs
We’ve enhanced the Hourly Pay Rate Endpoint. For detailed information on this change, refer to the Swagger documentation, which is contained within the Jemini application. If you need access or have any questions regarding the APIs, please raise an iHelp.
(JEM-21708)
Version: Jem 31.2.0 - 4 October 2024
What’s new in Pay?
New feature: Range Tables
To get a head start on Range Tables, check out our in-depth guides in Knowledge Jems:
Use Range Tables to automate the calculation of range-based deductions and allowances
If you need to make salary deductions or pay allowances based on range parameters, such as salary bands or the number of hours worked, range-based tables can help. Previously, these calculations had to be done manually, which was time-consuming and prone to errors. Our new feature, Range Tables, automates these calculations, ensuring efficiency, accuracy and ease of monitoring.
Navigating to Range Tables:
We’ve renamed the Pay Core Tables bubble to Pay Core & Range Tables. In this bubble, you can find the existing Core Tables bubble and the new Range Tables bubble.
Creating Range Tables:
Set up range tables using one of the following range types:
Full-Time Equivalent Salary
Actual Annual Salary
Hourly Rate
Pay Level
Gross Earning per Pay Cycle
Standard Earnings per Pay Cycle
Hours Worked per Pay Cycle
Days Worked per Pay Cycle
Choose to set the range table rate as $ amounts or percentages, then add your parameters.
Once you’ve created a range table, you can link it to a transaction using the applicability settings. This allows the range table to function like any other transaction, enabling you to assign it to an employee’s pay through their Pay Mode.
Permissions settings:
A new Range Tables permission, found within the Payroll permissions section in Security Profiles, needs to be enabled for users to access the Range Tables bubble.
JEM-20764
Pay Reporting Enhancements
New report: Pay Variance to Previous Net
This paginated report compares the previous net pay to the current net pay.
Report parameters:
Payroll
Paycycle
Is Standard Paycycle
Is Current Paycycle.
For each employee within the pay period, the report shows their current net pay, their previous net pay, and the pay variance between them.
Note for system administrators: To give users access to these reports, you must add them to the relevant Security Profiles. Learn how in How to give users access to new reports.
(JEM-21633)
We’ve decommissioned the generic ‘CostCentre GL Detail’ and ‘CostCentre GL Summary’ reports
On reviewing these two reports, we determined they’re no longer necessary because three other generic reports already provide the same information:
CostCentre GLDetail Paginated
CostCentreGLSummary Paginated
Cost Centre Pay
(JEM-21652)
We’ve updated several pay reports to cater to Multiple Employments enhancements
Given the extensive nature of these updates, we’re making progress across all reports systematically. Here’s what we’ve updated in this release:
‘Pay Summary Current’ report:
We’ve removed ‘Occupancy Organisation Component’ and ‘Occupancy Location’ from the report to better accommodate multiple employment scenarios. Numbers will be reported at employment level instead of employment stream level.‘Pay Variance’ report:
In both tabs, we’ve added ‘Position Title’ and removed ‘Net Pay Comparisons’ (because net pay is consolidated in the backend).Pay Variance to Ordinary Pay (Paginated)’ report:
We’ve added ‘Position Title’, ‘Organisation Component’, and ‘Location’ to this report to help identify pay details for each employment.
‘Employee Pay Calculation’, ‘Emp Pay Calculation Paginated’, ‘Pay Calculation Summary’, and ‘Pay Calculation Summary RLS’ reports:
We’ve improved how these reports handle multiple employments by excluding ‘Gross Dummy Transactions’, making the data more accurate and relevant.
(JEM-21469, JEM-21258, JEM-21632, JEM-21515)
What's new in People?
Pay Rate and Occupancy Enhancements
Pay Rate and Occupancy records can now have the same start and end dates
This enhancement allows for accurate recording of pay rate and occupancy data in scenarios such as immediate pay increases or when an employee joins and leaves the company on the same day.
(JEM-20263)
‘Actual Annual Salary’ and ‘Annual Salary (Full Time)’ in Pay Rate can now display up to eight decimal places
While employees were being paid the correct salary, this enhancement was needed in the user interface for greater accuracy when reporting on these details.
(JEM-20239)
People Reporting Enhancements
We’ve renamed and added new columns to the ‘Employee Headcount Analysis*’, ‘Starters’, ‘Terminations*’, and ‘Turnover Analysis*’ reports to allow for Level 2 and Level 3 Organisation Components
Renamed columns:
‘Org Structure Component’ is now ‘L0 Org Structure Component’
‘Org Structure Component Type’ is now ‘L0 Organisation Type’
‘Parent Org Structure Component’ is now ‘L1 Org Structure Component’
New columns:
Org Structure Name
L1 Organisation Type
L2 Org Structure Component
L2 Organisation Type
L3 Org Structure Component
L3 Organisation Type
Employment Name
Employment Stream
(JEM-21202)
The Employee Work Patterns report now has three extra columns: ‘Employment Name’, ‘Employment Payroll’, and ‘Employment Stream Position Title’
These columns will help identify pay details for each employment, particularly when there are multiple employments.
(JEM-21428)
What's new in Business?
Business Reporting Enhancements
We’ve renamed and added new columns to the ‘Position Est vs Occupancy FTE’ report to allow for Level 2 and Level 3 Organisation Components
Renamed columns:
‘Org Structure Component’ is now ‘L0 Org Structure Component’
‘Org Structure Component Type’ is now ‘L0 Organisation Type’
‘Parent Org Structure Component’ is now ‘L1 Org Structure Component’
New columns:
Org Structure Name
L1 Organisation Type
L2 Org Structure Component
L2 Organisation Type
L3 Org Structure Component
L3 Organisation Type
(JEM-21202)
We’ve added an asterisk to the name of the ‘Position Est vs Occupancy FTE’ report to indicate that the report doesn’t have row level security (RLS) implemented
The name is now Position Est vs Occupancy FTE*.
Note for consultants and system administrators: You may need to re-add this report to the relevant Security Profiles. Refer to How to give users access to new reports.
(JEM-21942)
What else is new?
What's fixed?
Here are the issues we've fixed since the last release
Work Patterns are now updating correctly. This issue only affected consolidated work patterns that appeared to exceed 24 hours per day (JEM-21875)
We’ve significantly enhanced the Onboarding view’s loading speed for a more efficient experience (JEM-20780)
The ‘Occupancy Details’ report now displays all employees as expected (JEM-21153)
API updates
For developers and consultants managing APIs
We’ve added and updated REST APIs in these areas:
Employment Agreement (Classification)
Employment Status
Location
Payroll
Payroll Transaction Configuration
Position Establishments (Manager’s ID, Organisation, and Organisation ID)
Provincial Holiday Location
Report Views
For detailed information on these changes, refer to the Swagger documentation, which is contained within the Jemini application. If you need access or have any questions regarding the APIs, please raise an iHelp.
(JEM-20983, JEM-20985, JEM-20995, JEM-20997, JEM-20998, JEM-20999, JEM-21000, JEM-21010, JEM-21567, JEM-21686)