For a mid-period raise, record the effective time, check the pay period boundaries, and decide whether earlier hours receive the increase. A placed worker's new rate might start on the 9th of the month, or on a Wednesday in the middle of a biweekly cycle, while payroll keeps running on its own fixed schedule. That leaves one pay period holding two rates, and whoever sets up the change has to get the split right before the next check goes out.
Hiring managers and small staffing teams see this most often after a client approves a higher rate partway through a period. The approval arrives, the worker expects the new rate right away, and nobody has decided which hours it covers. Three rules keep that decision from turning into a dispute. Match each hour to the rate in force when it was worked. Locate the effective time within the pay period. Decide on purpose whether the raise can reach back to hours already worked.
Those rules differ from place to place, so read each one as a question to check against the law where the worker is placed and against your client's terms, not as a finished answer.
Which rate applies to hours worked before the raise date?
For a raise that is not retroactive, hours worked before the effective date stay at the old rate, and hours worked on or after that date get the new one. The date that counts is the date the work was done, not the date the check is written and not the date someone approved the change. Keeping that line clean is the first job, because every later step depends on it.
Oregon's labor agency handles its own annual minimum wage change in a way that shows the principle clearly. The agency says that "Increases to the minimum wage are based on inflation (if applicable) and take effect on July 1st of each year," and it adds that "The hours worked on or after 12:01 a.m. on July 1 must be paid at the newest applicable rate." ( Oregon BOLI, Oregon Minimum Wage)
The date itself is not the lesson. Oregon's date is fixed by the state, and your raise date is one you choose. The principle carries over: one period can hold two rates, and your records have to show which hours fall on which side of the boundary.
Start by writing an exact effective date and time in the placement record, not only a day. "Starting the 9th" leaves room for argument about whether the 9th begins at midnight or at the first shift. "From 12:00 a.m. on the 9th, local time" ends that argument before it starts.
If your timesheets record clock-in and clock-out times, a shift that starts before the effective time and ends after it should be split at that time, and each part paid at its own rate. If your timesheets only record total hours per day, you have a gap to close before the first split week. Without start and end times, you have to estimate the split, and an estimate is hard to defend when the worker disagrees with it.
Here is a plain example. Suppose a worker starts the period on the 1st at the old rate, and the raise takes effect at midnight on the 9th. Hours worked from the 1st through the 8th go on the old-rate line, and hours from the 9th through the end of the period go on the new-rate line. Your payroll report should show two lines for the same worker in the same period, each with its own hours and rate, so anyone reading it can see the split without asking. One blended rate would hide the change and invite questions later.
Overnight shifts create a second version of the same problem. A worker who sees the split move around from one week to the next will stop trusting the timesheet, even if each individual number is right.
Workers also ask whether the old or new rate applies to a shift that was booked before the raise but worked after it. The booking date does not change when the hours were worked. Then say that rule plainly in the notice you send. A rule stated in advance is much easier to defend than one explained after the first disputed check.
Keep a short note for each change in the record: who approved it, when it was entered into payroll, and which hours the first pay run applied it to. When you revisit the change months later, that note answers most questions without anyone digging through old timesheets. It also helps whoever takes over the placement, who may not know the change happened mid-period at all.
Where does the pay period split, and when is the money due?
The rate split falls at the raise's effective time, within the pay period your payroll uses. Pay periods are not the same everywhere. Washington's wage rules recognize several arrangements: "A payment interval may be daily, weekly, bi-weekly, semi-monthly or monthly." ( Washington WAC 296-126-023)
A raise that starts on the first day of a period is simple. A raise that starts in the middle needs a split, and the split is only correct if you know the exact boundaries. Washington's code gives an example of a semi-monthly setup, in which "the first pay period covers the 1st day of the month to the 15th day of the month; the second pay period covers the 16th day of the month to the last day of the month." ( Washington WAC 296-126-023) In that setup, a raise that starts on the 16th begins a new period and needs no split. A raise that starts on the 9th cuts the first period in two, with the old rate covering the 1st through the 8th.
The payroll cut-off identifies the end of the period, rather than the moment the rate changes. When a client says "effective the 9th," someone still has to check which pay period the 9th falls in and where that period's boundaries sit in the payroll system. Keep a copy of the payroll calendar for every month you are working in, and check it before you send the new rate.
The same section covers a month-end case that catches people off guard. "In a thirty-one-day month, unless a different payment interval applies by law, the employer must pay wages for work performed between the 1st and 24th days of the month on the established pay day (the last day of the month)." ( Washington WAC 296-126-023) If your payroll runs on a schedule like that, a raise that lands near the end of a long month should be checked against the calendar for that exact month, not against the usual cut-off you remember.
Overtime adds another layer in the Washington semi-monthly example. Under the same section, and again "unless a different payment interval applies by law," the employer must pay overtime wages "no later than the 10th day of the following month for the overtime earned during the first pay period, and no later than the 25th day of the following month for the overtime earned during the second pay period." ( Washington WAC 296-126-023) If a raise affects overtime pay, check the calculation and due dates that apply under your own jurisdiction and pay interval. Keep the overtime correction tied to the hours it covers, so a later change does not obscure what was owed earlier.
Biweekly cycles deserve their own mention because the boundaries move in steps of two weeks. Pick the first day of one period, count forward, and write down the start and end of every period you will touch in the next few months. Put those dates on a calendar that the people approving rate changes can see. A raise approved on a Tuesday can land in the middle of a period that started the previous Monday, and whoever approved it may not know that.
Small teams often discover the boundary problem only when the first check arrives. A simple habit prevents that. Before you approve any mid-period change, write the next three pay dates and the period boundaries next to the proposed effective date. That short list makes the split visible while there is still time to move the date. If the client wants a start day that splits a period in an awkward place, ask whether it can move to the next boundary. That is often an easy conversation when the reason is clean payroll.
If you are a staffing firm, also check whether your client's timesheet cut-off matches your own payroll cut-off. When the two differ, a raise that is correct in one system can look wrong in the other. A client's report can show hours at the old rate while your check shows the new one, and that gap is much easier to explain before the change than after.
Can a raise reach back to hours already worked?
Sometimes, yes: a raise can be made retroactive, and at least one state's wage statute addresses that case directly. North Carolina's law says: "Wages may be retroactively increased without the prior notice required by this subsection." ( North Carolina G.S. 95-25.13)
That sentence has limits. Before choosing how far back to reach or how to pay the difference, check the applicable law, your client agreement, and your payroll practice. Do not assume that a state's permission for retroactive increases carries over to the place where your worker is placed. Check the rules for that location.
If you decide to make a raise retroactive, treat the difference as a correction, not a bonus. Show it as its own line on the next pay run, label it with the dates it covers, and keep the original timesheets attached to the record. A labeled correction can be checked line by line. A lump sum with no explanation invites questions and makes the old and new hours harder to reconcile later.
Before you promise back pay, confirm who approves the rate. In many staffing arrangements the client sets the bill rate and the firm sets the pay rate, and the two can change on different dates. A retroactive pay increase that the client never approved for those same hours can leave your firm paying a higher rate for hours it bills at the old one. Decide who has authority to approve a backdated rate before a dispute happens. Write down who signs off on each side, so that a backdated pay change does not depend on a single email thread.
Set a limit on the look-back before you start. A raise that reaches back to the start of the period is easy to explain. A raise that reaches back "as far as needed" sounds like an open-ended promise, and it is hard to close out. Write the earliest date you will correct into the record, and treat anything earlier as outside the change.
Be careful with wording in any message about a backdated rate. Saying the raise is "effective the 1st" invites the worker to ask about every day since then, while "a correction for hours from the 9th onward" is specific and easy to check. Pick words that describe the same dates your records show, and avoid vague phrases like "back to when it was approved."
Retroactive changes also reach past the worker's pay. Overtime hours affected by the increase need their own correction line, with the applicable overtime due dates checked separately. Tax withholding and benefits records may need the corrected hours before the correction is paid, so check with whoever runs those systems before you process it. A correction that pays the right amount but lands in the wrong system still creates a problem.
What should you check before the change goes live?
Confirm the decisions in writing before the new rate goes into payroll. Put all three in the placement record, and send the same dates to the worker and to the client, so no one is working from a different version of the change.
Then work through the steps in order. First, check whether the raise begins on a period boundary. If it does, no split is needed, but you should still record the date. Next, record the decision on retroactivity. Finally, tell the worker in plain words what changed and when. A short written notice costs far less than a disputed check.
If something changes after the record is set, update the record first and the pay run second. The record should never lag behind what was paid, because the record is what you will check when someone asks about a payment months from now.
Mid-period raises are routine once you have a process for them. A clear record makes the raise easier for the placed worker, your client, and your own bookkeeper to check.
Related guides: Check pay equity before approving an offer: 5 checks · Daylight saving day pay: 6 timesheet review steps · Florida back pay and suit deadlines: 2 dates to track.