Save the rule identity, not just the headline percentage
A margin-rule snapshot needs its product, account mode, quote unit, collateral asset, band boundaries and source version. A change in one visible percentage may be only part of a rule. Save the whole applicable row rather than copying a new number over an old spreadsheet cell.
The cited account schema includes leverage-bracket fields for notional limits, maintenance ratio and an auxiliary calculation parameter. Those fields illustrate why a single rate is insufficient to reconstruct every requirement. This article has not obtained a live account bracket or authenticated a rule change.
Use a deliberately limited comparison model
Suppose two fictional flat-rate sheets apply to the same entered notional 1000 in one stated quote unit. The earlier teaching rate is 0.5% and the later is 0.6%, with no additional terms under this explicitly simplified model. The arithmetic amounts are 5 and 6, a difference of 1 quote unit.
These are not a venue's actual maintenance amounts. A tiered, deducted, portfolio or other model can require additional fields. If those terms are missing, withhold the real requirement rather than extrapolating the flat-rate example.
| Teaching version | Supplied flat model | Conditional amount |
|---|---|---|
| Earlier | 1000×0.005 | 5 quote units |
| Later | 1000×0.006 | 6 quote units |
| Real account requirement | Not supplied | Unknown |
Keep threshold inclusion and scope unresolved when necessary
At an exact notional boundary, you need the source's inclusion rule. Do not assume which bracket contains the endpoint from a column heading alone. Retain floor, cap and the original wording so a reviewer can identify the missing convention.
Also keep the notional's definition. A wallet balance, a position notional and an order value are not interchangeable inputs simply because all are displayed in one currency. Comparing two rate sheets against different scopes would create a false rule-change result.
Effective time differs from when you saved the sheet
An invented rule stated effective at 2026-10-22T 00:00:00Z displays 08:00 on 22 October in Singapore. A local snapshot saved at 00:30 that day is seven and a half hours before the stated effective instant, not after it. Preserve the full dates and offsets.
Capture time records your observation. It cannot establish the first publication time or when a provider actually applied a rule to an account. Keep those events as separate fields and label a missing effective timestamp unknown.
A rule-sheet change checklist
For each changed bracket, retain the old and new source versions, floor and cap, notional definition, rate, auxiliary term, effective instant and capture instant. Identify a removed row separately from a row that was merely absent in an incomplete export. Mark which input stayed constant for the comparison. This prevents a changed position size from masquerading as a changed rule. A useful review result can simply be “versions differ, actual requirement not reconstructed” when a required term has not been supplied.
A rule comparison is not a liquidation estimate
Finish with changed fields, comparable input scope and unresolved calculation terms. Keep balance and position records separate from the rule sheet. A new margin-rate entry does not establish a realised loss, an automatic transfer or a provider error.
No liquidation price is calculated here. That would require a product-specific model and account evidence beyond two entered rule versions. This local journal does not change leverage, collateral or any live account setting.
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: 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.