On-Cycle Processing
Overview
On-cycle processing covers the normal production rhythm for payroll and absence. It is where predictable calendar patterns, repeatable controls, and volume-efficient batch groups matter most.
Common Scenarios
| Scenario | Calendar Type | Approach |
|---|---|---|
| Regular monthly payroll | On-cycle | One calendar per pay group per month |
| Regular absence run | On-cycle | Separate absence calendar linked to payroll target calendar |
| Quarterly bonus | On-cycle | Dedicated bonus calendar plus bonus run type |
| Manual payment correction | Off-cycle | Individual off-cycle group |
| 13th-month pay | On-cycle or off-cycle | Choose based on population scale and controls |
| Supplementary run | On-cycle | Separate supplementary calendar and run type |
| Advance payment | Off-cycle | Individual payee off-cycle group |
Recommended On-Cycle Pattern
- define the recurring period pattern
- create payroll and absence calendars for each pay group
- sequence absence before payroll where payroll depends on absence output
- use one calendar group per operational cycle
- review results before finalizing the whole group
Why On-Cycle Needs Discipline
On-cycle runs are where weak setup scales badly. A minor naming issue, wrong payment-date holiday rule, or loose run-type definition can multiply across every pay group every month.
Good Practice
- standardize naming by pay group and period
- keep absence and payroll sequence consistent from one cycle to the next
- reserve overrides for genuine exceptions, not routine processing
- document which run types are regular, supplementary, and bonus-oriented
Key Takeaways
- On-cycle processing should be repeatable and controlled.
- Repeatable calendar patterns reduce support effort.
- Stable run type and calendar group design are core production controls.