Why are penalties for some instances not getting applied even after the policy effective date?

When you modify the penalization policy—like changing its frequency or start date—midway through a cycle, the new settings don’t take effect immediately. This ensures consistency and prevents overlapping calculations for the same attendance period.

Why This Happens

Each penalization policy in Keka follows a defined cycle (Daily, Weekly, or Monthly). 
If you change the configuration (for example, from Weekly to Monthly) mid-cycle, the system defers the new settings to the next cycle.

This means:

• Penalties already calculated under the old policy remain unchanged.
• The new frequency applies only from the start of the next cycle.
• No recalculations occur for the ongoing period.

Example

If your policy was set to Weekly and you switch to Monthly on 15th October, the new configuration takes effect only from 1st November (or from your defined cycle start date, such as 4th November). 
Penalties between 15th–31st October will continue under the earlier weekly setup.

Resolution

If penalties don’t appear as expected:

• Check the policy change date: Mid-cycle updates apply from the next cycle.
• Verify the cycle start date: The effective date varies (e.g., 1st, 4th, or 10th).
• Review penalty types: Ensure each type (Late In, Early Out, Absence, etc.) uses the right frequency.

Tip

To avoid skipped or delayed penalties, make policy changes at the start of a new cycle rather than mid-month.