Trade Copier for Prop Firms: How It Works and What Breaks It
A trade copier for prop firms sends trade instructions from a source account to one or more receiver accounts. Three separate checks matter: permission for the exact accounts and software, technical execution on each receiver, and that receiver's own risk limits. A functioning connection does not establish permission or guarantee matching fills.
Background reading: trade copier overview and account compatibility considerations.
This page covers how a copier actually works, the rule problem and what can be done about it, the four technical failures that cost money, and how to size positions when the accounts are different sizes.
- A copier reproduces instructions and can spread the same losing exposure across several accounts. It does not create a trading edge.
- Check the exact firm, product, account stage, ownership, copying direction and software conditions before connecting accounts.
- Preserve honest trade and event records. Changes to IP addresses, order comments or timing do not make a prohibited setup permissible.
- Latency, symbol mapping, volume rounding and partial-close handling can make receiver positions diverge from the source.
- A balance ratio alone does not establish equal percentage risk: contract value, account currency, stop distance, costs and remaining loss allowance also matter.
How a trade copier works
Three parts. A master, where trades originate. A transport, which carries the instruction. And a slave, which reproduces it on another account.
A common MetaTrader construction uses a source EA to observe trading events and a receiver EA to submit corresponding requests. Products may use files, sockets, a server or another transport. Check the actual software documentation; MT4/MT5 labels alone do not establish cross-platform, hedging/netting or event compatibility.
What the slave has to do on every event is more than "open the same trade":
- Resolve the master's symbol to whatever this broker calls it, including suffixes.
- Calculate a receiver size against its own cash-risk budget and contract specification. Apply valid minimum, maximum and volume-step constraints. If the minimum lot would exceed the budget, skip or redesign the trade; do not increase size merely to force a valid order.
- Define whether stops and targets copy absolute prices or distances, then check the resulting receiver risk and the broker's accepted protection. Different quotes can affect that calculation; identical protection is not guaranteed.
- Respect the slave broker's minimum stop distance, which may be wider than the master's.
- Reconcile after a disconnect, so a reconnecting terminal does not duplicate open positions.
Reconciliation compares actual source and receiver positions with recorded event identifiers after a disconnect. Test duplicate events, missed acknowledgements and a receiver-only rejection before using a permitted setup. A reconnect or an accepted request is not proof that the intended position and protection exist.
The rule problem, stated plainly
Rules are product-specific. FTMO's allocation FAQ applies limits per trader or strategy, including substantially similar strategies; it does not mean that four evaluations are automatically a breach. The5ers' current terms require prior written notice and approval for qualifying user-owned, user-developed automated software and prohibit third-party-owned or developed software under section 11. Those conditions cannot be reduced to a general statement that all firms allow or ban copiers.
FundedNext's general copying FAQ describes copying between the same owner's eligible Challenge accounts with conditions, including a designated source, combined allocation and transport restrictions. Its Stellar Instant-specific FAQ permits copying between that person's Instant accounts but prohibits copying between different owners and between Instant and other CFD products. The general FAQ also contains broader funded-account restrictions. Resolve this published scope conflict with support for the exact accounts before connecting them; do not extend Instant permission to Challenge or other products.
Record the owner, source and receiver products, account stage, software, hosting method, strategy allocation and permitted direction. A personal account login or a customer's agreement does not override the firm's terms. Do not use timing randomisation or different IP addresses as a workaround.
Read the current terms and obtain any required written approval before connecting accounts. Keep the dated answer with the relevant rules. Reviews or restrictions need not wait until a payout request. Primary rules were checked on 16 October 2026: FTMO allocation, The5ers terms, FundedNext general copying FAQ and Stellar Instant-specific FAQ.
Four failures that cost money
1. Latency
A receiver request cannot be generated from an event before the source system observes that event. That does not prove a universal ordering of broker fill timestamps, which may use different clocks. Record source observation, transport receipt, request submission and execution confirmation on a comparable time basis. Acknowledgement is not a fill. Compare actual prices, direction, costs and missed events as well as elapsed time; there is no universal safe millisecond threshold for swing or short-target strategies. See the latency measurement guide.
2. Symbol suffixes
The source might use EURUSD while the receiver uses EURUSD.raw. Map the actual contract, not just the suffix: trading sessions, contract size, profit currency, tick value, order modes and stop constraints must be checked. A mismatch may reject or misroute a request. Read return codes and execution events; do not infer a working connection from a healthy-looking terminal.
3. Lot rounding
A calculated size may fall between valid volume steps. Rounding up can exceed the planned budget; rounding down may produce a valid smaller size or fall below the minimum. For a fictional USD account, assume $10 per pip per lot, a 20-pip stop, no additional costs and a $25 price-risk budget. The raw size is 25 / (20 × 10) = 0.125 lot. With a 0.01 step, 0.12 lot implies $24 price risk; 0.13 implies $26 and exceeds that budget. Costs, gaps and execution can increase the actual loss.
4. Partial closes and modifications
Test more than opens and full closes. If a source scales out, modifies a stop or trails protection, record the corresponding request, accepted quantity and actual remaining receiver position. A rejected or rounded partial close can leave a different exposure. Define how the system pauses, reports and reconciles this case instead of retrying blindly.
Sizing when the accounts are different sizes
These modes describe volume transformations, not a ranking of safety. First set the receiver's permitted cash-risk budget and available loss allowance, then check the resulting quantity and protection.
| Mode | Behaviour | When it is right |
|---|---|---|
| Balance proportional | Slave lot = master lot × (slave balance / master balance) | Can approximate equal percentage stop-risk only when currency, contract value, stop distance and costs match, before rounding. |
| Fixed multiplier | Slave lot = master lot × a constant | Use only after checking the resulting cash risk on each receiver; a constant does not adapt to different contracts or stops. |
| Fixed lot | Slave always trades the same size | May suit a defined fixed-cash-risk design with matching contract and stop assumptions; percentage risk changes as equity changes. |
Each receiver needs its own risk checks using its firm's actual balance/equity, reset-time, open-exposure and loss-limit definitions. A local guard can fail or execute late and does not guarantee compliance. Read contract specifications and use an account-currency estimate such as OrderCalcProfit where appropriate, then allow separately for costs and execution uncertainty. OrderSend acceptance is not execution confirmation.
What we run
JPTradingCapital's customer-operated EA Hub software and the separately hosted JPTC Algo are different products. This guide does not establish that a particular version includes a copier, reconciliation, cross-platform transport or an enforceable prop-firm risk guard. Verify the actual version documentation and permitted use before choosing any software.
The JPTC Algo is hosted by JPTC, so customers do not install or run it and do not need their own VPS. Hosting does not override broker or prop-firm rules or guarantee returns, passing or payouts. For a challenge passing service, establish the exact service scope and the program's permission first; customer control or consent alone does not authorise third-party trading or automation.
Related reading: how copier latency affects prop accounts, setting up a copier across multiple accounts, and the automated forex trading guide.
Do prop firms allow trade copiers?
How should I document permitted copy trading?
What is the best lot sizing mode for a copier?
Why is my copier not opening trades on the receiver?
Does copier latency matter?
Review the JPTC EA Hub
EA software with version-specific documentation and account-level risk controls. Review the selected programme’s current automation rules and test the chosen version; software does not guarantee compliance, a pass or a payout.
See the EA Hub