What does an MT5 trade copier do?

It routes eligible source-account instructions to supported follower accounts, applying the configured mapping and sizing rules. It does not provide a strategy, choose profitable trades or guarantee identical fills.

Does TradeCopier require a VPS for MT5?

TradeCopier’s core routing is cloud hosted, so users do not rent a separate personal VPS for that layer. Confirm the current component and availability requirements for the exact MT5 broker, server, account type and route.

Can an MT5 trade copier copy between netting and hedging accounts?

A route must explicitly support the intended account modes, and you must test the resulting behavior. Opposite-side entries, partial closes, reversals and protection updates can affect netting and hedging positions differently.

Do source and follower MT5 symbols need the same name?

No, but every route needs a verified mapping to the exact destination instrument. Check suffixes or prefixes, contract size, volume limits and step, order modes, fill policies and trading sessions rather than matching the name alone.

Does a successful MT5 request mean the trade filled?

No. Request acceptance and execution are different stages. Check the destination order, all linked deals or fills, and the resulting position before marking a copied event complete.

Why can two MT5 accounts show different position counts?

Netting combines deals into one position per symbol, while hedging can retain separate positions. Compare account mode, the action requested, linked deals, gross and net quantity, and the resulting position identities before treating different counts as an error.

Can I use TradeCopier on a prop-firm MT5 account?

Only when the exact account route is technically supported and the firm’s current rules permit the source, destination, ownership, program stage and connection method. Product compatibility does not grant permission.

What should I check when an MT5 copy is rejected?

Inspect the native rejection code, account trading permissions, exact destination symbol, volume minimum, maximum and step, stops distance, allowed order and fill policies, session state and available margin. Preserve the configuration and submitted request before changing or retrying it.

Does the MT5 comparison worksheet prove my route is supported?

No. The blank worksheet records source and follower facts to check, with references and dates. Confirm the current TradeCopier connection route, broker and account permissions, then run a controlled test of each required action before relying on the route.

MT5 Trade Copier: Account Modes, Symbols & Errors

An MT5 trade copier routes an eligible trading instruction from a source account to one or more supported follower accounts. Before using one live, verify the exact connection route, MT5 account mode, trading permissions, symbols, contract specifications, volume rules and destination results. A copier does not provide a trading strategy, select profitable trades or guarantee that two accounts receive identical fills.

Publisher disclosure: TradeCopier publishes this guide about its own product. Product statements describe the current public workflow checked on September 24, 2026; platform concepts come from the linked MetaQuotes documentation. No independent test in this article establishes latency, uptime, fill quality, profitability or universal broker compatibility.

What an MT5 trade copier must translate

“Copy this trade” is not one technical event. The source can create a market order, pending order, stop-loss or take-profit change, partial close, full close or reversal. The destination may use a different account mode, symbol name, contract size, volume step, execution mode or fill policy. The copier has to determine whether the event is eligible, transform supported fields, submit a destination request and record the result.

Source-to-destination stages in an MT5 copying workflow
Stage	Question to answer	Evidence to retain
Source event	What instruction or account change occurred?	Source account alias, symbol, action, side, requested quantity, order type, protection fields and timestamp
Copier decision	Was the event eligible, mapped and sized?	Configuration version, symbol mapping, sizing result, filters, route and any validation error
Destination request	What did the copier ask the destination to do?	Request or correlation ID, normalized symbol and quantity, request time and returned code
Broker outcome	Was the request accepted, rejected, partly filled or still unresolved?	Destination order, every linked deal or fill, native code and broker timestamps
Account state	Does the resulting position match the intended exposure?	Position identifiers, direction, quantity, protection fields and a post-event snapshot

A successful submission is not the same as a completed trade. MetaQuotes states in its OrderSend documentation that a successful return means the request passed basic checks and was accepted for further processing; it does not by itself establish that the requested market operation was executed. The destination order, deals and resulting position provide the stronger account-state evidence.

Check these MT5 requirements before connecting

MT5 trade copier connection requirements
Field	What to verify	Why it matters
Account identity	Source and follower aliases, broker and server	A platform name alone does not identify the account route
Account mode	Netting or hedging	Opposite-side deals and partial closes can produce different position states
Trading permission	Trading enabled and any applicable automated-trading permission	An authenticated account may still reject trading requests
Symbol identity	Exact source and destination symbols, suffixes, prefixes and instrument	Similar names do not prove equivalent contracts
Contract and volume	Contract size, minimum, maximum and volume step	The same displayed lot number can represent different exposure or be invalid
Order support	Market, pending, protection, time and fill policies required by the workflow	The destination may reject an unsupported combination
Connection method	Current TradeCopier setup for this route and what must remain connected	Requirements can differ by platform, broker, server or connector
Permission	Broker, prop-firm and account terms for the exact workflow	Technical compatibility does not grant contractual permission
Plan capacity	Trading groups and total connected accounts	The permanent Free plan currently includes one group and three total accounts

The MQL5 account-properties reference exposes facts such as trade mode, whether trading is allowed, whether Expert Advisor trading is allowed, margin mode, FIFO restrictions and whether opposite positions are permitted. Record the relevant properties for each MT5 account instead of assuming the source and follower match.

