This is version 1 2 3 4 5 6 7 8 9 10 11 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

When a leave policy is defined, there are a variety of decisions to be made for each policy:

• When does the policy start each year? Is it January 1st, the fiscal year begin date, or perhaps on the employee’s hire date anniversary?
• How will entitlement be based? Is it based on years of service, or hours worked?
• If using years of service, how are the years of service evaluated, by seniority date or date of hire?
• If using hours worked, which hours are applicable? Regular, Overtime, or Holiday?
• How much entitlement will be awarded for each service level?
• Is entitlement given in days, hours, or a percentage of earnings?

Each of the questions shown above may become a component of a leave policy, and each component has a number of possible responses or options. In ePersonality, the questions/ components are called Attendance Components. The possible options/responses are the Attendance Component Rules.

Attendance components may be defined and maintained on the Define Attendance Components (IAAC) form.

As each leave policy is created, users decide which components are necessary to define the policy. Once the components are decided, users choose which rule is applicable for each component.

When a policy is created, the rules for how much entitlement to give, when to give it and how and when the entitlement may be taken need to be defined. These rules are held in attendance components. Users are provided with a list of possible components and the rules available for each one and decide which of the attendance components will be necessary for each leave policy.

The attendance components allow a great deal of versatility for defining leave policies. In cases where the existing options may not allow for every possible policy rule, the UserCalc tool has been made available. With this tool, users are given the ability to create a custom calculation to derive necessary information for the policy. Users are also given the opportunity to carry amounts calculated in the attendance processing to payroll, and subsequently to employees’ pay stubs and financial ledgers. The link between attendance and payroll is established in the pay components. This concept will be discussed further in the “Detailed Information on Attendance Components” within this chapter, and in the “Linking Attendance and Payroll” chapter.

Attendance components are maintained on the IAAC form. High Line supplies the available AC codes, and their associated options/rules. Users may choose which rules will be available to policies, and what information may be overridden at policy entry.

Bracketed words represent fields in the Component Rules, Leave Accrual Record, or Leave Line forms that need to be filled in. (i.e. <Value>).

Each component has a table to define the rules that are available. The columns in the tables are described below:

• Rule - the index number of the rule
• Description - a brief description of the rule
• Logic - what the rule will do if chosen, and what other ‘pieces’ it may need to complete the logic
• Assoc. - if there are any associated attendance components needed, they are listed
• Go to - after this rule is chosen which attendance component should be evaluated next

The standard or most commonly used rule(s) for each component is indicated by the asterisks (*) in the rule column