CoinTracking - Profit/Loss Portfolio and Tax Reporting for Digital Currencies

[Andreas_CoinTracking]

Exactly. We have almost every exchange on the list. Depends on the customer needs and if there are already CSV direct imports available. Thank you again for your patience.

[jmd1982]

Few questions if anyone could possibly shed some light:

I have a weird issue with a few coinbase deposits. The deposits come from an unknown address (cointracking does not associate them with any of my added wallets) and when i view the blockchain this is what i see

https://i.imgur.com/SdbZtVj.png

1) any ideas? seems to be a cb to cb transfer but i have cb to cb pro transfers which do not read like this, its not a vault transfer either so i'm a bit stumped right now.
2) I seem to have some fee's on my ledger wallet deposits, not sure why, should i remove these?

example:  if i withdrawal from binance i would have a fee on the withdrawal entry and then i have a fee on the incoming ledger deposit entry.


3) i have some weird issue where the API refuses to pull in all my trades. I  didn't realize till i was more than half way through the coinbase pro API randomly leaves out entries. (maybe other exchanges as well im not too sure yet) Is there anyway i could quickly scan for the missing transactions and add them from the CSV into my API list? I know it says the csv and API cant both be used at the same time and i can't go 1 by 1 cause i would be here till next tax season.

4) how do i label deposits from wallets in which i can't figure out what they are so that they arent showing in the missing transaction list?

thank you

[Andreas_CoinTracking]

