Bi-Monthly pay cycles rely on a single stored payroll date, with the second payroll date being assumed by the system.
This can lead to inconsistencies when generating and rebuilding budget, payroll, and billing schedules, particularly when customer payroll arrangements do not align with the system's assumptions.
To improve accuracy and flexibility, introduce support for two explicitly stored payroll dates for Bi-Monthly pay cycles and ensure both dates are used consistently across all related processes.
This enhancement should allow administrators to configure and maintain two distinct payroll dates, require both dates to be populated, prevent duplicate day selections, and make the second payroll date available wherever payroll cycle defaults are configured. Budget date generation, billing schedules, contract processing, employee budget creation, and any schedule rebuild processes should use both stored payroll dates to ensure consistent outcomes.
The solution should eliminate the need for system-generated assumptions, reduce manual corrections, improve forecasting and invoicing accuracy, and better support customer-specific payroll arrangements, while ensuring all non-Bi-Monthly pay cycle functionality remains unchanged and unaffected