Skip to main content

Current period or one view displaying incorrect rate for an employee

The current period or one view shows an incorrect employee rate on the Payroll dashboard.

O
Written by Onyema Onyejekwe
Updated over a month ago

The Payroll dashboard serves as a crucial tool for monitoring employee compensation accurately. However, discrepancies such as incorrect employee rates can occur for several reasons, including data entry errors, outdated information, or integration issues with HR systems.

To resolve an incorrect rate, you need to update the rate toggle.


Understanding combined rate displays

When an employee has two different rates within the same period (e.g., due to a mid-period salary change), the system displays a combined rate by default.

For example, if an employee had an original rate of €13.01 and received a new rate of €12.49, the Current Period screen shows a total rate of €25.50 when you haven't enabled the toggle.

πŸ“ŒNote: This represents a display issue only. The system calculates and pays the correct amount at the appropriate rate.

View pay details

To view pay details separated by rate or appointment, follow the steps below in Portal:

  1. Click Employee, then in the search field, search for employee.

  2. Beside the relevant employee, click VIEW.

  3. Click Current Period or OneView then click BREAKDOWN.

  4. Turn on the Rate toggle then click OK.

Results after enabling the rate toggle

After you enable the Rate toggle, the system will:

  • Display the individual rates applied during the period.

  • Separate the hours worked at each rate

  • Clearly distinguish between old and new rates, including appointments.

This feature ensures transparency and makes it easier to verify pay calculations when rate changes occur mid-period.

πŸ“ŒNote:

  • You can use the toggle functionality for both standard pay and appointment-based entries.

  • If you leave the toggle disabled when an appointment contains multiple rates, the system will combine these rates into a single figure.

Did this answer your question?