A trader opens the dashboard, sees the account marked as failed and wants to know why. What happens in the next hour decides a lot. The trader might buy another challenge, file a chargeback or post a one-star review with a screenshot of their equity curve.
Most breach disputes don’t involve fraud or bad faith on either side. They come from a gap between how the firm calculates a rule and how the trader thinks it’s calculated. The trader saw a closed balance comfortably above the limit. The firm measured floating equity at 14:32 server time, during a spread spike, against a start-of-day reference the trader never thought about. Both are looking at real numbers. Only the firm can see all of them.
This guide covers the prop firm breach disputes operators run into most, what a good breach explanation contains, how to run a dispute workflow that doesn’t clog support, and the payout pre-checks that head off the other big source of arguments.
Why a breach dispute costs more than one ticket
Start with support time. To answer a breach question properly, an agent has to pull the trade log, find the rule version the trader bought, rebuild the calculation and write it up. Done by hand, that’s slow, and breach questions arrive in clusters after volatile sessions, when the queue is already full.
Then there are chargebacks. A trader who doesn’t understand why they lost the challenge fee is more likely to dispute the payment with their card issuer. Our article on the prop firm chargeback problem covers the payment side. A clear, evidenced breach explanation is the cheapest chargeback prevention you have, because it answers the question before the trader calls their bank.
Reputation is the third cost. Review sites and trading communities are where unexplained breaches end up, usually with half the context missing. Reputation management for prop trading firms starts with not giving people a reason to post.
The last one is repeat business. A trader who understands why they failed can decide to try again. A trader who feels cheated has already decided.
The breach disputes you’ll see most
Each type below has the same structure: what the trader believes, what actually happened and what removes the dispute at the source.
Equity vs. balance on the daily loss limit
Many firms measure the daily loss limit against equity, which includes floating losses on open positions. Many traders watch balance, which only changes when a trade closes.
Here’s a worked example. A $100,000 account has a 5% daily loss limit measured from the start-of-day balance. The limit is $5,000, so equity can’t touch $95,000 at any moment that day. The trader opens a position that moves $5,200 against them, then recovers, and they close it at a $1,500 loss. Their balance never dropped below $98,500. Their equity hit $94,800. The account breached the moment equity crossed $95,000, even though the trade closed well inside the limit.
Firms differ on the reference point. Some use start-of-day balance, some use start-of-day equity, and some use whichever of the two is higher. Whatever you use, write it into the rules with a worked example, show it in the dashboard and name it in every breach explanation.
Daily reset time and time zones
The trading day resets at a server time the trader may never have checked. A trader who thinks of their day as their local morning can have losses from two of their own sessions counted in one firm day. Every breach explanation should show the time in server time and in the trader’s local time, and the dashboard should show a countdown to the next reset.
Trailing drawdown
Trailing maximum drawdown follows the account’s high-water mark, so a profitable run raises the floor. Traders who remember the starting floor are surprised to breach while still in profit overall. The explanation needs three numbers: the peak, the floor it set and the equity reading that crossed it. If your trailing floor stops moving once it reaches the starting balance, say so in the rules and in the explanation.
Spread, slippage, swap and commissions
“I didn’t hit the limit, the spread did.” Spreads widen at rollover and around news, stop orders slip, and swap and commissions are charged against equity. If your calculation includes them, the explanation should show the price the trader actually got and the market price at that moment. If the breach happened on a price your feed recorded and the wider market didn’t, that’s a different conversation, covered further down.
News windows and prohibited strategies
Rules against trading around high-impact news, copy trading across accounts, group hedging and latency arbitrage produce disputes about interpretation, not arithmetic. These need evidence of the pattern and a dated, versioned rule. We covered detection and evidence packs in detail in how operators detect copy trading, group hedging and payout fraud.
Consistency rules and minimum trading days
These rules usually block a payout rather than fail an account, but traders experience it the same way: they hit the profit target and didn’t get paid. A consistency rule that limits how much of total profit can come from one day needs a progress indicator in the dashboard. Otherwise the trader discovers it when they request the payout, which is the worst possible moment.
Platform and dashboard showing different numbers
The trading platform shows one equity figure and your dashboard shows another, because they update at different intervals or one has already applied swap. Pick one source of truth for rule evaluation, tell traders which one it is, and make sure the prop firm dashboard displays the same number the evaluation engine uses. If you run several platforms, such as MT5, cTrader, DXtrade and Match-Trader, check each one separately. They don’t all report equity the same way.
What a good breach explanation contains
A good explanation lets the trader check the arithmetic without contacting anyone. It has six parts:
- The rule, quoted from the version the trader bought. For example: “Daily loss limit: 5% of start-of-day balance, measured on equity including open positions.”
- The reference values: the start-of-day balance, the limit in dollars and the resulting equity floor.
- The exact moment: which trade, the time in server time and the trader’s local time, and the equity at that moment.
- The evidence: the equity curve for the day with the breach point marked, plus the trade log.
- What happens next: whether the account can be restarted, reset at a discount or retaken, as your rules allow.
- How to appeal: who reviews the case, what they check and how long it takes.
Put together, it reads something like this:
Hi Jonas, your account breached the daily loss limit on November 4.
The rule: daily loss limit of 5% of start-of-day balance ($100,000), measured on equity including open positions. Your equity floor for the day was $95,000.
What happened: your EURUSD position opened at 14:05 server time (15:05 your time). At 14:32 server time, equity reached $94,780, below the floor. The position later recovered and closed at a $1,480 loss, but the limit is checked continuously on equity, not on closed trades.
The chart below shows your equity for the day with the breach point marked.
Your options: you can restart this challenge size at the discounted reset price. If you think the price at 14:32 was wrong, reply to this message and our risk team will check it against our price feed.
That’s what Kenmore’s Breach Explainer produces on its own. It shows the specific trade, its time, the rule it broke and the equity curve as evidence, in the trader’s language and on the channel they asked on. The example on the Agentic Prop Firm CRM page is a trader asking on Telegram, in German, at 02:14. The reply explains that one trade at 14:32 pushed daily drawdown past 5%, includes the marked equity curve and lists the restart option under the firm’s rules.
One requirement makes this work. The explanation has to come from the account’s own trade log, equity history and rule parameters, never from a generic rules page. A model asked “why did this account fail” without that data will write something plausible and wrong. Our guide to MCP for forex brokers and prop firms explains how to give an agent that access safely.
Write rules that can be explained
Many disputes are settled or lost before the trader buys the challenge, in the wording of the rules. Before you change anything else, check that your rules do the following:
- Define every reference point: balance or equity, the snapshot time for start-of-day values and what counts toward equity.
- Publish the server time zone and the daily reset time.
- Version the rules, and evaluate every account against the version in force when the trader bought it.
- Give a worked example for every numeric rule in your FAQ.
- State in advance what happens after platform errors, outages and bad ticks.
Our guide to designing a prop firm challenge goes through rules, phases and parameters in more depth.
The data you need to settle a dispute
You can’t settle an argument you can’t replay. For every account, store equity snapshots often enough to reproduce the breach moment, every trade with open and close prices and times, the bid and ask feed around the breach, the rule version the account was evaluated against and the full message history of the dispute. If any of that is missing, your risk team ends up deciding on trust, and so does the trader. The risk management module is where most of this data should already live.
A dispute workflow in four tiers
| Tier | Who handles it | What happens | Possible outcomes |
|---|---|---|---|
| 0. Self-serve | Dashboard or AI agent | Explanation with evidence, on request, in the trader’s language | Trader accepts, or escalates |
| 1. Support | Support agent | Adds context, checks for obvious errors, answers follow-ups | Closed with explanation, or escalated |
| 2. Risk review | Risk desk | Checks the price feed, platform logs and rule interpretation | Breach upheld or reversed |
| 3. Goodwill | Risk or operations lead | Decides on a reset, discount or refund | Approved by a person and logged |
Two rules hold this together. First, nobody below the risk desk can reverse a breach, and nobody at any tier can change the rules for an individual trader. Kenmore’s Decision Engine puts that action in the “never” tier. Once one trader gets a private exception, the rest of their trading community will ask for the same one.
Second, challenge resets and goodwill gestures are “ask first” actions. An AI agent or a support rep can propose one with evidence, and a person with authority approves it. The full logic for sorting actions this way is in our guide to AI agent permissions in a forex brokerage. It’s written for brokers, and the structure carries over to prop firms unchanged.
Tier 0 changes what a support morning looks like. In the example on Kenmore’s product page, 40 tickets arrived overnight. The Trader Support Agent answered 31 of them (status, rules and payout dates) and handed the other 9 to the support lead with summaries, so his day starts with the cases that need a person.
When the firm is wrong
Sometimes the trader is right. A bad tick from a liquidity provider, a platform freeze, an outage during the daily reset or a misconfigured challenge can all produce a breach the trader didn’t cause. Decide in advance what you’ll do in each case: reinstate the account at its pre-breach equity, refund the fee or offer a free retake. Write down the test you’ll apply. For example: was the price at that timestamp outside the range quoted by your other liquidity sources?
Reverse wrong breaches quickly, using the same standard of evidence you use to uphold them. Traders compare notes, and consistency is what they check.

