twimco.Let’s talk ↗︎
Menu
Field notes / Buying software

Washington DRS moves ERA login to WA.gov on December 1. Treat it like any identity cutover

Washington employers who file through DRS ERA must complete a one-time WA.gov registration when login moves off SAW on December 1. The account stays; the inbox and the 24-hour code decide whether payroll reporting still works.

Editorial engraving of a sunny HR office where a payroll supervisor opens a soft two-email registration screen while a specialist checks a paper list.

On December 1, 2026 Washington’s Department of Retirement Systems switches Employer Reporting Application login from Secure Access Washington to WA.gov. Employers complete a one-time WA.gov registration; DRS says the ERA account, information and access stay the same. Watch for two emails that day—a registration link and a registration code—and register within 24 hours before the code expires. Use the cutover to pressure-test any portal vendor on identity migration, code expiry and who owns the help desk when the named admin’s inbox is wrong.

What DRS announced

DRS Notice 26-017, posted November 3, 2026, tells Washington employers that on December 1, 2026 the Employer Reporting Application stops authenticating through Secure Access Washington and starts using WA.gov. The change is about how you log in. DRS says your existing ERA account, information and access remain the same.

Beginning December 1 you complete a one-time WA.gov registration. DRS will send two separate emails: one with a link to the ERA registration page, and one with the registration code. Register within twenty-four hours, before the code expires. If it expires you can still register, but you must call DRS Employer Support Services for a new code. This is part of a statewide move from SAW to WA.gov; other agencies transition on their own timelines.

The data did not move. The login did. Cutover failures will look like forgotten passwords and are usually lost registration emails.

The December 1 morning, as an ops drill

Before December 1. Confirm which people actually file ERA. Remove ex-employees from the mental model. Make sure the mailbox that will receive DRS mail is monitored that day—not an alias nobody opens.

December 1. Expect two emails. Do not wait for a "single sign-on feels fine" assumption. Complete registration while the code is live. If a backup filer needs access, finish their registration the same day instead of discovering the gap on a filing deadline.

If the code expires. Call Employer Support for a new one. Build that phone path into your internal runbook now: number, hours, who is allowed to call.

After registration. Smoke-test a non-destructive ERA action you already understand so you know the session works before a filing is due.

How the work moves

December 1 registration flow

  1. 1. Watch the inbox

    Two DRS emails: registration link and code.

  2. 2. Open the link

    Start one-time WA.gov registration for ERA.

  3. 3. Enter the code

    Complete within 24 hours before expiry.

  4. 4. Smoke-test ERA

    Confirm the session before a filing deadline.

  5. 5. If expired

    Call Employer Support for a new code.

Illustrative flow from DRS Notice 26-017; not a DRS screenshot.
The data did not move. The login did. Cutover failures will look like forgotten passwords and are usually lost registration emails.

Three questions for any portal identity cutover

Washington answered these for ERA. Your next government or benefits portal contract should answer them in writing.

1. What stays put when login moves? DRS said account, information and access stay. Ask vendors for the same sentence—and for a rehearsal that proves it.

2. How many messages, and how long is the code live? Two emails and twenty-four hours is a concrete pattern. Ask for message count, expiry, and the path when the admin inbox is wrong.

3. Who is the human backup? Expired codes require a phone call. Put vendor support hours and escalation in the cutover plan, not in a wiki someone finds after payroll fails.

Decision guide

Identity cutover vs data migration

ConsiderationDRS ERA Dec 1Ask your next vendor
What movesLogin only (SAW → WA.gov).Is data migrating or only auth?
What staysAccount, information, access.Prove it in a rehearsal
Time box24-hour registration code.Code TTL and resend path
Human backupEmployer Support for new codes.Named escalation with hours
Decision framework for portal contracts; DRS ERA is the worked example.

Who this note is for

Washington employers on ERA. Do the registration work. Calendar December 1. Brief whoever covers vacation that week.

Teams buying or renewing portals. Use DRS as a free example of identity cutover without a data migration. If a vendor cannot explain login moves this clearly, that is a buying signal.

Agencies watching WA.gov. Other systems will follow. Steal the two-email pattern and the twenty-four-hour code discipline for your own notices.

What not to invent

Do not claim ERA data migrates—DRS says it does not. Do not invent new ERA features in this cutover. Do not treat SAW deprecation timelines for other agencies as identical without their notices.

Why identity cutovers fail in ordinary companies.

The failure mode is boring. The registration email lands in a shared inbox that only the outgoing payroll clerk still filters. The code expires. Filing day arrives. Someone insists the "system is down" when the system is waiting for a WA.gov account that was never finished.

Put ERA registration on the same checklist you use for bank token rotations and tax portal MFA resets. It is identity work, not software feature work.

If you operate in multiple states, keep a simple register: portal name, next identity change date, named owner, backup owner. Washington's notice is easy to miss in a national HR ops calendar full of louder renewals.

Vendors who migrate login should be willing to send a dry-run message a week early to a test mailbox you control. If they cannot, ask how you are supposed to rehearse. DRS is giving a production cutover with clear rules; your commercial portals should not be vaguer.

Put this into practice

If you file ERA, assign a named owner for December 1 registration and a backup. If you buy portals for public-sector clients, add identity-cutover clauses that match this level of clarity. For help designing government and public sector portal cutovers where login moves and open work must survive, get in touch with your current admin roster and last filing calendar.

Keep a short evidence packet: the Notice 26-017 URL, who completed registration, the timestamp, and the smoke-test performed. Auditors and backup filers both need that trail.

If your organization files for multiple employer accounts, list each one. Partial registration is a common failure—people finish the account they use weekly and forget the quiet one.

Brief executives in one sentence: login moves December 1; data stays; two emails; twenty-four hours. That is enough for them to clear calendars without a slide deck.

HR and payroll should treat December 1 like a filing-critical day even if no report is due that morning. Identity cutovers fail on ordinary Tuesdays. Clear PTO conflicts for the named ERA owner and the backup.

If you use a PEOs or shared services center, confirm which legal entity receives the DRS emails. Shared inboxes across entities are how the wrong team deletes the code.

Run a five-minute tabletop the week before: "registration email is in spam, code expires in two hours, named owner is out sick." Decide who opens spam, who calls Employer Support, and who tells payroll to pause noncritical ERA edits until access is confirmed. Write the answers on the same page as the notice link. If your shared-services vendor owns ERA, make them show you their December 1 staffing plan in writing, including after-hours coverage for expired codes. Identity cutovers fail at the seams between employers and vendors more often than inside a single inbox. Ask for a screenshot of the WA.gov registration completion screen to be filed with your evidence packet the same day—not a week later when memories disagree. Confirm mobile MFA devices for the ERA owners before December 1 so the WA.gov step is not the first time someone learns their authenticator app was retired with an old phone.

Related work: Sutton Place.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Sutton Place ↗︎