Oregon Expands Wage Statement Rules Effective Jan. 2026

If you’ve ever stared at a paycheck stub like it’s a cryptic treasure mapmysterious codes, deductions with vague labels,
and a “NET PAY” number that feels both comforting and suspiciousOregon has heard your confused sigh.
Starting January 1, 2026, Oregon expands its wage statement rules in a very practical way:
employers must explain paystub earnings and deduction codes in writing at the time of hire.
Think of it as giving employees the “legend” to the payroll map, so “MED,” “401K,” “SFTDIF,” and “OR-PFML”
don’t look like secret agent abbreviations.

This updatedriven by SB 906doesn’t replace Oregon’s existing itemized wage statement requirements.
Instead, it adds a new plain-language disclosure step to help employees understand what those pay statements mean.
And yes, there’s an annual update requirement too, because payroll practices have a habit of evolving like houseplants:
quietly, continuously, and sometimes dramatically when you least expect it.

What Oregon Already Required: Itemized Wage Statements (The “Paystub Basics”)

Oregon employers have long been required to provide itemized wage statements (pay stubs) on regular paydays
and whenever wages, salary, or commissions are paid. In plain terms: if you pay someone, you generally must
show your work.

What typically must appear on an Oregon pay stub

Oregon’s wage statement rules require enough detail to show the “what,” “when,” and “why” behind a paycheck.
Common required items include the payment date, the work period covered, pay rate(s), gross and net wages, and
itemized deductions with their purposes. Additional details apply for non-exempt employees (regular and overtime hours/pay),
and for piece-rate workers (piece rate(s), number of pieces, and totals by rate).

If your payroll system already generates compliant stubs, you’re not starting from scratch.
But starting in 2026, Oregon wants employers to do something extra: provide the translation guide.

What Changes on Jan. 1, 2026: The New “Explain the Paystub” Requirement

Effective January 1, 2026, Oregon SB 906 expands wage statement compliance by requiring employers
to provide employees, at the time of hire, a written explanation of earnings and deductions shown on
itemized wage statements. This is often described as a “new-hire wage statement notice” or “paystub transparency notice.”

The goal is simple: employees should be able to look at a pay stub and understand what each earnings type,
deduction, contribution, and payroll code meanswithout needing a decoder ring or a minor in accounting.

Who needs to comply?

• Most Oregon employers with employees working in Oregon (with typical statutory exceptions such as the federal government and its agencies).
• New hires (employees at time of hire) starting on or after the effective date should receive the notice as part of onboarding.

When does the notice have to be provided?

• At the time of hire (build it into your onboarding checklist, right next to “I-9” and “Where’s the coffee?”).
• Reviewed and updated by January 1 of each year to reflect changes in pay practices, benefits, or payroll codes.

What the Written Explanation Must Include

SB 906 isn’t asking for a novel. It’s asking for clarity.
Oregon BOLI guidance emphasizes that the explanation should cover the key building blocks of earnings and deductions
that appear on itemized wage statements, including the codes used in payroll systems.

Required content (plain-English checklist)

1. Your established regular pay period
   Example: “Biweekly (every other Friday)” or “Twice monthly (15th and last day of the month).”
2. A comprehensive list of all pay rates employees may be eligible for
   Examples: hourly, salary, overtime, shift differential, piece-rate pay, commission-based pay, on-call pay, bonus pay.
3. All benefit deductions and contributions
   Examples: medical premiums, dental/vision, HSA/FSA, retirement contributions, employer match displayed on the stub.
4. Every type of deduction that may apply
   Examples: taxes, garnishments, union dues, repayment deductions (when lawful), benefit premiums, voluntary programs.
5. The purpose of deductions that may be made during a regular pay period
   The “why” behind each deduction category, in words a normal human uses.
6. Any allowances claimed as part of minimum wage
   If your business uses allowable credits (where applicable), the notice should explain them clearly.
7. Employer-provided benefits that may appear on the paystub as contributions/deductions
   Example: employer-paid benefits shown for informational purposes.
