Prop Firm EA for MT5: Rules, Setup, and Checks
By FXNook Lab team
You can use an MT5 EA on a prop firm account only if that firm’s current rules allow it and the EA follows the account’s conditions. MT5 compatibility by itself does not grant permission to automate trading, and no EA can guarantee compliance or a successful evaluation. Start with the firm’s rules, then match the EA to the account and test its behavior against the firm’s loss definitions.
Can you use an EA on a prop firm MT5 account?
There is no single rule for every prop firm. Some allow custom Expert Advisors, some place limits on automation or third-party tools, and others prohibit particular strategies or account arrangements. The answer may also depend on whether the account is in an evaluation phase or another stage, and on the specific account type.
MT5 is the trading platform, not the firm’s permission system. An EA may compile and send orders successfully while still violating a firm rule. Conversely, an EA that is permitted can fail to trade because of an MT5 setting, a broker condition, or an error in its own logic.
Separate these questions before attaching an EA: does the firm permit this method of trading, and can this EA operate correctly under the account’s technical conditions? Treat the firm’s rules as the authority for the first question. The EA’s inputs, logs, and testing can help answer the second, but cannot prove that the firm will accept its behavior.
Check the firm’s EA and trading rules first
Read the rules that apply to the exact account and stage you intend to use. Do not rely only on a general FAQ, an old saved screenshot, or a statement about a different account type. If the wording is unclear, ask the firm for a written answer and keep a copy of the applicable rules and their version or date.
- Automated trading: Is automated order placement allowed, and are there limits on how the EA may make or manage trades?
- Third-party EAs: May you run an EA you wrote, bought, or generated with a tool? Does the firm require you to disclose or approve it?
- VPS use: Is a virtual private server allowed? If so, are there location, provider, or account-access conditions?
- Copy trading: Are trade copiers, account mirroring, or shared signals allowed? Do the rules distinguish copying your own accounts from copying another trader?
- News restrictions: Are there limits on opening, closing, or holding trades around specified news events? Does the rule apply to pending orders as well as market orders?
- Weekend holding: Can positions remain open over the weekend or through a market close? Are there different conditions for particular instruments?
- Simultaneous accounts: Are multiple accounts permitted, and are there restrictions on running the same EA or taking correlated trades across them?
- Prohibited execution behavior: Do the rules restrict practices such as latency exploitation, price-feed abuse, or other forms of execution manipulation? Use the firm’s own definitions rather than guessing what a term covers.
These are firm-specific questions, not MT5 settings. A setting in the EA cannot make a prohibited method permitted. Likewise, a broker accepting an order does not establish that the prop firm allows the strategy behind it.
Save the relevant policy text and any written clarification before testing. Rules can change, and an EA setup that was permitted under an earlier version may not fit a later one. Recheck the current conditions before using the account, especially after a rule update or a change in account stage.
Match the EA to the account’s MT5 conditions
Prop firm accounts may use different brokers, server configurations, symbol names, contract specifications, and trading sessions. An EA developed on one demo account can therefore behave differently on another account even when both use MT5. Compare the account’s symbol specifications with the assumptions in the EA rather than copying settings from a different broker.
| Account condition | What to inspect in MT5 | EA setting or behavior to review |
|---|---|---|
| Symbol name | Market Watch and the symbol’s exact name, including any suffix or prefix | Whether the EA uses the chart symbol or a hard-coded name. A rule for EURUSD may not match a broker’s EURUSD variant. |
| Volume rules | Minimum volume, maximum volume, and volume step in the symbol specification | Whether calculated lots are rounded to a valid step and kept within the account’s allowed range. An invalid lot size can be rejected. |
| Contract and price details | Contract size, tick size, tick value, digits, and point size | Position sizing, stop distance, spread limits, and calculations that assume a particular number of digits or value per point. |
| Trading hours | The symbol’s sessions and the server time shown by the terminal | Session filters and news or time rules. Local computer time may differ from broker server time. |
| Execution and filling | The account’s execution conditions and supported order filling modes | Whether the EA selects a supported filling mode. In MQL5, CTrade provides SetTypeFillingBySymbol for selecting a mode based on the symbol. |
| Stop requirements | Minimum stop distance and any freeze-level restrictions in the symbol specification | Whether stop-loss, take-profit, and modification requests leave enough distance from the current price. |
| Account position mode | Whether the account uses netting or hedging | Whether the EA expects one position per symbol or manages multiple positions separately. Position-handling logic must fit the account mode. |
In MT5, the symbol specification is available from Market Watch by opening the symbol’s specification. MQL5 code can also query properties with functions such as SymbolInfoDouble and SymbolInfoInteger. For example, volume calculations should use the symbol’s volume minimum, maximum, and step rather than assuming a fixed lot increment.
Do not confuse points, pips, and price units in an EA input. A spread threshold or stop distance written for one quote format can be wrong on a symbol with a different number of digits. Fractional pricing, symbol suffixes, and contract differences are common reasons an EA’s filters or position sizing behave unexpectedly after moving it to another account.
Position handling matters too. An EA designed around separately ticketed positions may not manage trades the way its author expects on a netting account, where positions in the same symbol are combined. In MT5, functions such as PositionSelect and the CTrade class are part of position management; the EA’s assumptions need to match the account’s mode and its own trade-management logic.
Configure risk controls for the firm’s limits
Read the firm’s definition of daily loss and overall loss before entering numbers into an EA. The calculation may involve balance, equity, closed profit and loss, floating profit and loss, commissions, swaps, or a combination. Reset times and time zones can also differ, so do not assume a daily limit resets at midnight on your computer.
Overall loss rules can be static or may use a changing threshold, depending on the firm’s terms. A trailing threshold, for example, needs different monitoring from a fixed starting balance threshold. Use the written definitions for the account you have; a balance-only EA guard is not enough if the firm measures equity or includes open losses.
Review these controls in the EA and determine what happens when each one is reached:
- Position sizing: Identify whether lots are fixed, based on a percentage, or calculated from stop distance. Verify the calculation against the account’s contract and tick values, and make sure the final volume fits the symbol’s minimum and step.
- Maximum exposure: Set or verify limits for open trades, total lots, and simultaneous positions. Include pending orders if they can later become positions.
- Daily loss response: Establish whether the EA stops opening trades, closes positions, or takes another action at its own threshold. Decide how it handles a reset and whether it uses the firm’s server-day boundary.
- Overall loss response: Set a conservative internal stop point below the firm’s stated limit, with room for floating losses and execution changes where the account rules require them. The EA’s threshold should be based on the firm’s actual calculation, not a guessed balance figure.
- Equity changes: Find out whether the EA reads account equity or balance and whether it refreshes its baseline after a restart. A terminal restart should not silently reset a daily loss counter if the firm’s day is still in progress.
- Failure behavior: Decide what the EA should do if it cannot read a required value, loses a connection, or cannot close a trade. Its response should be visible and should not falsely report that a limit is enforced when it is not.
An EA’s internal risk stop is a guardrail, not the firm’s official limit system. It may not account for every fee, server-side rule, open order, or calculation detail used by the firm. Leave a margin below the stated threshold and monitor the account’s own equity and status rather than relying on the EA alone.
Test the EA on a matching MT5 account
Test in stages so a code problem, a settings problem, and a firm-rule question do not get mixed together. A successful compile only shows that MetaEditor accepted the code; it does not prove that orders will be accepted or that the EA follows a firm’s rules. Use the same MT5 platform version, symbol conditions, account mode, and relevant inputs as closely as possible.
- Compile for MT5. Open the EA’s .mq5 source in MetaEditor and compile it for MT5. If the source is .mq4, it is not made into an MT5 EA by changing the file extension. A conversion needs to account for differences such as MT4 orders versus MT5 positions and indicator handles.
- Review every input. Confirm the symbol, timeframe, lot calculation, stop and target units, spread and session filters, maximum trades, and loss thresholds. Make sure time-based settings refer to the clock the EA actually uses.
- Run the Strategy Tester. Select the intended symbol and timeframe, set the test period and deposit appropriately, and use the most suitable tick model available for the test. Inspect the Journal and Experts output as well as the trade list, including periods when the EA is expected to wait.
- Test limit behavior deliberately. Use controlled test conditions to see whether the EA stops new entries at its own daily and overall thresholds, handles open positions as designed, and behaves correctly after a terminal restart. Do not infer that the firm will calculate losses in the same way unless its rules say so.
- Forward-test in an allowed environment. Run the EA on a demo account or another environment the firm permits. Compare the actual symbol specifications and server time with the target account. Do not use a live evaluation as the first test of basic EA behavior.
- Exercise operational conditions. Observe behavior during wider spreads, rejected requests, slippage, disconnections, and reconnections where the test environment allows. Confirm that the EA does not repeatedly send invalid requests or resume trading with an incorrect loss baseline.
MetaTrader’s Strategy Tester can help check logic against historical data, but it cannot reproduce every live execution condition or establish compliance with a prop firm’s rules. Forward testing also cannot guarantee future behavior. Past or tested results do not guarantee future results, and a technical test does not guarantee that an evaluation will be successful.
For the general process of attaching and testing an EA, see How to Use an EA in MT5: Setup, Test, and Run. If the tester itself is not behaving as expected, the guide to MT5 Strategy Tester fixes covers common test setup problems.
Troubleshoot an EA that does not trade
Start with the terminal’s Experts and Journal tabs. The Experts tab shows EA messages and trade activity; the Journal records terminal events such as connection and trading-permission changes. Read the message at the time the EA should have acted, then compare it with the EA’s filters and the symbol’s conditions.
| Symptom or message | Where to look | Likely next check |
|---|---|---|
| No orders and no visible error | MT5 toolbar, EA properties, Experts tab | Make sure Algo Trading is enabled and that the EA is allowed to trade in its Common settings. Inspect the entry filters and whether the signal condition was reached. |
| EA reports a symbol it cannot find | Market Watch and EA inputs | Match the exact broker symbol, including its suffix or prefix, or configure the EA to use the chart symbol where appropriate. |
| Invalid volume | Experts tab and symbol specification | Compare requested volume with the symbol’s minimum, maximum, and step. In MQL5, trade result code 10014 means invalid volume. |
| Invalid stops | Experts tab and symbol specification | Check stop distance, price normalization, and whether a price moved before the request was processed. MQL5 trade result code 10016 means invalid stops. |
| Market closed or no entry during expected hours | Journal, symbol sessions, EA time inputs | Compare server time with the EA’s session filter and the symbol’s actual trading hours. MQL5 trade result code 10018 indicates that the market is closed. |
| Order rejected for filling mode | Experts tab and EA trade setup | Check whether the EA requests a filling mode supported for that symbol. A broker rejection is a technical or account-condition issue, not proof that the firm has approved the strategy. |
| EA is attached but does not enter | Experts tab, EA inputs, rule logic | Review spread, news, trading-hour, position-count, and signal filters. A filter can correctly block a trade even when the EA is running. |
Also inspect the EA’s own trade result handling. In MQL5, a successful call to CTrade.Buy or CTrade.Sell should not be treated as proof that the broker accepted the request; inspect the result with CTrade.ResultRetcode and its description. A rejected order may be caused by volume, stops, filling mode, permissions, market hours, or another account condition.
Distinguish a firm-rule restriction from an MT5 technical error. If the terminal reports Algo Trading disabled, invalid volume, or invalid stops, investigate the platform setting or request parameters. If the firm disallows a type of EA or trading behavior, changing those technical settings will not make the activity permitted.
For a broader MT5 diagnosis, see MT5 EA Not Taking Trades: Checks, Causes, and Fixes. FXNook Lab’s EA debugger can inspect an EA’s code and explain which logic or condition prevents it from trading; that code review does not replace checking the firm’s rules or testing on the relevant account.
Go live with a verification checklist
Before running an EA on an account where the firm’s rules apply, make one final pass through permission, configuration, and monitoring. Keep the checklist with the saved rule version and the EA version you tested. If the firm changes its terms, or the account is moved to a different stage or broker setup, repeat the relevant checks.
- The current firm rules permit this EA type, its source, and its method of operation.
- Any unclear rule has been confirmed with the firm, and the applicable rule version is saved.
- The EA uses the correct symbol, volume, contract, stop, session, and execution assumptions for the account.
- Position handling fits the account’s netting or hedging mode.
- Daily and overall loss controls reflect the firm’s written definitions, reset times, and treatment of equity and open trades.
- The EA has been tested with the intended inputs, and its behavior after a restart or connection interruption is understood.
- VPS use and any copying or simultaneous-account setup comply with the firm’s rules.
- You know where to monitor the terminal, how to stop the EA, and what behavior would make you stop it and investigate.
Keep monitoring after startup. Compare the account’s equity and trade history with the EA’s logs, especially around the firm’s daily reset and after connection interruptions. If live behavior differs from testing, stop the EA and identify the cause before restarting it; do not assume that the next trade will correct the discrepancy.
If the EA’s live decisions are hard to trace, FXNook Telemetry can report the rules it checks, decisions, orders, trades, and errors. It observes EA activity and does not place or change trades. The practical next step is to save the firm’s current rules, compare them with the account’s MT5 specifications, and test the EA under those conditions before using it on the account.
Questions
Are EAs allowed on prop firm MT5 accounts?
It depends on the prop firm, account type, and current rules. Check whether automated trading and your specific type of EA are permitted, including any conditions on VPS use, copying, or execution behavior. MT5 support alone does not mean the firm allows the EA.
Can I use a custom EA in a prop firm challenge?
Only if the challenge rules allow custom EAs and the EA’s behavior meets those rules. Ask the firm about unclear restrictions and keep its answer with the rule version that applies to your challenge. Test the EA on matching account conditions before relying on it.
Why is my MT5 EA not trading on a prop firm account?
The cause may be a disabled Algo Trading setting, a symbol mismatch, an entry filter, invalid volume or stops, a closed session, or a broker rejection. Read the Experts and Journal tabs at the time the EA should have traded, then compare the message with the symbol specification and EA inputs. A rule that prohibits the intended behavior is separate from a technical error.
How do I set EA risk limits for a prop firm account?
Use the firm’s written definitions for daily and overall loss, including whether they use equity, balance, floating losses, fees, and a particular reset time. Configure the EA’s own limits below the firm threshold with room for the account’s actual calculation, and test what it does when a limit is reached. The EA’s internal controls are guardrails, not a substitute for the firm’s monitoring.