You can run payroll monthly to save on processing fees — unless your state says that's illegal. There is no federal law telling private employers how often to pay. Instead, every state sets its own minimum pay frequency, and the spread is enormous: some states demand weekly paychecks for certain workers, others are satisfied with once a month, and a handful set no minimum at all. If your schedule is less frequent than your state's floor, every single pay cycle is a separate violation, each carrying its own penalty.
This guide maps the federal baseline, the state-by-state landscape, the lag-time limits most owners miss, what late payment actually costs, and how to pick a schedule that keeps you compliant without wasting money on unnecessary payroll runs.
The Federal Baseline: The FLSA Sets No Pay Frequency
The Fair Labor Standards Act — the federal wage law — does not require weekly, biweekly, or any other pay frequency for most private employers. Its only timing rule is that wages must be paid when due, which generally means on the next regularly scheduled payday after the wages are earned. An employer can even change its regular payday for legitimate administrative reasons, as long as the change doesn't delay wages workers have already earned or become a tool for dodging overtime.
That silence is exactly what trips people up. "The feds don't care" gets misread as "nobody cares." In reality, Congress left frequency to the states, and the states very much care. The Department of Labor maintains a chart of state payday requirements precisely because the answer to "how often must I pay?" is different in all 50 states.
What States Actually Require: Four Buckets
State rules fall into four broad minimums — weekly, biweekly, semimonthly (twice a month), and monthly — with footnotes and occupation-specific twists that matter enormously.
Weekly-pay states and occupation rules
A cluster of states requires weekly payment, at least for some workers:
- New York requires for-profit employers to pay manual workers — people who spend a meaningful share of their time on physical labor — every week, unless the state labor department grants permission to pay less often. Office and clerical workers can be paid semimonthly. This rule generated a wave of class-action litigation after courts allowed workers to seek liquidated damages equal to the late-paid wages even when everyone was eventually paid in full; the legislature responded in the 2025 budget cycle by limiting those damages for employers that pay on a regular schedule at least semimonthly.
- Massachusetts requires weekly or biweekly payment, with limited exceptions.
- California and Michigan tie frequency to occupation rather than imposing one universal schedule, so the right answer depends on what each employee does.
The lesson: in these states, one company can lawfully owe different schedules to different employees. A restaurant paying servers and line cooks biweekly while paying its office manager semimonthly may already be out of compliance on the kitchen side.
Biweekly and semimonthly states
Most states land here. Typical formulations include:
- Iowa requires most employees to be paid on a regular payday at least biweekly, semimonthly, or monthly, with wages due no later than 12 days (excluding Sundays and legal holidays) after the end of the period in which they were earned.
- New Hampshire requires weekly or biweekly payment; semimonthly or monthly schedules need written permission from the state labor department.
- Montana presumes a semimonthly pay period when the employer hasn't established one.
Monthly-pay states
A monthly schedule — 12 payroll runs a year, the cheapest option — is legal in some states but not most. North Carolina, for example, expressly permits daily, weekly, biweekly, semimonthly, or monthly periods. If monthly payroll is your plan, confirm your state is on this list before you commit; in a weekly-pay state, a monthly schedule isn't a cost saver, it's a violation factory.
States with no private-sector minimum
A few states set no minimum payday for private-sector workers — Florida is the frequently cited example (its monthly-pay rule covers state employees, not private business). Nebraska effectively leaves the payday to whatever the employer designates. "No minimum" doesn't mean "no rules": you still must pay on the schedule you promise, final-paycheck deadlines still apply, and wage-theft and contract claims still exist. It just means the frequency floor isn't the trap — the promises you make are.
The Lag-Time Trap: Payday Isn't Just About Frequency
Frequency is only half the rule. Many states also cap the gap between the end of the pay period and the paycheck — the lag time.
California's version is the most detailed and the most punishing to misunderstand. Under Labor Code section 204, wages earned from the 1st through the 15th of the month must be paid by the 26th, and wages earned from the 16th through month-end must be paid within about ten days after the period closes. Weekly and biweekly payrolls generally must be paid within seven days after the period ends, with overtime allowed a slightly longer runway. Iowa, as noted, allows up to 12 days excluding Sundays and holidays.
Why this matters: an employer can have a perfectly legal semimonthly frequency and still violate the law by running payroll three weeks in arrears. When you set up payroll software, configure both the frequency and the lag — and test the first two cycles against your state's deadline, not just against whether the math looks right.
What Late or Infrequent Pay Actually Costs
Penalties stack per employee, per pay period, which is how a "small" scheduling error becomes a five- or six-figure problem.
- California fines $100 per employee for an initial failure to pay on time and $200 per employee plus 25% of the unlawfully withheld wages for subsequent or willful violations — and that's before back pay, interest, attorney's fees, and court costs. A separate waiting-time penalty applies to late final paychecks: a full day's wages for every day the check is late, up to 30 days.
- New York spent years as the cautionary tale in the other direction: technical frequency violations alone supported damages of 100% of the wages, producing large settlements even where workers lost no pay. The 2025 amendment reins that in for employers paying at least semimonthly, but the weekly-pay obligation for manual workers remains on the books.
Two practical takeaways. First, ignorance of your state's rule is the most expensive kind — the penalties accrue automatically, pay period after pay period, whether or not any employee complains. Second, when states reform these laws, they narrow the damages, not the duty: compliance is still cheaper than the lawsuit about whether you had to comply.
Choosing (or Changing) Your Schedule Without Regret
If your state gives you a choice, pick the frequency deliberately rather than inheriting whatever your first payroll provider defaulted to.
Count the runs. Weekly means 52 payrolls a year; biweekly means 26; semimonthly means 24; monthly means 12. If your provider charges per run, moving from weekly to biweekly roughly halves processing fees. For a small hourly workforce, though, weekly pay is a recruiting advantage — many hourly workers strongly prefer it — so price the morale effect alongside the processing bill.
Remember overtime is untouched by frequency. Overtime is computed workweek by workweek under federal law no matter how often you pay. Switching from weekly to semimonthly changes when overtime is paid, never whether it's owed, and you may not time a switch to push overtime into a cheaper period.
Changing schedules is allowed — delaying wages is not. You can move from weekly to biweekly, run different frequencies for different employee groups where the law allows, and align paydays with your cash-flow cycle. What you cannot do is change schedules repeatedly, use a change to hold wages longer, or let the transition pay anyone later than the old schedule would have. Document the change in writing, tell employees before it takes effect, and audit the first full cycle under the new schedule for both frequency and lag-time compliance.
Watch multi-state creep. The moment you hire someone in a second state — even one remote worker — you inherit that state's floor, lag limit, and notice rules for that employee. Remote hiring quietly turns a single-schedule company into a multi-schedule one. Before extending an offer across state lines, look up that state's payday rule the same way you'd check its withholding registration.
Common Mistakes That Trigger Violations
- Assuming one schedule fits everywhere. The New York manual-worker rule and California's occupation-based scheme punish uniform national payrolls.
- Paying monthly because the software allows it. Your provider permits any frequency; your state may not.
- Forgetting lag time. Legal frequency plus a three-week processing delay still equals late wages.
- Misclassifying who counts as what. Calling kitchen staff or warehouse crew something office-like on paper doesn't change which rule covers them; duties control, not titles.
- Leaving the schedule undocumented. If no pay period is established, some states impose a default (Montana presumes semimonthly). Put the schedule in offer letters and the handbook so the default never applies by accident.
Keep Payroll Visible in Your Books
Pay frequency isn't just a compliance setting — it shapes your cash flow. Weekly payroll means money leaves the account 52 times a year in smaller pulses; monthly means 12 large ones. Whichever you choose, your books should make the pattern visible rather than burying it.
Run payroll through a dedicated clearing account so each pay run — gross wages, withheld taxes, employer taxes, benefits — reconciles as one unit, and reconcile that account every cycle, not at quarter-end. Tag per-run processing fees separately from wages so you can see exactly what a frequency change saves. When payday timing shifts cash needs (a biweekly schedule produces two three-paycheck months a year; semimonthly never does), forecast those months explicitly instead of discovering them in the checking balance. Clean per-cycle records also make penalty exposure calculable: if a schedule question ever arises, you'll know precisely which periods and employees are involved instead of reconstructing them under pressure.
Good payroll software handles the calculations, but the schedule itself is a management decision with legal and cash-flow consequences. Review it once a year — or every time you hire in a new state — against the current state chart rather than assuming last year's answer still holds.
Simplify Your Financial Management
Once your pay schedule is compliant, keeping the resulting cash-flow rhythm visible month after month is what separates calm operators from surprised ones. Beancount.io offers plain-text accounting that's transparent, version-controlled, and AI-ready, so every payroll run, tax payment, and processing fee stays queryable in your own ledger. Get started for free and see why developers and finance professionals are switching to plain-text accounting.