The RSU Wash Sale Trap: How a Tech Employee Lost $12,600 in Disallowed Losses Without Knowing

Almost every tech employee with restricted stock units eventually runs into the same tax problem, and almost none of them see it coming. The mechanics are simple to describe: RSUs vest and become taxable as ordinary income at the moment of vesting, the employee acquires the underlying stock at the fair market value on that date, and any subsequent gain or loss on the stock is treated as capital. So far, standard tax treatment. The trap appears when the employee decides — sensibly, by every traditional measure of investment hygiene — to sell some vested shares at a loss to harvest the loss for tax purposes, while simultaneously buying the same company's stock inside an IRA or 401(k), or letting their next RSU tranche vest, or participating in an ESPP. The wash sale rule disallows the loss. The disallowance is automatic, retrospective, and applies across all accounts owned by the taxpayer (and the taxpayer's spouse) including retirement accounts. Most tech employees never realize this has happened until their tax preparer flags it, by which point the loss is already gone.

The RSU wash sale problem is one of the most common and most expensive mistakes in tech-sector personal finance. It's particularly insidious because each individual transaction looks reasonable. Selling stock at a loss to harvest the loss is good practice. Continuing to participate in your employer's RSU program is good practice. Contributing to a 401(k) that holds employer stock as an option is good practice. Buying more of a depressed stock you believe in is good practice. The trap is the combination — the wash sale rule treats all of these transactions as connected, even when they happen in different accounts at different times. Once you understand the mechanics, the trap is avoidable. Until you understand the mechanics, it's nearly inevitable.

This is the story of how one tech employee lost $12,600 in disallowed wash sale losses across a single year, what went wrong, and what continuous lot-level scanning across multiple accounts would have prevented.

The Setup: $180,000 in Vested RSUs and a Plan That Should Have Worked

Priya is 34, a senior software engineer at a publicly traded tech company in Seattle. Her base salary is $215,000, plus an annual cash bonus of $30,000-$50,000, plus restricted stock units that vest quarterly. By the end of 2025, she had accumulated 850 vested RSU shares across two years of vests, with a total cost basis of approximately $180,000 (the fair market value at each vesting date, on which she paid ordinary income tax). She also held 300 unvested RSU shares scheduled to vest across the upcoming quarters of 2026.

In early 2026, the stock dropped sharply — a sector rotation away from tech compounded by a disappointing earnings call. By March, her vested shares were worth approximately $145,000, an unrealized loss of $35,000. Priya's financial advisor suggested she harvest the loss. The mechanics looked clean: sell the 850 vested shares at a $35,000 loss, capture the loss for tax purposes (worth $35,000 × 35.8% = $12,530 in tax savings at her combined federal and Washington state rate, though Washington has no income tax — so $35,000 × 32% federal + 3.8% NIIT = $12,530), and immediately buy a diversified tech ETF to maintain sector exposure. She did exactly that on March 14, 2026.

On April 8, 2026, her next RSU tranche of 75 shares vested.

On April 15, 2026, she made her annual IRA contribution of $7,000 and used it to buy more shares of the same employer stock — a move she'd been doing for several years as a way to dollar-cost-average into the company she believed in.

On May 1, 2026, her quarterly ESPP purchase executed automatically, acquiring 40 additional shares at a discounted price.

All four events — the March 14 loss harvest, the April 8 vest, the April 15 IRA purchase, and the May 1 ESPP purchase — fell within a 61-day window. By the time her tax preparer reviewed everything in February 2027, the wash sale rule had already silently disallowed every dollar of her March 14 loss.

What Exactly Happened: The Wash Sale Mechanics Across Accounts

The federal wash sale rule under IRC §1091 disallows a loss when the taxpayer acquires "substantially identical" securities within 30 days before or 30 days after the loss sale. The 61-day window (30 days before + the sale date + 30 days after) is calculated calendar-style, not trading-day-style. The disallowed loss is added to the cost basis of the replacement shares — meaning it's preserved as a future deduction when those replacement shares are eventually sold — but the loss cannot be used in the current year.

The critical part most investors miss: the rule applies across all of the taxpayer's accounts, including IRAs and other retirement accounts. When a wash sale happens entirely inside a taxable account, the loss gets added to the basis of the replacement shares and the investor eventually recovers it. When a wash sale happens because the replacement shares are inside an IRA, the basis adjustment to the IRA shares is meaningless — IRA basis doesn't affect anything because distributions are taxed as ordinary income regardless of underlying basis. The loss is effectively permanently destroyed, not just deferred.

This is the worst possible outcome of a wash sale and the specific trap Priya fell into.

Let's walk through what the IRS sees when looking at her 2026 transactions:

| Date | Account | Transaction | Shares | Wash Sale Impact | |------|---------|------------|--------|-----------------| | March 14 | Taxable brokerage | Sell 850 shares at loss | -850 | Triggering sale; $35,000 loss claimed | | April 8 | RSU plan (taxable) | RSU vesting | +75 | Replacement acquisition within 30 days | | April 15 | Traditional IRA | Buy shares | +175 (approx) | Replacement acquisition within 30 days | | May 1 | ESPP (taxable) | Quarterly purchase | +40 | Replacement acquisition within 30 days |

