PARiM's Pay Run report includes all the information needed to pay your employees based on the assigned shifts, jobs, and absences. The report is based on pay periods, that are defined with Pay Schedules that have been added to Employment Types.

On the left-hand side of the report, there is a powerful selection of different filters that make managing payroll data easy and allows you to review it based on different specific criteria.

PARiM Pay Run report has pre-set default filters visible and additional filters that can be included using the 'Add Filter' option.

  • Pay Period - pay periods set up by your company and for the custom period - Unscheduled pay period.

  • Pay Lock status - find easily payroll values that are locked or unlocked

  • Departments - People vs Location - option to decide whether you want to see payroll data done by a person in the department or done by a person at the location in the department.

  • Location - multi-selection option for viewing data by location.

  • Position - multi-selection option for viewing data by positions.

  • People - multi-selection option for your employees who have selected pay period for their contract, eg Weekly period and people who have weekly payout period on their contract. For the Unscheduled pay period, all employees will be shown within the filter.

  • Day - multi-selection option for viewing data by weekdays.

  • Employment Type - multi-selection option for your active employment types that have the selected pay period, eg Weekly. For the Unscheduled pay period, all the active employment types will be shown within the filter.

  • Event - multi-selection for specific Events. Filter available if you have the Events module activated on the Subscription page.

  • Tags - multi-selection for viewing data by shift tags.

TIP! Use the Save View functionality if you would like to easily view and open the Pay Run report with frequently used filters.

If you have any questions, please do not hesitate to contact us by email at or through the Chat function.

Did this answer your question?