MT5 Netting vs Hedging: Follow Three Deals Through Two Ledgers

By CrowdSent Blog Team

Netting vs hedging in MT5 changes how executed deals become open positions. A netting account allows one position per symbol; a hedging account can retain several, including opposing positions. The broker sets the account’s model. The worked ledgers below use the same three fictional deal quantities to explain why different position lists can both be correct.

This is an accounting example for reading records, not a trading strategy or a recommendation to choose either model.

Separate the order, deal and position

An order requests an operation. A deal records an execution; one order can produce several deals. A position is the resulting open holding. Under netting, a same-direction deal adds to the position, while an opposite-direction deal reduces, closes or reverses it according to quantity. MetaQuotes explains these relationships in its MT5 basic trading principles.

For this example, order labels O1–O3 and deal labels D1–D3 make the sequence easy to follow. They are invented references, not actual MT5 ticket numbers. H1–H3 identify the three fictional hedging positions.

Define the fictional sequence before comparing the ledgers

• Both accounts start with no position in the same invented symbol, EXAMPLE.
• O1 produces D1: buy 3 units. O2 produces D2: sell 1 unit. O3 produces D3: sell 4 units.
• Each order is assumed fully executed in one deal. There are no other events between the rows.
• On the hedging account, each order requests a new position. Neither sell order is a request to close H1.
• Units are fictional quantities. They are not lots, currency amounts or recommended sizes.
• Prices, fees, financing, margin and profit or loss are deliberately outside this quantity-only example.

Buy quantities have a plus sign and sell quantities a minus sign. The signed total is therefore +3 − 1 − 4 = −2. That calculation summarizes direction and quantity; the ledgers show which positions remain open. For real instrument measurements, see the separate explanation of units and contract size.

Netting vs hedging: follow the three-deal sequence

On a narrow screen, scroll the table sideways to see every column.

Read horizontally to compare the models after one event. Read vertically to reconstruct one account. On the netting side, D2 is a reduction and D3 is a reversal. On the hedging side, D2 and D3 add separate short positions while H1 remains long 3.

The netting vs hedging comparison holds the deal directions and quantities constant. It does not claim that every field in the accounts’ deal records would be identical: the same sell quantity has a different relationship to the existing positions.

Reconcile quantity without losing the position detail

The final netting ledger contains 2 open units, all short. The hedging ledger contains 3 long units and 5 short units, for a gross open quantity of 3 + 1 + 4 = 8. Its signed total is still −2.

Three useful checks therefore answer different questions:

• Executed volume: 3 + 1 + 4 = 8 units in each account over the sequence.
• Gross open quantity at the end: 2 units under netting, 8 under the stated hedging assumptions.
• Signed open quantity at the end: −2 units in both cases.

Calling all three figures “volume” without a definition creates an apparent discrepancy. A review note should name the measure, symbol and snapshot. “EXAMPLE: three open positions, gross 8, signed −2 after D3” preserves more evidence than “EXAMPLE: short 2.” Neither summary supplies a monetary result.

Keep opening and closing intent visible

On a hedging account, an opposite new opening trade does not automatically close the original position. A closing operation identifies the position being closed. MetaQuotes distinguishes these operations in its trade execution and closing documentation.

When reviewing an exported record, preserve the order reference, deal reference and position identifier alongside direction and quantity. The official MQL5 deal properties also distinguish deal type from entry classification, including entry, exit, reversal and close-by. A sell label alone does not provide that complete relationship.

For bot documentation, record the exact product and version, the supported account model, and how its instructions distinguish a new position from a closure. CrowdSent’s trading bots overview provides product background. Compatibility with either account model needs specific documentation; this ledger example does not establish it.

A read-only reconciliation worksheet

Start by recording the account model from the broker’s specification, not from the number of rows visible in a screenshot. Then record the exact symbol and contract definition, the export time and its time zone, and whether the file contains orders, deals or positions. These checks establish what the evidence can answer without requiring a new trade or any account-setting change.

Use one event row per deal, with its order reference, deal identifier, position identifier, direction, quantity and entry classification. Keep the original labels as well as any simplified explanation. For this exercise, D3 can be described as a reversal in the netting ledger, but do not invent an extra execution to make the explanation fit two rows. One recorded deal and two arithmetic effects are not contradictory.

Maintain a separate snapshot for open positions after the last included event. This is where gross and signed quantities belong. The executed-volume total belongs to the event list over the chosen interval. Comparing a daily execution total with a current open-position total mixes a flow and a snapshot. Both can be correct while differing substantially.

The fictional example gives a useful audit test. The event list totals eight executed units. The final netting snapshot contains two gross units and signed quantity minus two. The final hedging snapshot contains eight gross units and signed quantity minus two. A report labelled only “volume: eight” remains ambiguous until its time interval and measure are stated. Do not resolve that ambiguity by deleting the opposing position rows.