Total replacement shares acquired within 30 days of March 14: 290 shares.

The wash sale calculation: of the 850 shares Priya sold at a loss, 290 are matched against replacement shares — 290 / 850 = 34.1% of the loss is disallowed in the current year. The disallowance applies pro-rata:

$35,000 × 34.1% = $11,935 disallowed in 2026
Of which $7,210 (175/290 × $11,935) is permanently destroyed because the replacement shares are in an IRA
The remaining $4,725 is preserved as basis adjustment on the 115 taxable-account replacement shares (vested RSUs and ESPP), available as a future deduction when those shares are sold

In tax savings terms: Priya thought she had captured $12,530 in federal tax savings. The actual outcome was significantly different. Of the $35,000 loss claimed:

$23,065 (65.9%) remained valid and was deductible in 2026: tax savings of $23,065 × 35.8% = $8,257
$7,210 was permanently destroyed via the IRA wash sale: lost tax savings of $7,210 × 35.8% = $2,581
$4,725 was deferred via basis adjustment on replacement shares: present-value cost of approximately $4,725 × 35.8% × (1 - discount factor) — for a 5-year deferral at 7% discount, roughly $720 in present-value tax savings lost

Total tax value lost to the wash sale trap: approximately $3,300 in immediate savings and another $2,200-$3,300 in deferred value depending on holding periods on the replacement shares. The combined damage is in the range Priya's advisor never warned her about: $5,500 to $6,600 in destroyed or deferred tax value from a single loss harvest she thought would save her $12,530.

But that's only the first-order analysis. The actual figure in the headline of this article comes from compounding the problem across multiple loss harvests during the year — which is what happens to most tech employees, because RSUs vest quarterly, the stock keeps fluctuating, and the harvesting opportunities keep appearing throughout the year. Across the full 2026 tax year, Priya executed three loss harvests on her employer stock at different prices. Two of the three were partially or fully disallowed by overlapping vestings, IRA purchases, and ESPP cycles. Total disallowed losses across the year: $12,600 — of which roughly $7,200 was permanently destroyed via IRA wash sales and the rest was deferred for years.

Why Manual Tracking Almost Always Fails

The frustrating thing about the RSU wash sale trap is that it's mechanically simple to avoid in principle. The investor just needs to ensure that no replacement-stock acquisition happens in any account within 30 days before or after any loss sale of the same stock. That's a single rule. In practice, almost no one tracks it correctly when they're doing their own planning, for three reasons.

First, the relevant transactions happen across multiple accounts on different platforms. Vested RSUs are reported on the company's stock plan administrator (typically Fidelity Stock Plan Services, Morgan Stanley StockPlan Connect, or E*Trade Stock Plan Services). ESPP purchases happen on the same platform but as a separate transaction type. IRA contributions happen at whichever brokerage holds the IRA. Loss harvesting happens in the taxable brokerage account. Each platform shows the investor only its own transactions. None of them aggregates across accounts to flag wash sales.

Second, RSU vesting events are scheduled, not actively initiated. A vest that happens automatically on April 8 doesn't feel like a transaction the investor "made" — it just happened. But the IRS treats it as an acquisition of stock, and the wash sale rule applies to it identically to a purchase. Most investors think of wash sales in terms of active trades they could choose not to make. They don't think of automatic events like vestings, dividend reinvestments, and ESPP purchases as wash sale risks, even though they trigger the rule the same way.

Third, spouse accounts are also covered. If Priya's husband Daniel had an IRA holding shares of the same employer stock, transactions in his account during the 61-day window would also count as wash sale replacement events under the related-party rules. Tracking this across two people's accounts at potentially four different brokerages is genuinely difficult to do by hand.

The combination of these factors means that DIY wash sale tracking essentially never works correctly for tech employees with RSUs. Even diligent investors who consciously try to track it tend to miss at least one cross-account transaction per year. The damage from those misses adds up.

What Continuous Cross-Account Monitoring Catches

The reason this article exists in a sequence about tax loss harvesting software is that the RSU wash sale trap is the clearest example of a problem that software solves and humans don't. The required capability is not complicated in principle: monitor every account the investor (and spouse) controls, track every transaction by ticker and date, and flag any sale that would create a wash sale issue given pending or recent transactions in any account.

For Priya's situation specifically, a continuous monitoring system would have caught the problem at the planning stage, not the tax preparation stage. The system would have shown her:

