Washington pay frequency: monthly minimum. Established payday is the rule.
Washington requires employers to pay at least monthly (RCW 49.48.010). Most employers run more frequent cycles — biweekly or semi-monthly are most common — and once a payday is established, it must be honored consistently. Late wages, even by a few days, can trigger L&I administrative action plus civil penalties; willful refusal to pay can result in double damages under RCW 49.52.070. The monthly minimum is the floor; consistency and timeliness on the chosen schedule are what get enforced.
Pay Frequency Configuration
Enforces monthly minimum cadence; tracks established paydays for consistency; surfaces late-payment exposure in real time.
What those rules do as Washington payroll runs.
The hero card configuration: Flag on payday timing, Avoid on cadence change mid-period, Block on below-monthly.
When the configured payday approaches and payroll hasn't closed, Teambridge surfaces the timing risk: "Payday in 24 hours — 12 timesheets pending approval."
When an admin attempts to change pay frequency mid-pay-period, Teambridge surfaces an Avoid indicator. Cadence changes should align to pay-period boundaries.
Washington requires monthly minimum cadence. Configuration that would result in less frequent payment than monthly fails to save.
Deploy WA pay frequency in your Teambridge.
Tell us about your Washington pay schedule. We'll spin up cadence enforcement and 27 other Washington policies in a sandbox tenant.
Monthly minimum, but established payday is what gets enforced.
Washington's monthly-minimum rule is rarely the binding constraint — most employers pay more frequently. The harder constraint is the consistency requirement: established paydays must be honored.
Monthly minimum statutory floor
Washington requires employers to pay wages at least once per month — the lowest acceptable cadence. Weekly, biweekly, semi-monthly are all permissible. Most Washington employers run biweekly because it satisfies most state minimums (including more restrictive states like Illinois) and fits standard payroll cycles.
Notice of payday at hire
Employers must give workers notice of the regular payday and the place/time of payment at the time of hiring. Once established, the payday cannot be changed without proper notice. Mid-period cadence changes can trigger L&I enforcement.
Teambridge enforces the cadence consistently.
The monthly minimum is rarely the binding rule. The practical enforcement is around timely payroll close on the established payday.
Set at employer onboarding.
When a Washington employer is configured, pay frequency is set per worker classification. Hourly workers commonly get biweekly; salaried often get semi-monthly. Below-monthly cadences are blocked at config save.
Established date is the deadline.
Once a payday is set, Teambridge enforces it. Pay runs schedule against the payday; late runs surface as Flag indicators with WA willful-refusal exposure context.
Boundary-aligned only.
If an operator wants to change cadence (e.g., biweekly to semi-monthly), the change is gated to align with pay-period boundaries with proper worker notice (typically 30+ days).
Wage statement issued each payday.
Every payday triggers a wage statement (paystub) for each worker — see the wage-statement-requirements policy for required content.
Still evaluating? Get a free Washington compliance audit.
Send us your existing Washington scheduling and pay configuration. Our compliance team returns a written audit within 5 business days — every Washington-specific exposure ranked by risk and back-pay liability.