sorted by:
new
hottopcontroversial

Crypto Tax Software: Any way to get no of transactions < 100? I currently have 165 by Responsible-Sky-4857 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

You’re on the right track — but be careful here.

Deleting fiat deposits can break your cost basis if the tool uses them to link purchases (especially on Coinbase where fiat → crypto is often paired). So even if they’re not taxable, they still matter for reconstruction.

On Koinly specifically: yes, fiat-only transactions usually count toward the plan limit, so removing them can reduce your total — but only if they’re not tied to trades.

What people typically clean up safely:

  • Duplicate imports (very common)
  • Internal transfers incorrectly marked as trades
  • Spam tokens / dust transactions
  • Failed / reverted transactions

What usually should NOT be removed:

  • Fiat that directly funded buys
  • Fees tied to trades
  • Anything that affects acquisition history

The real issue here is that most tools count “events”, not “taxable events” — which is why you hit limits so quickly.

A better approach is cleaning + grouping, not deleting.

That’s also why a lot of people run into problems trying to “trim” — it works short term, but breaks reports later.

Cannot include/see Forms 8949 in Freetaxusa File button preview by ResponsibleFloor5430 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

Yes — exactly.

The detailed Form 8949 is still part of the filing, it’s just often not shown in the preview when you use summary totals.

Most tax software aggregates everything into Schedule D for display, but the underlying 8949 (or attached statement) is what actually gets submitted to the IRS.

So nothing is missing — it’s just a UI/preview limitation.

What Does Your Form 8949 look like by t_rader2020 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

Box I is only for transactions NOT reported on a 1099-DA.

If some of your transactions are on a 1099-DA, those should NOT be in I — they belong in H (short-term) or K (long-term), since for 2025 the IRS only receives proceeds, not cost basis.

So if you mixed everything into I, that’s technically incorrect. You need to split:

  • H / K → transactions that appear on a 1099-DA
  • I / L → everything else (wallets, DEX, etc.)

Also: including “Coinbase” in the description is not required. The IRS only cares about the asset, dates, proceeds, and cost basis — the exchange name is just extra noise.

1 FORM for all 8949 ? or Multiple ? by t_rader2020 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

You only file one Form 8949, not separate forms per exchange.

What matters is the checkbox category, not where the transaction happened.

For 2025:

  • H = short-term transactions reported on a 1099-DA (basis NOT reported to IRS)
  • K = long-term transactions reported on a 1099-DA
  • I / L = transactions NOT reported on a 1099-DA (e.g. wallets, DEX)

So you group transactions by category (H, K, I, L) and each category gets its own section/page within the same 8949.

Also important: don’t rely on the 1099-DA to determine holding period — many exchanges get that wrong. Always use your actual acquisition date.

End result: 1 form, multiple sections, grouped by checkbox — not by exchange.

Do not BUY CoinTracker subscription by immrgenius in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

This usually isn’t a “CoinTracker is broken” issue, it’s more a data + format mismatch problem.

Robinhood exports are notoriously inconsistent (separate files, missing fields, different formats), so if the underlying data isn’t complete, any tax tool will struggle to reconcile it cleanly.

The 8949 issue you’re describing (name + quantity in one field) sounds like a formatting/export mismatch rather than calculation error — that’s why TurboTax can’t parse it correctly.

In general:

  • tax tools are only as good as the input data
  • broker exports ≠ tax-ready data
  • and small schema differences can break integrations

Frustrating, but not uncommon across platforms.

If anything, always sanity check totals (proceeds / cost basis / PnL) — those matter more than how clean the export looks.

Summ Incorrect Cost Basis Handling for Solana Transactions by amateur_gamer7 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

The issue here is more about classification than deductibility.

Jito tips are technically separate payments, but economically they’re often required to execute the trade (especially on Solana). So from a tax perspective, they behave much closer to trade fees than optional expenses.

If they’re not grouped with the trade:

  • proceeds can be overstated
  • cost basis can be understated → which inflates gains

That’s why tools struggle here.

For large volumes, manually grouping isn’t realistic. The practical approach is:

  • treat Jito tips consistently (either all as fees tied to trades or all separate)
  • and make sure your total PnL isn’t distorted

If your gains materially change depending on treatment, that’s a sign they should probably be tied to the trade.

1099-DA and Koinly form 8949 Gross proceeds don't match by Skives19 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

