Retain the inputs that belong to each interval
A constant-input estimate can be useful for a deliberately simplified example, but a supplied ledger may contain different rates and notionals at different instants. Preserve each row’s instrument, time, unit, rate convention and relevant notional rather than copying the first row across the table.
Published funding-history schemas can provide a symbol, rate and funding time. Those market-data fields alone do not authenticate an account payment or establish which position qualified. Keep the source of the account movement separate from the source of a market rate.
Evaluate a clearly declared fictional model
Use the teaching formula amount = supplied notional × supplied rate for each row, with positive amounts defined here as costs and negative amounts as receipts. Enter notionals 1000, 500 and 500 in one quote unit, with rates 0.01%, 0.02% and −0.01%. The row amounts are +0.10, +0.10 and −0.05, totaling +0.15.
Applying the first notional and first rate to all three rows instead gives +0.30. That difference follows from using different inputs. Neither calculation is an authenticated venue settlement, and the sign convention is an explicit assumption of this model.
| Teaching row | Notional × rate | Model amount |
|---|---|---|
| 1 | 1000 × 0.0001 | +0.10 |
| 2 | 500 × 0.0002 | +0.10 |
| 3 | 500 × −0.0001 | −0.05 |
| Total | Entered row model | +0.15 quote units |
Do not turn a missing interval into a zero rate
If one expected row is absent, preserve the coverage gap. It could reflect an incomplete query, a different schedule or other missing evidence. Do not infer a zero accrual simply because no row appears in your export. A clock label and an interval count need their stated source conventions.
Keep rate units explicit. A decimal rate and a percentage string differ by a factor of 100. A quoted annualised figure is not interchangeable with an interval rate without a declared conversion model, and this example does not provide such a model.
Check the query boundary before calling two rows duplicate
Two exports can cover overlapping time ranges. If an API includes both endpoints, an event on their shared boundary can appear in both files. Preserve the source’s stated time-range semantics and the event’s scoped identity when combining them. Do not sum the same supplied accrual twice because it arrived in two downloads. Conversely, equal amounts at different supported instants can be separate events. The journal needs time and identity evidence, not an amount-only deduplication rule.
Keep Singapore display and valuation layers separate
A Singapore reader can display complete source instants in local time while retaining the original timestamps. An SGD reporting layer needs separate conversion evidence; changing the display currency label does not convert a quote-unit accrual into SGD.
A final comparison can show modelled rows, any supplied payment references and unresolved differences. It does not choose a funding trade, establish future rates or validate the linked commentary offer. Every notional and rate in the example is fictional.
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 market data
Funding history has separate symbol, funding-rate and funding-time data. A history rate is not an authenticated account payment. Checked 2026-10-21.