Skip to content

EAs and algo trading rules

Check an automated strategy against holding times, copying restrictions, news rules and execution risks before running it.

MultiFunded editorial team · Rule data checked 23 October 2026
· 4 min read

A glass circuit board connected to a checked trading plan
A glass circuit board connected to a checked trading plan

An EA can execute a plan consistently and still execute the wrong plan for an account. Before switching it on, translate the rulebook into testable operating constraints: symbols, size, timing, cumulative exposure, order behaviour and a reliable way to stop the system.

Check what the system actually does

Describe the strategy in ordinary language before relying on a software label. An indicator, execution assistant, trade copier and fully automated entry system perform different jobs. The claim that a product is an EA does not establish that its behaviour complies with the account's permitted practices.

Inspect how it handles price-feed delays, sudden spreads, rejected orders and partial fills. A system intended to exploit stale quotes or platform errors conflicts with the rules even if its developer calls it arbitrage-free. If you cannot explain the execution logic, ask the developer for a clear specification before connecting it to a paid account.

Express timing rules in the code and configuration

The 2-Step Standard minimum hold is 3 minutes, while Instant currently uses 30 seconds. The account's order timestamps determine elapsed open-to-close time. A bot that targets fast exits must be assessed against the chosen product rather than a generic statement that scalping is allowed.

Simulated funded gains from trades opened or closed within 5 minutes of a high-impact release may be removed. Check entries, stops, targets and emergency closes, not just the normal entry schedule. A news filter can fail if its calendar feed stops or its time zone is wrong; define a conservative failure behaviour rather than assuming the data always arrives.

Use account-level limits above strategy-level limits

Two EAs each respecting their own risk limit can still create excessive combined exposure. Give the account a shared view of open positions and pending orders. Count repeated entries on one idea together, and consider whether several symbols respond to the same driver. The account's daily and maximum-loss checks see the combined result.

MultiFunded also sets 100 lots per trade and 500 lots per day. Those are ceilings, not sensible default sizes. A smaller contract or a volatile symbol can still create substantial risk below a lot ceiling. Sizing should start from the tested dollar risk and instrument specification.

Test failures as carefully as normal entries

In a suitable practice environment, test a disconnected session, a restart with open positions, duplicate messages and a rejected close. Check whether the system recognises existing orders after reconnection or opens replacements. Save logs with timestamps so that unexpected positions can be traced to a specific decision.

Backtests do not prove live execution or account-rule compliance. Costs, data quality and order assumptions can change the result. Run forward tests that include the actual session schedule and rule settings. Record software version and parameter changes separately so that a later result can be attributed to the system that produced it.

Keep ownership and a stop procedure

Copying or mirroring between accounts, account sharing and third-party management are prohibited under the current MultiFunded rules. Buying a software licence does not transfer responsibility for the orders. Check whether a service sends common trades to many accounts or requires another person to operate your account before assuming it is your own automation.

Write down how to disable new entries, cancel pending orders and manage existing exposure if the system malfunctions. Verify that the procedure works without the failed component. Then review the account statement regularly. Automation reduces manual actions; it does not remove the need for supervision, records or a rule-compatible operating plan.

Key takeaways

  • Assess execution behaviour, not the EA label.
  • Apply holding-time, news and loss rules to every automated order.
  • Use combined account exposure limits and test a manual stop procedure.

Sources and rule check

MultiFunded-specific details were checked against the programme configuration and rulebook on 23 October 2026. Read the conditions attached to your own account before trading; educational examples do not predict results.

COMMON QUESTIONS

Questions about this guide.

No blanket approval follows from a software licence. The system's actual behaviour must comply with the account rules and prohibited-practice terms.

Current MultiFunded rules prohibit copying or mirroring between accounts, including your own and external accounts.

No. Verify the live order behaviour, costs, timestamps, account controls and failure handling separately.

Check the rules. Then choose.

Compare the complete conditions before paying for a simulated account.

Related guides

MultiFunded editorial team