Setting up Recurring Employee Claims

Helpful Hint

Please note that claims are referred to as expenses, or expense claims in the payroll platform.

Once you have created some expense categories (the tutorial can be found in Expense Categories - Creating and Managing), you can begin assigning these expenses to employees as recurring expenses, which will take effect every pay run.

To begin, select the Employees tab on the payroll dashboard:

Once you have chosen an employee, click the 'Pay Run Inclusions' tab in the 'Pay Run Settings' section on the left-hand side of the screen.

You will be taken to the following screen:


To add a new recurring expense, click the 'Add' button on the right of Expenses and complete the following details: 

  1. Select the appropriate expense category from the drop-down list. The list here will reflect the expense categories that have been added at a business level on the payroll settings > expenses page. 
  2. Select the location the expense should be costed against. This will default to the employee's default location however you can change this to another location that the employee is attached to.
  3. Enter the expense reimbursement amount to be applied per pay run.
  4. Enter any notes if you want the employee to see them on their pay slip.
  5. Enter the date this inclusion is to commence.
  6. Choose when this inclusion should cease ('on the following date', 'never' or 'after the following amount has been reached');
  7. Click on 'Save'.



Now, the next time you create a pay run that includes this employee, this expense will be automatically added. 

If you wish to edit an expense after it has been created, click its name in the list of expenses that have been assigned to this employee. You'll be able to edit any of the properties of that expense (apart from the expense category). 

To delete an expense, click the red cross on the far right hand side of its entry.


 You'll be prompted to confirm the deletion.


If you have any questions or feedback, please let us know via

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.