1. If you detected the missing transactions just add them manually as they appear in your CB account. They have a wallet as well. Or it is a subaccount.
2. We have this already on our improvement list reg. the deposit fee for ledger. For now please remove those fees manually after importing them.
3. Please make sure you have the latest API version installed - see Coinbase API issues (https://cointracking.freshdesk.com/a/solutions/articles/29000031012?lang=en). If you checked for the Vault topic already all transactions should come in via API. CSV and API could not be combined as it would lead to duplicates.
4. Please check this FAQ for options - either you find the counterpart transaction: White entries (no match) in Missing Transactions Report (https://cointracking.freshdesk.com/en/support/solutions/articles/29000033710-white-entries-no-match-in-missing-transactions-report)
and this one "Exchange closed or missing data due to wallet inaccessibility"(https://cointracking.freshdesk.com/a/solutions/articles/29000034626?lang=en)

[jmd1982]

thank you for the reply, i did a fresh import on all my csv files against a fresh import on my API in regards to the same exchanges/wallets and this is the difference
https://i.imgur.com/p8kWcQe.png

so the API fails to import about 690 or so entries compared to the csv file. Thats why i was asking if there was an easier way rather than going one by 1.  I already confirmed this with Christine she has access to my API's and said she would forward this issue on to the devs.

the keys are new for coinbase but i will try one more time and report back, thanks again

[Andreas_CoinTracking]

Okay, so we are working on this already via ticket which is better in that case as we can individually check your account here.

[shredhead1260]

I see that Binance chain is now supported for import. But I'm clicking on the address I added and it sends me to https://bscscan.org instead of https://explorer.binance.org/ so my wallet address is not the right one and it didn't import my transactions. I'm less familiar with this chain than ETH. Is this me doing something wrong or that you have not enabled import for my address?

[Andreas_CoinTracking]

Binance has 2 chains. Binance Chain and Binance Smart Chain (e.g. for smart contracts). We do support only the Binance Smart Chain (BSC) so far.
For the other chain you still need to add transactions manually.

[Spyderturbo007]

I'm currently staking a few coins with Coinbase which pays out every day.  This is generating a ton of transactions.  How is everyone else dealing with so many transactions?  I have the Pro plan, but soon I'll have to upgrade because of thousands of transactions that just pennies.

[FlacoEd]

So looks like this mega thread is for any questions related to cointracking? Ok then, here goes.

I have been adding fiat deposits for years using the 'deposit' designation. So far this has been fine, and all cap gain/loss calculations appear to be accurate, as the deposited fiat currency matches the fiat currency that I denominate my entire account in.

The problem I have run into is that last year I have added deposits to my account with a different fiat currency (I moved country and now earn this different currency). These deposits appear to have no cost basis so the entire amount is calculated as a capital gain in my report. I cannot for the life of me work out what category of deposit this should be listed as or what I need to do for it to work that same way as my original fiat deposits.

Any tips?

[Andreas_CoinTracking]

If it leads to "warnings" in the tax report you can use one or two settings in the extended tax report settings to avoid those warnings or even not calculating profits on FIAT (if allowed in your country).
Not sure if you changed your account currency to the "new" currency where you live now.
Please check this FAQ for details: Working with Two Fiat Currencies / Cost Basis 0 for FIAT (https://cointracking.freshdesk.com/en/support/solutions/articles/29000018222-working-with-two-fiat-currencies-cost-basis-0-for-fiat)

[shredhead1260]

how about XLM and EGLD import via blockchain?

[Andreas_CoinTracking]

We are working on Top15 Blockchain API imports so XLM would we one of the next available importers. Thank you for your patience.

[asdsvsdf]

I am trying to do my taxes via TurboTax and am importing my trades as TXF file but when I import them in TurboTax it says that every trade is missing the 'Sale Category' and requires I fill it myself for every trade which is a lot...

The sale category options are:

Box A - Short term covered
Box B - Short term noncovered
Box C - Short term not reported
Box D - Long term covered
Box E - Long term noncovered
Box F - Long term not reported
Box X - Unknown holding period

This post mentions the same issue from a year ago:  https://www.reddit.com/r/CoinTracking/comments/bd5l0u/cointracking_turbotax_cd_1099b_which_sale_category/

Is there anything I can do to get CoinTracking to fill this in for me in the file? It should have all the long and short info so idk why this is failing. Please help

I verified that this worked fine last year as my tax return properly has cryptocurrency split between long and short not reported (Box C and Box F) and I only used CoinTracking to import

EDIT: I went back into TurboTax 2019 to edit my old return and found out TurboTax changed how they handle trades. In 2019 TurboTax did not explicitly ask for sale category on each trade and seemingly determined this on their own (or the TXF file from CoinTracking accounted for this) but now it is and the info is missing in the TXF from CoinTracking. I think CoinTracking needs to urgently update their TurboTax file export to account for this, otherwise all people filling taxes using TurboTax and CoinTracking will have to manually write Sale category for every imported trade

From what I understand, the fix would be to ensure your TXF file simply marks each trade sale category as Box C or Box F depending on if they are short or long term respectively, but by not doing this all your users need to go trade by trade in TurboTax to edit which is a lot and very error prone

EDIT 2: After finishing my taxes with the import, looking at the raw 8949 tax form shows that long and short are properly represented with box C and box F entries respectively. idk why TurboTax warns about missing info if it defaults to the correct filing. as such this issue is less critical but is confusing to deal with because of the warning in TurboTax when importing CoinTracking info in their 'easy' flow

[Andreas_CoinTracking]

@asdsvsdf
Please send us a ticket or E-Mail to support@cointracking.info and I will check your account and send you some instructions.

[Andreas_CoinTracking]

Updates and Improvements

- New Blockchain import: Binance Smart Chain (BSC)
- New API import: FTX US
- HitBTC CSV Import now supports the new file format
- Several Binance API import fixes
- Binance CSV import for withdrawals now supports the new file format
- Exodus CSV import update
- FTX API import update
- Luno API import update
- OKCoin CSV import now supports the new file format
- Bitcoin.de API import fix regarding key signature issues
- Some Coinbase Pro API imports did not finish. This has been fixed.
- Export PDF of daily balance report shows incomplete data. This has been fixed.
- Form 8949 was updated with a new value "VARIOUS" for the sales acquire date, when multiple purchase dates exist
- Two new price conversion methods added ("Buy Price" and "Sell Price")

[PixxelDesign]

Updates and Improvements

- New Blockchain import: Binance Smart Chain (BSC)
- New API import: FTX US
- HitBTC CSV Import now supports the new file format
- Several Binance API import fixes
- Binance CSV import for withdrawals now supports the new file format
- Exodus CSV import update
- FTX API import update
- Luna API import update
- OKCoin CSV import now supports the new file format
- Bitcoin.de API import fix regarding key signature issues
- Some Coinbase Pro API imports did not finish. This has been fixed.
- Export PDF of daily balance report shows incomplete data. This has been fixed.
- Form 8949 was updated with a new value "VARIOUS" for the sales acquire date, when multiple purchase dates exist
- Two new price conversion methods added ("Buy Price" and "Sell Price")

Awesome! Waited for some time for the Binance update, thanks for your hard work.

[Convington]

Maybe I'm just too impatient, but it sure takes a long time for support to do anything  I mean, I did pay a good chunk of $$ for this service - so I would think I would get better than a 2 day wait for responses.

Ticket #51809 (waiting 2 days)

Ticket #52311 - a more concise version of the previous ticket since it was really a new topic that I responded with on the original.

**UPDATE** The combined and let me know they are on it.

[Andreas_CoinTracking]

@Convington
We are still checking your case. Raising another ticket with the same case only 4 hours ago plus this entry here is okay for us. Just to let you know that somebody needs to spend some time with a reply on all of those as well. We get back to you tomorrow and have now merged both of your tickets. Thank you for your patience.

[Convington]

@Convington
We are still checking your case. Raising another ticket with the same case only 4 hours ago plus this entry here is okay for us. Just to let you know that somebody needs to spend some time with a reply on all of those as well. We get back to you tomorrow and have now merged both of your tickets. Thank you for your patience.

Thank you.  If they read they will know I didn't "raise another ticket with the same case".  I should have created a new case to begin with, but I responded on my original because it was open and support was responsive.  Two days later I created a new case because I knew it was a new topic [and nobody was responding to the older case].  I guess I could have not opened another case with the new topic and then it would be 2 days and 4 hours since the updating of the previous case.  

My taxes hinge on this, so it is relatively important and not trivial .. US doesn't really like inaccurate tax reports and I'm fairly certain they have been inaccurate for all tax reports I've run in the system since 2017.  (**NOTE:  This is my fault, probably, because I had 2 Bittrex exchange accounts and changed APIs a couple of times).. I have been a loyal customer since 2017, so nothing bad to say about CoinTracking.

I will be patient now and thank you for merging the cases

[Andreas_CoinTracking]

Thank you for the clarification and your feedback. We are working on it. Thank you for your further patience.