8. All payroll codes used for pay rates and deductions, with a detailed description/definition
   This is the big onethe “legend” for the map.

Good news: the law doesn’t require perfect grammar or full sentences for every item.
It’s fine to format the notice like a clear list, glossary, or table-style guideas long as it’s
sufficiently detailed to explain what employees will see on their wage statements.

Delivery Options: How Employers Can Provide the Notice

Oregon allows flexibility in how employers deliver the written explanation, as long as the information
is available in a location that’s easily accessible to employees. This is helpful for employers who
already run digital onboarding or use an HRIS.

Common compliant delivery methods

• Paper handout during onboarding (the classic “Here’s your folder” approach).
• Email or electronic document (PDF, HR portal document, or onboarding packet).
• Link to a company intranet or server where the notice lives (make sure access is simple and stable).
• Physical posting in a conspicuous workplace location (works best when paired with a digital option for remote staff).
• Employee handbook inclusion if it’s truly accessible and updated annually.

The practical takeaway: you don’t need a custom notice per employee in most cases.
You need a company-specific explanation that covers the pay rates, deductions, and codes your payroll system uses
and you need to reliably make it available to employees at hire.

Practical Examples: What This Looks Like in Real Payroll

Let’s turn “compliance requirement” into something you can visualize.
Below are examples of how employers might translate payroll items into the kind of language that prevents confusion,
reduces disputes, and makes HR teams slightly less likely to develop eye twitches during payday.

Example 1: Earnings codes

• REG Regular hours worked at your standard hourly rate.
• OT Overtime hours worked at the overtime rate.
• SFTDIF Shift differential pay (extra pay for working certain shifts).
• BON Bonus pay (one-time additional compensation).
• COM Commission (performance-based pay tied to sales or other metrics).

Example 2: Deduction and contribution codes

• FIT Federal income tax withholding (required by law).
• SIT State income tax withholding (required by law, when applicable).
• MED Employee share of medical insurance premium.
• 401K Employee retirement contribution to a 401(k) plan (if elected).
• 401K-M Employer match contribution (often shown for informational purposes).
• GARN Wage garnishment (withholding required by a legal order).

Your actual code list may be longersometimes much longer. The key is to describe each code so employees can connect:
“This code on the stub” → “This is what it means” → “This is why it exists.”

Annual Update Requirement: Why It Matters More Than You Think

SB 906 requires employers to review and update the written explanation by January 1 of each year.
This is not just a calendar choreit’s your chance to keep the “paystub legend” in sync with reality.

Typical triggers for updating the notice

• New benefit plans or premium changes (hello, open enrollment).
• New payroll codes introduced by a payroll vendor update.
• Changes to deductions (new voluntary programs, updated garnishment handling, etc.).
• New pay types (shift differential added, new bonus structures, commission plan tweaks).
• Minimum wage changes that affect how certain wage items are presented.

If you treat the notice like a living document, the annual update becomes straightforward.
If you treat it like a “set it and forget it” poster from 2014… well, that’s how compliance gremlins are born.

Penalties and Enforcement: What’s at Stake?

Oregon’s wage statement rules are enforced through the state’s labor agency framework.
SB 906 authorizes civil penalties (often discussed as up to $500) for violations related to these requirements.
While the notice requirement is not the flashiest employment law change of 2026, it is the kind that can create
avoidable risk if employers skip it, misunderstand it, or implement it inconsistently.

The smarter strategy is to build the notice into onboarding, keep it accessible, and update it annuallythen
your compliance approach becomes repeatable instead of reactive.

Compliance Game Plan: A Simple 7-Step Checklist

1. Inventory your pay types (hourly, salary, overtime, differentials, bonuses, commissions, piece-rate).
2. Inventory deductions and contributions (taxes, benefits, retirement, garnishments, voluntary programs).
3. Export your payroll codes from your payroll provider (earnings codes + deduction codes + contribution codes).
4. Write clear definitions for each code (avoid jargon where possible).
5. Choose a delivery method (paper, email/PDF, HR portal, intranet link, posting, handbookideally with a digital backup).
6. Train the onboarding team so the notice isn’t “forgotten” during busy hiring stretches.
7. Schedule an annual review in Q4 so you’re updated by January 1 without a last-minute scramble.

