A FundingPips customer says a difference of just $7.07 between the equity captured by the prop firm’s risk system and the balance visible in MetaTrader 5 led to the permanent termination of a funded account, raising a broader question over what evidence traders can access when automated drawdown systems record a breach that is not visible on their trading terminal.
The October 6 Trustpilot reviewer describes himself as a premium or VIP FundingPips customer who had purchased more than 12 accounts and successfully passed five of them. According to the complaint, his Live Funded Master Account, number 20973645, was permanently terminated after FundingPips’ system recorded what the trader describes as a $7.07 floating-equity discrepancy.
The customer says MetaTrader 5 showed that all positions had been liquidated and closed with a balance of $24,052.92. He argues that this figure remained within the permitted loss limits, while FundingPips’ backend allegedly captured a slightly lower equity value and treated the account as having crossed its breach threshold.
The allegation has not been independently verified. The reviewer did not publish the complete account statement, exact breach threshold, affected instruments, position sizes, server timestamps or tick-by-tick equity data needed to reconstruct the event. No case-specific public response from FundingPips establishing the accuracy of the disputed equity reading was identified.
FundingPips Says Its Server-Side Equity Record Is Final
FundingPips’ published trading mechanics provide important context because they directly address situations where a customer’s terminal and the company’s risk system appear to disagree.
The firm says its risk-management systems monitor account equity continuously on the backend. Its documentation states that if a breach occurs, server-side data is considered final regardless of any lag or delay visible locally in the trading terminal or dashboard.
That makes this case different from a simple argument that the MetaTrader balance should automatically override FundingPips’ records.
FundingPips currently operates several account models with different maximum-loss and daily-loss structures, while accounts purchased before September 28, 2026 can fall under separate legacy rules. The October 6 reviewer does not publicly identify the precise account model or purchase date, making it impossible from the available information to independently calculate the exact equity floor that applied to account 20973645.
Across its published models, however, FundingPips makes clear that floating losses can count toward a breach and that hard loss-limit violations can result in immediate account closure. Dave Finances recently examined a separate FundingPips dispute over a drawdown breach after a trader alleged that stop-loss slippage during a news event pushed a profitable account through its limit.
A $24,052.92 Closing Balance Does Not Reveal the Lowest Intraday Equity
The distinction between balance and equity is central to the new complaint.
According to official MetaTrader 5 documentation, account equity reflects the balance adjusted for factors including commissions and floating profit or loss on open positions. Balance, by contrast, primarily reflects realized account results after positions are closed.
This means a final balance of $24,052.92 does not by itself establish that the account’s equity never dipped below a FundingPips threshold seconds earlier.
An open position could briefly produce a larger unrealized loss before recovering slightly during liquidation. Spread changes, commissions, rapid price movement and differences in when individual systems sample account state can also cause the lowest recorded equity to differ from the figure eventually visible after all positions have closed.
A similar evidentiary problem appeared in a recent Blue Guardian account-breach dispute, where a trader questioned why visible losses appeared smaller than the amount necessary to trigger the firm’s automated equity limit. In that case, the key missing information was also the minimum server-recorded equity and the precise timestamp at which the threshold was crossed.
The Trader Says FundingPips Would Not Release the Underlying Records
The strongest part of the October 6 complaint is therefore not necessarily the $7.07 figure itself. It is the trader’s claim that the records needed to verify that figure were not provided.
The reviewer says he requested server logs, timestamps and tick data showing how FundingPips determined the breach. According to the customer, support declined to provide the information and treated the relevant records as internal.
That claim also remains unverified. Dave Finances has not seen the support conversation or established exactly what records were requested, what FundingPips provided in response or whether the firm’s customer terms require those records to be disclosed.
But technically, the dispute should be reconstructable.
The important data points would include the account’s applicable daily or maximum-loss floor, the lowest equity recorded by FundingPips, the exact server timestamp of that reading, the open positions at that instant and the bid-and-ask prices used to calculate their unrealized P&L.
If those records show equity moving $7.07 through a valid threshold before recovering during liquidation, FundingPips’ decision would be consistent with its published rule that a momentary server-side breach remains a breach.
If the server records never show the account crossing the applicable floor, or if the disputed equity value cannot be reconciled with the underlying prices and positions, the customer’s allegation would become substantially more serious.
Prop Trading Turns Tiny Data Differences Into Account-Level Events
The wider issue is that prop-firm risk engines give small differences in account data unusually large economic consequences.
In a conventional brokerage account, a temporary $7 pricing or equity discrepancy might create a slightly different P&L result. On a funded prop account sitting directly against a hard drawdown threshold, the same difference can determine whether the entire account survives.
That changes the importance of infrastructure transparency.
Retail traders interact primarily with the frontend they can see: MetaTrader, a web terminal or a dashboard. The firm, however, may enforce rules using a different backend process that samples equity more frequently, receives prices at slightly different moments or records values the frontend never visibly displays.
This does not automatically mean the backend is wrong. Client software can lag, interfaces can refresh more slowly than servers and a brief loss can disappear before a trader visually registers it. Recent allegations involving platform lag and synchronization problems have demonstrated how differently the same trading event can appear at the interface and execution layers.
But if the backend is contractually authoritative, then the backend also becomes the evidence that ultimately matters when a customer challenges an enforcement decision.
FundingPips Has a Transparency Problem to Manage Even If the Breach Was Correct
There is an important distinction between proving that FundingPips made an incorrect decision and questioning whether its dispute process gives customers enough information to test that decision.
The current public evidence does not prove the account was wrongly terminated.
In fact, FundingPips’ published rules strengthen the company’s position on one key point: a local MetaTrader display is not necessarily the controlling record. The company explicitly says its backend monitoring remains authoritative when local displays lag.
But that policy creates a corresponding trust problem if customers cannot obtain enough information to reconcile an irreversible breach.
FundingPips does not necessarily need to disclose proprietary risk-engine architecture, infrastructure providers or every internal monitoring mechanism. A trader contesting a drawdown breach does not need the firm’s source code.
They need a much smaller set of facts: the threshold, the lowest equity, the timestamp and the prices that produced it.
This issue has appeared elsewhere in recent FundingPips account termination disputes, where customers similarly questioned the evidence underlying automated or technical enforcement decisions. The individual allegations are different, but the commercial problem is similar: the firm controls the data used to terminate the account while the trader has limited ability to independently audit that decision.
The $7.07 Is Small, but the Precedent Is Not
A seven-dollar difference sounds trivial in isolation. On a prop account, it is not.
The value traders are protecting is not merely the $7.07. It is the evaluation fees already paid, the time required to pass an account, the remaining earning opportunity and any future payouts that depend on keeping the account active.
That is why increasingly automated prop-trading businesses may eventually need more standardized breach receipts: an automatically generated record showing the applicable rule, threshold, lowest equity, timestamp and relevant account state whenever a hard breach occurs.
Such a system would not prevent traders from disputing the outcome, but it would move arguments away from screenshots and recollections and toward auditable numbers.
For FundingPips, the October 6 review remains a single unverified customer allegation and is not evidence that its equity engine systematically calculates accounts incorrectly. The firm’s own published rules also provide a plausible explanation for why the trader’s MT5 display and backend risk record might not match.
The unanswered question is narrower and more important: if a difference of only a few dollars can permanently terminate a funded account, can the company show the trader exactly when those few dollars existed?
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape.