Prop Firm EA Rules 2026: Practical Checklist

Prop firm EA rules 2026 are not defined by one industry-wide standard. Every firm can set its own conditions, and those conditions may differ between account types, platforms, evaluation stages and funded stages.

The fact that a firm allows Expert Advisors does not mean every EA, setfile or trade copier is acceptable. Traders need to check both the general trading rules and the specific rules that apply to automation.

EA permission is usually conditional

Prop firms generally take one of three approaches to automated trading.

Some firms allow EAs as long as the strategy trades under normal market conditions and does not exploit technical weaknesses. Others allow EAs only after checking the software or receiving information about how it works. A third group restricts certain types of automation, even though ordinary trade management tools may still be accepted.

For example, the official FTMO strategy FAQ allows algorithmic trading while maintaining restrictions against forbidden trading practices. FundedNext publishes a separate EA policy, while the FXIFY EA rules describe a pre-approval process.

This is why a simple statement such as "EAs are allowed" is not enough. The trader still needs to confirm what kind of EA is allowed and under which account conditions.

Check the rules at every level

Before running an EA, read the rules for:

• The prop firm itself
• The exact challenge or account model
• The trading platform being used
• The evaluation and funded stages
• The relevant trading instruments
• News, weekend and overnight trading
• Copy trading and account management
• Server activity and order frequency

A rule shown on a general FAQ page may not apply to every product. Terms can also change after a trader has purchased a challenge.

Save a dated copy of the applicable rules and support response. This gives you a reference if the website is updated later.

Our FTMO overview, FundedNext guide and FXIFY guide can help organise the first comparison, but the prop firm's current written terms remain decisive.

Commonly prohibited forms of automation

Most prop firms are concerned about how an EA trades, not simply whether code is involved.

Automation is more likely to cause problems when it attempts to exploit delayed prices, data-feed differences, execution errors or unusually fast order handling. Strategies built around latency exploitation, server flooding or unrealistic fills may be rejected even when the platform technically accepts the orders.

Cross-account behaviour is another sensitive area. Coordinated trading, opposite positions across related accounts, account sharing and copying trades from an unknown third party can trigger a review.

An EA should also not be designed to bypass daily loss limits, maximum loss rules, consistency requirements or other account restrictions. Hiding exposure across several positions does not change the underlying risk.

The practical test is straightforward: would the same strategy still make sense with normal spreads, slippage and execution? If the edge disappears as soon as market conditions become realistic, it is unlikely to be suitable for a prop account.

Third-party EAs and identical trading patterns

A widely distributed EA can create a problem even when its strategy is legitimate.

If many traders use the same software with the same setfile, they may open nearly identical positions. A prop firm may interpret those accounts as coordinated or copied activity. This risk becomes more serious when every user has the same entry time, stop loss, take profit and position-management sequence.

Changing the magic number or trade comment does not make the strategy unique. Those fields identify orders, but they do not alter the underlying trading pattern.

Where permitted, traders can use settings appropriate to their own account, risk tolerance and broker conditions. However, randomising settings purely to avoid detection is not a sensible solution. The configuration should remain logically connected to the strategy.

Ask the software provider whether the EA is widely distributed, whether setfiles can be customised and whether the strategy depends on identical execution across users.

Strategy consistency matters

Some prop firms compare how an account was traded during evaluation with how it is traded afterwards.

A trader who passes using manual swing trades and then immediately switches to an aggressive automated strategy may face questions. The same applies when the funded-stage EA uses materially different instruments, holding periods or exposure.

Consistency does not mean that every trade must look identical. It means the core trading method and risk behaviour should remain recognisable.

Decide how the EA will be used before starting the evaluation. If the intention is to use automation later, it is usually cleaner to validate that same approach during the challenge, provided the firm's rules permit it.

No EA can promise that a challenge will be passed. Software can enforce execution and risk controls, but it cannot control spreads, slippage, market gaps or the sequence of winning and losing trades.

Risk settings must match the prop account

A setfile designed for a personal trading account may be unsuitable for prop-firm rules.

Check whether the EA calculates risk from balance or equity. Review how it handles several open positions, correlated symbols, partial closes, trailing stops and pending orders. Basket risk is particularly important because several individually small trades can create substantial combined exposure.

The EA should recognise the prop firm's reset time for daily limits. It should also include commissions, swaps and floating P/L when monitoring equity.

Useful controls include:

• A daily loss stop
• A total equity floor
• A maximum number of open positions
• A cap on combined symbol exposure
• A spread filter
• A session filter
• A cooldown after losses
• A manual emergency stop

These controls should sit comfortably inside the firm's official limits. Using the full permitted loss allowance leaves little room for execution differences.

Test the complete operating setup

Backtesting the entry logic is only part of the work.

Run the EA in a simulated environment using the same broker conditions, symbol names, contract specifications and account currency expected during the challenge. Confirm that lot sizing, stops, partial closes and session times behave correctly.

Restart the terminal and check whether the EA reconstructs its state. Test what happens after a lost connection, rejected order, spread spike or manual intervention. An EA that forgets its basket state after a restart can behave differently from the strategy that was tested.

Trade copiers need the same attention. They may support MT4, MT5, cTrader, DXtrade, TradingView and other platforms, but symbol mapping, lot scaling and execution rules still require validation.

Obtain written confirmation

When a rule is unclear, contact the prop firm's support team before trading.

Describe the EA accurately without disclosing proprietary source code. Explain whether it opens trades, copies trades, manages existing positions or performs both functions. Ask whether approval is required and whether any restrictions apply to third-party software.

Keep the response. A Discord comment or statement from another trader is not a substitute for confirmation from the firm.

Final pre-launch checklist

Before connecting an EA:

• Download the latest account rules
• Confirm EA and copier permission
• Check prohibited strategy definitions
• Confirm news and holding restrictions
• Verify daily reset time
• Identify whether drawdown is static or trailing
• Test risk using equity, costs and floating positions
• Validate all broker symbols
• Test terminal restarts and connection loss
• Keep logs and written approval
• Start with the intended strategy configuration
• Monitor the first trading sessions closely

For a practical view of the software, controls and account-side setup, continue with the JPTC EA Hub overview.