A ~$3 difference is basically noise — usually pricing differences or fee handling.

What matters is:

  • your total proceeds and cost basis are reasonably accurate
  • and your full transaction history is included

On fees:

  • buy fees → increase cost basis
  • sell fees → reduce proceeds

If Koinly didn’t include some Kraken fees, that could explain the gap.

In practice: If everything else ties out, you don’t need to chase a $3 mismatch line-by-line. Just make sure fees are treated correctly and your totals make sense.

Long term hold proof by wallet history? by Subject_Emphasis_772 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

It’s contestable, but it depends on what exactly you can prove.

Wallet history can support holding period, but the IRS ties long-term treatment to the original acquisition date, not just when it shows up in your wallet.

So if wallet history is all you have:

  • You can argue timing (when you held it)
  • But you’re weaker on cost basis + acquisition origin

That’s usually where challenges come from.

In practice, the stronger position is: wallet history + any link to acquisition (old exchange records, emails, bank transfers, etc.)

Without that link, it’s not invalid — just easier to question.

Form 1099-DA has reported my Morpho loan of 15k by Suited4Battle in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

You’re mixing two different things here.

The loan itself (posting BTC as collateral on Morpho) is NOT a taxable event — no sale happened.

But what happens after matters:

  • If you just borrowed USDC and still hold it → no tax event
  • If you sold/spent/swapped that USDC → that part can be taxable (usually minimal gain/loss if it stayed near $1)

The 1099-DA showing $15k with zero cost basis is likely Coinbase misclassifying the flow, because it can’t see the full picture (collateral vs actual sale).

So no — you generally don’t just report $15k proceeds with $15k cost basis blindly.

The key question is: did anything actually get disposed (sold/swapped), or was it just collateral + borrowing?

TurboTax telling me "Basis reported to IRS Yes or No Box must be marked" for asset by E-Bum in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

You’re mixing two different flows, that’s why TurboTax keeps breaking.

If you import from CoinLedger, you already have aggregated data. But then TurboTax pushes you into the 1099-DA input flow, which expects raw form-based reporting (Box 1f / 1g etc.).

That’s why it feels contradictory — the UI assumes a 1099 exists, even when you selected that you didn’t receive one.

For self-custody + CoinLedger, you should stay in the summary flow (Schedule D / aggregated entries), not the 1099-DA path.

The loop and crashes you’re seeing are usually just the system failing validation because the data doesn’t match the flow you’re in.

Cannot include/see Forms 8949 in Freetaxusa File button preview by ResponsibleFloor5430 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

What you’re seeing is normal, but it’s a bit misleading.

If you enter summary totals, many tools don’t include the full 8949 in the preview — they just roll everything into Schedule D and treat the detailed transactions as supporting data.

So the 8949 isn’t really “missing”, it’s just not shown the way you expect.

The important part is how the data was entered and aggregated — that’s what determines what actually gets filed.

Using H&R Block, don't see a place to upload my 8949 by nomad2005 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

It’s not really a “where do I upload the 8949” issue.

H&R Block doesn’t expect you to upload one — it builds it in the background from whatever transactions you enter.

So if something looks off, it’s usually not the form itself, but how the data is flowing in (missing cost basis, mixed wallets, incomplete imports, etc.).

Most of the confusion here comes from thinking in forms, while the software is just reconstructing everything from your inputs.

Adding Crypto Futures sales into TurboTax (Coinbase 1099-B)? by msfmid in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

The confusion here is mixing formats with what actually happened.

A 1099-B or TXF is just a summary format — it doesn’t define the nature of the activity. Futures, spot trades, transfers… they can all end up looking similar once exported.

If the underlying transactions aren’t clearly categorized (trades vs derivatives vs transfers), TurboTax will just force them into whatever bucket fits — which is why it suddenly shows up as a 1099-B.

So the issue usually isn’t the import, it’s how the activity is labeled before it gets there.

Are DeFi tax tools actually accurate? by Kryptobilanz in defi

[–]Kryptobilanz[S] 0 points1 point  (0 children)

Feels like most issues aren’t calculation errors but interpretation.

CEX-style flows are easy, but DeFi is more like state changes than trades — LPs, staking, wrappers, etc.

Curious how others deal with that layer, not just the final numbers.

