Tracking cost basis when transferring crypto from Fidelity to Robinhood - help needed

Quick question - if I've already transferred some ETH from Coinbase to Kraken last month without keeping records, am I totally screwed for taxes? Or can I somehow go back and piece this together from the blockchain transactions?

You're not totally screwed! For past transfers, you can still go back to your original platform (Coinbase in your case) and download your transaction history. Most exchanges keep this data available for several years. Look for your original purchases and note the dates and amounts. The blockchain itself doesn't store cost basis information, but it does verify the transfer occurred. So match up the transaction hashes from Coinbase with the receiving transactions in Kraken to confirm which assets moved where.

Does it work with all exchanges? I've got stuff spread across Binance, Kraken and some old Dogecoin in a hardware wallet I've had since like 2017.

I'm always skeptical of these crypto tax tools. How accurate was it really? Did you double-check any of the calculations or just trust what it spit out?

It works with over 500+ exchanges and platforms, including all the major ones like Binance and Kraken. They also support importing from hardware wallets, though you might need to export transaction details first depending on which wallet you're using. Dogecoin from 2017 is definitely supported! I was skeptical at first too, so I manually checked a few transactions against my records. Every calculation matched up perfectly. What impressed me most was how it identified transfers between wallets vs. actual buys/sells. It even caught some weird DeFi transactions that I had forgotten about. Their support team answered within hours when I had questions about a specific transaction that looked weird.

Wait how does this actually work? Does it like hack the IRS phone system or something? Seems kinda sketchy tbh.

There's no way this actually works. I've tried everything to get through to the IRS and always end up waiting 2+ hours or getting disconnected. If this actually worked, everyone would be using it.

It's completely legitimate - no hacking involved! It basically navigates the IRS phone tree for you and waits in the queue on your behalf. When an agent is about to pick up, it calls you and connects you directly. It's like having someone else wait on hold for you. I was honestly surprised too, but it's a real service that saves you from wasting hours listening to that terrible hold music. Nothing sketchy about it - just a smart solution to a frustrating problem.

Do you still have to manually match up the transfers or does Koinly do that automatically?

Koinly does automatically match most transfers between wallets that you've connected. It looks at the timestamps and amounts to identify when you've moved crypto between your own wallets rather than buying or selling. Sometimes with very common amounts (like exactly 1 ETH) you might need to manually confirm it's a transfer, but the system flags these for review. The real time-saver is that once you've imported all your exchange data, it calculates your complete tax position with all the correct cost basis information.

Robinhood's crypto service has actually improved a lot this past year. They finally added wallet transfers and their tax documents are pretty good now. The main advantage is having stocks and crypto in one place. But yeah their fees are still higher than dedicated exchanges.

This is incredibly helpful advice, especially the point about using blockchain explorers! I'm completely new to crypto transfers and honestly didn't even know those tools existed. Just checked out Etherscan and it's amazing how much transaction detail is available there. Quick newbie question - when you mention "specific identification" as a cost basis method, how does that actually work in practice? Is that something you declare on your tax return, or do you need to set it up somewhere beforehand? I've been doing small weekly Bitcoin purchases on Fidelity for about 6 months and I'm worried I might have already locked myself into FIFO without realizing it. Also, are there any red flags or common mistakes I should avoid when documenting everything? I don't want to accidentally create problems for myself down the road by organizing my records incorrectly from the start.

Great questions @4bed2ed7dafd! Specific identification is actually chosen when you file your tax return, not beforehand. You're not locked into FIFO just because you've been making regular purchases. The IRS allows you to use specific identification as long as you can adequately identify which specific coins you're selling/transferring with proper records. For your weekly Bitcoin purchases, you'll want to document each one separately with date, amount purchased, price per coin, and any fees. When you eventually sell or transfer, you can then choose which specific purchases those coins represent (maybe you want to use the highest cost basis to minimize gains, etc.). Common mistakes to avoid: - Don't mix up transfer dates with original purchase dates in your records - Always save transaction hashes for transfers (these are your proof) - Don't rely on exchange cost basis reporting - they often get it wrong for transfers - Keep records even for small amounts - those $50 weekly purchases add up - Screenshot everything before transferring, don't just rely on CSV exports The key is being able to trace every coin back to its original purchase. As long as you can do that with clear documentation, you have flexibility in your tax strategy later. @ccd7091be888 any other red flags you've encountered that newcomers should watch out for?

