When you trade on margin the platform and the broker’s back‑end are constantly checking whether your account still has enough equity to support open positions. That checking is what produces margin call notices and, if things go too far, automatic stop‑outs (forced liquidations). The math is straightforward, but the real‑time implementation combines market data, position accounting, margin rules and execution logic. Below I explain the pieces step by step, show simple worked examples and highlight real‑world behaviours you should know about. Trading carries risk; this article is educational and not personalised advice.
The basic math every trader should know
At the heart of every margin system are three numbers: balance, equity and used margin. Balance is the settled cash in your account. Equity is balance plus the unrealised profit or loss on open positions. Used margin is the total amount the broker has reserved to keep those positions open.
Brokers express safety as a margin level percentage. The standard formula is:
Margin level (%) = (Equity ÷ Used margin) × 100
If equity falls, the ratio falls. Brokers publish two thresholds tied to that ratio: a margin‑call level (a warning) and a stop‑out level (automatic action). For example, if your account equity is $800 and your used margin is $1,000, margin level = (800 ÷ 1000) × 100 = 80%. If your broker’s margin call is 100% and stop‑out 20%, you would already be below the margin‑call threshold and would be warned; automatic liquidation wouldn’t start until the margin level hits 20% or less.
Where real‑time calculations happen: market data and the risk engine
Real‑time margin monitoring is a streaming problem. Market prices move every tick; that changes the mark‑to‑market P&L and therefore equity. To translate price changes into margin events, brokers run a risk engine that:
- receives live market data feeds for every instrument you hold,
- converts those prices into your account currency (if required),
- marks every position to market and recalculates unrealised P&L,
- updates equity, free margin and margin level,
- compares margin level against configured thresholds, then
- triggers notifications or liquidation workflows when limits are breached.
These steps typically run inside a low‑latency event loop on the broker’s servers. For most retail platforms the system recalculates on every price update (every tick) or on small internal intervals (tens to hundreds of milliseconds) so the margin level you see is effectively live.
Margin rules and instrument specifics
Margin required per position isn’t a single number for all products. The engine uses per‑instrument (and sometimes per‑account) margin rules. Those rules may include exchange initial/maintenance margins for futures, broker day margins for CFDs, or percentage‑of‑notional rules for FX. The risk engine applies any instrument multipliers, contract sizes and client‑specific leverage to compute the used margin that feeds the margin‑level formula.
Multi‑currency accounts add a conversion step: the engine converts foreign‑currency cash and position values into the account base currency using current FX rates. It also applies financing (swap) charges, commissions and any manual adjustments; these all affect equity and therefore margin level.
Alerts vs forced liquidation: the usual workflow
Brokers generally use two stages to protect accounts. First comes the margin call: a margin level where the broker warns the client to add funds or reduce exposure. Second comes stop‑out: a lower margin level where the system starts closing positions automatically.
A typical workflow runs like this in real time. As soon as a price tick arrives the risk engine recalculates equity and margin level. If margin level drops below the margin‑call threshold, the platform records an alert and (depending on broker policy) sends notifications to the trader. If margin level then reaches or falls below the stop‑out threshold, an automated liquidation routine executes. That routine usually selects positions for closure according to broker policy — commonly the most losing positions first, or positions requiring the largest margin, although some brokers use other priority rules — and issues market orders to close them until margin level returns above the stop‑out threshold or all positions are closed.
Concrete example: how a stop‑out unfolds numerically
Imagine you have $2,000 balance and open trades whose used margin totals $800. Initially, your equity equals balance ($2,000) and margin level = (2000 ÷ 800) × 100 = 250%.
Market moves against you and unrealised losses reach $1,400. Equity is now $600 and margin level = (600 ÷ 800) × 100 = 75% — below a common margin‑call threshold of 100%. A margin‑call alert is generated.
Losses continue and equity reaches $160. Margin level = (160 ÷ 800) × 100 = 20%. If your broker’s stop‑out is 20% or lower, the automatic liquidation engine starts. It might close your largest losing position first; after that close your equity and used margin are recalculated and the engine checks whether to stop or continue closing positions.
This example shows how margin calls give you a chance to act, while stop‑outs are automatic emergency measures executed by the broker’s systems.
Priorities, netting and partial closes
The order in which positions are closed during a stop‑out varies. Many brokers close the positions with the largest negative P&L first because removing the biggest loss produces the fastest lift to equity. Others close positions consuming the most margin or use FIFO rules on accounts where that’s mandated. Some platforms support partial closes or reduce position sizes by fixed steps.
If positions offset each other (hedged or correlated), netting rules apply: the system may calculate net exposure across correlated legs before deciding what to close. These policies are implementation choices and will be listed in your broker’s terms and trading conditions.
Timing, latency and execution realities
Although calculations are deterministic, real markets introduce timing issues. Price ticks arrive at different latencies; your platform chart and the broker’s risk engine may briefly see slightly different prices. During very fast moves or illiquid periods, the engine may process several adverse ticks before the liquidation orders execute, producing slippage. That is why you sometimes get stopped out at a worse price than the price that triggered the stop‑out.
In extreme cases—market gaps or when feeds disconnect—broker systems rely on the last known quote, a fallback feed, or exchange prices. Some systems also include “price collars” or require exchange confirmations for certain instruments, which can add slight delay but protect against erroneous executions.
Special cases: futures, exchanges and day margins
For futures and exchange‑cleared products, margin requirements come from the exchange (initial and maintenance). Brokers may enforce higher “house” margins. Day trading margins are often lower for intraday use and reset to higher overnight margins at session cutoff. The risk engine must be aware of these regime changes so it applies the correct used‑margin numbers when calculating margin level.
Practical caveats traders should know
The theoretical margin formula is simple but real accounts are affected by additional items that the risk engine includes in equity and used margin: open orders that reserve margin, pending funding/rollover charges, unrealised swap charges, commissions, corporate actions and any manual adjustments. All of these can change the margin level without a market price move.
Also, broker policies differ. Some send aggressive margin‑call notifications; others may skip margin‑call alerts and go straight to stop‑out under volatile conditions. The liquidation order, partial close options and whether the broker will accept margin deposits during an active liquidation are all policy choices. Check your broker’s trading conditions and terms.
Risks and caveats
Automated margin systems are designed to prevent negative balances and protect the firm and the trader from runaway losses, but they are not infallible. Fast markets, gaps and thin liquidity can cause slippage and executions at prices far from the trigger price. Network latency and data‑feed interruptions can produce temporary mismatches between the price you see and the price the risk engine used. In rare cases, forced liquidations can complete at a net negative balance; your broker’s contract will describe whether they absorb that loss or pass it to the client. Because of these factors, rely on sound risk management: use appropriate position sizes, set stop losses thoughtfully, keep a buffer of unused margin, and understand your broker’s margin and stop‑out policies. Remember that trading carries risk and nothing in this article is personalised advice.
Key takeaways
- Margin level = (Equity ÷ Used margin) × 100; brokers compare that ratio to their margin‑call and stop‑out thresholds to decide actions.
- Real‑time systems recalculate on each price update: market data → mark‑to‑market P&L → equity → margin level → alert/liquidation if thresholds breached.
- Liquidation rules (which positions are closed first), multi‑currency conversions, day vs overnight margins and broker policies all affect the real‑world outcome.
- Slippage, gaps and feed/latency issues mean margin events can execute at worse prices than those that triggered them; manage leverage and maintain a cushion to reduce risk.
References
- https://mondfx.com/what-is-stop-out
- https://www.equiti.com/sc-en/news/trading-ideas/what-is-a-stop-out-level-and-how-does-it-differ-from-a-margin-call/
- https://genesis.global/platform/marketplace/real-time-portfolio-margin/
- https://learn.optimusfutures.com/margin-calls-explained
- https://global.vantagehelpcenter.com/hc/en-us/articles/10948711085839-What-is-stop-out-and-how-is-it-calculated
- https://axelprivatemarket.com/what-is-stop-out-level-in-forex-trading/
- https://www.litefinance.org/blog/for-beginners/margin-trading/margin-level-in-forex-trading/