Changing Pay Frequency: Reconcile the Bridge Period and Annual Pay
Updated: 13 hours ago
The awkward paycheck in a frequency change is often the one between two familiar schedules. Employees know their old payday, and payroll knows the new recurring calendar. The difficult question is what happens to the work, deductions and cash between them. An apparently missing week can be wages scheduled for a later check, an actual uncovered interval or a mistake in the explanation. Those outcomes need different responses.
Start with the last old payment, the first new payment and the payment after that. Give each one an inclusive work period, a payday and a supported calculation. Then reconcile what each employee has already earned, received and had deducted. A change from weekly to biweekly should not quietly become a change in the wage agreement.
This guide is for U.S. employers changing how often they pay employees, including changes between weekly, biweekly and semimonthly schedules. It provides a Pay-Frequency Bridge Calendar and Reconciliation you can copy into a controlled document. It does not decide which schedule is lawful for a particular workforce or change the fixed workweek used to calculate overtime.
If the change exposes a limitation in your current payroll service, turn the bridge requirements into a software conversation.
SelectSoftware Reviews offers free advisor help with payroll software options. Ask shortlisted providers to show the transition period, deduction dates and first new payment before accepting a recurring-calendar demonstration.
Contents
Approve the schedule before moving the payroll boundary
Write down the affected legal employer, work locations, employee groups, current frequency and proposed frequency. Include the compensation arrangements and any collective-bargaining or employment agreements that constrain the change. A provider's ability to select monthly payroll does not establish that your employees may lawfully be paid monthly.
Check both how often wages must be paid and how long payment may lag behind the work. Those are separate restrictions. Notice requirements, designated paydays, special occupations and final-pay rules can also matter. Obtain the applicable requirements from the responsible agency or qualified reviewer before announcing a date. Do not treat a generic national notice template as a legal conclusion.
Two official examples show why the review must be specific. Texas Workforce Commission guidance distinguishes nonexempt employees, who generally must be paid at least twice monthly, from exempt employees, who generally must be paid at least monthly. Its operational advice is to give advance written notice identifying the last old payday and the first two new paydays. That advice is useful for planning; it is not a nationwide statutory notice period.
California's Labor Commissioner addresses a biweekly-to-semimonthly change directly: prior notice and compliance with the applicable payday requirements matter. Its page also explains different timing rules and exceptions. Do not copy the Texas frequency distinction or one California interval into another jurisdiction without checking the actual rule.
Where employees are represented, involve the appropriate labor-relations reviewer before implementation. The NLRB's good-faith bargaining guidance identifies duties concerning changes to wages, hours and other mandatory bargaining subjects. An employee announcement does not replace a required bargaining process.
Keep the resulting decision short and usable: who may change, what dates are approved, what notice or agreement work must occur and who verified it. If a population needs a different route, keep it separate. A successful change for one salaried group should not automatically move every hourly employee into the same schedule.
Put three payments on the same coverage map
Keep four terms distinct. The workweek supports weekly wage calculations. The pay period groups the work included in a payment. The payday is when wages are paid. The processing cutoff is when a provider needs approved inputs or funding. These dates can be related without being interchangeable.
For each affected group, identify the final payment under the old schedule. Record the work it actually covers, including adjustments or late items. Do not assume that a check paid on the fifteenth covers the first through the fifteenth. A payment can cover an earlier period, and a special run can carry corrections from several periods.
Next, assign the first new payment and the following new payment. Place their covered intervals immediately beside the old interval. Look for a worked day that appears nowhere and a worked day included twice. Review time, earnings and any salary allocation together, rather than deciding that consecutive date labels prove the amounts are complete.
Keep work dates separate from pay dates in the comparison. An interval without a payday is not necessarily an interval without wages earned. However, a longer wait for cash can still violate an applicable payment deadline or create a serious employee problem. The legal timing check and the wage-coverage check both need an answer.
Preserve the underlying records. For covered nonexempt employees, 29 CFR 516.2 includes the payment date and covered pay period among required payroll information, alongside wage and deduction details. A summary calendar should point to that evidence; it should not overwrite the old history when a new schedule starts.
A provider change adds another boundary. Name the issuer of each payment, including any short bridge run, and cancel obsolete automatic processing only through the approved control. Two systems can each believe they own the first new check. A clean coverage map can still produce duplicate cash if payment ownership remains ambiguous.
Read a weekly-to-biweekly bridge from work to money
Consider a fictional employer planning an April 2027 change. Assume its reviewer has separately approved the schedule for the affected workforce. The dates illustrate coverage and communication, not a legal schedule for every state.
Last old payment: work from April 5 through April 11, paid April 16.
First new payment: work from April 12 through April 25, paid April 30.
Following new payment: work from April 26 through May 9, paid May 14.
The covered work intervals are continuous. April 12 is not left behind, and April 11 is not included in both systems. Employees will nevertheless go from the April 16 payment to the April 30 payment, rather than receiving another weekly check on April 23. The announcement must explain that change in cash timing.
Assume one employee earns $24 per hour and works 40 hours in each relevant week, with no other compensation or adjustment. The last old gross payment is $960. The first new gross payment is $1,920 for 80 hours. The higher check is two weeks of ordinary wages, not a pay increase or a special transition bonus. Actual net pay still depends on withholding and deductions.
Now examine a different employee in the same new pay period. They work 46 hours in the first week and 34 in the second. Under the ordinary federal weekly overtime assumptions used here, the 80-hour total does not eliminate the six overtime hours. At the same $24 rate, with no other earnings affecting the regular rate, straight-time pay is $1,920 and the additional half-time premium is $72. The simplified gross result is $1,992. State rules or other compensation can change the required calculation.
The dates cover consecutive work intervals, while the space between paydays changes. Verify both before releasing the schedule.
If April 30 is too late under the applicable rules, the example is not permission to use it. Revise the boundary, arrange an approved earlier wage payment or choose another lawful transition. Then rebuild the later periods so a short first payment does not leave the same work inside a subsequent full payment.
Keep the workweek intact when checks cover longer periods
A frequency change does not by itself move the overtime workweek. Preserve its established start day, time and time-zone treatment in both timekeeping and payroll. Confirm that employees with different workweeks remain correctly configured.
29 CFR 778.104 treats workweeks separately and does not permit averaging hours over multiple weeks to avoid overtime. A semimonthly period can cut through a workweek; it cannot make the remaining hours disappear. Retain enough time detail to reconstruct the complete week across the period boundary.
Check the export range used by timekeeping. A report that ends at midnight on the new cutoff can exclude the final shift or include a shift twice if the receiving system interprets the end date differently. Test the actual records for the last old interval and first new interval, including overnight work and late corrections where relevant.
Also preserve payment timing. 29 CFR 778.106 generally places overtime on the regular payday for the period in which the workweek ends, with a limited rule for amounts that cannot yet be determined. A transition project or a missed internal cutoff is not a general authorization to defer earned wages.
Use employee-level comparisons when testing the boundary. Include at least a straightforward hourly case, a week with overtime and a period that splits a workweek if the proposed schedule does so. Add actual workforce exceptions, such as multiple rates, commissions or a separate state overtime requirement. A combined batch total can conceal one person being short and another being overpaid.
Reconcile salary without guessing a day rate
Begin with the approved compensation agreement, not the amount on the most recent check. An annual salary, a weekly salary and a per-period salary do not necessarily describe the same promise. Determine what the salary covers and which reviewed method applies to a partial transition period.
For a fictional annual salary of $62,400, ordinary allocation arithmetic gives $1,200 across 52 payments, $2,400 across 26 payments or $2,600 across 24 payments. Those figures show how payment size can change while the stated annual amount remains the same. They are not a universal proration rule or evidence that every calendar has exactly those payment counts.
For a limited reconciliation example, assume a reviewed agreement defines $62,400 over 52 full compensated weeks at $1,200 per week. Twenty weeks have already been covered and paid at $24,000. The remaining 32 weeks require $38,400, which could be scheduled as 16 payments covering two full weeks each at $2,400. The total is 36 payments covering the agreed 52 weeks. This invented arrangement illustrates coverage arithmetic; it does not settle a calendar-year cash total, a partial week or the terms of another salary agreement.
Count the actual scheduled payments in the relevant year and the work attached to each. A biweekly calendar can produce an extra payday in some calendar years. Wages paid during a tax year can also reflect work from a different service period. Do not force a year-to-date cash total to an annual salary label without understanding the compensation basis and dates.
For a midyear change, retain the agreed salary basis, amounts already paid, work already covered, remaining coverage and the approved calculation for any short period. Compare the proposed result with the agreement. If it differs, investigate the cause before changing a final paycheck merely to make a spreadsheet total match. A budget target does not authorize taking back earned wages.
Do not turn salary into an hourly rate by dividing by 2,080 without checking the arrangement. For salaried nonexempt workers, 29 CFR 778.113 connects the regular-rate calculation to the hours the salary is intended to compensate and addresses salaries covering longer periods. Obtain the approved weekly calculation rather than treating a frequency conversion as an overtime-method decision.
Have the reviewer sign off on an employee-level example before applying it to the population. Retain the source instruction and the explanation for the partial period so the next processor can reproduce it. A correct recurring salary amount does not prove that the one-off bridge amount is correct.
Rebuild each deduction from its own remaining instruction
A deduction can follow a coverage month, an annual election, a percentage of eligible compensation, a fixed amount per paycheck or a separate order. Changing frequency affects those instructions differently. Inventory them before allowing payroll to apply its default conversion.
For benefit premiums, distinguish actual payroll collection dates from the number of paydays. Some schedules exclude an extra check in a three-paycheck month. For other benefits, an election change, leave period or arrears arrangement may alter the amount still to collect. Ask the benefits owner to approve the remaining schedule instead of assuming that annual cost divided by new frequency is sufficient.
Consider a fictional approved collection target of $2,400, with $900 already collected. The responsible benefits reviewer confirms that $1,500 remains and that 16 future checks are eligible for collection. The planned amount is $93.75 on each of those checks. Dividing the original target by 26 produces about $92.31 and ignores both the history and the actual remaining calendar.
That example is a collection reconciliation, not a rule for every benefit or deduction. Health FSA administration, retirement contributions, garnishments, loan repayments and other arrangements require their own governing instructions. Preserve percentages, limits, priority rules and required approvals; do not convert everything into an equal fixed-dollar installment.
Use the approved remaining amount and eligible collection dates. The example does not determine a plan's legal or tax treatment.
Document how rounding will be handled when the remaining amount does not divide evenly. Name the person who approves any final adjustment and verify that the payroll system can implement it. Do not rely on an unexplained last-check correction, especially where a limit, employee authorization or external payment schedule constrains the deduction.
Finally, check the receiving side. A changed payroll collection schedule does not automatically change a carrier invoice, retirement remittance instruction or other downstream obligation. Finance and the administrator need to know what will arrive, for which period, and how a difference will be resolved.
Check withholding inputs and the first new preview
Set the correct new payroll period in the tax calculation and verify which payment first uses it. Review any short transition run with the processor under the applicable instructions; do not improvise a tax method because the gross amount resembles half of an ordinary payment.
Current IRS Publication 15-T distinguishes annual inputs on Form W-4 from the additional per-pay-period amount in Step 4(c). Preserve those meanings when configuring the change. An annual amount should not accidentally become a per-check deduction, and a per-check instruction should not silently become an annual target.
For example, $25 of additional withholding applied to 52 payments produces $1,300; applied to 26 payments, it produces $650. This is only arithmetic illustrating frequency, not a recommendation for an employee's withholding. Payroll should not double a submitted election on its own to preserve a guessed annual result. Give employees a clear route to review their elections using current IRS guidance or their own adviser.
Compare the first preview with the supported instructions: period, wages, withholding inputs, deduction dates and expected cash. Do not promise that unchanged annual salary means unchanged net pay per check. A larger covered interval, different deduction dates or a submitted election can explain a difference, but each needs to be traceable.
Ask a prospective payroll service to process the awkward first check, not just a normal pay cycle.
SelectSoftware Reviews can help you discuss payroll software choices. Bring the coverage map and deduction reconciliation, then ask providers to demonstrate their implementation and support scope for that specific change.
Use the Pay-Frequency Bridge Calendar and Reconciliation
Copy the following cards into a controlled document. Complete one set for each population with a different pay agreement or schedule. Keep personal bank details, full SSNs and employee tax forms in their approved systems; use secure references here.
The three payment cards use the same fields so you can compare their boundaries directly. The final section records the decisions that connect those payments. Dates without calculation support are not a completed bridge.
A. Last payment on the old schedule
1. Covered work: Inclusive start/end dates and final time or salary source: ______.
2. Payment timing: Scheduled payday, applicable wage deadline and funding/approval cutoffs: ______.
3. Wage result: Compensation basis, expected gross and employee-level comparison reference: ______.
4. Deduction instruction: Collection dates, applicable amounts or percentages and approval reference: ______.
5. Payment owner: Issuing system, authorized releaser and actual payment confirmation: ______.
B. First payment on the new schedule
6. Covered work: Inclusive start/end dates, including any short bridge interval: ______.
7. Payment timing: First new payday, applicable wage deadline and funding/approval cutoffs: ______.
8. Wage result: Approved calculation, expected gross and employee-level comparison reference: ______.
9. Deduction instruction: First new collection treatment and supporting approval: ______.
10. Payment owner: Issuing system, authorized releaser and actual payment confirmation: ______.
C. Following payment on the new schedule
11. Covered work: Inclusive start/end dates and relationship to the first new interval: ______.
12. Payment timing: Following payday, applicable wage deadline and funding/approval cutoffs: ______.
13. Wage result: Expected recurring calculation and comparison reference: ______.
14. Deduction instruction: Collection treatment and any planned rounding adjustment: ______.
15. Payment owner: Issuing system, authorized releaser and actual payment confirmation: ______.
D. Reconciliation and release
16. Wage coverage: Unpaid or duplicated work intervals, resolution and reviewer: ______.
17. Workweek check: Preserved weekly boundaries, complete hours and overtime review: ______.
18. Salary check: Pay agreement, history, remaining coverage and approved partial-period method: ______.
19. Collection check: Approved target or governing rule, collected amount and remaining eligible dates: ______.
20. Withholding check: New payroll period, employee instructions and first-preview result: ______.
21. Employee notice: Required review, issued version, affected audience and contact route: ______.
22. Contingency: Lawful response to a missed wage deadline, funding failure or material preview error: ______.
23. Final responsibility: Release decision, unresolved items, post-payment reviewer and review date: ______.
Coverage rule: Every earned interval must have a supported payment path. An open amount or legal-timing question needs a named owner before the affected deadline; a green calendar cell does not resolve it.
After-payday status: Replace scheduled with the actual payment result and retain the original expectation. Investigate a missing or returned payment before issuing a replacement that could pay the employee twice.
Tell employees what the first payments will cover
Show the last old payday and first two new paydays with the work periods attached. Explain the longer or shorter interval between payments plainly. Employees need enough information to distinguish a change in timing from a reduction in pay, an extra deduction or a missing payment.
Use a message suited to the employee group. An hourly employee needs to know which work dates and approved hours appear on each check. A salaried employee may need the approved explanation for a short period. An employee whose deductions change needs to know which first check uses the new collection schedule. Do not send everyone the same take-home estimate.
Describe any transition assistance only after its terms and payroll treatment are approved. An advance is different from wages already earned, and a repayment arrangement is different from a routine benefit deduction. Do not promise an automatic recovery from future wages without the appropriate review and authorization.
Provide a trusted question route before the gap occurs. Payroll can explain the dates and implemented instructions; individual tax advice or a disputed legal wage entitlement may need a different reviewer. Ask managers to route questions rather than inventing calculations or telling employees that the software decides the rule.
If a date changes after the first announcement, replace the notice deliberately. Identify the superseded version, tell the affected group what changed and update the bridge record. An old PDF and a new portal calendar can otherwise leave employees relying on different promises.
Close the bridge with employee-level comparisons
Rehearse the final old, first new and following new payments using the approved facts. Compare each employee's covered work, gross calculation and deductions before comparing the total funding requirement. Retain the reviewed register version so a later edit cannot replace the evidence of what was approved.
Include an interrupted case in the rehearsal. What happens if time arrives late, the provider cannot represent a short period, a salary calculation is disputed or funding cannot be released on the planned day? Name the authorized response while a lawful payment option remains available. A project milestone should not be the only place the wage deadline is recorded.
Choose a release decision from the evidence. Proceed when coverage is continuous, weekly calculations are preserved, salary and deduction instructions are approved, payment timing is lawful, funding is arranged and the employee message is accurate. Hold or change the affected route when a consequential item is unresolved. An unaffected group may have a separate decision; do not hide the boundary inside one project-wide approval.
After payment, match the actual result to the preview and bridge record. Check employee receipts or exception reports through the normal secure process, reconcile tax and deduction outputs, and investigate unexpected differences. The second new payment matters because an initial manual adjustment can be repeated accidentally by recurring configuration.
Keep the bridge until both new payments and their downstream records have been reviewed. Record what became the ordinary schedule and which temporary settings were removed. The useful endpoint is a reproducible payroll routine, with no unexplained work interval, deduction balance or transition adjustment waiting for someone to remember it.
Questions about the first new checks
Is biweekly the same as semimonthly?
No. Biweekly means every two weeks; semimonthly means twice each month. The covered dates, weekday pattern and ordinary number of payments differ. Use the actual calendar and approved pay terms, including any extra payday, rather than relying on the word bimonthly.
Can the first check be smaller?
It can cover a shorter approved interval, but the amount must follow the pay agreement and applicable rules. Explain exactly what work it covers and where the remaining work will be paid. A short check is not proof of an error, and calling it a bridge check does not excuse an underpayment.
Does changing frequency require a new payroll provider?
Not necessarily. Ask the current service to demonstrate the approved coverage, calculation, deduction and reporting requirements. If it cannot support the needed route, compare a different configuration or service with a concrete transition case. A new vendor is not itself a solution to an unresolved wage rule.
Can the change wait until January to make everything simpler?
A year boundary can make some reconciliations easier, but it does not remove notice, wage timing, weekly calculation, benefit or history requirements. Choose a boundary the business can support. Keep prior-year work and current-year payment dates distinct rather than assuming January starts every balance at zero.
If your approved bridge needs software or service support your current arrangement cannot provide, take the record to a payroll advisor.
SelectSoftware Reviews offers free payroll software matching help. Use the resulting options to ask providers who will own the transition checks and verify the first new payments.
Continue planning the payroll handoff:
About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.
