Take Features

Take features include:

• Entitlement links.

  You can link each take element to one or more entitlement elements. If you link to more than one entitlement element, specify the order in which the elements are to be used. When an absence occurs, the system takes from the first entitlement (until it is depleted) before taking from the next entitlement.

• Absence types and reason codes.

  You create absence types to describe the categories of absences that are relevant to your organization such as illness, vacation, personal, or work injury. Within each reason type, you can define codes that further describe the reason for the absence; for example, flu or back problems. The type and reason that are associated with an absence event populate system elements that you can use in absence formulas.

• Approvals.

  You can require that absence events be approved before they are processed. If you select this option, a user needs to select the Manager Approved check box when entering an absence on the Absence Event Entry page. Otherwise, the event is not processed. (Absence Take - Calculation page)

• Combining absences.

  You can instruct the system to create one row of positive input for multiple instances of the same type of absence within the same pay period or create a separate row of positive input for each absence event (Absence Take - Calculation page.) Or you can instruct the system to create one row of positive input for all absence takes (Installation Settings page.)

• User-defined fields.

  You can enter any information in as many as four user-defined fields on the Take element's Calculation page. This information updates the daily data when you run the Take process and can be available for your absence formulas.

• Earning and deduction links.

  You can link each take element to the earning or deduction elements for which you want to generate positive input. You can also indicate the units, percent, rate, or amount to be returned when the calculation rule for the earning or deduction element is Rate × Units or Rate × Units × Percent.

• Generate matching absence data.

  If you use the mapping feature, the system generates matching absence data for a mapped take element when an absence event is reported. You can also use a formula to specify the conditions under which the Take process generates matching data.

• Day formula.

  Define the formula that the system uses to evaluate each day of the absence. The formula returns the number of absence units that the system compares to the absence entitlement balance to calculate paid and unpaid units.

• Automatic offset.

  When you link a take element to an entitlement that accrues per absence, you specify conditions for reducing the entitlement balance.

• Time period requirements.

  You can select up to three time period requirements that must be met before an absence can be paid: an eligibility date that must be reached, a minimum absence period, or a wait per absence.

• Linked absences.

  You can instruct the system to link related absences of the same type that fall within a specified period of time. During absence entry, users enter the begin date of the original related absence. When absences are linked, they can share the same entitlement or the same wait period. You define the period of time over which absences can be linked.

• Negative entitlement.

  You can specify what to do if there's not enough entitlement to cover an absence: allow a negative entitlement balance (up to the limit that you specify), treat the absence as unpaid time, or redirect the days to be processed by the set of take and entitlement rules that is associated with another take element.

• Priority processing for same-day absences.

  You can enable users to enter more than one absence event for the same day or you can use the automatic priority processing feature. When more than one event is entered for a payee for the same day, the system refers to the priority that you assigned to each take element to determine which absence event to process for the specified day.