Determine How Sign-Offs Are To Be Processed

Determine the transaction maintenance window.

Determine if you want to use a one-day or two-day transaction maintenance window. This window is used when evaluating transactions related to an employee sign-off that are at the beginning of a new pay period but could affect the previous pay period.

Example

If the pay period ends on Sunday, the window allows transaction maintenance through Monday or Tuesday.

About the transaction maintenance window

The transaction maintenance window determines how transactions in the first two days of a new pay period affect an employee sign-off in the current pay period. Due to certain calculation and posting rules, transactions which fall on the first or second day of a new pay period could be pulled back into the current pay period and affect time there. Therefore, these transactions need to be accounted for when determining whether an employee sign-off needs to be removed during an edit to a transaction.

This only applies to transactions that have not yet been assigned to a Pay Group Instance. For example, an Adjustment will always have a Pay Group Instance, so it never uses the transaction maintenance window. But clocking records are not assigned a Pay Group Instance until they are paired up by the calculations process.

Example

Your pay period ends on Sundays and you have the indicator set for a two-day window. An employee signs off on the current time card. They clock in on Tuesday morning (this is actually a new pay period but you have not run the close pay period process yet, so it is still the future pay period). The employee does not have a corresponding out punch to that in punch so it is not yet tied to a Pay Group Instance, since according to rules configuration, that punch could end up being tied to either the current or next pay period. If a supervisor deletes or modifies that clocking, since it is not tied to a Pay Group Instance and it is within the two day window, the employees sign-off is removed.

By contrast, using the previous example, if you set the transaction maintenance window indicator to one day, the sign-off would not be removed. However, if the clocking occurred on Monday morning, the sign-off would be removed since the shortest window is a one-day window.
Determine if a transaction request is assumed to be approved or denied. This decision also affects whether an employee sign-off is removed or retained.
- With the Assume Approval method, it is assumed that any transaction request that an employee makes will be approved by the supervisor. So if an employee enters a clocking request and then signs off on the time card, they are assuming that the supervisor will approve the request. Therefore, if the supervisor does approve it, it should not remove the employee's sign-off. But if the supervisor cancels or denies it, it should remove the employee's sign-off. For more information, see Assume Approval method below.
- With the Assume Denial method, it is assumed that any transaction request that an employee makes will be denied by the supervisor. So if an employee enters a clocking request and then signs off on the time card, they are not signing off on that particular clocking. If the supervisor approves the request, it is a change to the employee's time card and the sign-off should be removed. But if the supervisor cancels or denies the request, the sign-off should not be removed. For more information, see Assume Denial method below.

Note

For both the Assume Approval and Assume Denial methods described below, the following information applies:

The tables assume that the employee has already signed off.
A request can be a clocking, calendar, or adjustment request.
In the examples in the tables, the action of adding a request or transaction would always occur after the employee has signed off.
All other actions in the table could occur on a new request or transaction (one that was added after the employee signed off) or on an existing request or transaction (one that was existing prior to when the employee signed off).

Assume Approval method

This table explains the effect on the employee sign-off when using the Assume Approval method.

Who initiates	Action	Sign-off removed?
Employee	Adds, edits, or deletes a request	Yes
Manager/Supervisor	Cancels or denies a request	Yes
Manager/Supervisor	Approves a request	No
Manager/Supervisor	Adds, edits, or deletes a transaction	Yes

Note

When the Assume Approval method is used, a message appears during the "Review Requests Report" step of the pay period close process stating that any unhandled pending requests will be canceled and the affected employees' sign-offs may be removed.

Assume Denial method

This table explains the effect on the employee sign-off when using the Assume Denial method.

Who initiates	Action	Sign-off removed?
Employee	Adds, edits, or deletes a request	No
Manager/Supervisor	Cancels or denies a request	No
Manager/Supervisor	Approves a request	Yes
Manager/Supervisor	Adds, edits, or deletes a transaction	Yes

Exceptions to sign-off removal

There are two exceptions to the removal of employee sign-offs:

A duplicate clocking entered after the employee signs off

If the system determines that a clocking is a duplicate, the employee sign-off is not removed.
Automatic adjustments

If an automatic adjustment is updated by the calculations process, the employee sign-off is not removed.