Payroll Specialist

I start by pulling and reconciling the source data about a week before pay date: new hires, terminations, salary changes, timesheets, overtime, and any manual adjustments like bonuses or expense reimbursements. I cross-check hours against the time and attendance system, in my last role that was Kronos feeding into ADP Workforce Now, and flag anything that looks off before it hits the payroll register. Once the data is locked, I run a preview or trial payroll and review the register line by line, comparing gross-to-net for a sample of employees against the prior cycle to catch anomalies. I get sign-off from my manager or finance lead, submit for processing, and confirm the funding file matches what's being disbursed. After payday I reconcile the general ledger postings and file or schedule the tax deposits, then keep a short log of anything unusual for the next cycle.

I've run payroll in ADP Workforce Now, Workday Payroll, and Gusto, and I supported a migration from an in-house ADP instance to Workday at my last company. My part was building the parallel run: for two full cycles I processed payroll in both systems side by side and reconciled every employee's gross pay, deductions, and net pay line by line, not just the totals. We found a handful of mismatches, mostly around how each system rounded pre-tax deduction caps and how garnishments were sequenced, and I logged those as configuration tickets before go-live rather than letting them surface after real employees got paid wrong. I also wrote a one-page cutover checklist for the team covering data freeze dates, final approvals in the old system, and who to contact if something didn't map correctly. For me, parallel testing is the only way to trust a new system with real paychecks.

I treat compliance updates as a standing task, not something I react to. I'm subscribed to tax authority notices for the jurisdictions we operate in, and I follow professional payroll body updates for changes like annual wage base and threshold adjustments each new tax year. My payroll software vendor also pushes tax table updates, but I never assume those are complete. I verify new minimum wage or statutory rate changes against the official source before the first payroll of the new tax year runs. When a jurisdiction changes something mid-year, like a new paid leave mandate, I read the actual legislation or the official guidance, not just a summary blog post, and I document the effective date and what changed in our internal payroll procedures file so the next person doesn't have to relearn it. I also keep a calendar of known annual deadlines so nothing gets discovered at the last minute.

Payroll data is some of the most sensitive information in the company, so I treat access control as the first line of defence. I only pull reports with the fields I actually need for a task rather than exporting full employee records by habit, and I make sure payroll system permissions are set so managers can see their team's time and attendance but not compensation details unless their role requires it. Physical and digital hygiene matters too: I don't leave payroll registers open on a shared screen, I use company-approved file transfer methods rather than emailing spreadsheets, and I lock my screen every time I step away. When HR or a manager asks about someone's pay, I confirm they have a legitimate business reason and the right authorisation level before sharing anything, and I keep a short record of who requested what and why for sensitive cases like garnishments or pay disputes. I also make sure former employees' access is removed immediately.

During a routine pre-submission review, I noticed one department's overtime hours had roughly doubled compared to the previous three pay periods, with no corresponding change in headcount or project activity. Instead of assuming it was a one-off busy week, I pulled the raw time clock data and compared it against the exported totals in our payroll system, ADP at the time, and found that a recent update to how the time and attendance integration rounded shift boundaries was double-counting a portion of hours worked across a shift change. I flagged it to IT and the department manager before running payroll rather than after, which meant we caught roughly forty employees who would have been overpaid, some by several hundred pounds. We corrected the integration mapping, reran the preview, and I documented the issue and the fix in our procedures file so it would be checked automatically going forward instead of relying on someone noticing a pattern by eye.

An employee came to me convinced their pay was short by several hours, and they were understandably frustrated because rent was due that week. I didn't get defensive or ask them to just wait for the next cycle. I pulled up their timesheet and the payroll register with them on a call, walked through exactly how their hours, overtime, and deductions were calculated, and found that a shift differential hadn't been applied correctly for two days that pay period. I acknowledged the mistake directly rather than blaming the system, told them the exact amount owed, and asked our processor to run an off-cycle correction so they weren't waiting until the next scheduled payday. I followed up myself once the payment went through instead of leaving it to an automated notification. The employee's frustration was really about feeling unheard as much as the money, so explaining the calculation clearly and moving fast on the fix mattered as much as the correction itself.

At my last company we expanded from processing payroll in four states to twelve within about a year, and each new state came with its own withholding registration, unemployment insurance rate, and in some cases paid leave contributions. I built a tracking sheet for every state we operated in listing registration status, filing frequency, and any state-specific forms, so nothing depended on my memory. The trickiest case was an employee who worked remotely in one state but the company had no existing tax registration there, so I coordinated with our accountant to get the state withholding and SUTA accounts set up before their first paycheck, rather than processing it incorrectly and amending later. I also had to explain reciprocity rules to a couple of employees living in one state and working in a neighbouring one, so they understood why their withholding looked different from a colleague's. Keeping a living reference document was what made the expansion manageable instead of chaotic.

The first step is always confirming the exact amount and cause before telling anyone a number, so I recalculate the correct pay from the source timesheet or rate change and compare it to what was actually disbursed. For an underpayment, I push for an off-cycle correction payment as fast as our processor allows rather than making the employee wait for the next scheduled cycle, since it's our error, not theirs. For an overpayment, I follow whatever recovery policy and applicable wage law apply. In the US that often means getting written acknowledgment from the employee before any deduction, since many states restrict how and how much you can take back from a future paycheck without consent. I always loop in HR or legal before deducting anything if the amount is large or the employee disputes it. I document the root cause, whether it was a manual entry error, a system miscalculation, or a late change that didn't get processed, and note what would prevent it recurring.

Year-end starts for me in the autumn, not January, because W-2 accuracy depends on catching problems while there's still time to correct them. I run a pre-year-end audit comparing each employee's year-to-date wages, taxes, and benefit deductions in the payroll system against the general ledger, and I specifically check things that tend to drift, like imputed income for group term life insurance, fringe benefits such as personal use of a company vehicle, and any manual off-cycle payments that might not have flowed through normal tax calculations. I reconcile pension contributions against plan limits so nobody's over the annual cap without us catching it, and I confirm any relocation or severance payments were taxed correctly. Once year-end documents are generated, I spot-check a sample against known employee data before distribution, then file the required returns and handle any reconciliations before the deadlines. Any corrections after distribution get handled through an amended filing, and I document exactly why the correction was needed.

For new hires, I make sure the effective date, prorated salary or hourly setup, and benefit eligibility waiting period are entered before the first payroll deadline, and I double check the pay is prorated correctly for a partial period rather than defaulting to a full period's pay. For terminations, the rules vary a lot by jurisdiction and that's where I'm most careful. In states with strict final pay timing laws, like California requiring final pay on the last day worked for an involuntary termination, I coordinate with the manager and HR as soon as I hear about a termination so the payment is ready on time, including unused leave payout where required. I calculate the final pay manually rather than trusting an automated run to catch every nuance: prorated salary, any final commissions or bonuses owed, and required deductions, then have it reviewed before release. Missing a final pay deadline can trigger statutory penalties in some jurisdictions, so I treat those dates as hard deadlines, not targets.