If a real export cannot be reconciled, identify the missing evidence before explaining the difference. Possibilities to check include an incomplete time range, a different symbol, a partial execution, a closing rather than opening instruction, or an intervening event absent from the extract. These are questions for the source records, not conclusions established by a mismatch. Preserve the original export and record which question remains unresolved.

Do not pool unlike instruments into a single signed quantity. Two units of one contract and two of another do not necessarily offset economically. This guide intentionally holds the symbol and units fixed. Even within that narrow setup, a matching signed total does not establish matching financing costs, margin treatment, execution prices or profit.

For the separate question of price instructions and fill evidence, read the market-order versus limit-order guide. For current product information, see CrowdSent’s service and membership overview. Neither link establishes undocumented MT5 account-model compatibility.

A changed closing instruction produces a different ledger

Consider a separate variation, not a continuation of the original table. Start again with H1 long three units. This time the second one-unit sale is explicitly a partial closure of H1, rather than a new opening instruction. H1 then has two long units remaining and no H2 is created. If the third four-unit sale is still a new opening instruction, the final hedging list contains long two and short four.

The signed quantity is still two minus four, or minus two. The gross open quantity is now two plus four, or six, rather than the original eight. Executed volume across the three events remains three plus one plus four, or eight. This variation isolates the significance of the second instruction: the direction and quantity did not change, but its relationship to an existing position did.

Compare all three final snapshots without mixing their assumptions. The original netting example has gross two and signed minus two. The original hedging example, with every instruction opening a new position, has gross eight and signed minus two. The revised hedging example, with a partial closure at D2, has gross six and signed minus two. The shared signed total cannot reconstruct the missing position detail by itself.

A useful review question is therefore not just “Was this a sell?” but “Which position relationship does the execution record identify?” The account specification, position identifier and entry classification help answer it. A screenshot showing only symbol, direction and size may be insufficient. Mark that limitation instead of assuming all opposite transactions must have had the same purpose.

These are retrospective reading exercises. They do not instruct a reader to place a closing or opening order, and they do not test a broker’s execution interface. Actual account permissions, instrument definitions and product documentation remain outside the fictional ledger.

Frequently asked questions

Are the example’s units the same as MT5 lots?

No. “Unit” is an invented counting measure here. Converting an actual account volume into underlying quantity requires the instrument’s contract definition. The integers make the ledger arithmetic readable without implying a tradable order size.

Why does the netting account end short 2 rather than short 4?

Immediately before D3, it is long 2. The four-unit sale first offsets those two units, leaving two units in the short direction. The check is +2 − 4 = −2.

Does D3 represent two separate executions in the example?

No. The assumptions give O3 one execution of four units. Describing two units as offsetting the long and two as the remaining short is an arithmetic decomposition of D3, not an additional deal or an additional order.

How would a same-direction increase look?

As a separate variation, replace D2 with a buy of 1. After D2, netting would show one long position of 4; hedging would show long positions of 3 and 1. The original table deliberately keeps D2 as a sale to illustrate reduction.

Would a final sell of 2 make both accounts empty?

If only D3 changes to a sell of 2, keeping D2 as a sell of 1, netting would finish flat: +3 − 1 − 2 = 0. Hedging would retain long 3, short 1 and short 2 under the new-position assumptions. Its signed total would be zero, with six gross open units.

Can these ledgers show which account made more money?

No. They contain quantities but no execution prices, valuation price or charges. There is no numerical basis for calculating either account’s profit, loss or required margin, much less ranking the models.

Is Close By another name for a new opposite position?

No. Close By is a hedging-account operation involving two existing opposite positions. If their quantities differ, the difference remains open in the larger position’s direction. It is outside the hedging ledger, whose three orders all request new positions.

Does seeing one position prove an account uses netting?

No. Both example accounts have one position after D1. That screenshot alone cannot distinguish their models. The broker’s account specification provides the necessary context before later rows are interpreted.

Which record detail explains why D2 affects the accounts differently?

Its relationship to a position matters. In this example, D2 reduces the netting position but opens H2 under hedging. The position identifier and entry classification provide evidence that the sell direction and quantity alone leave out.

Does support for MT5 prove a bot supports both accounting models?

A general platform label is insufficient evidence. The relevant documentation should explicitly address the account model and the product version being evaluated. An undocumented assumption about closing behavior leaves the intended position outcome unresolved.

Source documentation checked 24 October 2026. Educational explanation from the CrowdSent Blog Team. Numerical examples and identifiers are fictional unless stated otherwise. This article does not provide investment recommendations.