Compare source and follower specifications side by side

Download the blank MT5 broker and platform specification worksheet (CSV) and make one copy for each proposed source-to-follower route. Its 33 criteria place source and follower values, dated reference URLs, evidence notes and comparison status in the same row. Leave unknown fields blank and marked not_checked; controlled route tests start as not_run. Do not put account numbers, passwords, tokens or unredacted logs in the file.

High-impact source and follower facts to compare before a controlled test
Check	Source evidence	Follower evidence	Unresolved difference
Account mode and permission	Mode and trading permissions from the source account	Mode and trading permissions from the follower account	Whether netting, hedging or a permission restriction changes the intended action
Instrument and contract	Exact source symbol, contract size and tick properties	Exact follower symbol, contract size and tick properties	Whether the mapping represents the same instrument and exposure
Volume and order rules	Minimum, maximum, step and required order types	Minimum, maximum, step, allowed order and fill policies	Whether the calculated request is valid at the destination
Session and costs	Trading session and published account costs	Trading session and published account costs	Whether availability or broker charges alter the planned workflow
Route and outcome	Current connection instructions and a redacted source event	Current follower connection instructions, request, deals and resulting position	Whether the exact direction and action have actually been demonstrated

The MetaQuotes account-properties and symbol-properties references define many MT5 fields. Broker-specific values, costs and permissions need the broker's current account and instrument records. A completed worksheet helps find a mismatch; it does not establish that TradeCopier supports a particular broker, connector, direction or action. Confirm the route in the current product flow and test each required action under permission.

Distinguish orders, deals and positions

MetaQuotes defines an order as an instruction, a deal as an execution and a position as the resulting trading obligation. Its MT5 basic-principles documentation also explains that one order can result in several deals. This distinction changes how a copied event should be checked.

A destination order can exist without a completed fill.
Several partial-fill deals can belong to one destination order.
A deal can increase, reduce, close or reverse a net position.
Equal order counts do not prove equal position exposure.
A rejection does not prove execution, and an expired order can still have earlier partial fills. Inspect all linked deals before determining the final exposure.

Use stable order, deal, position and correlation identifiers where they are available. Do not force unlike identifiers into one field or infer a fill solely from a copier success message.

Netting and hedging accounts behave differently

MT5 supports netting and hedging position-accounting systems. The broker sets the mode for the account. In netting mode, only one common position can exist for a symbol; a new same-direction deal increases it, while an opposite deal can reduce, close or reverse it. In hedging mode, multiple positions for the same symbol can coexist, including opposite positions.

Questions to test for netting and hedging followers
Source event	Netting follower check	Hedging follower check
Second same-direction entry	Does it increase one common position by the intended amount?	Does it create or update the intended separate position?
Opposite-side entry	Does it reduce, close or reverse the existing net position?	Does it create a separate opposite position or close a selected position?
Partial close	Is the common position reduced by the verified filled quantity?	Was the intended position selected and reduced?
Stop-loss or take-profit change	Which protection values remain on the common position?	Which individual position received the change?
Full close	Is the net quantity actually zero?	Are all intended position tickets closed?

Test the behavior you actually use. A copier can appear correct after one simple open and still diverge on an opposite-side trade, partial close or protection update.

Verify symbol and volume rules instead of matching names

One broker may publish EURUSD while another uses EURUSD.a; a metal or index can have a different alias, contract size or calculation model. Matching text is only the start. The MQL5 symbol-properties reference documents fields for trade mode, contract size, minimum and maximum volume, volume step, order modes, execution mode, fill modes, stops level and other instrument rules.

For every route, keep a mapping record with:

raw source symbol and exact destination symbol;
instrument and contract identity, including contract size where applicable;
source quantity, sizing rule, unrounded destination quantity and submitted quantity;
destination minimum, maximum and volume step;
rounding direction and the reason for any cap or rejection;
supported order, fill and expiration policies;
the configuration version and test date.

Use the side-by-side MT5 specification worksheet to retain the source and follower values and their dated references before recording a mapping decision. A blank or unverified field remains unresolved.

A correct symbol mapping does not guarantee equal prices or fills. Source and destination accounts can see different spreads, liquidity, sessions, quotes and broker decisions. If the destination quantity cannot satisfy its step or limits, record the explicit outcome instead of silently describing the copy as exact.

Use the current TradeCopier connection flow

TradeCopier is a live cloud trade copier for supported account routes. Its core routing is hosted, so users do not rent a separate personal VPS for that routing layer. The exact platform connection can still have route-specific components and availability requirements. Follow the current in-dashboard instructions or support guidance for the exact broker, server, account type and direction you intend to use.

The MetaTrader platform-settings documentation describes terminal permissions and automated-trading settings. It does not document TradeCopier’s current connection architecture; use it for MT5 terminology, then use TradeCopier’s current setup flow for the product-specific steps.

Work through two account-state diagnosis examples

