A raise gets approved, but the paperwork doesn't reach payroll until two cycles later. An employee's timecard was short six hours because a punch got missed. A new hire's pay rate was entered a dollar low, and nobody caught it for a month. Every one of these ends the same way: someone was paid the wrong amount, and now you have to make it right without creating three new problems in the process.
Retro pay and payroll corrections are a normal part of running payroll. They are not a sign that something is broken. What matters is handling them cleanly, because a sloppy correction can throw off taxes, overtime, deductions, and your quarter-end totals, and can leave an employee confused about what they were actually paid and why. A clean correction does the opposite: the employee gets exactly what they're owed, and your records stay tidy.
This guide walks through what causes retro pay, how it's calculated, how taxes get handled, how corrections ripple into overtime and deductions, when to use a correction versus an off-cycle run, and how to reconcile afterward, all inside ADP Workforce Now. Your people need to get paid correctly. We make that happen.
Retro pay, short for retroactive pay, is money owed for work already performed that wasn't paid correctly the first time. Understanding the cause matters, because the cause shapes how you fix it.
Common Triggers
The most common trigger is a pay change with an effective date in the past. A raise is approved effective the first of the month but doesn't get entered until the second pay period, so the employee was underpaid at the old rate for the gap. Promotions and rate corrections work the same way. Another frequent cause is time that didn't make it into the original run: missed punches and timecard errors, hours entered late, or a shift that got dropped. Then there are outright entry errors, like a wrong rate keyed during new hire onboarding in ADP.
Retro Pay Runs in Both Directions
Retro pay can run in either direction. Usually it's money owed to the employee, but sometimes an overpayment needs to be recovered, which comes with its own rules. Naming the cause precisely is the first step, because "we owe them retro" is not enough to fix it correctly. You need to know the old value, the new value, and the exact period affected.
The core of a retro calculation is a difference over a defined window. You figure out what the employee was actually paid for the affected period and what they should have been paid, and the gap is the retro amount.
Hourly, Salaried, and Missed Hours
Say an hourly employee's rate went up but the raise landed two pay periods late. For each of those periods, you take the hours they worked, calculate pay at the old rate versus the new rate, and the difference is what's owed. For a salaried employee, you compare the salary received against what they should have received at the new salary, prorated for the days involved. Missed hours are more direct: the hours that were dropped, paid at the correct rate.
Where the Details Slip
The arithmetic isn't hard, but the details are where people slip. You have to use the right rate for the right window, count the exact hours or days affected, and be careful when a rate change lands partway through a pay period. In ADP Workforce Now, retro pay can be entered so it's identified clearly rather than buried inside regular earnings, which keeps the calculation transparent and easy to explain. An employee who can see exactly how their retro was figured is an employee who trusts their paycheck.
Retro pay is wages, and wages are taxable. That part is simple. The wrinkle is that retro pay is often paid in a later period than the work it relates to, and that timing has tax consequences.
Taxed in the Period Paid
Generally, retro pay is taxed in the period it's actually paid, not the period the work happened in. So a retro amount paid in a later cycle gets added to that cycle's wages and taxed accordingly. Because retro pay can be treated as supplemental wages under IRS Publication 15 in some situations, the withholding on it may be calculated differently than on regular wages, which sometimes surprises employees. The same logic applies to bonus payrolls in ADP. It's still all reconciled through their overall tax picture, but the per-check withholding can look different than they assumed.
Wage Bases and Quarter Boundaries
Payroll taxes and wage-base considerations also come into play, especially near year-end or quarter boundaries, when a retro payment can push a high earner past the Social Security wage base. The specific tax treatment of supplemental wages and the applicable rates are set by tax authorities and can change, so verify current rules with official IRS sources or your advisor. The safe habit is to run retro through payroll properly so taxes are calculated correctly, rather than handing someone cash or a manual check that skips the withholding.
Here's the trap that catches even experienced payroll people: a retro rate change can change overtime that was already paid. Overtime for non-exempt employees is generally based on a regular rate of pay, and if that rate goes up retroactively, the overtime for those periods may have been underpaid too.
Picture an hourly employee who worked overtime during the weeks their raise should have been in effect. If you only pay the retro difference on their straight-time hours, you've shorted them on the overtime premium for those same weeks, because the overtime was calculated on the old, lower rate. A complete retro calculation revisits the overtime at the corrected rate, not just the base hours.
This is exactly why "just add a few hundred dollars of retro" often isn't right. The retro on straight time is only part of it; the overtime recalculation can be the part that gets missed. Working through the affected periods carefully in ADP Workforce Now, including any overtime, is what makes the correction actually complete. The FLSA overtime pay requirements governing overtime and the regular rate are set by law and can change, so confirm specifics with your advisor, and see our guide to overtime compliance and labor cost control for the bigger picture.
Retro pay doesn't just add wages; it can move deductions too, and forgetting that is a common source of a second-round correction. Percentage-based deductions are the clearest example. If an employee contributes a percentage of pay to a retirement plan, additional retro wages may mean an additional contribution, and possibly an additional employer match, for those amounts, all still subject to the annual 401(k) contribution limits.
Other deductions depend on how they're set up. Some are flat amounts that don't change with a little extra pay; others are tied to earnings and will move. Garnishments have their own rules about what portion of pay is subject to withholding under the Consumer Credit Protection Act, and additional wages can change that math. If you're not sure your garnishment setup in ADP is handling retro correctly, check it before the run.
The lesson is to look at the whole paycheck, not just the gross retro number. Before you finalize a correction in ADP Workforce Now, check which deductions should move with the added wages and which shouldn't, so the net result is right and you're not back fixing a missed 401(k) contribution next month. Getting the deductions right the first time is what separates a clean correction from a chain of them.
When something was paid wrong, you have choices about how and when to fix it, and picking the right path saves headaches.
When the Next Regular Payroll Is Enough
Sometimes the cleanest option is to include the retro or correction in the next regular payroll. The amount is identified clearly, the employee sees it on their normal check, and you avoid an extra processing event. For many routine retro situations, this is the simplest, calmest approach.
When an Off-Cycle Run Makes Sense
Other times an off-cycle payroll run in ADP makes more sense. If an employee was significantly underpaid and waiting until the next regular payday would be a real hardship, or if a correction needs to happen before a quarter or year closes, running an off-cycle payment gets the money out and the records right on the needed timeline.
Making the Call
The judgment call is about urgency, size, and timing. A small retro with no time pressure usually belongs in the next regular run. A large shortfall or a fix that has to beat a reporting deadline often justifies an off-cycle payment. Either way, the goal is the same: correct wages, taxes, and records. Hair on fire because someone was badly underpaid and payday is two weeks out? That's a classic off-cycle situation, and the kind of call we help clients make every week.
A client with roughly sixty employees approved a round of mid-year raises, but the approvals reached payroll two cycles after the effective date. Several employees had been paid at their old rates for those two periods, and a few of them had worked overtime during that window. The payroll administrator knew retro was owed but wasn't sure how to handle the overtime piece.
We worked through it in ADP Workforce Now period by period. For each affected employee, we calculated the straight-time difference between the old and new rates, then revisited the overtime for those same periods so the premium was corrected at the proper rate, not the old one. We checked percentage-based retirement deductions so the contributions and match tracked with the extra wages, and confirmed the retro would be taxed correctly in the period paid.
The figures are rounded and illustrative, but the shape is what counts. Because the raises were sizable and one employee faced a real shortfall, the client chose an off-cycle run to get the money out promptly. Afterward we reconciled the totals so the corrected wages, taxes, and deductions all tied out. The employees got exactly what they were owed, overtime included, and the records were clean going into quarter-end.
Is retro pay taxed differently than regular pay?
Retro pay is taxable wages, and it's generally taxed in the period it's actually paid. Because it can be treated as supplemental wages in some cases, the withholding on it may be calculated differently than on a regular paycheck, which can surprise employees. It all reconciles through their overall tax picture, but the per-check withholding can look different. Confirm current rules with your advisor or official IRS sources.
Do I need to fix overtime when I pay a retroactive raise?
Often, yes. Overtime for non-exempt employees is generally based on the regular rate of pay, so if a rate goes up retroactively, the overtime paid at the old rate for those periods may have been underpaid too. A complete retro calculation revisits the overtime for the affected weeks, not just the straight-time hours. When in doubt, confirm the specifics with your advisor.
Should I run a correction on the next regular payroll or do an off-cycle run?
It depends on urgency, size, and timing. A small retro with no time pressure usually fits cleanly into the next regular run. A large shortfall, a real hardship for the employee, or a fix that has to happen before a quarter or year closes often justifies an off-cycle payment. The goal either way is correct wages, taxes, and records.
The payroll teams that stay calm about corrections built habits that prevent most of them and clean up the rest quickly. They get pay changes to payroll before the effective date whenever possible, so retro is the exception. They review timecards before finalizing a run to catch missed punches early. And when a correction is needed, they work it completely the first time: straight time, overtime, deductions, and taxes, all in one pass.
They also reconcile after every correction, confirming the adjusted totals tie out before quarter-end so there are no surprises when the reports run. Handled this way, retro pay stops being a source of anxiety and becomes just another routine part of running payroll well.
We're former ADP service professionals, and we work with ADP exclusively. When a retro situation or a payroll correction has you second-guessing the numbers, you're not opening a ticket and waiting in a queue or sitting on hold. You get a dedicated consultant who knows ADP Workforce Now and how to work a correction so it ties out the first time. We've got you.
Staring at a retro calculation and not sure the overtime is right? REQUEST A CONSULTATION.
ADP and the ADP logo are registered trademarks of ADP, Inc. This article is general guidance only and not tax or legal advice. Tax treatment of supplemental wages, overtime rules, and related requirements are set by authorities and change over time. Confirm specifics with your licensed advisor and official IRS sources.