How Does Weekly Payroll Work? (w/Examples) + FAQs

Weekly payroll means paying employees every seven days, for 52 paychecks a year instead of 26 or 24. The Fair Labor Standards Act sets wage and overtime rules. It leaves ordinary pay frequency to state law. The Copeland Act forces weekly certified payroll, but only on certain federal construction contracts.

The choice matters most to hourly and lower-income workers. They plan rent and bills around each check. It also matters to small businesses weighing faster employee cash flow against the cost of extra payroll runs. Employers who misjudge their state's rules, delay a payday, or miscalculate overtime risk wage claims and lost trust.

This article reflects federal payroll rules as of July 2026. Wage law changes over time and varies by state. Confirm current figures and your own state's rules before you change a real pay schedule. This explains the mechanics in plain terms, but loop in your accountant or an employment attorney before you act on your own specific case.

How Weekly Payroll Works in Practice

Weekly payroll is a pay schedule where an employer closes the books on hours and wages every single week. The employer then pays workers on a fixed day soon after. A worker earning $20 an hour for a standard 40-hour week gets that check within days, not weeks later. Employers on this schedule run payroll 52 times a year, versus 26 for biweekly, 24 for semimonthly, and 12 for monthly.

The idea is simple, but the workload is not. Each weekly run repeats the same steps: collect time records, calculate gross pay and overtime, apply tax withholding, then move net pay into employee accounts. Doing that 52 times a year, instead of 12 or 24, multiplies the fees, the staff hours, and the chance of a mistake. A provider that bills per run makes this cost obvious fast, since a weekly cadence can run close to double what semimonthly costs.

Weekly pay is common in industries with lots of hourly or tipped work, including restaurants, retail, and construction. Workers in these jobs often have thin savings. A shorter gap between work and pay helps them avoid a missed bill or a costly loan. Salaried, exempt staff rarely see weekly pay, since their pay doesn't change week to week and a longer cycle costs less to run.

Running payroll weekly also leaves little buffer to catch a timekeeping error before the deposit goes out. A biweekly or monthly employer has extra days to review a stray punch before money moves. A weekly employer often has only a day or two between the workweek's close and payday, so accurate time tracking matters even more. Many weekly employers use automated time-clock software to keep that tight turnaround from becoming a source of mistakes.

Staffing agencies often lean on weekly pay for a competitive reason, not a legal one. Temp workers can usually choose among several agencies for the same shift, and the agency offering faster pay often wins the placement. That business pressure, not a state mandate, is why weekly pay is so common in staffing and gig-adjacent work even outside states that require it.

The Federal Baseline: What the FLSA Requires

No federal law tells a private employer how often to pay staff. The Fair Labor Standards Act sets the federal minimum wage at $7.25 an hour, effective July 24, 2009. It also requires overtime pay of 1.5 times an employee's regular rate after 40 hours in one workweek. A workweek, under the law, is a fixed, repeating block of 168 hours, seven straight 24-hour days, and every overtime calculation uses that one window.

Where the FLSA does mention timing, it stays vague. Wages are due "on the regular payday for the pay period covered," says the Department of Labor's wage guide. That line tells an employer to be prompt, but names no specific interval.

New owners often assume some federal rule forces a biweekly or semimonthly cycle. It doesn't. The choice belongs to the employer, on top of whatever the state requires.

One real exception proves the rule. Under the Copeland Act and the Davis-Bacon Act, contractors on federal construction contracts must file a certified weekly payroll using Form WH-347 or an equivalent. It lists every worker's hours, wage rate, and deductions for that single week. A private employer with no government contract answers only to its state's rule, not this one.

Missing a certified payroll deadline on a covered contract can hold up payment on the whole project. It can also trigger a Department of Labor review. Someone who has only worked on government contracts may wrongly assume weekly certified reporting is a universal federal standard. It isn't: it applies to one narrow slice of construction work, and everyone else starts from the state layer described next.

