EAs can behave differently on different brokers because of spreads, execution speed, symbol specifications and server time. Testing on several demo accounts before committing to one broker can reveal surprises.
A method: run the same EA with the same settings on two or three demo accounts for a few weeks, logging every signal and fill. Compare the number of trades, average slippage, and results.
Differences may come from symbol suffixes, contract sizes, minimum lot steps or stop level requirements. An EA expecting a symbol name of EURUSD may fail silently on a broker using EURUSD.r or similar.
Demo execution is not always identical to live execution, so a small live test is the final step. Still, demo comparison catches many configuration issues.
It is also worth comparing historical data quality, since backtests on poor data can mislead.
Running two demo accounts side by side for a month is the most reliable way to see the difference in practice.
Have you seen an EA behave very differently across brokers?
Testing an EA across several brokers before choosing one
-
FXS London Scalper
- Posts: 975
- Joined: Sun Oct 18, 2026 12:25 pm
Testing an EA across several brokers before choosing one
FXS Official Team | London Session Desk
-
Amanhasnoname
- Posts: 2060
- Joined: Fri Oct 30, 2026 9:45 am
Re: Testing an EA across several brokers before choosing one
The symbol suffix issue is probably the most common silent failure, and it is worth building the EA so it reads the chart symbol rather than a hardcoded name. Pairing that with a startup check that prints the contract size, lot step, minimum lot, stop level and digits for the symbol to the journal makes configuration differences obvious on the first run instead of weeks later. Five-digit versus four-digit pricing and different point values still catch people out when stops and targets are written in points.
Server time is the other big one. If the EA has session filters or daily reset logic tied to the clock, a broker on GMT+2 versus GMT+3 or one that shifts for daylight saving at a different date will move every trade window. Converting everything to UTC inside the code avoids that, and comparing the first trade timestamps across the demos is a quick sanity check.
When comparing results, it helps to match signals one to one rather than looking only at totals. If a signal fired on one account but not another, the cause is usually a spread filter, a stop level rejection or a missing tick, and each of those points to a different fix.
Server time is the other big one. If the EA has session filters or daily reset logic tied to the clock, a broker on GMT+2 versus GMT+3 or one that shifts for daylight saving at a different date will move every trade window. Converting everything to UTC inside the code avoids that, and comparing the first trade timestamps across the demos is a quick sanity check.
When comparing results, it helps to match signals one to one rather than looking only at totals. If a signal fired on one account but not another, the cause is usually a spread filter, a stop level rejection or a missing tick, and each of those points to a different fix.