Separate the execution from each expense movement
A fill quantity and a commission amount belong to different fields. A later credit can relate to that expense without creating another execution. Keep the scoped fill reference, fee asset and each movement’s source identity rather than adding every related row to the fill quantity.
The cited account schema illustrates that commission amount and asset are separate data. It does not prove that your own source provides rebates or establish a venue policy. Every movement in the following teaching ledger is explicitly invented.
Compare a debit and credit in one unchanged asset
Suppose an entered fee debit is 0.020 FEE units and a separately supplied related credit is 0.005 FEE units. Under the declared model, net expense is 0.015 FEE units. The credit does not reverse the original fill or change its base-asset quantity.
Keep both gross movements instead of overwriting the debit with the net value. A later review may need to establish whether the credit really relates to that fee, whether it is final and whether its asset definition matches the debit.
| Fictional movement | Entered asset amount | Interpretation |
|---|---|---|
| Original fee debit | 0.020 FEE | Expense movement |
| Related partial credit | 0.005 FEE | Separate supplied credit |
| Conditional net expense | 0.020 − 0.005 | 0.015 FEE |
| Execution quantity | No new fill supplied | Not changed by this arithmetic |
An equal amount or nearby timestamp does not prove the relationship
A credit can have another purpose. Preserve its source type and available reference rather than assigning it to a fee because the numbers are convenient. If the relationship is not supported, report the debit and unallocated credit separately.
Likewise, two copies of one credit should not be counted twice. Preserve original rows with their scopes and a documented grouping rule. Do not erase a source record simply because its amount resembles another movement in the same asset.
A CAD layer needs a declared valuation convention
A Canadian reporting view can convert each movement using supplied rates and times, but it must say which convention is used. Converting debit and credit at their own times can differ from valuing a net asset quantity once at a later price.
Neither method is prescribed here. Without conversion evidence,0.015 FEE remains an asset quantity, not 0.015 CAD. A stable-looking asset label or a current market quote cannot substitute for the missing historical valuation input.
Retain gross movements, conditional net and unresolved attribution
A useful result lists the debit, the credit, their identity evidence, original asset and the chosen reporting convention. It can show the conditional net expense while keeping the actual relationship and authenticity of supplied records separate.
This guide authenticates no rebate, fee schedule, account balance or tax treatment and recommends no trade. The amounts are fictional. The optional linked offer is not independently validated by a reproducible expense calculation.
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: Spot account data
Illustrative account-trade maker/side fields and account records, not authenticated records from a real account. Checked 2026-10-21. - Python documentation: rational arithmetic
Exact rational arithmetic independently checks the invented numerical examples; no actual fee, signal or trade is authenticated. Checked 2026-10-21.