The minimum wage figure matters here too, since every overtime and worked-example calculation later in this article starts from an hourly rate. Many states and cities set their own minimum wage well above the $7.25 federal floor, and an employer always owes the higher of the two rates. A payroll system built only around the federal number, without checking the local one, will underpay every affected worker on every single check.

Does Your State Require Weekly Pay?

Federal law stays silent on ordinary pay frequency, so states fill the gap. They do not agree with each other. Some set a floor of "at least twice a month." Others carve out weekly pay for specific kinds of workers, while a few leave employers mostly free to pick their own schedule.

Treat this as the single most important legal fact in this topic: never assume your state matches the federal approach. Never assume it matches a state you've worked in before, either. The three examples below show how differently states can treat the same question.

New York is the clearest case of a true weekly mandate. State law requires manual workers, people whose job is mostly physical labor, to be paid weekly. Clerical and other workers must be paid at least twice a month. An employer that wants to pay manual workers less often than weekly must first apply to the state for permission, or risk a wage claim on every late payday.

California takes the opposite approach: it sets a floor, not a weekly mandate. Under Labor Code Section 207, wages must be paid at least twice each calendar month, on regular paydays set in advance. The law ties the payment date to which half of the month the work fell in. An employer can still choose weekly pay in California, and many hourly and construction firms do, but the law itself only forces semimonthly at minimum.

Connecticut leans toward more frequent pay for most employers by default, though the exact rule depends on the type of work and any exception the state has approved. Confirm the current rule directly with the state's wage division rather than assume a number. The safest process, in any state, is to check its labor agency directly before you set or change a schedule. A wrong guess here is a legal error, not a formatting one.

Which Situation Applies to You?

Whether weekly pay is required, optional, or the wrong fit depends on where you operate, who you employ, and what contracts you hold. The three situations below cover most real businesses. Read the one that matches your setup, since the right first move differs across all three.

If You Operate in a State With Its Own Pay-Frequency Rule

Start by sorting your workers into the categories your state uses. One state can treat manual and clerical staff differently under the same law. A landscaping company with both grounds crews and office staff in New York may need to pay the crews weekly, while office staff stay on semimonthly pay. Confirm each classification with your state labor department or an employment attorney before you assume one schedule fits your whole payroll.

Guessing wrong here means back pay and penalties, not only an awkward fix later. A single misclassified worker can trigger a wage claim that reaches back months. The state calculates the shortfall from the date the wrong schedule began. Fix the classification once, in writing, and review it again any time a worker's duties change.

If Your Team Spans Multiple States

A remote-first company with staff in five or six states faces a harder problem. Each state's rule applies to the workers physically in that state, not to the company as a whole. Running one single frequency company-wide is simpler to manage, but it only works if you pick a cadence that satisfies the strictest state you operate in, often weekly or semimonthly rather than monthly.

Many multi-state employers standardize on biweekly, then add a weekly carve-out for any state, like New York, that legally demands it. A company with hourly workers in both New York and Texas might run biweekly payroll company-wide, but carve out a weekly cycle only for its New York manual workers. That keeps one system for most of the business while still meeting the one state's real mandate.

If You Hold a Federal Construction Contract

A contractor on a Davis-Bacon-covered federal job has the least freedom of anyone in this article. Certified weekly payroll is mandatory, no matter what state law would otherwise allow. This holds even in a state like California, where ordinary state law would only require semimonthly pay, because the federal contract clause overrides that state floor. Build your systems to produce a compliant weekly report from day one.

This rule applies project by project, not company-wide. A contractor can run ordinary biweekly payroll for its office staff, while filing certified weekly payroll only for the crew on the covered contract. Missing even one week's certification can delay a progress payment on the entire job, which makes the paperwork a cash-flow issue, not only a compliance one.

Worked Example: Calculating a Weekly Paycheck

