Tax-Loss Harvesting Software: An Automated Review Checklist

Tax-loss-harvesting software can make a complicated review easier to organize. It cannot make a loss useful by itself, predict a market move, or guarantee that a trade will receive a particular tax result.

The useful question is not whether a tool uses machine learning. It is whether the review starts with complete tax-lot data, identifies a real tax purpose for a sale, catches known conflicts, and leaves the investor with records to verify the result. This checklist describes the controls software should support before someone treats an unrealized loss as a tax opportunity.

Start With the Exact Tax Lot

A position total is not enough. Each purchase can have a different acquisition date, basis, holding period, and gain or loss. An automated review should show the exact lot, quantity, basis, current value, and the broker's sale-method setting before a sale is considered.

Specific-share identification can produce a different result from a broker's default method. The IRS explains the identification and recordkeeping rules for securities in Publication 550. Confirm the lot instruction with the broker before the trade, then retain the confirmation.

For the records to collect before a sale, use the lot-level pre-sale checklist.

Match the Loss to a Real Tax Use

Software should distinguish an unrealized loss from a usable loss. Under federal capital-gain netting rules, capital losses offset capital gains; only a remaining net capital loss can generally reduce up to $3,000 of other income for an individual return, with unused amounts carried forward. IRS Topic 409 summarizes that sequence.

Before ranking a sale, the review should ask:

What capital gains and losses have already been realized this year?
Is there a planned gain that independently supports a sale?
Is the loss short-term or long-term, and how does that fit the complete return?
Would a carryforward be more useful than using the loss now?
What state tax and income-based consequences need separate review?

A loss used to offset an intentional gain is consumed. That can raise the gain position's basis, but it is not a free tax result. The matched-pair guide explains the trade-off between a current gain offset and preserving a loss for another year.

Treat the Wash-Sale Check as a Blocking Control

The IRS wash-sale rule can disallow a loss when stock or securities are sold at a loss and substantially identical stock or securities are acquired within 30 days before or after the sale. A useful system should flag known purchases, but it cannot establish that every household account or future purchase has been captured.

The review should cover the sale itself and the surrounding purchase calendar, including:

recurring taxable-account investments and dividend reinvestment;
purchases at another broker;
a spouse's accounts where applicable;
IRA purchases, which can have a different basis consequence; and
scheduled RSU vesting or ESPP activity involving the same security.

No software label can guarantee that a proposed replacement is not substantially identical. Compare its benchmark, holdings, concentration, fees, liquidity, and tracking behavior for investment reasons, and obtain qualified advice when the tax classification is material or unclear. Continue with the household wash-sale guide for the cross-account review.

Keep Investment Decisions Separate From the Tax Screen

An automated alert should not become an instruction to sell. A loss may be large but still be a poor trade if it disrupts the allocation, creates unacceptable concentration, has no suitable replacement, or has little current tax use.

Consider a hypothetical $8,000 loss lot and a separate $8,000 planned long-term gain. If both sales fit the investment plan and the loss survives wash-sale review, the items may offset under the federal netting rules, subject to the rest of the return. The gain has been recognized and the loss has been used; the result is not an $8,000 permanent tax saving. A replacement for the loss position can also begin with a lower basis and create a larger taxable gain later.

The right output is therefore a review queue: what to inspect, what conflicts to resolve, and what assumptions affect the estimate. It is not a prediction of which security will rise or a promise that every red lot should be sold.

Require a Clear Audit Trail

Before acting on any software-generated idea, preserve:

the lot data and chosen sale method;
the reason for the sale and the intended use of the loss;
the replacement comparison and wash-sale calendar;
the trade confirmation and any broker-specific lot instruction; and
year-end Forms 1099-B, Form 8949, and Schedule D reconciliation records.

Those records help an investor and tax adviser test what actually happened rather than relying on a dashboard estimate. They also expose missing accounts, partial wash sales, and basis adjustments that an automated screen may not know about.

What Good Automation Does—and Does Not Do

Good tax-aware software can collect lot data, calculate consistent screening fields, surface possible conflicts, and make a review repeatable. It should explain its inputs and leave the investor in control of the trade.

It does not replace complete household data, a broker's execution confirmation, investment judgment, or individualized tax advice. Start with the tax-loss-harvesting algorithm guide for the decision fields a sell-signal workflow should show, then use this checklist to test whether the underlying inputs are complete.

Bottom Line

The value of tax-loss-harvesting software is disciplined review, not a magic model. Verify the lot, the tax use, the wash-sale window, the replacement, and the records before treating an automated alert as a trade candidate.