Account Exposure: What a Stop-Loss Price Does Not Show

A stop-loss price for one order does not describe the whole account’s exposure. Distinguish asset value, a planned exit difference, execution costs, open commitments and custody access. These examples use simple unleveraged spot holdings and do not calculate derivatives liquidation or borrowing obligations.

A stop-loss price for one order does not describe the whole account’s exposure. Distinguish asset value, a planned exit difference, execution costs, open commitments and custody access. These examples use simple unleveraged spot holdings and do not calculate derivatives liquidation or borrowing obligations.

One hypothetical holding, two distinct measures
1,000Ten units bought at 100
50Planned gross difference to 95
70Gross loss if exit averages 93

A planned stop-based difference is conditional on execution. It is not a guaranteed maximum loss.

BTKWIN.COM · EDUCATIONAL EXAMPLE

Separate position value from a planned exit difference

For a simple spot holding, a notional valuation is quantity multiplied by the chosen valuation price. A planned difference to an exit level measures another amount: the price distance multiplied by that quantity under assumed execution. Label these in separate columns so a small intended loss is not mistaken for the entire asset exposure.

Ten units purchased at 100 have a raw entry value of 1,000. A planned sell stop at 95 produces a hypothetical five-unit price difference per asset unit, or 50 overall. The 1,000 holding has not become a 50-value holding merely because the stop exists. You still own ten units until confirmed sales or other movements change that quantity.

The CME position-size lesson connects size and stop distance in its educational context. Our examples retain only the basic arithmetic. They do not transfer futures contract specifications or suggest one appropriate sizing percentage for every reader.

A stop trigger is not a guaranteed execution price

If the stop condition occurs but ten units sell at an average of 93, gross proceeds are 930 and the loss relative to 1,000 is 70 rather than 50. A stop-limit order can instead remain partly or entirely unfilled if suitable buyers are unavailable within its limit. Identify the resulting order type before estimating what it can accomplish.

The Investor.gov stop-order bulletin explains these distinctions for stocks. For digital assets, also check the actual product’s trigger reference and execution rules. The general distinction between a condition and its outcome does not establish identical mechanics across markets.

Add hypothetical entry and exit costs totaling four. The loss becomes 54 if execution matches 95 and 74 if it averages 93. An estimate labeled risk of fifty is incomplete if it is intended to include known costs but silently omits them. Keep price difference and cost assumptions explicit.

Aggregate instructions that can affect the same account

Suppose three hypothetical positions each have entry value of 1,000 and a planned gross exit difference of 50. Their combined values are 3,000 and their summed planned differences are 150. Looking at each row separately should not hide the arithmetic total if all three can affect the account during the same period.

Hypothetical positionEntry valuePlanned difference before fees
First1,00050
Second1,00050
Third1,00050
Sum3,000150

This sum is a starting review, not an estimate of every possible loss or its probability. Actual fills can differ, and the assumed events may not occur together. State the scenario, then test alternatives. Do not label the worst case you happened to imagine as a mathematically established maximum.

Different symbols can share economic dependencies

Holding an asset directly alongside a product tracking that same asset can increase dependence on the same price driver. Several tokens can also share a sector, issuer, network or service dependency. Counting names alone does not establish that their risks are independent.

Investor.gov’s diversification explanation describes diversification and its limits. For an account map, add columns for shared underlying asset, issuer, venue and required network. This identifies dependencies without assuming fixed future correlations or promising protection against losses.

Convert valuations into one reference currency at a stated time before aggregating them. A position worth 1,000 of one quote currency and another worth 1,000 of a different currency do not simply total 2,000 of either. Preserve the original quantities and conversion rates. The exchange-rate return guide shows how currency changes add another valuation effect.

Open purchase orders are potential commitments

Current holdings do not show every instruction already submitted. Separate owned assets from open orders and examine what would happen if the orders filled. Cash reserved for a purchase cannot simultaneously be treated as fully available for an unrelated withdrawal or another instruction under the same reservation assumptions.

Assume an existing asset allocation of 500 and two additional purchase instructions worth 300 and 400. If both execute without an offsetting sale, the amount allocated can become 1,200 before fees and price changes. Looking only at the current 500 misses the potential effect of instructions the system already holds.

Check identifiers for duplicates after connection failures or replacements. Closing an app or stopping a local program does not prove that an exchange canceled accepted instructions. The GTC cancellation guide explains how to reconcile the active remainder before replacing it.

Custody and access are separate from market price

Splitting one asset between two custodians can change reliance on a single service without changing the asset’s price movement. Holding several assets in one account can spread some price dependencies while leaving access dependent on one provider. Record asset, custodian and account type separately.

Consider a scenario in which you need funds while withdrawal is temporarily unavailable. That is an access question that a sell-stop level alone does not resolve. Use the wallet helper to review custody models and the transfer helper to distinguish an account restriction from a broadcast transaction problem.

Do not treat moving assets as an automatic consequence of drawing a dependency map. Transfer has fees, compatibility requirements and operational risks of its own. If evaluating it, calculate the actual route separately. The map’s purpose is to identify what a proposed action changes, including what remains dependent on the same underlying factor.

Test partial execution as well as a worse price

Write explicit scenarios for exits matching the plan, exits at less favorable prices and incomplete exits. For our ten-unit example, selling all at 95 produces gross proceeds of 950; selling all at 93 produces 930. Selling only four at 94 produces 376 and leaves six units held.

That last scenario does not realize the entire difference between 1,000 and 376 as a closed-position loss, because six units remain. Record cash received and remaining holdings independently, with a documented valuation or cost allocation when needed. Otherwise a partial fill can produce a misleadingly large loss number.

Recognize the boundary of the simple spot model

Margin and derivatives introduce collateral, maintenance requirements, liquidation, settlement and possibly shared-account obligations. Quantity times price alone does not explain everything the account can lose or owe. Identify the exact product and the balances it can use before applying a model.

Review holdings, potential order fills, costs, shared dependencies and access assumptions together. Include obligations outside the account when deciding what funds are available for a task. No universal risk percentage follows from this table. Its practical value is exposing duplicated orders, incompatible units and reliance on an execution price that the order does not guarantee.

Continue reading

English content and examples reviewed: 27 October 2026. Read the Arabic edition.

تامر طعمه
تامر طعمه
Articles: 484