Seeing the math is the clearest path to understanding weekly payroll. Walk through one real employee's check, from hours worked to money in the bank. Assume Marcus is an hourly, nonexempt warehouse worker earning $19 an hour. He clocks 46 hours in one workweek, 6 hours past the 40-hour overtime line, and his employer pays him weekly every Friday.

Start with straight-time pay: 40 regular hours times $19 equals $760. Overtime pays 1.5 times the regular rate, so $19 times 1.5 equals $28.50 an hour, and 6 hours at that rate equals $171. Add the two amounts and Marcus's gross pay for the week is $931, a number his employer must be able to reproduce for any audit or wage dispute. The table below breaks that same week down from gross pay to the deposit that lands in his account.

Federal income tax withholding varies by worker, since it depends on the W-4 each employee filed. Employers calculate it using the IRS withholding tables in Publication 15, so the $84 figure above is an illustration, not a fixed rate. Social Security and Medicare, by contrast, are flat statutory rates: 6.2% and 1.45% of gross wages, the same in every state. Any state or local income tax would add one more line to this table, without changing the federal math above it.

This same math repeats every week under a weekly schedule. That is exactly why the FLSA's single-workweek rule matters here: each week's 40-hour line resets on its own. A slow 30-hour week followed by a busy 50-hour week still owes 10 hours of overtime for that second week, never averaged down. A biweekly or semimonthly employer runs this same per-week math internally, but waits to cut a check until the longer period ends, which confuses workers who expect overtime over the whole pay period.

Payroll Lessons: Three Decisions That Changed the Outcome

Three real payroll situations show how weekly pay decisions go wrong in different ways. Each one teaches a different lesson, not a repeat of the last. Together they cover a math error, a cost surprise, and a legal-timing mistake.

Maria's Overtime Miscalculation

Maria manages a diner that pays kitchen and counter staff weekly. Her payroll clerk started adding hours across two adjoining weeks whenever a shift spilled from Saturday into Sunday, then dividing by two for an "average" week. That method undercounted overtime for anyone whose hours were front-loaded into the first week, since the FLSA measures each workweek on its own. The table below shows the gap this created for one cook across two real weeks.

The correct method owed the cook 6 hours of overtime pay in week one. The averaged method owed none at all, a shortfall that would repeat for every high-week, low-week pair. The mistake was common: treating the workweek as a flexible bucket, rather than a fixed window the employer sets once and can't shift later. Once Maria's accountant caught the pattern, the diner owed back pay for every affected period, far more than the few minutes correct math would have taken.

Devon's Frequency Switch

Devon owns a five-person landscaping crew. He switched from monthly to weekly pay after two employees said a once-a-month check was hard to stretch. The switch solved the cash-flow complaint fast, but Devon hadn't priced out the added cost, since his payroll service billed per run, not per employee. Running payroll 52 times a year instead of 12 more than quadrupled his processing charges, a stacking cost that ate into a thin crew's margin.

Devon's mistake was assuming happier, more frequently paid staff was worth any price. His accountant helped him land on biweekly instead. It cut the wait for pay nearly in half compared with monthly, while keeping the annual bill under $1,000. The lesson reaches past landscaping: a pay-frequency change is a real cost decision, worth the same scrutiny as any other recurring expense.

Priya's Final-Paycheck Deadline

Priya runs HR for a startup with remote staff in four states. Everyone was paid biweekly, except a small group of manual workers in New York, paid weekly to satisfy that state's rule. When a New York warehouse worker was fired on a Tuesday, Priya scheduled his final check for the next regular weekly payday, five days later. New York law treats a firing differently from a routine pay cycle: it requires the final check by the next regular payday at the latest, a rule that happened to fit her weekly schedule.

Priya's mistake was assuming every state's final-pay rule mirrors its regular-payday rule. Several states instead require immediate or next-day payment after a termination, no matter the normal cadence. After that close call, she built a state-by-state final-pay chart into her offboarding checklist. The fix cost an afternoon of research; skipping it could have cost a wage claim and a state penalty.

Weekly Pay vs. Other Pay Frequencies