Common Mistakes to Avoid (Because Payroll Already Has Enough Drama)

• Using generic templates without customization: A template is a starting point, not a finish line.
• Forgetting payroll codes: SB 906 is especially focused on code explanationsdon’t bury the lede.
• Posting the notice somewhere “accessible” that no one can actually access: If employees need three passwords and a quest map, it’s not accessible.
• Skipping the annual update: Outdated notices create confusion and can undermine trust.
• Overcomplicating the language: The point is to explain, not to impress.

So… Is This Actually Helpful? Yes (And Not Just for Compliance)

When pay stubs are confusing, employees ask questions. When employees ask questions, HR answers them.
When HR answers them, sometimes it’s quick and easyand sometimes it’s an avalanche of emails that begin with,
“Hi, I think payroll stole my money?” (Spoiler: it’s usually a benefits premium, a tax withholding change,
or a misunderstanding of pay periods.)

By requiring a clear wage statement explanation at hire, Oregon is nudging employers toward a healthier payroll ecosystem:
fewer surprises, fewer disputes, and fewer panicked messages at 6:02 a.m. on payday.

Experience Notes: What Employers Are Running Into in the Real World (Approx. )

Since this Jan. 2026 change is all about clarity, the most common “experience” employers report isn’t a legal battle
it’s a practical one: translating payroll reality into human language. Many payroll systems were built by people who
genuinely love abbreviations. Employees? Not always.

One typical scenario looks like this: an employer pulls a payroll code export and discovers a small rainforest of entries
not only “REG” and “OT,” but also codes for training pay, on-call pay, retro adjustments, holiday pay, multiple bonus types,
and benefit lines that show both employee deductions and employer contributions. The first draft of the notice can feel like
writing a glossary for a fantasy novel (“In the Age of SFTDIF, the Night Shift Warriors…”). The best teams solve this by grouping
codes into categoriesearnings, taxes, benefits, retirement, garnishments/otherthen giving short, consistent definitions.

Another common experience: multi-state employers realize Oregon’s requirement is specific enough that a “one-size-fits-all”
national wage notice doesn’t quite work. The fix is usually simplecreate a base company notice and then add Oregon-specific
sections for required items (pay period explanation, deduction purposes, allowances if applicable, and the full payroll-code key).
Employers with remote workers also learn quickly that “posting it in the breakroom” is not a great strategy when the breakroom is
someone’s kitchen table in Bend. Many shift to a dual approach: provide the notice in an onboarding packet (email/PDF) and also
store it permanently in the HR portal.

HR teams also notice a surprising side benefit: once employees have the paystub “legend,” the tone of pay-related questions changes.
Instead of “What is this mystery deduction?” the question becomes “I see MED is my medical premiumcan I confirm which plan tier I’m on?”
That’s a much easier conversation, and it tends to reduce the stress level on both sides. In workplaces with frequent schedule changes or
differential pay, the notice can prevent confusion about why two paychecks with the same number of hours don’t always look identical.

Finally, employers who plan ahead tend to have the smoothest experience. The practical winners are those who schedule an annual SB 906
review during open enrollment or year-end payroll setupbecause that’s when benefit rates, deductions, and payroll vendor changes are most
likely to shift. When the notice is updated as part of normal year-end housekeeping, the January 1 update requirement feels like a routine
tune-up rather than a compliance fire drill. The overall lesson employers are learning is refreshingly simple: when payroll is understandable,
trust improvesand when trust improves, payday becomes less of an event and more of what it should be: normal.

Conclusion

Oregon’s expanded wage statement rules effective January 2026 are about more than adding paperworkthey’re about reducing confusion and increasing transparency.
If you’re an employer, the winning move is to treat the new SB 906 notice like a living “paystub guide”: accurate, accessible, and updated every year.
If you’re an employee, you should expect clearer explanations of earnings, deductions, and payroll codes at hireso your pay stub finally reads like a paycheck,
not a puzzle.