<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Risk Management on WebNotes</title><link>https://v2.webnotes.in/tags/risk-management/</link><description>Recent content in Risk Management on WebNotes</description><generator>Hugo</generator><language>en-IN</language><lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://v2.webnotes.in/tags/risk-management/index.xml" rel="self" type="application/rss+xml"/><item><title>How to fix an 'order rejected: RMS' error on Zerodha</title><link>https://v2.webnotes.in/how-to-fix-rms-rejection-zerodha/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-fix-rms-rejection-zerodha/</guid><description>&lt;p&gt;When &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt; rejects an order with a message beginning &lt;strong&gt;&amp;ldquo;RMS:&amp;rdquo;&lt;/strong&gt;, &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&amp;rsquo;s&lt;/a&gt; internal Risk Management System has blocked the order before it reached the exchange. RMS is a pre-trade validation engine that checks margin, position limits, scrip restrictions, OI caps, and other broker-level risk parameters. The sub-code that follows &amp;ldquo;RMS:&amp;rdquo; identifies the specific check that failed.&lt;/p&gt;
&lt;p&gt;Unlike exchange-level rejections (which carry NSE or BSE error codes), RMS rejections are issued by Zerodha&amp;rsquo;s servers. The exchange never processes a RMS-rejected order, so there is no exchange acknowledgement number for such orders.&lt;/p&gt;</description></item><item><title>SL (Stop Loss limit) order on Kite</title><link>https://v2.webnotes.in/sl-order-kite/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/sl-order-kite/</guid><description>&lt;p&gt;An &lt;strong&gt;SL (Stop Loss limit) order&lt;/strong&gt; is a conditional order type that becomes active only when a user-defined trigger price is reached. Once triggered, it enters the exchange order book as a standard &lt;a href="https://v2.webnotes.in/limit-order-kite/"&gt;limit order&lt;/a&gt; at a separately specified limit price. On &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;, &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&amp;rsquo;s&lt;/a&gt; trading platform, this order type is selected by choosing &amp;ldquo;SL&amp;rdquo; from the order type dropdown, after which two price fields appear: the &lt;strong&gt;trigger price&lt;/strong&gt; and the &lt;strong&gt;limit price&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The SL order is primarily used for risk management, to exit a losing position automatically when the market moves against a trader&amp;rsquo;s expectation. It is also used to enter positions on breakouts, where a trade is initiated only after the price clears a specific level.&lt;/p&gt;</description></item><item><title>SL-M (Stop Loss Market) order on Kite</title><link>https://v2.webnotes.in/sl-m-order-kite/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/sl-m-order-kite/</guid><description>&lt;p&gt;An &lt;strong&gt;SL-M (Stop Loss Market) order&lt;/strong&gt; is a conditional order type that monitors the market for a trigger price and, when that trigger is reached, submits a &lt;a href="https://v2.webnotes.in/market-order-kite/"&gt;market order&lt;/a&gt; to the exchange for immediate execution at the best available price. On &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;, &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&amp;rsquo;s&lt;/a&gt; trading platform, an SL-M order is placed by selecting &amp;ldquo;SL-M&amp;rdquo; from the order type dropdown and entering only a single price field: the &lt;strong&gt;trigger price&lt;/strong&gt;. Unlike the &lt;a href="https://v2.webnotes.in/sl-order-kite/"&gt;SL (Stop Loss limit) order&lt;/a&gt;, no separate limit price is specified. Once triggered, execution is at whatever price the market offers.&lt;/p&gt;</description></item></channel></rss>