When an organization approves a salary increment in March with an effective date of January 1st, the payroll team faces immediate reconciliation challenges. The system must recalculate compensation for January, February, and March, determine the back pay owed for each month, and ensure future payroll runs reflect the updated salary without discrepancies.<\/p>\n
Manual approaches to retro payroll processing<\/a> introduce errors when HR teams track variances across multiple closed periods, match increments to affected employees, and manually adjust component entries. Onfinity ERP automates the entire workflow from salary update through variance calculation to component transfer, eliminating the reconciliation burden while maintaining verification controls at each stage.<\/p>\n The retro payroll process begins when HR updates an employee’s salary record with an effective date that falls within a previously closed payroll period. The system identifies all affected months, calculates the difference between the old and new salary for each component, and generates variance amounts that represent the back pay owed.<\/p>\n These calculated variances appear in a dedicated retro pay result window where HR reviews the amounts before any commitment. The system shows separate line items for basic salary arrears, housing allowance arrears, and special allowance arrears, giving payroll administrators component-level visibility into what will transfer to employee records.<\/p>\n Once verification is complete, HR transfers the retro components to employee payroll records. These arrears amounts then flow automatically into the next regular payroll run, ensuring employees receive both their current month salary and the back pay owed from previous periods in a single payment.<\/p>\n Onfinity supports direct salary updates through employee work information screens where HR enters the new compensation amount and specifies the effective date. The system maintains versioning history, showing the original salary on the join date and the revised amount with its retroactive effective date.<\/p>\n For organizations processing multiple salary changes simultaneously, the increment upload function accepts Excel files containing employee numbers, effective dates, component names, and increment values. Each file creates an increment batch record that populates salary changes across all listed employees, automatically flagging them for retro processing based on effective date logic.<\/p>\n The Excel structure requires specific columns: employee number, effective date, service type (increment or bonus), component name, input value type, and either an increment amount or percentage. HR teams choose between fixed value increases or percentage-based adjustments, ensuring batch payroll management<\/a> flexibility for different compensation scenarios.<\/p>\n When executing a retro payroll run, HR creates a named retro process, selects the payroll and period where back pay will be included, and chooses the event group that triggered the calculation. If the retro run should process only specific employees rather than the entire payroll population, HR creates an assignment set containing the affected employee records.<\/p>\n The system executes retro calculations only for employees in the selected assignment set, generating variance amounts for each affected component. This selective processing prevents unnecessary calculation cycles for employees without salary changes while ensuring accurate retroactive salary adjustments<\/a> for those who require them.<\/p>\n Event groups categorize the type of change that triggered the retro calculation, such as salary increments, allowance revisions, or bonus adjustments. This classification helps HR track why back pay was generated and supports audit requirements when reconciling payroll changes across fiscal periods.<\/p>\n After the retro payroll run executes, the retro pay result window displays calculated variances by employee and component. The transfer status remains blank until HR explicitly moves the amounts to employee records, preventing premature inclusion in payroll runs.<\/p>\n If verification reveals incorrect amounts or missing employees, Onfinity provides two rollback options. Component-level rollback removes specific arrears entries from employee work information while preserving the retro run record itself. Full retro record rollback erases the entire run from all windows, allowing HR to correct underlying issues and re-execute the calculation from scratch.<\/p>\n This dual rollback capability gives payroll administrators granular control over corrections. Minor adjustments use component rollback to reverse only the affected entries, while fundamental errors in run parameters trigger full rollback to restart the process with corrected inputs.<\/p>\n Once verification confirms accuracy, HR clicks the transfer button to move retro components into employee payroll records. The system marks the transfer status as complete and populates arrears amounts in the component entry section of each affected employee’s work information.<\/p>\nHow the Retro Payroll Workflow Manages Past Period Adjustments<\/h2>\n
Two Methods for Initiating Salary Changes That Trigger Retro Calculations<\/h2>\n
Controlling Retro Calculations with Assignment Sets and Event Groups<\/h2>\n
Verification and Rollback Controls Before Final Transfer<\/h2>\n