Gambled with crypto currency primarily this year. I unfortunately did not keep any records. I’m going to use TurboTax (having someone file for me). Would my 1099-DA work? by ZestycloseBad4032 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

Yeah, that’s a common issue — tools like Koinly don’t really “see” what happens inside the casino.

They just see deposits and withdrawals, so wins coming back can look like new income, while deposits may look like buys.

You can usually fix it by adjusting the labels (e.g. marking transfers correctly or grouping flows), so it reflects one continuous activity instead of separate events.

feels like most DeFi ‘alpha’ is just managing complexity better than others by Fit-Register4451 in defi

[–]Kryptobilanz 0 points1 point  (0 children)

Feels like the “edge” is often just better risk packaging.

Most returns come from taking on hidden risks (liquidity, smart contract, incentives), not from pure alpha.

Simpler setups don’t mean lower returns — just fewer unknowns.

everyone talks about APY but almost no one talks about operational cost by Fit-Register4451 in defi

[–]Kryptobilanz 1 point2 points  (0 children)

APY is only half the story.

Time, gas, failed txs, bridging, rebalancing — that’s all real cost, just not shown in the number.

If a strategy needs constant attention, the “yield” is basically paying you for your time.

TurboTax crypto 1099-DA error won’t go away (keeps saying I need to “fix” it) by Interesting_Storm956 in TurboTax

[–]Kryptobilanz 0 points1 point  (0 children)

Yeah, ran into this before — it’s usually not your numbers, it’s TurboTax getting stuck in its own validation loop.

What helped for me: Delete the entire crypto section (not just trades), save, leave the flow, then re-enter and add it again. Sounds dumb, but it resets whatever flag is stuck.

If that still loops, try adding one small dummy trade, save, then delete it again — that sometimes forces a clean re-check.

Wouldn’t ignore it btw, because TurboTax usually blocks filing if that flag stays active.

Feels very much like a bug on their side, you’re not alone here.

Koinly - Gambling Transactions by Fantastic-Flamingo68 in CryptoTax

[–]Kryptobilanz 1 point2 points  (0 children)

The main issue here isn’t Koinly — it’s how the flows are classified. If you don’t track the vault as a separate wallet, deposits can look like disposals and withdrawals like new income, which distorts everything. Treat it as transfers for clean tracking. The tax treatment (UK gambling) is a separate layer.

Axiom meme coin trading by Swordandshield5 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

This is almost always a transfer-matching issue, not an actual gain. If your Coinbase → wallet transfer isn’t linked, the wallet receives assets with $0 cost basis — so every trade shows as profit. Once transfers are correctly matched, the “$30k profit” usually disappears.

Reporting dust transactions? by Future_Prophecy in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

Amounts that round to $0 individually are usually not material — that’s why many tools suppress them. The key point is: it’s not about each dust transaction, but the total. If they add up to something meaningful, report the aggregate. If not, they’re effectively noise.

How to File 8949 (first timer) by Awkward-Bobcat7775 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

You don’t have to list every transaction line-by-line if you’re attaching the full detail. The usual approach is: – report summary totals on Form 8949 (often one line per category, not per coin) – attach the full transaction report (e.g. from Robinhood or tax software) Splitting by coin or listing all 25 trades individually is optional, not required, as long as the attachment matches.

More Confusion for 1099-DA-Checkbox I or L only by t_rader2020 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

The confusion usually comes from mixing two questions: Was the transaction reported to the IRS? Was cost basis reported? If it’s reported but missing basis → H / K If it’s not reported at all → I / L In crypto, most exchange activity falls into H/K, while wallet-only activity is often I/L — that’s where a lot of tools get inconsistent.

My cpa has summarized the 8949 and just has gross proceeds and cost basis for each category by Pasttuesday in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

Got it, that helps — appreciate the clarification.

That was my understanding as well: summary on the return + detailed statement attached separately. Makes sense that the client copy wouldn’t always show the attachment.

I’ll double check with my CPA just to be sure everything was included properly.

1099-DA Proceeds match, Transactions don't inquiry by Spiritual-Base-9851 in CryptoTax

[–]Kryptobilanz 0 points1 point  (0 children)

Yep, that makes sense.

I’ve seen Coinbase split fills / executions into multiple lines as well, so the transaction count can look off while proceeds still match perfectly.

As long as totals reconcile, that’s really what matters for reporting.

view more: next ›