Results Data

Payments and Balances

User Roles

Event Types

Fixed Values CANNOT be used in Rate Tables.

A Fixed Value can hold multiple values, one for each period.

Fixed Values can contain Formulas and Lookup Tables.

A Fixed Value can act as a placeholder in a rule.

Titles

Participants

Positions

Position groups

Role types

Business Units control access to Organization Data.

You can assign multiple Business Units to a Processing Unit.

You can share reference data across Business Units.

Calculation runs are completed separately for each Business Unit.

Position Groups

Earning Codes

Event Types

Earning Groups

Any user for which you are a proxy

Any user account in the system

The administrator account only

Your user account only

You can delete Processing Units after a Pipeline has been run.

You can use Processing Units to process subsets of data.

You can create as many Processing Units as needed.

Calculation runs are completed separately for each Processing Unit.

You can assign only one Business Unit to each Processing Unit.

To determine the deposit amount

To calculate monthly attainment

To aggregate a position assignment's credits

To allocate classified transaction data

The assignment of a title to a position

The assignment of a plan to a position

The assignment of a manager to a position

The assignment of a participant to a position

Rate Tables can be effective dated. Lookup Tables CANNOT be effective dated, but each cell in the matrix can be effective dated.

Rate Tables have a single dimension. Lookup Tables can have more than one dimension.

Rate Tables can be used in any rule. Lookup Tables can be used only in incentive rules.

Rate Tables CANNOT handle step commissions. Lookup Tables can handle step commissions.

Run the Finalize stage to prevent compensation from being paid.

Review the Classify stage results to ensure accuracy.

Review the verbose log files.

Run Compensate and Pay in full mode.

Only the Reward stage needs to be completed.

Successfully complete the Classify, Allocate, and Reward stages.

Successfully complete a Compensate and Pay pipeline.

Only the Allocate stage needs to be completed.

You CANNOT delete a period once a Pipeline has been run for that period.

Leaf periods on a Calendar CANNOT contain gaps or overlap.

You can change the dates of a period after a Pipeline has been run without causing a disconnect in the results.

You can have two rules with the same name, as long as they are on different Calendars.

If you end date a position or participant, it is deleted from the system.

If a participant has non-zero results data in a period, you can set the end date for the participant to the last day of the period.

If the Credit End and Process End fields on a position extend beyond the effective end date, the position continues to be processed.

You can end date a position or participant version if there is NO results data associated with that version.

A Rate Table Variable

A Rate Table

A Fixed Value

A Fixed Value Variable

To define the details of the category hierarchy

To match fields on classifier records with assigned Variables

To match fields on classifier records with fields on transactions

To organize products into categories

Rolling category hierarchy results

Rolling measurement and incentives

Rolling deposit results

Rolling credits results

Classify, Allocate, Reward, and Pay

Classify, Allocate, Reward, and Post

Reward, Pay, Post, and Finalize

Classify, Allocate, Pay, and Post

Manually adjust the value of the transaction and re-run Compensate and Pay.

Modify the credit rule and re-run Compensate and Pay.

Modify the Territory used in the credit rule and re-run Compensate and Pay.

Manually adjust the value of the credit and re-run Compensate and Pay.

Generic attributes

Territories

Formulas

Classification rules