Payout pre-checks: the other half of the problem
Disputes don’t stop at breaches. A funded trader who requests a payout and gets refused feels it more, because real money is involved. Kenmore’s Payout Pre-Check runs a six-point checklist as soon as a request arrives:
| Check | What to verify | Where it usually goes wrong |
|---|---|---|
| Profit target met | Closed profit against the target, after commissions and swap | Target reached on equity but not yet closed |
| Minimum trading days | Days with qualifying trades, by your definition of a trading day | Trader counts days in local time, the firm counts in server time |
| Consistency rule | The largest single day’s profit as a share of total profit | One news day carries the whole result |
| KYC | Identity verified and the name matches the payout method | Payout account in someone else’s name |
| No open breach | No breach or pending review on the account | A review still open from an earlier dispute |
| No prohibited-strategy flags | Copy trading, hedging across accounts, latency patterns | Mirrored trades on a linked account |
A pre-check checks. It doesn’t decide. In Kenmore’s setup no payout is ever approved automatically. The agent presents each case as clean or flagged, with the evidence attached, and someone on the risk desk approves with one click. In the product page example, 14 payouts were pre-checked overnight. Twelve came back clean and two were flagged, one for the consistency rule and one for trades mirrored on another account. The risk manager approved the twelve in about a minute and spent her time on the two that needed it.
That split matters for more than speed. When every case lands in the approval queue looking the same, reviewers start approving on autopilot. When clean and flagged cases arrive separately, the reviewer’s attention goes where the risk is. For the payment side (rails, timing, crypto versus bank transfers), see how brokers and prop firms handle withdrawals.
Prevent the dispute before the breach
The cheapest dispute is the one that never starts. Three changes do most of the work.
Show remaining drawdown live, in dollars, against the same numbers the evaluation engine uses. A trader who can see “$1,240 left today” makes different decisions from one who has to calculate it.
Offer warnings as limits approach. Kenmore’s Drawdown Guard is enabled by the firm and switched on by the trader, who gets a warning as they near the daily or overall loss limit. In the product example, a trader who has just breached buys a new challenge, turns Drawdown Guard on and gets warned at 80% of the daily limit.
Explain the rules at purchase, with worked examples, inside the checkout or onboarding flow. A PDF linked from the footer doesn’t count. A trader who has worked through the equity-versus-balance example before placing a trade won’t be surprised by it after a breach.
Metrics worth tracking
- Breach disputes closed on first reply
- Tickets resolved without a human
- Payout approval time
- Chargeback rate on accounts that failed a challenge
- Repurchase rate after a failed challenge
- Breach reversals by cause: bad tick, platform issue or misconfiguration
The first three are on Kenmore’s agentic scorecard. The last one tells you where your own systems are creating disputes, which is the list to fix first. For the operational side of running all this, our overview of prop firm CRM software covers the full challenge lifecycle.
Frequently asked questions
Should prop firms refund failed challenges?
Not as a general policy, because the fee pays for the evaluation. Refund or reinstate when the firm’s own systems caused the breach, such as bad ticks, outages or a misconfigured challenge. Publish those criteria so the decision doesn’t look discretionary.
How quickly should a breach dispute get a response?
The first explanation can be immediate, because all the data already exists the moment the breach happens. Human review should have a published response time that your risk desk can actually meet.
Can an AI agent explain breaches accurately?
Yes, if it reads the account’s own trade log, equity history and rule parameters. Without that data it will produce a plausible general answer that may be wrong for this account. Accuracy depends on data access and on a field dictionary that defines every rule parameter.
Who should be allowed to reset a challenge?
Treat a reset as an “ask first” action. Support or an AI agent can propose it with the evidence, and someone on the risk desk approves. Nobody should be able to change the rules for one trader.
What’s the fastest way to reduce breach tickets?
Show live remaining drawdown in the dashboard, add a worked equity-versus-balance example to onboarding and make the breach explanation self-serve. Each of these answers a breach question before anyone has to ask it.
Request a Consultation on Reducing Prop Firm Breach Disputes
Get expert guidance on explaining breaches with evidence, pre-checking payouts and keeping your support queue under control. We’ll help you tighten rule definitions, set up a tiered dispute workflow and give traders clear answers from their own account data, in their own language.
Together, we’ll review your challenge rules, dispute history and payout process and outline the changes that cut tickets, chargebacks and negative reviews.