AI for Financial Advisors & RIAs

Tax-Loss Harvesting at Scale: AI Tools for Advisors

How AI changes tax-loss harvesting from a quarterly project to a daily scan. Tools that work, wash-sale rules, and the build vs. buy decision.

Tax-loss harvesting (TLH) is one of those workflows where the math is undeniable but the operational cost has historically been high. Net of the wash-sale rule, of cost-basis tracking, of timing — a fully-automated daily TLH process is meaningfully more valuable than a quarterly manual one.

The major TAMP and robo platforms (Schwab, Betterment, Vanguard, Wealthfront) deliver daily TLH at scale. For RIAs not on those platforms — or running custom portfolios — AI-augmented TLH is the way to match that capability without licensing the whole stack.

The math behind continuous TLH

The standard reference number: continuous TLH adds 0.5-2.0% to after-tax returns annually for taxable accounts, depending on market conditions, client tax bracket, and portfolio turnover. Higher in volatile years, lower in calm years.

For a $5M taxable account at a 1% TLH alpha and the client's marginal rate, the annual realized benefit can run $20k-$50k. Multiplied across an RIA's taxable book, the firm-level number gets significant fast.

This is real money that's leaking when TLH is done manually.

What's actually hard about TLH

Three things make TLH operationally expensive:

1. Wash-sale rule

You can't realize a loss on a security and buy back a "substantially identical" security within 30 days before or after. Substantially identical is a regulatory grey area for ETFs (VTI and ITOT? Probably substantially identical. VTI and VXUS? Not.). Most firms are conservative here. AI doesn't fix the regulatory grey area but does help apply the firm's policy consistently across thousands of positions.

Wash-sale also applies across accounts — selling at a loss in your taxable account and buying the same security in your IRA within 30 days triggers a permanent disallowance, not just a deferral. This is where most manual TLH gets it wrong.

2. Cost-basis tracking

Loss harvesting requires lot-level cost basis. Most custodians provide this; some don't, or provide it inconsistently across account types. Tax-lot accounting (specific identification vs. average cost vs. FIFO) compounds the complexity.

3. Replacement security selection

You sell a position for a loss. You need to replace it (or stay out for 31 days). The replacement should track the original closely enough to keep portfolio exposure intact but not be "substantially identical" under the wash-sale rule.

Pre-mapped replacement pairs (e.g., VTI ↔ ITOT for total market, IVV ↔ VOO for S&P 500) is the standard playbook. AI doesn't invent these — but it does maintain them, apply them consistently, and watch for new replacement opportunities as new ETFs launch.

Where AI specifically helps

Five places:

1. Daily scan vs quarterly project. A scan that runs daily across every taxable lot in every household identifies harvestable losses the day they appear. Manual TLH usually catches the obvious ones at quarter-end and misses small intra-quarter opportunities.

2. Cross-account wash-sale checking. When the AI sees the full household — taxable + IRA + spouse + joint — it can check wash-sale exposure across all accounts before recommending a sale. Critical for clients with concentrated households.

3. Replacement security application. Maintain firm-approved replacement pairs in code. AI applies them consistently and flags edge cases (e.g., what if the replacement is also at a loss?).

4. Realized-loss budgeting. Most clients have a useful annual realized-loss target (often $3,000 for ordinary income offset, more if there are gains to offset). AI can pace harvesting throughout the year to hit the budget without over-realizing.

5. Year-end optimization. December gets crowded. AI prioritizes harvests by impact and processes them in a controlled cadence rather than the December 31 fire drill.

Build vs buy in 2026

Three options:

Option A: Use a TAMP that includes TLH. Schwab, Envestnet, Pontera, and others offer this. Simple. Constraint: you're using their model portfolios.

Option B: License a TLH-specific platform. Tools like Vise, Smartleaf, and others overlay TLH on whatever custodian you use. Subscription cost typically $10-50/account/year. Works well if you have a unified account base.

