86 / 97
Soft Breach
Working definition
A rule breach whose stated consequence is something other than ending the account — a warning, a suspension pending review, a requirement of further trading, or a constraint on what may be withdrawn.
A soft breach is a rule condition that fired without ending the account. The same trigger word applies as in a hard breach; the sentence describing the consequence says something else — a warning, a suspension pending review, a requirement of further trading days, or a constraint on what may be withdrawn rather than on whether the account exists.
It is the more confusing of the two states to be in, and the reason is not psychological. A hard breach announces itself: the account is closed and there is nothing ambiguous about that. A soft breach leaves you holding a notification, an account in some state, and a document that has to be read carefully before you know which of several quite different situations you are in.
The word describes the consequence, not the severity
Nothing about soft refers to how far past a threshold the account went, or to how the account was traded. It refers only to what the agreement attached to that condition. The same numeric threshold, crossed by the same trade, can be terminal under one programme’s terms and a warning under another’s — and a condition usually written softly can be written terminally by a document that chose to.
That is why the distinction cannot be inferred and has to be located. A rule of this kind is written in two parts that are usually not adjacent: a sentence defining the condition, which carries the number and gets quoted in marketing material, and a sentence stating what happens when the condition is met, which decides your situation and typically sits several sections away under a heading about consequences or violations. Reading the first and assuming the second is where most of the confusion around this word originates.
The two failure modes, and they point in opposite directions
Both are common enough to be worth naming, and each one wastes something different.
The first is treating a soft breach as terminal. An account is suspended pending a review, the trader reads the notification as an ending, stops engaging, and the account lapses through inaction into exactly the outcome the document had not imposed. The cost is an arrangement that did not have to end.
The second is treating it as a conversation that has been opened. A notification arrives with no stated duration, no named review and no condition for resumption, and the trader waits — for a decision that the document never committed anyone to making, on a timetable nobody agreed. The cost here is time, and often the window in which anything else could have been done.
The defence against both is the same and it is unglamorous: find the consequence sentence for the specific condition named, and check it against what is observably true of the account.
The account’s state is evidence the notification may not contain
The account’s own state is the practical instrument, and it is the one people reach for last.
An account that still accepts an order was not terminated, whatever a message implied. An account that accepts nothing, shows no positions and offers no withdrawal is not meaningfully suspended, whatever a message said. Where the wording and the state disagree, the state is the harder fact — it is the system’s own account of what was actually done, rather than a description of it.
The same check applies to what the notification omits. Where it names no duration, no review and no condition for resumption, the honest reading is that the document does not commit to any of those. That is a fact about your position, not a gap that waiting will fill.
Soft is not the same as costless
The word does real damage here. A constraint on a payout is a financial consequence that leaves the account intact: the arrangement continues, and the money does not arrive, or arrives reduced, or arrives only once further conditions are met. Nothing about a consequence being non-terminal makes it cheap, and “soft” is a reliable way to stop reading at precisely the point the document became relevant to money.
Consistency conditions are where this shows up most visibly in published terms: where publishers state a consequence for them at all, it is not always termination — a payout reduced, delayed, or made conditional on additional trading days all appear. Which makes them the clearest illustration of the general point. The rule is the trigger; the softness is the outcome; and the same rule written with a terminal consequence would be a hard breach.
The arithmetic is unchanged by the account surviving
Given the rule text and your own account record, whether the stated condition was actually met on your numbers is a closed question with a definite answer — and it does not become less worth asking because nothing was terminated. Where a payout is constrained on the grounds that a condition fired, that computation is the entire substance of the disagreement. Where the rule text will bear more than one reading, it can be computed under each, and the spread between the readings is itself informative.
What that record cannot establish is anything about intent, about whether a quote was fair, or about what would have happened otherwise; those limits are set out in what a trading statement can prove. The question worth asking is not “was this fair” but does the rule, as written, produce this outcome on my numbers?
Where to start
The full taxonomy of what can be breached — and why only some of it is about losing money — is in what a funded trading account breach means. Where a consistency condition is what fired, the consistency rule calculator computes your largest day against all three bases such a rule can use, and reports the spread between them, because the base the rule meant is frequently the whole argument.
Where the disagreement has stopped being about the arithmetic and become about who can be asked to look at it, the routes and the precondition on each are in where a funded-account breach dispute can go.
Where a payout has been reduced or refused on grounds you would rather have recomputed from your own daily record than argue about in general terms, that is Payout-Denial Recompute.
Commonly confused with
Neighbouring concepts that get used interchangeably, and the distinction that actually separates them.
- Hard breach
The same trigger word, the opposite outcome. A hard breach ends the account — it is closed or its positions are liquidated. Which one you have is not derivable from the threshold you crossed or from how far past it you went; it is stated in the sentence of the agreement describing consequences, which is usually not the sentence defining the condition. That separation is why the two words are needed at all.
- A warning that is not a rule event
A message advising caution — that an account is approaching a limit, or that a pattern has been noticed — is not necessarily a breach of anything. A soft breach is a condition that actually fired and whose stated consequence was not termination. The difference matters because only one of them is a countable event under an agreement that may treat repetition differently from a first occurrence.
- A payout denial
Overlapping but not the same. A soft breach can produce a constraint on a payout, which is one route to a withdrawal being reduced or refused. But a payout can also be refused for reasons that are not breaches at all — an unmet threshold, an outstanding verification, a timing condition. Establishing which applies decides what document you are arguing from.
- Consistency rule
A specific condition rather than a category of consequence. Consistency conditions are the case where a non-terminal consequence most visibly appears in published terms — where publishers state one, it is not always termination. But the rule is the trigger and the softness is the outcome, and a consistency condition written with a terminal consequence would be a hard breach despite being the same rule.
How to measure it in your own data
A definition you cannot test is a definition you have to take on trust. This is the shortest honest route from the concept to a number you computed yourself.
- Records you need
The sentence of your agreement stating the consequence for the specific condition named, the notification itself with its timestamp and its exact wording, and the account's own observable state — whether an order can be placed, whether positions remain open, whether a withdrawal request is available. Where a payout is affected, the terms governing withdrawals as well.
- What you compute
Read the consequence sentence for the named condition rather than for breaches generally, and establish which of the non-terminal forms it describes: a warning that is recorded, a suspension with a stated review, a requirement of further trading days, or a constraint on what may be withdrawn. Then check whether the notification states a duration, a review, a condition for resumption, or nothing — because a suspension without any of those is indistinguishable in practice from a termination that was not called one.
- What the answer tells you
The account's observable state is the more reliable of the two signals, and it is the one people check last. An account that still accepts an order was not terminated whatever the message implied, and an account that accepts nothing is not meaningfully suspended whatever the message said. Where the notification names no duration and no review, the honest reading is that the document does not commit to one — which is a fact about your position rather than a gap to be filled by waiting.
If this has already cost you
If a condition fired without ending the account and a payout is constrained because of it, the arithmetic behind that condition can be recomputed from your own daily record.
- Payout-Denial Recompute“Does the arithmetic behind my denied payout actually hold?”Will not establish: Whether the firm must pay. A recomputation shows whether the stated condition was met under the stated rules; contract interpretation and enforcement belong to the firm, a regulator where one exists, or your own adviser — armed with arithmetic instead of assertion.
- Prop-Breach Forensics“Why did my prop evaluation actually fail?”Will not establish: Whether the firm’s rules are fair, or whether you would have passed with different luck. It reconstructs what happened; it does not adjudicate the firm.
Intake is not open yet, so none of these can be commissioned today. They are listed here so you know the measurement exists and what it would and would not settle — the launch list hears first.
Work it out yourself
Free calculators that take this concept as an input. Each shows its working, so the number it gives you can be checked rather than taken on trust.
Questions and answers
Does a soft breach mean I keep the account?
A soft breach means the stated consequence was not termination. That covers materially different situations: a warning recorded against the account, a suspension pending a review, a requirement to trade further days, or a constraint on what may be withdrawn while the account continues. Which of those applies is stated in the agreement, and they differ enough that "soft" on its own is not yet an answer to what happens next.
Can a soft breach still cost me money?
Yes, and this is the part the word obscures. A constraint on a payout is a financial consequence that leaves the account intact — the arrangement continues and the money does not arrive, or arrives reduced, or arrives only after conditions are met. Nothing about a consequence being non-terminal makes it costless, and treating soft as harmless is a reliable way to stop reading at the point the document became relevant.
How do I tell a soft breach from a hard one?
Not from the threshold, and not from how far past it the account went. From the sentence stating the consequence for that particular condition, checked against what is observably true of the account. Where the two disagree, the state is the evidence: an account that still accepts an order was not closed, whatever the notification implied.
Does a soft breach count against me later?
Whether occurrences accumulate, and whether a second is treated differently from a first, is a property of the agreement rather than a general rule. It is worth establishing at the time rather than at the second occurrence, because the answer changes what the next one costs. Outside that agreement nothing accumulates anywhere: there is no register and nothing is reported to any authority.
Is the arithmetic still worth checking if the account survived?
The arithmetic is the same closed question either way. Given the rule text and your own account record, whether the stated condition was actually met on your numbers has a definite answer — and where a payout is constrained on those grounds, that answer is the whole substance of the disagreement. A specific discrepancy is worth considerably more than a general grievance.
Related terms
Derived from the links this entry makes and the entries that link back to it.
In the research
Soft Breach comes up in two research notes on this site.