Topic: CoinTracking - Profit/Loss Portfolio and Tax Reporting for Digital Currencies - page 14. (Read 122619 times)

Okay, that´s fine, thank you. We need the individual account info as mentioned before via ticket/E-Mail.

I just told you how to replicate the bug.

We would need the individual information/account to investigate.

I figured it out. It has something to do with manual entries. I sent coins from personal wallet to kraken exchange, so I entered manually that I withdrew x amount of coins from my personal wallet.

While importing kraken data, it for some reason cointracking info thinks x coins withdrawn from personal wallet is the same entry as x coins deposited to kraken, so it skips that and doesnt import the deposit data. I think it will be easy to replicate this for your devs.

@KooperTooper
It would be helpful for us if you could send us your ledger file via Ticket/E-Mail [email protected] so that we can investigate on that. Thank you in advance.

For some reason cointracking.info does not import BTC deposit data from kraken correctly. It only shows 1st deposit, and the later ones are not imported. Tried api and csv.

When I review csv import data, missing btc deposits all say "skipped: trade already exists", even though they aren't showing up under "Enter coins-> Overview". Some sort of bug, I can add manually, but please fix it.

@lifeiscrypto
Okay we will do this.
@theratears
If you add those transactions manually or via Blockchain APIs before then there would be duplicates. You could adjust the CSV via a text editor and delete the API jobs to have a good cutover or you delete all previous transactions and use the CSV importer for Zerion only.

I noticed that there is now a zerion csv import. If i do this import will it duplicate all the transaction that i already have? just trying to work out the difference between this while also importing from me metamask address for example.

This sounds like a great solution to me yes, VEN2 ticker for the pre-swap VeChain values. Ok, for transactions older than 04.08.2018 I will introduce the value manually. Thanks!!

We have both on our improvement list.

It would be great to have some CSV import for Coinlist, and API for Coinlist PRO

We have prices back until 04.08.2018 for VEN. We would make them available under a VEN2 ticker as VEN is impulseVEN now. Could you confirm? In this case you would need to rename the old transaction ticker from VEN into VEN2.
If you have trade earlier then a price is available please adjust the asset value manually like we recommend for NFTs: https://cointracking.freshdesk.com/a/solutions/articles/29000038312?lang=en

Thank you for your reply.

Forget about the swap for a moment. In March 2018, before the swap, I had trades done between VEN and other coins (VEN = VeChain back then), right now there is no value assigned to VEN for those trades. Let's say I have to do a tax report for 2018 right now (and therefore the buy and sell values in 2018 are relevant). How can I solve this with Cointracking? do I need to input buy and sell values manually for those old trades?

Updates and Improvements

API
- new API import: KuCoin Futures
- Celsius (transaction type adjustment)
- Import for Kraken Earn transactions

CSV
- new CSV import: KuCoin Futures
- new CSV import: Bison
- Binance (ETH 2.0 Staking now imported)
- Celsius (transaction type adjustment, support for new transaction types, Trade IDs now imported)
- Gate.io (support for new format)
- HitBTC (support for new format)
- Uphold (support for new format and new transaction types)
- BSDEX (support for new format)
- Kraken (support for Earn transactions, import of FIAT fees when FIAT transfers are disabled)
- OKCoin (support for new format and interest)
- BlockFi (support for ACH transactions)
- Exodus (Update for deposit fees)

Blockchain
- new blockchain imports: AVAX & TERRA
- SOLANA (SPL transfers now correctly imported, support for DEX trades)
- ETH (OpenSea atomizer support)
- MATIC (Curve Staking support)
- Fix last import date display on blockchain import pages

Other
- several Ticker updates for correct assignments and price history
- tax report (KAP+SO, ACB and HMRC improvements, German headers in PDFs)
- new partner benefits
- Speed optimization of the recalculation
- From now on you can manually delete up to 5000 transactions at once in the table on the Enter Coins page. To delete more transactions, please use the "Bulk Edit/Delete" function.

Source: https://cointracking.info/new_features.php

I just checked this today and it doesn't seem to be fixed for those that had the old VeChain token in the past. I know that after the token swap the token is VET but VEN still shows on our old records which are relevant for taxation. So if you follow what it says here https://cointracking.freshdesk.com/en/support/solutions/articles/29000025684-ven-into-vet-swap you are not replacing in your old records VEN by VET, you still keep some VEN records, then you do a trade record (VEN to VET) and then you have maybe some more records using VET already.

I think in this case those that we had VEN we should automatically had renamed that token to something like "VEN2" or "VEN (old)" (as it is done for example with "GNT") and keep the records of whatever values they had in the past. Instead we have now assigned the incorrect coin "ImpulseVen" to it. Also it would be good to have some sort of notification about changing the assignation of a ticker like this. I think that another example (not 100% sure of this one) would be BitBay, which back in 2019 when I first introduced it in Cointracking "BAY", now "BAY" is the ticker for "CryptoBay".

If they do not come in via your ETH importer they are not supported yet. It is on our improvement list as well. Thank you for your patience.

Thanks. Is it only Erc1155 that are not imported? How about Erc721?
Thanks

@jjj0x
1. Handling of rebased Token is described here: Handling of Rebase token or elastic coins like AMPL (https://cointracking.freshdesk.com/a/solutions/articles/29000038326?lang=en)
2. Please send us a ticket/E-Mail to [email protected] with your account user name to check. All transactions should be imported. You could download the CSV file to compare if something is wrong on coinbase end providing the data.

Coinbase Pro is lame

Has anyone noticed if they have missing trades for XRP sales in the few weeks preceeding the delisting Jan 2021

My coinbase pro API seems to have imported All non Xrp token trades properly into Cointracking for the last year.... but for whatever reason
it did not import my XRP sales Jan 2021 .... I cant figure out if its a coinbase pro exporting issue or a cointracking importing issue.  Again all the non XRP
trades seem to have imported fine.

I see the XRP sales in my coinbase pro history so not sure why its not in cointracking

How are people treating the issue of olympus style tokens -- Such as sOHM, Time/Memo, Invictus

they are rebasing several times a day sometimes continuously

can anyone share how they are handling the income reports ?   

What a Pain in the ASS!

i just converted to gOHM so i dont have to deal with this anymore.   but Invictus and Snowbank are still ongoing income rebases