- Significantly faster calculation of all data
- New calculation of margin, futures and derivative transactions, now included in the Capital Gains Report
- Improved "Best Prices" conversion method (by market volume) for coin-to-coin transactions
NeuTransactions in the same second get picked in a way to minimize gains- Fully automated depot separation
- Optimization and correction of some rules for HMRC, AVCO and ACB reports
- Schedule D, Schedule 1 and Form 1040 exports added to all Form 8949 PDF downloads
Questions and Answers about the new tax reports
Question:
When creating tax reports for past years, I now get a slightly different result than with the old tax reports.
Answer 1:
The new reports take transaction fees for deposits and withdrawals into account and correctly deduct them from the purchase pools. This can lead to slightly different values.
Answer 2:
The number of transactions can differ between the old and new reports, as new reports combine several purchase pools for some sales.
Purchases grouped from multiple purchase pools are marked in the final report with the total number of used pools (see image).
In the detailed report you can view all individual purchase pools - as before.
Answer 3:
Due to our improvement of the "Best Price" method, there may be slight deviations in the asset values for coin-to-coin transactions. Especially if you sold an Altcoin with a small market cap.
Old Best Price calculation method:
Priority 1: All FIATS (EUR, USD, GBP ...)
Priority 2: BTC
Priority 3: Altcoins
New best price calculation:
Priority 1: All FIATS (EUR, USD, GBP ...)
Priority 2: Coins prioritized according to market cap
Answer 4:
Due to the constant optimization of our imports, it may be that new historical transactions have been imported since the last tax report generation. This can be checked on the Trade List (Full View) page with the column "Add Date".
This results in different historical values and a possible shift in purchase pools.
Answer 5:
Since generating the old report you have changed or added some trades or removed warnings.
Question:
I have more warnings when using depot separation than without a depot separation
Answer:
The separation of lots / depots requires that all movements of coins are correctly entered with a deposit and a withdrawal.
If some of these entries are missing, this leads to empty purchase pools and thus to warnings.
1) Example without deposits and withdrawals:
January 1st, 2020 - Buy 1 BTC from Kraken
January 2nd, 2020 - Buy 1 BTC from Kraken
January 3rd, 2020 - Buy 1 BTC from Poloniex
January 4th, 2020 - sale of 1 BTC at Poloniex
Result without depot separation:
- Sale of 1 BTC from the Kraken purchase pool from January 1st, 2020
Closing position in the tax report:
- 1 BTC at Kraken (January 2nd)
- 1 BTC at Poloniex (January 3rd)
Result with depot separation:
- Sale of 1 BTC from the Poloniex purchase pool from January 3rd, 2020
Closing position in the tax report:
- 1 BTC at Kraken (January 1st)
- 1 BTC at Kraken (January 2nd)
2) Example with deposits and withdrawals:
January 1st, 2020 - Buy 1 BTC from Kraken
January 2nd, 2020 - Buy 1 BTC from Kraken
January 3rd, 2020 - Buy 1 BTC from Poloniex
January 4th, 2020 - withdrawal of 1.00 BTC for Kraken (incl. 0.01 BTC fee)
January 4th, 2020 - deposit of 0.99 BTC at Poloniex
January 5th, 2020 - sale of 1.99 BTC at Poloniex
Result without depot separation:
- Sale of 0.99 BTC from the Kraken purchase pool from January 1st, 2020
- Sale of 1.00 BTC from the Kraken purchase pool from January 2nd, 2020
Closing position in the tax report:
- 1 BTC at Poloniex (January 3rd)
Result with depot separation:
- Sale of 0.99 BTC from the Kraken purchase pool from January 1st, 2020 (which was transferred to Poloniex on January 4th and was still there at the time of the sale)
- Sale of 1.00 BTC from the Poloniex purchase pool from January 3rd.
Closing position in the tax report:
- 1 BTC at Kraken (January 2nd)
This Q&A list is constantly updated.