Read the average prop-firm forum thread and you’ll see the same story on repeat.
A trader passes the challenge. Maybe FTMO 100K, maybe FundedNext, maybe MyFundedFX. They get the funded account. They connect the same EA that got them through evaluation — the one that ran clean, hit the profit target, made it look easy. A week later the account is closed. Rule violation. No detailed explanation, just the notice.
The forum reaction is always identical. Prop firms are a scam. They wait until you’re profitable, then they find a technicality. They don’t want to pay. Every thread on r/FTMO, MQL5, and half of Trader Twitter runs the same script.
Here’s the uncomfortable part: the prop firm isn’t lying. In almost every case, the trader actually did violate a rule. They just didn’t know which one — because the rule they broke wasn’t the one they were watching.
FTMO explicitly allows Expert Advisors. So do FundedNext, The5%ers, MyFundedFX, and Topstep. There is no pre-approval process. There is no source-code submission. Running an automated strategy on a prop account is a normal, expected thing in 2026. The line has never been “EAs banned” versus “EAs allowed.” The line is a small, specific list of technical triggers that will close your account regardless of whether your EA is technically permitted. If you’re new to the concept, our explainer What is a MetaTrader Expert Advisor and how does it work? covers the fundamentals.
Most traders read the homepage — “EAs permitted” — and skip clause 5.4 of the Terms. That’s where the actual account-killers live. Not in the strategy itself. In how the strategy interacts with the platform.
This article breaks down what those triggers actually are in 2026, based on the current FTMO Forbidden Trading Practices page and how major prop firms enforce their rules right now. We’ll show you five patterns that get accounts closed. We’ll tell you which ones your EA is probably triggering without you knowing. And we’ll tell you honestly which of those patterns Nordman Connector helps with — and which are on you to solve.
Your EA isn’t getting banned because prop firms hate automation. It’s getting banned because your EA is doing three things you didn’t design it to do.
If you’re running an EA on a funded account and you’re not sure what those three things are, reading on will save you a challenge fee. If you’re about to buy a “prop-firm EA” from an MQL5 marketplace, reading on will save you more than that.
Everyone talks about the 5% daily loss cap. Everyone talks about the 10% max drawdown. Those aren’t the ones that catch you off guard. Those are the ones you’re watching.
The triggers that actually close accounts are structural. Your EA hits them without you knowing they exist.
FTMO’s Forbidden Trading Practices page states it plainly: an EA that causes “an excessive number of more than 2,000 server requests per day on individual simulated trades or pending orders being opened, modified, or closed” is grounds for corrective action, up to termination.
Most traders never think about this number. They see their EA opens 10 trades a day and assume they’re nowhere near a limit. What they miss is that every modification counts as a request. Every tick-by-tick stop-loss trail. Every pending order adjustment. Every partial close. Every trailing-take-profit recalculation.
An EA that trails a stop-loss on every new tick during the London session can fire hundreds of modification requests per hour — hypothetically crossing the daily cap before lunch on a volatile day. It never opens a bad trade. It never violates drawdown. And it still closes the account, because it’s classified as platform abuse.
If your EA modifies orders on tick events, you should audit its request count against a full trading day. Most retail-built EAs weren’t designed with this constraint in mind.
This is the one that gets the strictest enforcement across every serious prop firm. FTMO, FundedNext, MyFundedFX, Topstep — all of them treat latency arbitrage as a hard ban, not a warning.
The definition is broader than most traders realise. It doesn’t just mean running an EA that reads a faster feed than the broker’s. It includes any strategy where the entry logic depends on the trader being faster than the market price update. Tick-scalping systems that flip in and out within seconds fall under this umbrella. So do strategies that fire on price gaps between the broker’s feed and an external data source.
The technical detection is straightforward. Prop-firm risk systems flag accounts where average trade duration is under a firm-specific threshold (often under a minute) combined with a high win rate on entries taken during price micro-gaps. Once flagged, the review looks at the entry timing relative to price movement. If your EA is consistently entering on the tick immediately preceding a favourable move, the account is closed.
The uncomfortable follow-on: a legitimate scalping strategy can look like latency arbitrage to an automated review system. On a hypothetical setup — say you scalp EURUSD with 3–5 tick targets and your win rate sits above 65% — you’re going to get looked at. This isn’t a reason not to scalp — it’s a reason to expect scrutiny and keep your entry logic documented.
This one catches even careful traders because it’s not consistent across account types.
On the FTMO Challenge and Verification stages, news trading is unrestricted. Traders spend two months getting used to trading through NFP, CPI, and FOMC without any restriction. Then they hit the funded stage on a Standard account and the rule flips: according to FTMO’s current terms, no new positions within 2 minutes before or 2 minutes after a scheduled high-impact release.
Traders don’t realise the rule changed. Their EA is still configured the same way it was during evaluation. On the funded account, one trade opened 90 seconds before NFP is enough to close the account.
The Swing account has no news restriction, but comes with lower leverage. If your strategy trades news, the Standard account will kill you and the Swing account will limit your position size. Most retail traders default to Standard because it looks better on paper and never adjust.
If you need to track macro release schedules directly on your chart, tools like the MT4 News Indicator or NinjaTrader News Indicator display upcoming events with countdown timers. But knowing when a release hits and preventing your EA from trading during the window are two different problems — and most retail EAs don’t solve the second one.
The rule as of mid-2026 on FTMO Standard funded accounts: 2 minutes before, 2 minutes after. Confirm this on FTMO’s current terms before you run any EA that fires during macro releases. Rules on this shift once or twice a year.
Here’s the honest layout of what actually happens with each strategy type in 2026. Save this. Screenshot it. This is the part that ends most arguments.
| Strategy Type | Prop-Firm Status | What Actually Happens |
|---|---|---|
| HFT / Latency Arbitrage | STRICT BAN | Automated review flags account within days. Termination with no payout. |
| Tick Scalping (sub-30s trades) | HIGH RISK | Not banned outright but reviewed aggressively. Consistent sub-minute duration + high win rate = flag. |
| Grid / Martingale | FLAGGED, NOT BANNED | FTMO and FundedNext both allow. Account triggers manual review. One bad sequence blows the daily cap in one move. |
| Third-party EA (widely adopted) | CAPITAL ALLOCATION RISK | FTMO imposes a $400,000 capital allocation limit per trader or strategy across all accounts. Popular MQL5 marketplace EAs can trigger this across multiple clients running the same code. Verify current limits in FTMO’s FAQ and Terms & Conditions. |
| Hyperactive EA (>2000 req/day) | AUTO-TERMINATION | Flagged by platform, not by risk team. No exception. |
| News trading on Standard funded | STRICT BAN | 2-minute window before/after high-impact events on FTMO Standard funded accounts. Applies on funded stage only. |
| News trading on Swing funded | PERMITTED | Lower leverage caps make aggressive news scalping structurally unprofitable anyway. |
| Copy trading from external analytical outputs | CASE-BY-CASE | Reviewed manually. Third-party analytical output following often denied. Your own setups across your own accounts — permitted. |
| Discretionary EA (trader-approved entries) | FULLY PERMITTED | Semi-automated tools like bracket-order managers and one-click panels are welcomed. |
If you’re in the top four rows and you’re not sure your account is safe, keep reading. If you’re in the bottom four rows, your risk is procedural, not structural.
Most traders debating prop-firm bans argue about the strategy. Is grid banned. Is martingale banned. Can I scalp. Can I run news.
Almost nobody talks about how the EA actually behaves under real conditions. That’s where accounts die.
Three patterns keep showing up in retail-built EAs that pass evaluation and blow the funded account inside a week:
That last point matters more than the other three combined. Here’s the good news buried in all of this: not one of these patterns is your strategy. Retry loops, tick-by-tick modifications, uncapped request counts — that’s implementation, not edge. Your entry logic didn’t get your account closed. The code around it did. And code can be re-engineered.
Everything in the previous section is an engineering problem, not a strategy problem. Which means it has an engineering solution — one that doesn’t touch your entry logic.
What that looks like in practice:
This is the specific work we do at Nordman Algorithms: auditing existing EAs against prop-firm technical constraints and rebuilding the parts that generate violations, or developing an EA from scratch to your specification. Your strategy logic stays yours. We re-engineer how it talks to the platform.
Two things we won’t do. We won’t make a losing strategy profitable — your edge is your math, and a technically clean EA that loses money just loses it cleanly. And we don’t build HFT or latency-arbitrage systems — the strategy itself is banned, and no engineering makes it legitimate.
Request an EA Audit or Custom Build →
Running your strategy from TradingView alerts instead of a local EA? Then the execution-layer problem is already solved off-the-shelf — that’s Nordman Connector, a cloud copier with ~0.5s webhook execution (based on our internal measurements). The cloud server receives and validates each TradingView alert, the Receiver EA inside your terminal places the order — no custom code, no symbol mapping. Routes: TradingView to MT4, TradingView to MT5, TradingView to NinjaTrader. One subscription, €25/month, 5-day free trial.
Either way, if you want to see our infrastructure running before you talk to us: Nordman Algorithms YouTube playlists — real setups, real orders landing.
Nordman Algorithms provides software infrastructure for trade automation and does not offer financial advice, trading recommendations, or managed trading services. This article is for informational and educational purposes only. Trading leveraged instruments such as Forex and CFDs carries a high level of risk and may not be suitable for all investors — only risk capital should be used. Full Risk Disclosure: nordman-algorithms.com/risk-disclosure
