Trading Fees in Multiple Currencies Worksheet
Total explicitly valued fee rows while keeping unvalued costs visible.
A hypothetical 0.0001 BTC fee valued at 50,000 USD per BTC contributes 5 USD. A 2 EUR fee valued at 1.10 USD per EUR contributes 2.20 USD. The valued total is 7.20 USD over two rows and two fee currencies. A row with no rate remains unvalued and is excluded from that subtotal.
What this helps you check
Fees paid in different assets cannot be added as if they share a unit. This ledger retains original fee-asset amounts and values each row only when you supply a positive conversion rate to one reporting currency. It makes the coverage of the resulting cost total explicit.
Valued costs is a partial subtotal whenever an unvalued row remains. The original asset totals are still useful for reconciliation, but they cannot be combined across currencies without rates. This worksheet does not determine tax basis, prescribe valuation timing or reconstruct a portfolio return.
Your worksheet
No account connection requiredInputs are processed in your browser by this calculator. There is no quote lookup or file upload for the calculation. Site measurement and consent are handled separately by the site's privacy and consent controls.
CSV schema: timestamp (iso8601), fee_asset (text), fee_amount (number), rate_to_reporting (number). Header required; comma delimiter. Numeric fields use decimal points. Timestamps require Z or a numeric UTC offset. The original input remains unchanged.
Interactive calculation requires JavaScript. The method and hypothetical worked example below remain readable.
Your result
Calculated from supplied values. See the notes and boundaries before interpreting the result.
Check the example by hand
A hypothetical 0.0001 BTC fee valued at 50,000 USD per BTC contributes 5 USD. A 2 EUR fee valued at 1.10 USD per EUR contributes 2.20 USD. The valued total is 7.20 USD over two rows and two fee currencies. A row with no rate remains unvalued and is excluded from that subtotal.
- Valued costs
- 7.2USD
- Valued rows
- 2
- Unvalued rows
- 0
- Fee currencies
- 2
Exact example inputs
{
"reporting_currency": "USD",
"csv": "timestamp,fee_asset,fee_amount,rate_to_reporting\n2026-01-01T00:00:00Z,BTC,0.0001,50000\n2026-01-01T01:00:00Z,EUR,2,1.10"
}The example is invented to demonstrate the method. It is not a current market quote, a provider's fee schedule or verified trading performance.
How the worksheet works
- fee_amount>=0; a supplied rate_to_reporting must be >0.
- valued_row=fee_amount*rate_to_reporting; sum only explicitly valued rows.
- Keep missing-rate rows with status 'Unvalued', count them and warn that the aggregate is partial.
- Also preserve sums by original fee_asset without combining different units.
Valued costs is a partial subtotal whenever an unvalued row remains. The original asset totals are still useful for reconciliation, but they cannot be combined across currencies without rates. This worksheet does not determine tax basis, prescribe valuation timing or reconstruct a portfolio return.
Boundaries to keep in view
- Rates and timestamps are supplied by the user; no live or historical price fetch.
- Do not silently use rate=1 for a same-looking ticker.
- No tax classification, cost-basis determination or automatic provider CSV conversion.
Compare resources for this task
Fee-ledger preparation needs original denominations and transparent valuation coverage. Transaction tools, portfolio records and spreadsheets can help organize the data, but a total is only as complete as the rates and records supplied.
Official sources and scope
The sources document formats, mechanisms or record workflows. The arithmetic and editorial comparison on this page use the supplied worksheet definitions.
- Kraken ledger versus trades
Trade fee estimates differ from actual ledger deductions and currencies.
Reference checked 2026-10-01. Consult the source for current product rules. - Koinly custom prices
User-supplied dated rates; original assets and valuation currency remain distinct.
Reference checked 2026-10-01. Consult the source for current product rules. - CoinLedger universal manual CSV
Provider-specific UTC transaction template, field mapping and already-included fee considerations.
Reference checked 2026-10-01. Consult the source for current product rules. - Delta transaction CSV template
Base, quote and fee currencies and explicit time zone; this CSV does not support shorts/margin.
Reference checked 2026-10-01. Consult the source for current product rules.