Some organizations use fixed balance periods with clearly defined start and end dates (e.g. quarterly or yearly).

At the end of the fixed balance period, all positive balances must be settled, while negative balances are ignored or reset according to company rules.

Business Purpose

• Ensures compliance with labor law and payroll rules
• Prevents long-term accumulation of overtime
• Provides predictable settlement cycles

System Behavior

• Balances accumulate throughout the fixed period
• At attendance closure of the final month:
  • All positive balances are automatically forced to payout
  • Negative balances are excluded from further calculations

Some organizations prefer running (floating) balance periods defined by a number of months rather than fixed dates.

Each monthly balance must be settled within a defined lifespan starting from its origin month.

Business Purpose

• Enforces timely overtime compensation
• Prevents indefinite balance carryover
• Aligns with regulatory requirements

System Behavior

• Each monthly balance is tracked with its origin month
• At each monthly closure:
  • The system identifies balances reaching the end of the running period
  • The oldest positive balance is automatically settled

Organizations may choose between explicitly tracking overtime hours or managing overtime purely as a cumulative balance.

Business Purpose

• Supports different operational and reporting needs
• Enables separation of paid and compensatory overtime
• Allows simplified setups where detailed tracking is not required

System Behavior

Tracked overtime activities

• Overtime is marked directly on shifts using overtime activities
• Marked hours do not increase worked time or cumulative balance
• Paid and compensatory overtime is tracked and reported separately

Cumulative balance only

• Monthly balance is calculated as the difference between worked time and working time fund
• Balances accumulate across periods
• Remaining positive balance is settled at the end of the balance period

Some organizations impose limits on whether positive or negative balances may be carried forward.

Business Purpose

• Prevents excessive overtime accumulation
• Enforces stricter attendance discipline
• Reduces manual corrections

System Behavior

• Configuration can disallow positive or negative balance carryover
• Monthly attendance closure validates balance rules
• Closure is blocked if balances violate configured restrictions

When an employee’s contract ends, any remaining balance must be settled immediately.

Business Purpose

• Ensures correct final payroll settlement
• Prevents balance carryover beyond employment

System Behavior

• In the termination month:
  • All positive balances are automatically paid out
  • Negative balances are handled according to company policy

Organizations often require immediate visibility of balances directly on the roster.

This is achieved through dedicated balance-related properties linked to report metrics.

Business Purpose

• Improves transparency for planners and employees
• Supports informed scheduling and overtime decisions
• Reduces reliance on separate reports

System Behavior

• Key balance indicators are displayed on the roster, such as:
  • Transferred balance from previous periods
  • Balance created in the current period
  • Balance carried forward to the next period
  • Paid and refundable balances

Clear visibility of paid overtime is required for payroll validation and compliance.

Business Purpose

• Prevents double payment of overtime
• Supports legal and contractual limits

System Behavior

• Monthly and yearly paid overtime balances are displayed
• Values become available after attendance closure

Organizations using tracked overtime need to distinguish between different compensation types.

Business Purpose

• Supports mixed compensation models
• Improves clarity for employees and HR

System Behavior

• Paid and compensatory overtime is tracked and reported separately
• Aggregations are shown for defined periods (e.g. yearly)

When an organization starts using the system in the middle of a balance period, existing balances must be imported.

Business Purpose

• Ensures continuity during system migration
• Prevents loss of historical balances

System Behavior

• Initial balances are loaded using a dedicated initial balance property
• Imported balances become part of cumulative calculations
• Applicable only to fixed balance periods

An employee transfers from one organizational unit to another during a month.
Balance periods are defined at the unit level and differ between the two units.

System Behavior

• The employee’s balance period changes on the transfer date
• For the original unit, the effective balance period is limited to the employee’s membership validity
• Any positive balance at the end of this period is forcibly settled
• A new balance period starts for the employee in the target unit

Business Value

• Prevents mixing balances across units
• Ensures correct settlement during unit changes
• Supports accurate payroll processing