Start with the two contract identities
A near contract and a later contract can share an underlying label while having different delivery dates, units and specifications. Save each exact product identifier and the source version separately. A continuous chart label is not enough to identify the two instruments in an account record.
Exchange-information schemas illustrate separate contract-type, delivery and size metadata. They do not prove that your two entered products are economically interchangeable. Keep those fields beside the execution records rather than copying a multiplier from the old contract into the new row.
Retain both execution legs, even for one combined instruction
A provider may support a combined spread instruction, but your evidence still needs to identify the closing and opening legs and their outcomes. A submitted instruction is not a receipt for both legs. Keep any partial fills and unresolved quantities visible rather than describing the whole rollover as completed.
Do not change the instrument identifier on an existing position row and call that a migration. Preserve the old entry, the reported close and the new entry as separate records. This journal does not send or recommend an order; it organises evidence that you already possess.
Equal contract counts need not mean equal entered exposure
In a fictional linear-unit model, two old contracts at 0.5 base units per contract represent 1 base unit. One new contract at 1 base unit per contract represents the same entered quantity. The equality follows from these teaching multipliers, not from the matching number of contracts.
If the new multiplier is unavailable, comparable exposure remains unknown. Even matching base quantity does not establish equal risk, margin or price sensitivity across different products. Keep the unit model explicit rather than presenting this arithmetic as a hedge recommendation.
| Fictional leg | Contracts × supplied multiplier | Entered base exposure |
|---|---|---|
| Old close | 2×0.5 | 1 base unit |
| New open | 1×1 | 1 base unit |
| Same contract count assumed | Not sufficient | Multiplier evidence still needed |
Separate a price gap from the old trade result
For another invented linear example, an old one-unit position entered at 95 and reported closed at 100 has a gross price difference of 5. A new entry at 103 has its own entry record. The 3-unit gap between 100 and 103 is not automatically a realised loss or a net rollover cost.
Commissions, execution timing and other cash movements need separate evidence. A Singapore display in SGD must not be combined with USD-quoted leg prices without a documented conversion. The display currency, contract quote and collateral asset can all be different fields.
A compact two-leg record
Use one row per leg with a shared journal reference and a separate exact contract ID. Include the entered multiplier and its unit, filled contract count, execution time with offset, quote currency, commission asset and remaining quantity. A combined instruction reference can link the rows; it should not replace either leg identifier. If the closing record has two partial executions, retain both rather than letting a single average hide an unresolved remainder. Match only records from the same stated rollover instruction.
Close only the parts supported by the records
Report each leg's identity, quantity, price, source and status. If only the old leg is confirmed, preserve the open question about the new leg. If both are supplied, distinguish a claimed execution from independently authenticated evidence; a typed CSV does not verify itself.
The resulting comparison can show a quantity mismatch or a missing specification. It cannot establish a safe rollover date, available liquidity, net account result or the suitability of a new contract.
The optional link below leads to this site's separate crypto signals and Telegram updates offer. The record method is usable without that offer. It does not independently verify the offer, establish country eligibility or turn the teaching example into an actual transaction.
Primary sources and scope
- Binance Developer Docs: COIN-M exchange information
Separate contract size, base, quote, margin asset, contract type and delivery metadata; schema example, not local product eligibility. Checked 2026-10-21.