Understanding DBA Overrides

When an employee is processed through a payroll cycle, the system uses the information on the employee's timecards to calculate DBA amounts. Sometimes you must override the monetary amounts associated with a deduction or a benefit, or override the amount of hours for an hourly accrual. For example, if an employee begins employment during the middle of a pay period, you might override DBA amounts so that they reflect only the portion of the pay period in which the employee actually worked. You can attach these DBA overrides to the employee's timecards.

Occasionally, you might need to override DBA amounts when an employee does not have any timecard records to process through a payroll cycle. For example, if an employee is on unpaid leave and does not have any timecards to process, you might still want to calculate a benefit for the employee.

You might also want to enter DBA overrides without attaching them to timecards, even if the employees have timecards, or timecards will be created for them during the payroll cycle. For example, if you want to override the amount of a DBA for a group of autopay employees, you can enter the DBA overrides without entering timecards for those employees.

When you enter an override that is attached to an existing timecard, the system uses the information on that timecard to derive account information that is used to create journal entries for the DBAs. When you enter standalone overrides, the system uses one of these scenarios to determine how to prorate and attach the DBA override amount across the employee's timecards.