Great questions @4bed2ed7dafd! For specific identification, you don't need to set anything up beforehand - it's something you elect on your tax return when you actually sell. The IRS allows you to choose your accounting method as long as you can substantiate it with proper records. Since you've been doing weekly DCA purchases, you're actually in a great position! Just make sure you're tracking each individual purchase with its own date, amount, and price. When you eventually sell, you can then choose which specific "lots" you're selling from (maybe the highest cost basis ones to minimize gains). Common mistakes to avoid: - Don't mix up transfer dates with original purchase dates - Keep transaction hashes for every transfer (these are permanent proof) - Don't delete screenshots or CSV files thinking you can re-download them later - Avoid rounding numbers - keep exact amounts including all decimals The good news is that since you haven't sold anything yet, you haven't "locked in" any accounting method. You have flexibility until you actually realize gains or losses. Just keep documenting everything clearly and you'll have options when tax time comes! @ccd7091be888 probably has more insights on the specific ID method since they mentioned it.

Great questions @4bed2ed7dafd! Let me break this down for you: **Specific identification** is a tax accounting method where you specify exactly which crypto units you're selling (by purchase date and price) rather than using FIFO or LIFO. You don't need to "set it up" beforehand - it's something you choose when preparing your tax return. The key is having detailed records that allow you to identify specific purchases. Good news: you haven't locked yourself into FIFO! You can generally choose your accounting method each tax year as long as you're consistent within that year and have proper documentation. **Red flags to avoid:** - Don't mix up transfer dates with original purchase dates - Never guess at prices or dates - always use actual transaction records - Don't lose track of fees (they affect your cost basis) - Avoid using round numbers that don't match your actual transactions **Documentation best practices:** - Keep original exchange confirmations/emails - Screenshot everything before transferring - Save blockchain transaction hashes - Note any wallet addresses involved - Record the exact time/date of transfers Since you've been DCAing for 6 months, you're actually in a great position - just export all your Fidelity history now and you'll have everything you need. The regular purchase pattern will make tracking much easier than someone with random large transactions. @ccd7091be888 any other tips for someone just getting started with crypto record keeping?

Great questions @4bed2ed7dafd! Let me break this down for you: **Specific Identification** is actually declared when you file your taxes, not beforehand. You're not locked into FIFO just because that's what exchanges default to. When you sell crypto, you can choose to use specific identification on your tax return by identifying exactly which coins/tokens you're selling (by purchase date and price). You just need detailed records to support it. For your weekly Bitcoin purchases, you're actually in a great position! Just make sure you're tracking each purchase separately - date, amount of Bitcoin, price per Bitcoin, total cost including fees. This gives you maximum flexibility later. **Common mistakes to avoid:** - Don't round numbers - keep exact decimals for Bitcoin amounts - Always include fees in your cost basis calculations - Don't rely on just screenshots - export actual CSV data when possible - Keep records of wallet addresses used for transfers - Don't delete old exchange accounts until you're sure you have all historical data **Red flags:** - Inconsistent record-keeping methods between tax years - Missing documentation for large transactions - Forgetting to account for hard forks or airdrops if you received any The IRS guidance says you can change accounting methods between tax years with proper documentation, so you're not stuck with whatever method the exchange uses. The key is having detailed records to support whatever method you choose when you file.

Great questions @4bed2ed7dafd! For specific identification, you don't need to set anything up beforehand - it's a choice you make when filing your tax return. The IRS allows you to use different methods as long as you're consistent and can substantiate your records. Since you've been doing weekly purchases, you're definitely not locked into FIFO - you still have flexibility. The key for specific identification is having detailed records that can prove which exact coins you're selling/transferring. So for each weekly purchase, document the date, amount, price per coin, and total cost including fees. When you eventually sell, you can choose which specific purchases those coins came from (maybe selling the highest cost basis ones first to minimize gains). Common mistakes to avoid: - Don't mix up transfer dates with original purchase dates - Always include fees in your cost basis calculations - Keep records of wallet addresses involved in transfers - Screenshot everything before transfers (exchange interfaces change) - Don't rely solely on exchange records - they can disappear @ccd7091be888's advice about blockchain explorers is spot on. Those transaction records are permanent and can save you if exchange records ever get lost or corrupted. I'd also suggest keeping both digital and printed copies of your key transaction records, just to be extra safe.

