Copy the documented fields before comparing totals
A contract can name a base asset, quote asset and margin asset separately. The cited exchange-information schema illustrates those fields alongside contract size. Preserve their actual meanings rather than labelling every amount dollars because the quoted price appears in USD.
For each supplied account record, keep product identity, account mode, collateral asset, quantity and observation time. This does not establish whether a product is available to a Canadian reader or whether the supplied balance is authenticated.
Do not add unlike quantities
Imagine one fictional ledger contains 0.01 units of a coin collateral asset and another contains 100 units of a token collateral asset. The sum 100.01 is not a meaningful collateral total because the units differ. Preserve the two quantities in their own asset rows.
A contract-count field is another unit again. Without the relevant contract specification it cannot be substituted for a collateral quantity or a base-asset exposure. Keep that missing evidence visible rather than inferring a multiplier from a familiar ticker.
| Fictional supplied field | Unit | Permitted reading |
|---|---|---|
| Coin collateral 0.01 | Coin units | Separate asset quantity |
| Token collateral 100 | Token units | Separate asset quantity |
| Naive sum 100.01 | Mixed units | Not a valid collateral total |
A valuation layer needs its own evidence
If a Canadian report values those assets in CAD, retain the price/rate, direction, timestamp and source for each asset. Do not silently assume a stablecoin equals a fiat dollar or substitute a current price for a historical observation.
The Bank of Canada describes its daily rates as indicative. A daily fiat rate is not proof of an account-specific conversion or a token's CAD price. Without appropriate asset-rate evidence, you can reconcile quantities while withholding a common-currency total.
Wallet total is not automatically an available amount
Account schemas can separate wallet, available and transferable measures. Keep their scopes intact. A valuation of a total asset holding is not evidence that the same value can be moved or used as margin, and an unrealised change is not a recorded cash transfer.
For a position comparison, preserve collateral additions, fee debits and other movements separately from price changes. Otherwise a larger CAD display could be misreported as trading performance when it reflects a different quantity or a new valuation input.
A unit-safe reconciliation table
Give each row an asset identifier, quantity, balance scope, observation instant and account or product reference. Put an optional CAD valuation in separate columns with its own price and timestamp. Preserve the unconverted quantities so a reviewer can reproduce or reject the valuation without losing the original ledger. If the coin price and token price were observed on different dates, flag that mismatch before summing the CAD outputs. A shared reporting currency does not make the source assets identical or prove that either can be withdrawn.
Report what was reconciled, not which product is better
The completed sheet should show exact asset quantities, comparable dates, any documented valuation layer and the limits of the evidence. A missing conversion remains unknown. Different collateral assets cannot be ranked for safety or profitability from two balance strings.
This method does not connect a wallet, transfer collateral or recommend a margin product. It simply preserves unit boundaries so an apparent numerical comparison does not claim more than the records support.
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. - Binance Developer Docs: USD-M futures account schema
Separate wallet/available/withdrawable fields and documented leverage-bracket fields; no live account settings or margin requirement verified. Checked 2026-10-21. - Bank of Canada: Daily exchange rates
Daily rates are indicative aggregates, not evidence of an account-specific executed conversion; no current rate used here. Checked 2026-10-21.