Broker costs and features
P&L based exit at Indian brokers: scope, fills and loss limits
A P&L based exit can initiate square-off when a chosen combined profit or loss threshold is reached. The broker's position scope, order mode and pending-order policy determine what happens next, and the final loss can exceed the trigger. Dhan, FYERS, Upstox, Angel One and Groww describe different implementations; this page compares their official documentation.
Facts checked 14 Oct 2026 against 13 sources. No affiliate links. Not investment advice.
P&L based exit: what happens when the limit is reached
A P&L based exit monitors a combined profit or loss amount and initiates an exit when that condition is met. It can cover selected positions, eligible account positions or an F&O group, depending on the broker. An alert-only setting simply notifies you. Neither the label nor the trigger amount guarantees your final realised loss.
Dhan, FYERS, Upstox, Angel One and Groww publish relevant features, with different scopes. The comparison below records what their own pages establish on 14 October 2026. We did not place orders or test execution. 'Not found' means the search did not verify a native feature; it does not prove the broker lacks it.
A kill switch answers whether you can place further orders. This page asks what happens to positions already open when a rupee threshold is reached.
Which book does the broker's P&L trigger actually watch?
Official descriptions checked 14 October 2026. This is a documentation comparison, without a winner or hands-on execution test. Source IDs point to the numbered list below; unspecified fields remain unverified.
| Broker/interface | Feature | Positions covered | Time/reset scope | Execution described | Pending orders | Trading afterwards | Sources |
|---|---|---|---|---|---|---|---|
| Dhan app | P&L Exit | Intraday; help excludes Delivery and MTF | For the day, until commodity market is open | Market price; final P&L may differ | Help says same-scrip corresponding orders get 'squared off'; other pending items need manual cancellation | Optional Kill Switch; prerequisites apply | dhan-app / dhan-pending |
| Dhan API | P&L Based Exit | Docs list INTRADAY and DELIVERY product types | Current day; reset at trading-session end | Applicable positions exited; this API page does not specify exit order type | Separate Manage Kill Switch API requires closed positions and no pending orders | enableKillSwitch parameter; confirm product scope | dhan-api |
| FYERS | Smart Exit | All/Custom selection from intraday equity and intraday/overnight F&O; delivery/MTF excluded | Take a Break resets next day; Smart Exit persists unless deactivated or all covered positions close | Exit mode: Market order with Protection; alert-only also available | Cancellation behavior not established by cited overview | Take a Break has selection and new-order conditions | fyers-exit / fyers-break / fyers-setup |
| Upstox | P&L Alerts with Automatic Square-Off | Combined P&L of selected positions/legs | Validity not stated in cited announcement | Alert only or automatic square-off orders; order type not stated | Cancellation behavior not stated | Auto Kill Switch still on roadmap in staff update of 12 Oct 2026; launch not verified | upstox-pnl |
| Angel One | Secure Exit | Published scope: equity intraday and F&O positions | Reset time not stated in cited update | Exit at Market shown in update | Pending orders cancelled; update describes cancellation before square-off | Post-exit trading lock not established by this update | angel-exit |
| Groww | Safe Exit: Limit loss at | Across F&O positions | Valid until end of day | Positions exited; order type not stated in cited article | Related open orders cancelled | F&O Lock is a separate control; automatic link not established here | groww-exit / groww-help |
| Zerodha | Native cumulative-P&L exit not found | No verified native scope; forum reply of 4 Oct 2026 gave no ETA | Not verified for a P&L exit | Not verified; segment Kill switch is a different feature | No P&L-exit cancellation claim | See separate Kill switch comparison | zerodha-controls / zerodha-roadmap |
| Kotak Neo | User-defined account-wide exit not found | No verified native scope in pages searched | Not verified for a P&L exit | Bracket exits and risk-desk exits do not establish this feature | No P&L-exit cancellation claim | See separate Kill switch comparison | kotak-orders |
Dhan app and API are separate rows because their own descriptions differ on Delivery. FYERS' separate setup guide establishes All/Custom selection and when monitoring stops. Groww's Safe Exit help says its profit-limit setting is being gradually rolled out, so the Protect Profit description does not promise availability in every account. Upstox evidence comes from its product-team community announcement; user replies and roadmap requests do not establish launched capabilities.
Trigger → exit order → fill → final result
- 1
The selected P&L reaches the condition
The broker watches the book described in its feature. A gain elsewhere does not necessarily offset a loss in the selected group. Confirm which positions the displayed total includes before relying on the number.
- 2
The chosen action starts
An alert-only setting leaves positions open. Exit mode initiates orders. Dhan app help describes market-price exits; FYERS explicitly says Market order with Protection. The Upstox announcement does not name a uniform order type.
- 3
Each order still needs an execution
A trigger is not a fill. Upstox explicitly says final execution depends on market conditions and liquidity. Dhan warns that realised P&L can differ from the set amount, particularly in volatility. Check order status and remaining quantities.
- 4
Compare fills and account costs with the trigger
Use actual executed prices when reviewing the loss. Keep the broker's monitored P&L definition separate from after-charge results. If the docs do not specify whether charges or already-closed trades are included, leave that question unresolved.
Illustrative slippage: a ₹3,000 trigger becomes a ₹3,100 cost
Made-up arithmetic, not a market observation, broker test or suggested loss limit. Assume a single long position of 100 generic units, monitored loss ₹3,000 at the trigger, an exit fill ₹0.75 lower than the trigger mark and an illustrative ₹25 of costs not already in the trigger total. No lot size, statutory rate or real contract is assumed. Amounts are shown to the nearest paisa without intermediate rounding.
- Loss visible when the trigger fires
- ₹3,000.00
- Additional adverse fill movement: 100 × ₹0.75
- ₹75.00
- Realised price loss: ₹3,000 + ₹75
- ₹3,075.00
- Illustrative additional costs, assumed for arithmetic only
- ₹25.00
- After-cost loss: ₹3,075 + ₹25
- ₹3,100.00
Dhan P&L Exit: app wording and API wording differ
Dhan's app help says to set maximum profit and maximum loss on intraday positions for the day. It says open positions other than Delivery and MTF are exited when the condition is reached. The page also warns that square-off happens at market price and the actual P&L may differ.
Its separate DhanHQ API documentation lists INTRADAY and DELIVERY in the productType field. That is a material interface difference. We retain both descriptions rather than turning the app exclusion into a blanket statement about every Dhan route. The API documentation also says the configuration resets at the end of the trading session.
For an app user, check the products shown in the active setup. For an API user, confirm the actual supported scope with Dhan before relying on the Delivery field. This page supplies no code or broker-connection instructions.
Dhan's separate pending-order FAQ says corresponding pending orders for the same scrip get 'squared off', while other pending positions need manual cancellation. We preserve that wording without treating it as automatic cancellation of every pending order. The API page's separate Manage Kill Switch endpoint requires all positions closed and no pending orders; it does not describe automatic cancellation by the P&L Exit flag.
“actual P&L may differ from set values”
Source: [1]
FYERS Take a Break: conditions beyond the loss number
Select all eligible positions
The support page says Take a Break cannot be enabled if even one position is excluded.
Check the action mode
Smart Exit has Exit and Alert only modes. The Take a Break description says the chosen action happens first, then the new-position restriction applies.
Account for orders placed after enabling it
FYERS says Take a Break will not activate if new orders are placed after enabling it but before Smart Exit triggers. The support page's troubleshooting repeats this condition.
Check the next-session state
FYERS says Take a Break resets on the next trading day. Its Smart Exit setup guide says monitoring persists across days unless manually deactivated or all covered positions are squared off. Check the selected book and both settings at the next session.
Upstox, Angel One and Groww do not describe the same basket
Upstox's product announcement describes choosing positions and monitoring their combined P&L. It offers a notification or an action that places square-off orders. Its execution caveat is part of the feature description, not an exceptional assumption added by us. The announcement leaves session validity and pending-order handling unstated. In the same thread on 12 October 2026, staff member Samit said Lock and Trail Profit would be available the following month, with Auto Kill Switch still on the roadmap. That is a dated plan, not a verified launch.
Angel One's Secure Exit update describes overall profit and loss triggers for equity intraday and F&O positions, with pending-order cancellation before square-off. It also says triggers can be edited or removed. The cited update does not give a post-exit trading lock or a reset time, so those cells stay unverified.
Groww's Safe Exit article describes F&O positions being exited and related open orders cancelled when the chosen loss is crossed. The trigger lasts until the end of the day. Its separate Protect Profit setting responds when displayed profit falls to a chosen level. A profit-protection threshold and an absolute-loss threshold are different conditions.
These official descriptions help identify the right control. They do not settle undocumented details such as inclusion of fees, all previously closed trades or newly added positions. Ask about those details using the feature and interface name, rather than the broad phrase 'daily loss limit'.
Four controls that are often called a daily loss limit
A conceptual map using the documented broker features; no prop-firm contract or trading-limit amount is asserted.
| Control | What it refers to | What to establish |
|---|---|---|
| Selected-position P&L exit | The combined group chosen in the feature | Which positions are selected; which action mode is active |
| Eligible account/F&O exit | The eligible book named by the broker | Delivery exclusions, new-position handling and P&L definition |
| Trading lock | Permission to place further orders | Whether it also cancels or closes anything; never infer this from the name |
| Prop-firm daily-loss condition | The terms of that separate account or contract | Read the specific rules; a broker exit setting does not establish that a contract limit is met |
The prop-firm row is a distinction in terminology, with no named firm promoted and no contract rule reproduced. See the existing prop-firm rules guide for that separate subject.
Why an exit trigger does not settle a prop-firm rule
Searches for daily loss limits can lead to funded-account or prop-firm terms. A broker's rupee trigger describes an execution feature. It cannot establish the calculation, reset, fees or breach treatment in an unrelated contract. Compare the definitions rather than assuming matching labels mean matching limits.
The prop-firm rules explainer covers that separate terminology. This guide makes no legal verdict on a prop arrangement, names no firm as an option, and does not claim an auto-exit satisfies anyone's contract. It also offers no recommended risk percentage or trading strategy.
Keep a record that explains the next trigger
- 1
Before using the feature, write down the scope
Record the interface, covered products, selected positions and action mode. Keep any broker answer about fees or realised trades beside the setup. A saved threshold without those details is an incomplete record.
- 2
After a trigger, reconcile the result
Record the trigger mark, actual fill prices, rejected or unfilled quantities and separately charged costs. The slippage glossary explains the price difference; use the order history for what actually happened.
- 3
Separate the next-order decision
Record whether a trading lock was enabled and whether its stated conditions were met. An exit can close the selected book while another order remains possible. A written checklist is useful context, but it is not an execution control.
Questions the official descriptions still leave open
For your broker and interface, establish whether the P&L includes closed trades, costs and positions added after setup. Establish how partial fills and rejected exits are handled. Establish whether the feature resets automatically and whether you need to configure it again before a new session.
Our table deliberately keeps those unknowns visible. It is based on documents checked on the stated date, not a test of latency, reliability or execution quality. Those limits also prevent a feature comparison from becoming a performance ranking.
Use the pre-trade checklist generator to put your own written rules into a routine. Keep the broker's exit configuration, the permission to place more orders and your after-trade notes as separate items to reconcile.
Sources
Every figure on this page comes from one of these. Each was checked on the date shown.
- [1]Dhan app help: Set P&L Exit · checked 14 Oct 2026
- [2]Dhan P&L Exit pending-order help · checked 14 Oct 2026
- [3]DhanHQ Trader's Control API · checked 14 Oct 2026
- [4]FYERS Smart Exit: scope and execution · checked 14 Oct 2026
- [5]FYERS Take a Break conditions · checked 14 Oct 2026
- [6]FYERS Smart Exit setup: All/Custom selection and persistence · checked 14 Oct 2026
- [7]Upstox product-community announcement, 21 January 2026 · checked 14 Oct 2026
- [8]Angel One Secure Exit product update, updated 3 October 2025 · checked 14 Oct 2026
- [9]Groww F&O risk-management update, 6 October 2026 · checked 14 Oct 2026
- [10]Groww Safe Exit help: validity and profit-limit rollout · checked 14 Oct 2026
- [11]Zerodha Kill switch help · checked 14 Oct 2026
- [12]Zerodha forum: P&L exit roadmap reply, 4 October 2026 · checked 14 Oct 2026
- [13]Kotak Neo orders and portfolio support directory · checked 14 Oct 2026