Punches After Batch Close or Payroll Processing
This feature enables employees to perform punches via Timeclock (including ZenTime, WebTimeClock, and Mobile Time Clock) even after transaction batches are closed or payroll is processed. Any punches made after closure are stored in a new transaction batch, ensuring previous (closed) batches and processed payroll remain unaffected, and users can continue recording work time without interruption or confusing errors.
Functionality
1. Punches Allowed Post-Batch Closure/Payroll
- Employees may continue to punch in/out through any Timeclock platform after a batch is closed or payroll is processed.
2. Automatic New Transaction Batch Creation
- When a punch is performed after batch closure or payroll processing, the system automatically creates a new transaction batch for those punches.
- This ensures the integrity of closed/processed batches and keeps new punches isolated.
3. Data Association & Integrity
- Each new punch is:
- Stored in the new transaction batch
- Properly associated with the correct employee and time period (week)
4. Universal Application
- This logic applies to all ZenTime, WebTimeClock, and Mobile Time Clock deployments.
5. No Error or Interruption
- No error message or workflow stoppage will occur when users punch after batch closure/payroll processing.
- Users experience seamless, uninterrupted time tracking, regardless of payroll or batch status.
6. Transaction Week Handling
- Punches after batch close will trigger a new transaction for the current or forthcoming week, consistent with existing payroll period logic.