Balance Accumulators in Batch Processing

This topic describes various aspects of how the batch process handles balance accumulators.

Updating Balances

The system loads the value for an accumulator from the end of the previous period. When the accumulator is processed, the value for the current period is added to the historic value to maintain an up-to-date balance. For each period, the batch process pulls forward the accumulator likewise.

Creating New Instances

When defining an accumulator, assign such attributes as level, based-on date, and period to cover—such as calendar year. Level determines whether to keep separate counts per job or across jobs by employee. You can add specifications by adding user keys, such as contract or department. The period and based-on date determine the applicable time period. These attributes determine how and when the batch process creates and keeps separate instances of the same accumulator. The system creates a new instance of balance and segment accumulators anytime that you change the value of a key field. Balance accumulators also spin off a new instance for each new period.

Writing to the Result Tables

How you set up the Accumulator page tells the system whether to write the accumulator to the results tables. The system determines when to drop balance accumulators, using the number of months to maintain after end date and comparing the accumulate through date of each instance with the current pay period begin date.