Pending RSU vest on April 8 (already known from the vesting schedule)
Pending ESPP purchase on May 1 (already known from the company's enrollment)
Scheduled IRA contribution timing (configurable by the investor)

Knowing this, the system would have flagged March 14 as a problematic date to harvest losses on the same stock, because any sale on March 14 would create wash sale issues with the April 8 vest and the May 1 ESPP purchase. The system would have proposed alternatives:

Delay the harvest until May 31 — past the 30-day window from both April 8 and May 1. The stock would be at a different (possibly less favorable) price, but the loss would be clean.
Suspend ESPP participation for one quarter — losing the ESPP discount on the May purchase, but preserving the harvest.
Postpone the IRA contribution to a date outside the wash sale window — straightforward for Priya, since IRA contributions can be made anytime through the tax filing deadline.
Harvest a smaller amount of stock, sized so that even with the replacement acquisitions, the wash sale disallowance is minimal.

Each of these alternatives has trade-offs. Option 1 introduces market risk. Option 2 sacrifices ESPP discount value. Option 3 is essentially free but requires planning. Option 4 captures partial value. The right choice depends on the investor's specific situation, the stock's price trajectory, and the relative value of each piece. But all four options are dramatically better than walking blindly into a $5,500-$12,600 disallowance.

This is the work software does that humans don't: continuously evaluate the interaction between dozens of scheduled, automatic, and discretionary events across multiple accounts, flag conflicts before they happen, and present specific tactical alternatives that preserve the most tax value. None of the individual calculations are hard. The hard part is doing all of them, all the time, without missing the cross-account links that trigger the rule.

What Priya Should Have Done Going Forward

After her 2026 tax preparation revealed the $12,600 in disallowed losses, Priya restructured her approach for 2027. Three changes were sufficient to prevent the problem from recurring:

First, she designated harvest windows. Looking at her RSU vesting schedule, ESPP cycle, and planned IRA contributions, she identified two windows per year — typically late June and late November — when no scheduled acquisitions of her employer stock would occur within the surrounding 61-day periods. Loss harvesting on employer stock would happen only in those windows. Other harvesting (on her diversified portfolio) continued year-round under different rules.

Second, she switched her IRA holdings to a broad index fund. Concentrating retirement savings in her employer's stock was an unrelated risk-management problem on top of the wash sale issue. Holding the IRA in a total-market fund eliminated the IRA leg of the wash sale concern entirely, removing the most expensive part of the previous year's disallowance.

Third, she elected to sell vested RSUs immediately upon vesting. Many tech employees hold vested RSUs hoping for further upside, but this concentrates risk in a single stock that is already correlated with their employment income. Selling immediately upon vesting moves the proceeds into a diversified portfolio and dramatically reduces the frequency of large unrealized losses on the employer stock, which in turn reduces the need to harvest losses on it and the wash sale exposure that comes with harvesting.

For Priya, the combination of these three changes reduced her 2027 wash sale exposure to effectively zero on her employer stock, while preserving full harvesting flexibility across the rest of her portfolio. Her diversified portfolio continued to generate harvested losses through normal lot-level scanning, with no wash sale risk because she didn't hold concentrated positions outside the employer stock.

What This Means for Tech Employees Generally

Priya's situation is not unusual. Almost every tech employee with quarterly RSU vesting, ESPP participation, and an IRA holding the same stock has some level of wash sale exposure they don't know about. The exposure is highest for:

Employees at companies whose stock is volatile enough that loss harvesting opportunities arise frequently
Employees who let RSUs accumulate rather than selling immediately upon vest
Employees who concentrate retirement savings in employer stock
Two-earner couples where both spouses work at the same company or hold similar stock

The damage compounds over multi-year careers. A tech employee who has been at a public company for ten years, harvesting losses periodically without proper wash sale tracking, may have lost five-figure or even six-figure tax value across that period — money that should have been theirs but was permanently destroyed by misaligned cross-account transactions.

The right approach for tech employees specifically isn't to avoid loss harvesting on employer stock — the harvesting is valuable when executed cleanly. It's to either (a) execute the harvesting in designated windows that don't overlap with vests, ESPP cycles, or planned IRA purchases, or (b) use continuous cross-account monitoring software that flags wash sale risks before they occur. Either approach works. The combination of frequent automatic acquisitions across multiple accounts and active harvesting in any of those accounts is what produces the trap.

For background on the rate brackets that determine the value of avoiding wash sale disallowance, see capital gains tax rates 2026. The lot-level mechanics that make cross-account tracking work in practice are detailed in our optimal tax lot selection and unrealized losses hiding in winners deep dives. For investors at the NIIT threshold like Priya, see net investment income tax NIIT 2026. For the broader compounding case for continuous monitoring versus annual reviews, see Marcus's $600,000 portfolio scenario. And for a different scenario showing how lot-level decisions transform a single position from a tax problem into a tax opportunity, see Sarah's NVDA case study.

The RSU wash sale trap isn't exotic. It's the natural and frequent result of the intersection between routine tech-employee compensation structures and a tax rule written in 1921 to handle a different problem. Avoiding it requires either careful planning around specific dates and accounts, or software that handles the tracking automatically. Walking into it can cost the kind of money most investors think they're carefully harvesting their way out of paying.