Great questions @4bed2ed7dafd! For specific identification, you don't need to set it up beforehand - it's something you can elect when you file your taxes, as long as you have detailed records to support it. The IRS allows you to choose your accounting method each tax year, but you need documentation showing exactly which coins you're selling/transferring. With your 6 months of weekly DCA purchases, you're actually in a perfect position to use specific identification if you keep good records. Just make sure you document each purchase separately (date, amount, price) so you have the flexibility later. Common mistakes to avoid: 1) Don't mix up transfer dates with original purchase dates, 2) Always save the blockchain transaction hash as proof, 3) Don't forget to account for network fees in your cost basis, and 4) Keep records even for small amounts - they add up. The IRS doesn't require any specific format for your records, but consistency is key. A simple spreadsheet with Date, Amount, Price, Platform, and Transaction ID columns works great. The most important thing is being able to trace every coin from purchase through transfer to eventual sale. @ccd7091be888 mentioned TaxBit and CoinTracker - both are solid choices that can help automate this tracking if you want to avoid manual spreadsheet work.

Great questions @4bed2ed7dafd! For specific identification, you don't need to set anything up beforehand - it's a method you can elect when you file your taxes. The IRS allows you to choose which specific shares/coins you're selling as long as you can adequately identify them (date purchased, amount, price). This is actually more flexible than FIFO since you can optimize for tax efficiency. Since you've been doing weekly DCA purchases, you're in a perfect position to use specific ID. Just make sure you're tracking each purchase separately - date, amount of Bitcoin, price per Bitcoin, total cost including fees. When you eventually sell, you can choose to sell the highest cost basis coins first to minimize gains (or lowest cost basis if you want to harvest losses). For red flags to avoid: Don't round numbers or estimate - use exact amounts and dates. Don't change your accounting method randomly between tax years without good reason. And definitely don't lose those transaction records! I keep mine in multiple places (Google Drive, local backup, printed copies for the big transactions). The fact that you're thinking about this now puts you way ahead of most crypto investors who scramble to piece everything together at tax time!

Great questions @4bed2ed7dafd! For specific identification, you're not locked into FIFO just because you've been making regular purchases. You actually choose your cost basis method when you sell, not when you buy or transfer. However, once you use a specific method for a particular crypto, you need to be consistent with that method going forward. Specific identification means you can choose exactly which "lots" (specific purchases) you're selling. So if you bought Bitcoin at $30K, $45K, and $60K, you could choose to sell the $60K lot first to minimize gains (or the $30K lot to maximize losses for tax purposes). You document this choice on your tax return and in your records. For common mistakes to avoid: - Don't rely on exchange records alone - they can disappear or change - Always save transaction hashes from transfers as permanent proof - Keep records in multiple formats (CSV + screenshots + blockchain links) - Don't mix up transfer dates with original purchase dates - Document any fees separately since they affect your cost basis The fact that you're thinking about this now puts you way ahead of most people! Just start with a simple spreadsheet tracking each weekly purchase with date, amount, price, and fees. That foundation will serve you well no matter which cost basis method you eventually choose.

Great questions @4bed2ed7dafd! For specific identification (SpecID), you typically declare it on your tax return when you sell - it's not something you need to set up beforehand with the exchange. The key is having detailed records that allow you to identify exactly which coins you're selling. Since you've been doing weekly DCA purchases, you're actually in a perfect position to use SpecID later if it becomes advantageous. You haven't locked yourself into FIFO - that's just the default method exchanges use for their own tracking. When tax time comes, you can choose the method that works best for your situation, as long as you have the records to support it. For avoiding red flags: 1) Never estimate or guess at purchase prices - always use actual transaction data, 2) Keep transaction hashes for every transfer between wallets, 3) Don't mix up transfer dates with purchase dates in your records, and 4) If you're using multiple cost basis methods across different coins, document why and be consistent within each asset type. The biggest mistake I see people make is not accounting for network fees during transfers - make sure to track those separately as they can affect your cost basis calculations. @ccd7091be888 probably has more insights on common documentation pitfalls to avoid!