Tax-Loss Harvesting in India: Set-Off Rules, Carry-Forward, and a Clean Execution Workflow
If March feels like a scramble every year, it is usually not because capital gains math is hard. It is because the process is messy. Tax-loss harvesting is simple in concept: you realise eligible capital losses so they can reduce eligible capital gains. The “eligible” part is the whole game. In India, the rules that […]
If March feels like a scramble every year, it is usually not because capital gains math is hard. It is because the process is messy.
Tax-loss harvesting is simple in concept: you realise eligible capital losses so they can reduce eligible capital gains. The “eligible” part is the whole game.
In India, the rules that drive almost every decision are these: short-term capital loss (STCL) can be set off against short-term capital gains (STCG) and long-term capital gains (LTCG), while long-term capital loss (LTCL) can be set off only against LTCG under the current framework.
If losses are still left after set-off, capital losses can typically be carried forward for up to eight assessment years, but only if you protect the carry-forward by filing correctly and on time.
This guide is built for a documentation-first, CA-friendly close. You will get:
- A simple set-off matrix you can apply before placing any sell.
- Carry-forward rules and the filing timing gate you should treat as non-negotiable.
- A month-end close style SOP: decide, execute, archive, reconcile, then CA review pack.
Educational only. This is not trading advice, and it is not personalised tax advice. Your costs, holding periods, and classifications matter.
What Tax-Loss Harvesting Can and Cannot Do
Tax-loss harvesting works only when the loss is realised. Paper losses do not reduce tax. This is a compliance-first framework, not a trading recommendation.
The One-Sentence Definition
Tax-loss harvesting is the act of selling an investment at a loss so the loss can reduce taxable capital gains, then deciding whether and when to reinvest based on suitability and costs.
What Is In Scope
For most investors, the cleanest use case is listed equity and equity mutual funds, because reporting is broker-led and capital gains classification is standard (concept-level, product rules vary).
This also extends to other capital assets where you have taxable capital gains and clean documentation.
What Is Out Of Scope
Capital losses do not reduce salary or interest income. The Income Tax Department’s public guidance is explicit that a loss under “Capital gains” is not set off against other heads.
Also out of scope: categories where the law blocks set-off or carry-forward entirely. The biggest example is crypto or VDAs, covered later as a caution[1].
Practical takeaway: Treat harvesting like a close process. Decide what you can legally set off, then sell only what you can defend with records.
Set-Off Rules You Must Apply First
The highest-impact mistake is selling “loss positions” without first checking whether the loss type can actually offset the gain type you have this year.
The Simple Set-Off Matrix
| Loss type | Can set off against | Cannot set off against | Notes for documentation |
| STCL | STCG and LTCG | Other heads (salary, interest, etc.) | Keep contract notes, broker CG report, and lot mapping. |
| LTCL | LTCG only (current framework) | STCG and other heads | Track holding period clearly, and keep corporate action notes. |
| VDA loss (crypto) | Not allowed | Everything, and no carry-forward | The Act disallows set-off and carry-forward for VDA losses. (Income Tax India[1]) |
Why this matters operationally:
You should not “harvest LTCL” to reduce STCG under the current rules, unless a specific transitional provision applies for that loss year and you have verified it (see the 2026 watchlist section).
Delivery Matters For Character
For typical investor harvesting, you are usually dealing with delivery-based holdings that fall under capital gains.
Intraday and F&O can move you into a different tax treatment bucket (business income for many cases), which changes set-off logic and documentation.
Special Restriction: VDA Losses
The restriction is unusually strict. The law states that no set-off of loss from transfer of a virtual digital asset is allowed against other income, and the loss cannot be carried forward.
Carry-Forward Rules And Filing Timing
If this year’s gains are not enough to absorb your losses, carry-forward is the next lever. But it has a gate you should treat like a hard control: filing timing.
How Long Can You Carry Forward
Under the classic framework, capital losses can be carried forward for up to eight assessment years following the year in which the loss was first computed.
The Filing Condition You Should Not Gamble With
Carry-forward for many losses generally requires that you file the return within the time allowed under the due date rules (commonly discussed with the section 139(1) due date condition).
The Income Tax Department’s tutorial content repeatedly frames on-time filing as a requirement for carrying forward losses (with specific exceptions like house property loss).
If a client has missed the due date, treat it as a CA decision point, not a DIY assumption. The cost of getting this wrong is that the loss may not be available later.
What To Store For Future Years
Carry-forward only helps if you can reproduce the number. Store, at minimum:
- Loss year and bucket (STCL or LTCL).
- Scrip or ISIN, quantity, buy and sell dates, and charges.
- Broker CG report version used, contract notes, and demat movement.
- Corporate action notes (splits, bonus, mergers) that change cost basis.
A Clean Harvesting Calendar For March
A clean calendar reduces two risks: last-week execution errors and last-week documentation gaps.
Week-By-Week Plan
T-30 days (early March): gains snapshot and data cleanup
- Pull realised gains to date, split by STCG and LTCG.
- Download the latest broker capital gains statement (do not rely on app screens).
- Identify corporate actions in the FY that may affect cost basis.
T-14 days: shortlist and set-off plan
- Decide a loss booking range, not a single exact rupee target.
- Apply the set-off matrix before deciding what to sell.
- Estimate costs: spreads, exit loads for funds, brokerage, and taxes elsewhere.
T-7 days: execute in tranches
- Sell in batches so you have time to fix quantity, settlement, or lot mapping issues.
- Archive contract notes and trade confirmations the same day.
T+7 days (early April): reconcile and lock
- Reconcile contract notes, broker CG report, and demat movement.
- Freeze a CA review pack: one summary page plus evidence links.
Settlement And Delivery Cautions
Avoid last-day “I will fix it later” assumptions. Even if a trade is executed, your documentation and reporting feeds may lag. Build buffer time so you can correct errors while statements are still easy to retrieve.
Lot Selection And Cost-Basis Discipline
Most harvesting problems are cost-basis problems. The set-off rules are stable and simple. The data is where things break, especially with multiple brokers and corporate actions.
Choose A Consistent Method
Use a method consistent with broker reporting and your own ledger, then document it. The goal is not to “optimise tax” by switching lots casually. The goal is to produce a number that ties out across evidence.
Practical rule: do not switch lot logic mid-year without a written note explaining why and how you reconciled the change.
Build A Minimal Lot Ledger
Your ledger does not need to be complex. It needs to be traceable.
| Asset (ISIN/Scrip) | Buy date | Buy qty | Buy value (incl charges) | Sell date | Sell qty | Sell value (net) | ST or LT flag | Broker | Corporate action notes | Supporting file link |
| Example | 2025-06-10 | 100 | … | 2026-03-20 | 100 | … | ST/LT | Broker A | Split on … | FY26/BrokerA/… |
Reconciliation Checkpoints
Use a three-way tie-out:
- Contract notes: ground truth for executed trades and charges.
- Broker capital gains report: convenient summary, but can have mapping issues.
- Demat statement and corporate actions: validates holdings movement and flags basis breaks.
If any one of the three does not match, do not “patch” during filing week. Fix it immediately after execution, while the trade context is fresh.
The Clean Execution Workflow You Can Reuse
This is a client-ready SOP that separates decisions from controls. Your CA does not need your market thesis. Your CA needs clean inputs, clear evidence, and clean reconciliation.
Step 1: Snapshot Gains And Loss Capacity
Owner: Client
Input: Broker CG report to date, realised gains summary
Output: Gains snapshot (STCG, LTCG) and a rough loss capacity range
Evidence stored: Latest CG report export
Step 2: Shortlist Harvest Candidates
Owner: Client, optional adviser input
Input: Portfolio holdings, unrealised loss list, exit loads and liquidity checks
Output: Candidate list prioritising clean records
Evidence stored: Candidate list with one-line rationale per position
Step 3: Validate Set-Off Logic
Owner: Client, CA for edge cases
Input: Candidate list, gains snapshot, set-off matrix
Output: Approved harvest list (STCL and LTCL targets) plus exclusions
Evidence stored: Set-off decision notes
Step 4: Choose Lots And Create The Trade Ticket
Owner: Client
Input: Lot ledger, broker lot view (if available), holding period flags
Output: Trade ticket (scrip, qty, lot IDs, expected ST or LT tag)
Evidence stored: Lot selection screenshot or export, and ledger version
Step 5: Execute And Download Proofs
Owner: Client
Input: Trade ticket
Output: Executed trades
Evidence stored: Contract notes and trade confirmations saved same day
Broker platforms typically provide contract notes and capital gain reports, but you should still verify them against your own ledger and demat movement.
Step 6: Reconcile And Lock
Owner: Client, CA for exceptions
Input: Contract notes, updated broker CG report, and demat statement period
Output: Reconciled realised gains and losses
Evidence stored: Tie-out sheet and exception log
Step 7: Prepare CA Review Pack
Owner: Client prepares, CA reviews
Input: Reconciled summary + evidence folder
Output: CA-ready pack with one-page summary and links
Evidence stored: Final “as filed” pack folder
Documentation Pack And CA Review Checklist
Documentation is not admin work. It is the control that makes your numbers defensible.
What To Store, Minimum Set
| Document | Where to download | Why it matters | Common issues |
| Broker capital gains statement | Broker back office / tax reports | Primary summary used for ITR CG schedule | Wrong holding period tags, missing corporate action adjustments |
| Contract notes for each sell | Broker contract note archive | Ground truth for trade, quantity, and charges | Not downloaded, or incomplete for partial fills |
| Demat statement (FY period) | Depository / broker demat | Validates holdings movement and corporate action entries | Mismatch across brokers, missing ISIN mapping |
| Corporate action records and notes | Exchange notices, broker notes, demat entries | Explains cost basis shifts | Split/bonus not captured in ledger |
| Lot ledger export | Your spreadsheet | Single source of truth tying all evidence | Primary summary used for the ITR CG schedule |
Review Questions For CA
- Was the return filed on time for carry-forward eligibility, and if not, what is the impact?
- Are there any classification edge cases (capital gains vs business income)?
- Are there exemptions or restricted categories involved (for example, VDAs)?
- Do broker CG report totals tie to contract notes and demat movement?
Common Mistakes And Compliance Checks
To scale this across clients, build a habit of checking failure points.
Rule Mistakes
- Trying to set off LTCL against STCG under the classic rule set.
- Trying to set off capital losses against salary or interest income.
- Treating VDA losses like equity losses. The law blocks set-off and carry-forward.
Process Mistakes
- Filing late and assuming carry-forward still applies without verifying.
- Harvesting on the last trading day with no time to reconcile.
- Relying on screenshots instead of contract notes and exports.
Data Mistakes
- Corporate actions breaking cost basis and holding period.
- Multiple brokers with inconsistent reporting formats and duplicate scrip names.
- Partial fills are not reflected cleanly in a manual ledger.
Pre-Filing Compliance Checklist
| Check | Why it matters | Pass criteria | If fail, what to do |
| Set-off matrix applied | Prevents invalid offsets | STCL and LTCL used only where allowed | Recompute before filing, adjust carry-forward |
| VDA excluded | VDA loss restriction | No VDA loss set-off or carry-forward claimed | Separate reporting, do not net against gains |
| Filing timing confirmed | Carry-forward gate | Return filed within the required timeline for loss carry-forward | Escalate to CA immediately |
| Three-way reconciliation done | Prevents mismatch notices | Contract notes = CG report = demat movement | Build an exception log and resolve before ITR |
| Corporate actions captured | Fixes basis errors | Split/bonus/merger notes match demat entries | Update ledger, regenerate gains |
2026 Rule Change Watchlist And Updates
Tax frameworks stay defensible when they include a change log with effective dates and sources.
What Is Changing In April 2026
The Income-tax Bill, 2025[2] (as introduced) states commencement on 1 April 2026.
The official FAQ material also discusses the shift in terminology from “assessment year” to “tax year” and how tax year 2026–27 aligns with the transition.
One-Time Relief To Watch: Brought-Forward Capital Losses
Here is the practical watch item for tax-loss harvesting:
A savings clause in the Income-tax Bill, 2025 says that brought-forward losses under the head “Capital gains” (under section 74 of the repealed Act) from tax years beginning before 1 April 2026 shall be set off against income under the head “Capital gains” computed under the new Act.
That wording is broader than the classic “LTCL only against LTCG” constraint, and media coverage[3] has described it as a one-time widening for pre-1 April 2026 LTCL to be set off against STCG from tax year 2026–27.
Control to adopt: Do not operationalise this based on headlines. Verify the enacted text, any notified commencement provisions, and any clarifications before applying it to a client file. Use your update log and have a CA sign-off gate.
How To Communicate Changes To Clients
Use a short change note:
- What changed (one sentence).
- Effective date.
- Who it impacts (brought-forward losses only vs all future losses).
- Required action (update the set-off matrix, update the SOP, update templates).
Annual Tax Framework Update Log
| ITR instructions/portal help | What changed | Effective from | Where to verify | Impact on SOP |
| Set-off matrix | Any change to LTCL vs STCL offsets | FY / tax year | Final Act text and official FAQs | Update matrix page and training |
| Carry-forward and due-date gates | Any change to filing requirement | FY / tax year | Official guidance | Add or adjust “hard gate” step |
| Transitional provisions | One-time rules for pre-transition losses | April 2026 onwards | Savings clause and notifications | Add CA sign-off step |
| Portal schedules | ITR schedule updates for CG | Filing season | ITR instructions / portal help | Update mapping checklist |
Conclusion
Tax-loss harvesting in India becomes predictable when you treat it like a close process, not a last-week trade list.
- Start with the set-off matrix. STCL vs LTCL logic comes before sales.
- Protect carry-forward rights by treating filing timing as a hard gate.
- Run a controlled workflow: decide, execute, archive, reconcile, then CA review.
- Use a standard documentation pack to prevent cost-basis and statement mismatches.
- Maintain an annual watchlist for law changes and effective dates, especially around April 1, 2026.
FAQs
Under the classic framework, long-term capital loss is set off only against long-term capital gains, while short-term capital loss can be set off against both short-term and long-term capital gains.
However, from April 1, 2026, you should verify whether a transitional provision applies to brought-forward capital losses from years before the new Act’s commencement, because the savings clause language can be broader.
Carry-forward of capital losses is typically treated as a “file on time” item. Income Tax Department guidance repeatedly frames timely filing (due date logic) as a condition for carrying forward many losses, with some exceptions like house property loss.
If the due date was missed, treat it as a CA escalation, not an assumption.
There is no universal requirement to rebuy. Reinvestment is an investing decision driven by suitability, costs, and portfolio intent. For a clean process, keep reinvestment decisions separate from your compliance controls so your documentation remains clear and your lot tracking stays consistent.
Minimum set: broker capital gains statement, contract notes for each sell, demat statement for the period, corporate action notes, and your lot ledger export. These allow you to reconcile the numbers across independent evidence trails before filing.
Generally, no. Loss under the head “Capital gains” is not set off against income under other heads in the Income Tax Department’s public guidance.
No. The law disallows the set-off of VDA loss against other income and also disallows carrying it forward to later years.
Maintain a minimal lot ledger and do a three-way reconciliation: contract notes, broker CG report, and demat movement. Corporate actions are a primary driver of mismatches, so log them as they occur, not at filing time.
