Setting Up Rollup and Master Accrual DBAs for Sick Accrual Requirements (Release 9.2 Update)

Many state and local jurisdictions, as well as federal agencies, now require mandatory sick pay accruals. A single timecard may be subject to two to three different sick pay accrual requirements. To accommodate these legislated requirements, you can set up rollup and master accrual DBAs. The rollup accrual DBA is used to calculate a single sick pay accrual requirement using a single jurisdiction's prescribed rate and limits. The rollup accrual is then added to a master accrual DBA, which stores the accrual balance for the employee. When two or more jurisdictions apply to the same timecard, the sick pay accrual calculation is performed for each applicable rollup accrual DBA, but only the accrual giving the most sick pay accrual to the employee is added to the master accrual DBA balance. When the employee uses sick time, this time is applied against the balance on the master accrual DBA.

The rollup accrual DBAs are linked to the master accrual DBA through the Basis of Calculation on the master accrual DBA.

Each individual rollup accrual calculation references the master accrual balance but uses its own year-to-date (YTD) and inception-to-date (ITD) limits to determine whether or not to calculate accrual. If the YTD or ITD limit of the individual rollup accrual is lower than the current master accrual balance, no accrual calculates but no part of the master accrual balance will be refunded, since the master accrual balance may come from multiple sources.

The system stores the accrual DBA information in the Payroll Transaction Constants (F069116) and the Payroll Transaction Constants - Tag File (F06911T) tables.