Choosing a pay frequency trades employee cash-flow benefits against employer processing costs. The right answer changes with your workforce and your state's floor. Weekly pay gets money to workers fastest, and it lines up cleanly with the FLSA's single-workweek overtime rule, since no multi-week period needs matching up before the check goes out.

That clarity has a real cost: 52 processing cycles a year runs roughly double the effort of semimonthly, and the gap shows up directly in a payroll provider's invoice. A business weighing the switch should price out its own provider's per-run fee before deciding, rather than assume the convenience is free. The figure below lines up all four schedules side by side, so the trade-off is easy to scan at a glance.

Biweekly pay is the most common private-sector schedule in the United States, and it splits the difference well. Employees get a check every other Friday, while the employer's annual run count drops from 52 to 26. Its one real complication is that 26 pay periods don't divide evenly into 12 months. Two months a year get three paychecks instead of two, which can confuse budgeting if nobody plans for it.

Semimonthly pay always produces exactly 24 periods and two checks a month, which simplifies monthly budgeting. It complicates overtime math, though, since a semimonthly period rarely lines up with the FLSA's fixed workweek. Payroll systems have to split the overtime math across the two workweeks inside each semimonthly period, rather than treating the period as one block.

Monthly pay is the rarest of the four. It mostly appears for salaried, exempt staff whose pay doesn't move with hours worked. It costs the least to run, at only 12 cycles a year, but it is the hardest schedule for a lower-income hourly worker to live on. That is exactly why few states allow monthly pay for hourly staff without an exception on file.

No single frequency wins in the abstract, since the right fit depends on your workforce, not on habit. Match your state's legal floor and your workforce's pay type first. Then weigh how much processing cost your business can absorb. A small team of salaried staff can often afford monthly pay, while a shop full of hourly workers rarely can.

Mistakes to Avoid

• Averaging hours across two weeks to calculate overtime, instead of applying the 40-hour line to each single workweek, which shorts employees who front-load their hours.
• Assuming federal law sets a weekly, biweekly, or any other specific pay frequency, when the FLSA leaves that choice to state law and employer policy.
• Switching an existing team's pay frequency without the written notice some states require, turning an operational change into a wage-notice violation.
• Miscalculating a new hire's first paycheck, by paying for the wrong period or failing to prorate a partial first week correctly.
• Missing a state's final-paycheck deadline after a firing, since several states require immediate or next-business-day payment regardless of the normal payday.
• Skipping certified weekly payroll paperwork on a federal construction contract, which can freeze payment on the entire project.
• Letting a bank holiday quietly push a payday later without telling employees in advance, which creates avoidable calls to HR.
• Deducting cash shortages, uniforms, or tools from wages so pay drops below minimum wage, or so it cuts into required overtime pay.
• Moving salaried, exempt staff onto a weekly cycle to "keep things simple," which adds real cost with no legal rule driving the change.

Do's and Don'ts of Running Weekly Payroll

Do

• Put your pay frequency and specific payday in writing, in the employee handbook and every offer letter, so no one has to guess when money arrives.
• Confirm your state's minimum pay-frequency and final-pay rules before you set or change a schedule, since assumptions here carry legal risk.
• Build a full year's payroll calendar in advance, marking every bank holiday that will push a payday earlier.
• Reconcile time cards against the workweek before every run, catching a missed clock-in while it's still cheap to fix.
• Keep certified payroll records for at least three years on any federal construction contract, since audits can reach back that far.
• Give employees written notice before any pay-frequency change takes effect, matching whatever lead time your state requires.

Don't

• Don't assume federal law sets your pay frequency; the FLSA leaves that decision to your state.
• Don't average hours across two workweeks when calculating overtime for a weekly or near-weekly schedule.
• Don't change an existing employee's pay frequency without the written notice some states require.
• Don't let a bank holiday silently delay a payday without telling staff ahead of time.
• Don't classify a worker as exempt purely to avoid the cost of processing their pay weekly.
• Don't ignore a state's final-pay deadline simply because it differs from your normal payday.

