For each unique set of requirements, one RDO scheme is created in ProServer. Go to menu 5,9 then complete the following configuration (mandatory fields*):

CONFIG OPTION	VALUE	OVERVIEW & EXAMPLES
RDO Scheme Number*	A unique scheme number.	1 - 99
Employee Scheme Identifier*	Identifies the field name, operator and values used to determine scheme eligibility.	If field xx = xx then an employee is eligible for this scheme. Fields available for selection should all be `EMP` and `PERSON` fields.
Accrual Codes*	Identifies which pay elements RDO accrual should calculate on.	Select from the list of pay elements.
RDO Accrual Code*	Identifies which pay element (11, 12 or 13) is used for RDO accrual and consequently where the leave balance will be maintained.	Options: 11 = Leave C 12 = Leave D 13 = Leave E The selected pay element will create a negative timesheet for RDO accrual (this is what enables the balance to increase).
RDO Payment Code*	Identifies which pay element is used to pay RDO when it is taken.	This pay element is configured in Affinity to reduce the relevant RDO leave balance.
Accrual Calculation Frequency*	Indicates if accruals will be calculated on a daily basis or per pay period.	Note that daily accrual frequency can only be used if work schedules are in use or timesheets are captured daily.
Cycle Start Date	The start date if the RDO cycle does not align with the pay period.	If a cycle start date is entered, this will be used instead of the pay-period-start date.
Cycle Length	The number of days in a standard RDO cycle.	Used to manage cycles that span multiple pay periods. Defaults to 1 if no cycle length is specified.
Accrual Percentage Flag	The percentage rate that that can be applied to determine the RDO accrual.	If this value is 5% and Accrual Calculation Frequency = Daily, then a timesheet record for each 'day transaction' is created to deduct 5% of hours and accrue them towards RDO. If this value is 5% and Accrual Calculation Frequency = Per Pay Period, one transaction row in a timesheet is created to calculate 5% of all eligible hours.
Daily Accrual Minimum Hours	A value in hours and decimals that the system uses as a threshold above which daily hours will accrue to the RDO scheme.	If this value is 7.6, then daily timesheets under the following scenarios will be created: Day 1: 8 hours would create an RDO accrual of 0.4 hours. Day 2: 7.6 hours would create no RDO accrual. Day 3: 6 hours would create no RDO accrual. Day 4: 9 hours would create an RDO accrual of 1.4 hours.
Per Pay Period Accrual Hours	A value in hours and decimals that the system uses as a threshold above which period hours will accrue to the RDO scheme.	If this value is 76, then daily timesheets under the following scenarios will be created: Period 1: 80 hours would create an RDO accrual of 4 hours. Period 2: 76 hours would create no RDO accrual. Period 3: 60 hours would create no RDO accrual. Period 4: 90 hours would create an RDO accrual of 14 hours.
Maximum RDO Balance	The maximum number of hours that the RDO balance can hold.	If this value is 38, for employees in this scheme the maximum hours that can be held as an outstanding RDO balance is 38.
Maximum Daily Accrual	The maximum number of hours that can be accrued towards the RDO scheme on a daily basis.	If this value is .6 any accrual above 0.6 of an hour each day will not count.
Maximum Per Pay Period Accrual	The maximum number of hours that can be accrued on a per-pay-period basis.	If this value is 2.0 any accrual above 2 hours each pay period will not count.

Scoping client requirements

Table of contents

Where we start