Example 1: the position count changed. Assume a hypothetical account starts flat, then fully fills a 0.30-lot buy and a separate 0.10-lot sell for the same symbol. With netting, the result is one 0.20-lot long position. With hedging, separate opening instructions can leave a 0.30-lot long and a 0.10-lot short position. A command that explicitly closes part of an existing hedging position is a different action. Check the request and deal records before deciding whether the copier selected the wrong operation.

Both examples have 0.20 lot of signed net quantity, but the hedging account retains two positions and 0.40 lot of gross quantity. Equal net quantity does not prove equivalent margin, protection settings, financing or close behavior. Record the account mode and intended position identity when reporting a mismatch.

Example 2: the requested volume is invalid. Suppose a hypothetical destination accepts a minimum of 0.10 lot in 0.10-lot increments, with a maximum above 0.20 lot. A sizing rule calculates 0.15 lot. That quantity cannot be submitted unchanged under those rules. Rejecting the copy leaves it unexecuted; rounding down to 0.10 or up to 0.20 changes exposure. The appropriate behavior must come from a documented configuration, not an assumption that every copier uses the same rounding rule.

Record the calculated size, submitted size, destination limits, selected policy and actual filled size. If a calculated size falls below the minimum, do not silently raise it and call that an exact copy. Retest the calculation after an instrument specification or multiplier changes.

Hand the verified constraints into a controlled test

Once the account mode, instrument rules and expected exception behavior are known, use the event sequence in the Free MT5 setup and controlled-test guide. Cover market opening, protection changes, pending orders and cancellation, partial and full closure, opposite-side events, rejection and reconnect behavior where supported. The guide explains a small Free-plan workflow; technical permission and support still need to be confirmed for every account.

A historical strategy backtest does not validate this route. It does not reproduce live source detection, connection interruptions, destination acceptance, partial fills or broker-account state.

Classify failures before taking recovery action

Common MT5 copier exceptions and the next evidence to inspect
Observed exception	Possible causes	Next check
No destination request	Ineligible event, filter, mapping failure, unavailable route or validation error	Source event, rule result, configuration version and copier error
Rejected order	Permission, symbol, market state, price, volume, stops, margin or unsupported policy	Native code, destination symbol properties and account permissions
Partial fill	Available liquidity or destination fill policy	All linked deals, remaining working quantity and current position
Different quantity	Multiplier, cap, minimum, maximum, step or rounding	Raw sizing calculation and submitted destination quantity
Different position count	Netting-versus-hedging behavior or another account action	Account mode, every linked deal and before-and-after positions
Timeout or missing response	Delayed evidence, connection interruption or unresolved destination state	Request ID, later orders, deals and positions before retrying
Unmatched close	Earlier missed event, selected-position mismatch, manual action or account-mode difference	Position history, close request, deals and current exposure

Do not blindly repeat an instruction when the outcome is unknown. A timeout does not prove that nothing executed, and a retry can create duplicate exposure. MetaQuotes notes that transaction events following one request can arrive through several stages; its OnTradeTransaction documentation also says arrival priority is not guaranteed. Reconcile the destination account first, then use the current supported recovery procedure.

Separate copier routing from broker execution

A defensible timing record uses separate timestamps for source detection, copier processing, destination submission, broker acknowledgement and final fill evidence. “Execution speed” is ambiguous when these stages are combined.

Detection time starts when the source event becomes observable to the connection.
Routing time covers eligible copier processing between the observed source event and destination submission.
Acknowledgement time ends when the destination reports that it accepted, rejected or otherwise classified the request.
Fill time ends only when the relevant execution evidence exists.

The owner reports a 10–15 ms routing-latency range, but no public dated methodology currently establishes it as an independently verified benchmark. The range does not include every broker acknowledgement or fill, and it is not a guarantee for a route, region, account, instrument or market condition.

Do you need a VPS for an MT5 trade copier?

TradeCopier’s core copying service is cloud hosted, so its normal product model does not require the user to rent a separate personal VPS for the routing layer. That answer does not make every MT5 connection identical. Confirm the current connection component, what must remain authenticated or available, and the recovery behavior for your specific route.

A local EA copier is a different operating model. It may require terminals and a computer or VPS to remain running. Do not copy generic EA-folder, IP-address or local-VPS instructions into the TradeCopier setup unless the current route documentation explicitly requires them.

Check broker and prop-firm permission separately

Technical support is not contractual permission. A broker or prop firm can restrict automated trading, third-party services, account management, external signals, ownership combinations or particular connection methods. The rule can also differ between an evaluation, simulated funded account and live account.

Describe the exact source, follower, owner, program stage, platform and connection method when asking for a written answer. Preserve that dated response and recheck it after a rule, program, account or connection change. TradeCopier does not guarantee prop-firm compliance, challenge completion or payouts.

For product access, review the current plan limits and getting-started path. The Free plan is permanent, with one trading group and three total connected accounts. Its detailed setup and test sequence belongs to the linked Free MT5 guide; this page focuses on diagnosing account-mode, instrument and connection differences.

Primary references

Sources and public TradeCopier product pages were checked on September 24, 2026. Platform, broker, product and account rules can change; verify the current documentation for a real connection.