Generation Control & Frequency
Overview
Generation control determines whether an element should resolve for a given payee and calendar. It is commonly used to enforce frequency rules and prevent elements from resolving on every run.
Typical Uses
- quarterly or annual payments within monthly payroll
- skip logic for probation, anniversary, or eligibility milestones
- controlled supplementary payments
- country-specific timing rules that should not be hard-coded inside the earning formula
Interaction With Calendars
Generation control can be defined at element level and overridden at calendar level. This allows a standard element design to behave differently for special runs without duplicating every element.
Frequency Design Questions
| Question | Why it matters |
|---|---|
| What event enables the element | Controls frequency and timing |
| Is the rule stable enough to define globally | Avoids excessive calendar overrides |
| What happens in retro or segmentation | Prevents inconsistent replay behavior |
| Does the pay period frequency need deannualization | Affects amount conversion and eligibility |
Common Failure Modes
- generation control blocks an element but the team debugs the formula instead
- a calendar override exists for one month and is forgotten the next month
- retro replays a period without rechecking the intended generation event
Key Takeaways
- Generation control is a precision tool for selective resolution.
- Calendar overrides should be used carefully and documented.
- Frequency rules must be tested with retro and off-cycle scenarios.