Thanks for the tip! I just looked at the actual Schedule D form in the PDF and you're right - there's a discrepancy. The main software screen shows $0 carryover, but Schedule D Line 16 is showing the $4,000 remaining loss amount. So it looks like the calculation is correct in the actual forms but just displaying wrong in the summary screen? Do you think I should contact the software company about this display issue or just ignore it since the actual form seems correct?

If the actual Schedule D shows the correct $4,000 carryover amount, then your tax return is being filed correctly and you should be fine. This is definitely just a display issue in the software interface. It's still worth reporting to the software company since others might be confused by the same issue. Take screenshots of both the incorrect summary page and the correct Schedule D to include with your report. But as far as your taxes are concerned, you're good to go - the IRS receives the actual forms, not the software's summary screens.

This is good advice. Numbers get fuzzy when we rely on memory. I've messed up carryovers before because I was working from memory instead of having my previous return open while doing my current taxes.

That's interesting! So are you saying some providers might actually allow employee contributions after December 31st, or is it more about how they classify the contributions internally? Has this approach ever caused issues with the IRS for you?

It's more about how they classify contributions internally. The IRS rules are still the same (employee contributions by Dec 31, employer by tax filing deadline), but some providers don't track the distinction in their system - they just report the total contribution amount. This approach hasn't caused me problems, but it requires careful record-keeping on your end. You need to document what portion was intended as employee vs employer when you file your taxes. The risk is if you exceed your allowed contribution limits for either category. I always consult with my tax professional to ensure my allocations are correct before finalizing my tax return.

Thanks for clarifying this! A lot of people confuse the deadline for establishing the plan with the deadline for contributions. I learned this the hard way last year when I set up my Solo 401(k) in February for the previous tax year, thinking I could still make employee contributions. Expensive lesson!

I tried this route and it was a nightmare. The software technically "allows" you to adjust basis, but doesn't help you calculate what the correct basis should be. I ended up paying a CPA $350 to fix my return after I'd already spent hours trying to figure it out myself.

Thanks for the validation. I've already started asking around for recommendations for next year. Did you find any specific questions that helped you separate the knowledgeable CPAs from those just claiming to understand crypto?

I ask them to explain how they handle specific crypto situations that I know are tricky - like liquidity pool rewards, token airdrops, or NFT transactions. The ones who give vague answers or just say "we can handle any crypto situation" without details are the ones to avoid. The good ones will be honest about what they know and don't know. My current CPA straight up told me he specialized in DeFi and mining operations but wasn't as familiar with NFTs. That honesty was refreshing, and he ended up partnering with an NFT tax specialist for that portion of my return. Transparency about their limitations is a huge green flag.

Eh, I disagree. The CPA did complete part of the work, so paying nothing would be unfair. The $250 partial payment makes sense. And honestly, most CPAs are overwhelmed during tax season - it sounds more like miscommunication than intentional deception.

This is why I just do my own taxes now. I spent $600 on a CPA two years ago only to find a mistake that could have cost me $1200. H&R Block software is like $70 and has handled everything I've thrown at it including rental property and some basic stock trades.

Couldn't this approach create headaches later when you switch to actual bookkeeping software? I imagine there's a lot of manual data entry and potential for errors when migrating from spreadsheets.

You make a valid point about potential migration headaches, but most early startups have such low transaction volume that it's not a major issue. When I migrated from spreadsheets to Wave, I only had about 200 transactions to deal with. It took one afternoon to set everything up properly. The bigger risk actually comes from overcomplicating things early on. I've seen founders spend thousands on comprehensive accounting systems they don't need yet, which diverts precious capital from growth. The spreadsheet approach forces you to understand your finances intimately before you delegate or automate. When you do upgrade, you'll make better decisions about what you actually need versus what's nice to have.

I used Bench for about a year. They're good if you want hands-off bookkeeping and don't have super complex needs. The main limitation I found was with customized reporting - sometimes I needed specific breakdowns for investors that their standard reports didn't provide. Their tax prep add-on was pretty solid though.