Pros and Cons of Weekly Payroll

Pros

• Faster cash flow for hourly and lower-income workers who plan bills around each check.
• Overtime lines up cleanly with the FLSA's single fixed workweek, with no multi-week period to reconcile.
• A smaller per-check amount makes any single payroll mistake cheaper to catch and fix quickly.
• Can reduce turnover among hourly staff who specifically value more frequent pay.
• Easier to fix a payroll error fast, since only one week of wages is ever at stake.

Cons

• Running payroll 52 times a year costs more in provider fees and staff time than a longer cycle.
• More frequent bank transfers can mean more per-transaction banking fees over a year.
• Harder to justify for salaried, exempt staff whose pay doesn't change from week to week.
• More paydays create more chances for a compliance mistake, like a mistimed deduction or a missed overtime calculation.
• Complicates payroll consistency across a multi-state team, if different offices land on different frequencies.

What to Do Next

1. Pull your specific state's pay-frequency and final-pay rules from its labor department before you set or change any schedule.
2. Decide your pay cadence and put it in writing, in the employee handbook and every offer letter.
3. Build a 12-month payroll calendar that flags bank holidays and adjusts each affected payday in advance.
4. Confirm your payroll software or provider correctly applies the FLSA's single-workweek overtime rule, not a multi-week average.
5. Gather W-4s, state withholding forms, and direct-deposit authorizations before your first weekly run.
6. Loop in your accountant or payroll provider if you run multi-state payroll, or certified payroll on a federal contract.
7. Consult an employment attorney before you change an existing team's pay frequency, since some states require advance written notice.

Frequently Asked Questions

Is weekly payroll legally required?

No, not for most employers. Federal law sets no pay-frequency mandate, but some states, including New York for manual workers, do require weekly pay for specific worker categories as of 2026.

How many paychecks does an employee get on weekly pay?

Fifty-two paychecks a year, one for each week, compared with 26 for biweekly, 24 for semimonthly, and 12 for monthly pay.

Does weekly payroll cost more to run than biweekly?

Yes. Running payroll 52 times a year roughly doubles the per-run provider fees and staff hours of a 26-run biweekly schedule, even though total wages paid stay the same.

Can an employer switch from biweekly to weekly payroll?

Yes, an employer can generally switch, but several states require written notice before the change takes effect, so confirm your state's rule before you announce a new schedule.

How is overtime calculated under weekly pay?

By the single workweek. The FLSA requires 1.5 times the regular rate for hours over 40 in that one fixed week, never averaged with any other week.

Do salaried employees get paid weekly too?

Rarely. Weekly pay concentrates among hourly, tipped, and lower-wage workers. Salaried exempt staff are usually paid biweekly, semimonthly, or monthly, since their pay doesn't vary by hours.

What happens to my first paycheck when I'm hired mid-week?

It's prorated. A new hire's first check typically covers only the days worked in that partial week, at the same hourly or salaried rate as a full week.

Is my last paycheck due immediately after I quit or get fired?

It depends on your state. Some states require immediate or next-business-day payment after an involuntary termination, while others allow payment on the next regular payday.

Do independent contractors get paid on a weekly payroll schedule?

No, not through payroll at all. Contractors are paid under the terms of their contract, not an employer's payroll cycle, and they receive a 1099 rather than a W-2.

Which states require weekly pay?

It varies. New York requires weekly pay for manual workers specifically, while most other states set only a minimum frequency, such as semimonthly, so check your own state's labor department directly.

Does a bank holiday delay a weekly payday?

Often, yes. A payday that lands on a bank holiday typically moves to the closest prior business day, and employers should tell staff about that shift in advance.

How does weekly pay affect year-end tax reporting?

It doesn't change the total. A W-2 reports total annual wages and withholding regardless of pay frequency, so weekly pay means more pay stubs, but the same year-end tax paperwork.