Option C: Custom AI build. What we deploy. Sits inside your existing infrastructure, applies your specific wash-sale policy and replacement pairs, integrates with your custodian feeds. Higher upfront cost ($40k-$120k); lower per-account cost at scale; full firm control.

The right choice scales with firm size and customization needs. Below $500M, option A or B is usually correct. Above $1B with custom portfolios, option C pays for itself within Year 1 against the alpha generated.

What goes wrong

Three common deployment errors:

Aggressive substantially-identical interpretation. Some early TLH tools interpret "substantially identical" loosely (treating any S&P 500 tracker as different from any other). Risky. Conservative interpretation: pre-vetted replacement pairs only.

Cross-account blindness. If the system only sees the taxable account, it misses wash-sale exposure in the household's IRA or in the spouse's accounts. Make sure the data layer is at the household level, not the account level.

No advisor approval gate for high-impact harvests. A $50k harvest in a $1M account is material. The system should pause for advisor review on high-impact harvests, not auto-execute. Reg BI implications.

Compliance considerations

TLH itself is generally fiduciary-aligned (it benefits the client) but the execution layer raises questions:

  • Best-execution obligations under FINRA Rule 5310 apply to trade execution
  • Reg BI applies to the recommendation to harvest (technically a recommendation to sell)
  • Fee disclosure for AI-augmented TLH services — most firms disclose this as part of their service offering
  • Recordkeeping for the decision-making process — what trigger fired, what alternatives were considered, why this trade
These are not blockers, just requirements. Build the audit trail from day one.

Realistic ROI for an RIA

A firm with $500M AUM, of which 60% is taxable book ($300M):

  • Conservative 1% TLH alpha = $3M/year added after-tax client value
  • At 1% management fee, that creates 1-3% retention/referral lift = potentially $30k-$90k incremental annual revenue from improved client outcomes
  • Plus capacity recovery from automating what was a quarterly manual effort = 50-100 advisor-team hours/year
Custom build cost: $40k-$120k. Recurring cost $1k-$3k/month. Payback inside 12-18 months.

If you're running a taxable book of $200M+ without continuous TLH, that's the highest-impact deployment after pre-meeting briefs and held-away monitoring.

This is one of the conversations we have weekly. If you want to scope it for your firm, that's a 30-minute call.

Frequently asked questions

What's the wash-sale rule and why does it matter for AI TLH?

The wash-sale rule (IRC §1091) disallows losses where you buy a substantially identical security within 30 days before or after the loss sale. It applies across all your accounts and your spouse's accounts. AI TLH must check across the full household and apply the firm's policy on what counts as 'substantially identical.'

How much alpha does continuous TLH actually add?

Industry research (Vanguard, Wealthfront whitepapers, Betterment data) generally finds 0.5-2.0% annual after-tax alpha for continuous TLH vs. no harvesting, depending on market volatility, client tax bracket, and portfolio composition. Higher in volatile years like 2020 and 2022, lower in calm years.

Can we just use Schwab/Vanguard/Wealthfront's built-in TLH?

Yes if you're using their model portfolios. The constraint is the model portfolios. If your firm runs custom asset allocation, custom security selection, or held-away coordination, you need your own TLH layer on top of (or instead of) the platform offering.

What's the typical replacement-pair playbook?

Pre-vetted replacement pairs across major exposures: VTI↔ITOT (total market), IVV↔VOO↔SPY varies (S&P 500), AGG↔BND (bond aggregate), VEU↔IXUS (intl), etc. The firm's compliance team approves the pair list. AI applies it consistently across the book.

Do we need to disclose AI use in our TLH workflow?

Most RIAs disclose AI-augmented portfolio management in their Form ADV Part 2A under 'Methods of Analysis' and in service-level documentation. The disclosure should be specific to what the AI does and what oversight exists. Standard with our deployments.

Related guides

Need help implementing this?

//prometheus does onsite AI consulting and implementation in Milwaukee. We set it up, train your team, and make sure it works.

let's talk