Payroll Changes Even When Payroll Is Not Running
The payroll period between paydays is when many of the next payroll’s problems are created.
A manager hires somebody Monday.
Payroll is Friday.
The payroll coordinator hears about the employee Thursday afternoon.
That is not really a payroll-calculation problem.
It is an employee-change workflow problem.
Create a payroll change queue
Employee changes should not live only in someone’s inbox.
Track events such as:
- new hire;
- compensation change;
- department change;
- location change;
- status change;
- termination;
- rehired seasonal worker;
- address update;
- deduction change.
The queue can be simple.
The important thing is that payroll has one place to determine what changed since the previous run.
New employees
Payroll Relief allows new employee records to be created and includes employee information used for payroll and reporting. Official documentation also supports employee imports.
A new-hire workflow should therefore end with a clear status:
Payroll-ready
—not merely:
Hired
Those two events may occur on different days.
Employee Self Service can change the intake process
AccountantsWorld describes Payroll Relief Employee Self Service as an optional module that digitizes onboarding and ongoing employee-data management.
That can shift part of data entry toward the employee.
But it still requires the employer to manage the process.
Employees completing forms does not guarantee:
- correct compensation;
- correct department;
- correct pay schedule;
- correct first payroll date.
Employer facts still need employer review.
Active, inactive and terminated are not synonyms
Current IRIS documentation makes a specific distinction.
It describes an inactive employee as one expected to be re-employed, such as a seasonal employee, while a terminated employee is one not expected to return.
That distinction can affect how a business handles seasonal workers.
Do not mark everyone who temporarily disappears from the schedule as permanently terminated without understanding the intended status.
Reports can help audit workforce changes
Payroll Relief provides employee reporting that can include hired, pending-new-hire and terminated populations, along with active/inactive filtering.
A useful employer practice is to compare the payroll population periodically against:
- current HR roster;
- active employee list;
- recent hires;
- recent departures.
The goal is to find mismatches before payroll.
Compensation changes deserve an effective date
“Give Kevin a raise to $28 an hour.”
That instruction is incomplete.
Payroll needs:
- new rate;
- effective date;
- whether prior hours are affected;
- approving manager;
- whether the change is permanent.
Effective dates prevent a salary or rate change from being applied to the wrong payroll period.
Terminations need a payroll checklist
A termination event may involve more than changing status.
The employer should determine:
- final hours;
- PTO treatment according to applicable rules/policy;
- commission or bonus amounts;
- deduction implications;
- direct-deposit considerations;
- employment status in payroll;
- final document delivery.
State law can affect final-pay timing, so legal/compliance questions should be checked against authoritative government guidance rather than guessed from a software article.
Close the loop
Every employee change should have:
Requested
Verified
Entered
Reviewed
Effective
If payroll coordinators adopt only one habit from this article, make it this:
Do not treat “I emailed payroll” as proof that the payroll record changed.