I used FreeTaxUSA last year and ran into a really annoying issue with their state tax calculations that almost cost me money. I live in a state with no income tax, but I had some income from work I did in California. FreeTaxUSA kept trying to file a resident return for California instead of a non-resident return, even though I clearly indicated I was just working there temporarily. The software's interview questions about multi-state situations were confusing and didn't seem to account for my specific scenario. I caught the error during my review, but it took multiple attempts to get the forms right. Had to manually override several fields that the software kept "correcting" back to the wrong values. If I hadn't been careful, I would have overpaid California taxes by about $800. Their help documentation for multi-state filing was pretty sparse too. Eventually got it sorted out, but it made me realize that FreeTaxUSA really assumes you have a straightforward tax situation. Anything even slightly complex and you're mostly on your own to figure it out.

I've been using FreeTaxUSA for about 3 years and had a particularly annoying experience with their cryptocurrency tax reporting last year. The software technically supports crypto transactions, but the process is incredibly manual and error-prone. I had transactions from multiple exchanges (Coinbase, Kraken, and some DeFi stuff), and FreeTaxUSA basically just gives you empty fields to fill out without much guidance on how to calculate cost basis correctly, especially for things like staking rewards or DeFi yield farming. The worst part was when I tried to report some NFT sales - the software had no clear category for them, and their support basically said to "treat them like other capital assets" without explaining which forms to use or how to calculate the basis when I received them as airdrops. I ended up spending probably 15+ hours trying to get everything right, cross-referencing with IRS publications and crypto tax guides. Compare that to friends who used more expensive software with built-in crypto integrations - they were done in a couple hours. So if you have any significant crypto activity, just know you'll be doing most of the heavy lifting yourself. FreeTaxUSA will accept the numbers you give it, but don't expect much help figuring out what those numbers should be.

This thread has been incredibly helpful! I'm actually a tax professional and wanted to add one more perspective that might be useful for Sean and others in similar situations. With your combined income of ~$186k and October marriage date, you're in a pretty good spot. The single withholding you both had for most of 2025 likely means you won't need as aggressive additional withholding as some couples do. One thing I always tell clients in your situation: after you both update to option 2(b), wait about 2-3 paychecks to see how the new withholding feels, then run the IRS Withholding Estimator. This gives you real data to work with rather than estimates. Also, consider this a learning year. Your 2025 tax return will give you the perfect baseline for setting up your 2026 withholding perfectly. Keep good records of what you did this year (copies of both W4s, when you submitted them, etc.) - it'll make next year's planning much smoother. The fact that you're thinking about this proactively puts you way ahead of most newlyweds. You've got this!

This thread has been incredibly educational! As someone who just went through the exact same situation (married in September, similar income levels), I can confirm that going with option 2(b) was definitely the right choice for us. One small thing I'd add that helped me feel more confident about the process: I actually called my payroll department before submitting my updated W4 to ask them to walk me through exactly what would change on my paystub. They showed me the difference between what was being withheld at the "married" rate versus what would be withheld with the 2(b) option checked. Seeing the actual dollar difference per paycheck really helped me understand why this change was necessary. The increase in withholding was significant but not shocking - about $180 more per paycheck for me. When I explained to the payroll person that my spouse and I have very similar incomes, she said "oh yeah, you definitely need to do this or you'll owe at tax time." Sean, you're smart to tackle this now rather than discovering the issue next April! The peace of mind is worth the extra effort upfront.

The $600 threshold is definitely the key here, and it sounds like you're on the right track with your understanding. Since you mentioned your uncle didn't have investments or rental properties, the main things to look out for would be interest earned on his bank accounts after his death, any final paychecks that came in after he passed, or dividends from any stocks he might have owned. One thing that catches a lot of people off guard is that even small amounts of interest can add up over time if the estate stays open for several months. If you're settling things quickly and the only income is minimal bank interest, you'll likely stay well under the $600 threshold. The EIN letter language is indeed standard - they send the same wording to everyone regardless of the actual filing requirements. It's meant to cover all situations, but the $600 gross income rule still applies to determine if you actually need to file Form 1041 for your specific situation.

I went through this exact same situation when my aunt passed away last year. The EIN letter really does make it sound mandatory, but you're absolutely correct about the $600 threshold still applying. In my case, the estate only generated about $85 in bank interest over the 8 months it took to settle everything, so no Form 1041 was needed. The key thing I learned is that "gross income" specifically refers to money the estate EARNED after death - not the value of assets that already existed. So in your uncle's case, his checking account balance, retirement funds, and truck value don't count toward the $600. Only new income like interest earned on those accounts after his passing would matter. If he didn't have investments generating dividends or rental properties, you'll probably stay well under the threshold. Keep track of any interest earned on the estate bank account though - that's usually the main source of income for simple estates like this. As long as it stays under $600 for the tax year, you can ignore that "must file" language in the EIN letter.

Has anyone tried contacting Cash App support about this? I'm having the same QBI calculation issue and wondering if they're aware of the bug where it doesn't update when expenses change.

I've been dealing with QBI calculations for years as a freelance web developer, and I can confirm that Cash App's automatic calculation often gets it wrong, especially with the recalculation issue you mentioned. Here's what works for me: First, calculate your QBI manually using your Schedule C net profit as the starting point. For freelance graphic design work like yours, your QBI should generally equal your Schedule C profit (total income minus business expenses) with a few potential adjustments. The key adjustments to watch out for: - If you have any guaranteed payments or W-2 wages from the business, subtract those - If you have investment income mixed in with business income, that needs to be separated out - Self-employment tax deduction and health insurance deductions don't affect QBI - those are separate Since you're in a service business, also be aware that if your taxable income exceeds $182,050 (for 2023 taxes), phase-out limitations start applying to your QBI deduction. My advice: Calculate it manually first, then override whatever Cash App shows. I use a simple spreadsheet to track this each year so I don't have to rely on buggy software calculations.

I've been wrestling with this exact same issue for the past three days and finally got it resolved! After trying most of the suggestions in this thread, what worked for me was a combination of clearing browser cache AND checking my network settings. It turned out my router's DNS settings were causing issues with the Free File authentication servers. I switched from my ISP's default DNS to Google's public DNS (8.8.8.8 and 8.8.4.4) and suddenly everything started working again. Also wanted to mention that if you're on a shared network (like apartment wifi or a coffee shop), that might be part of the problem. The IRS systems seem to get confused when multiple people are accessing from the same IP address. I had to switch to my phone's hotspot to complete the login process. Your saved data will definitely still be there - mine was completely intact after being locked out for days. Don't lose hope! The filing deadline stress is real, but there are so many solutions in this thread that one of them will work for your situation.

I went through this exact same frustrating experience last month! The password field clearing with no error message is maddening - you feel like you're going crazy because there's no indication of what's wrong. Here's what finally worked for me after days of trying everything: I had to completely sign out of my Google account in my browser before attempting to log into Free File. Apparently there was some kind of session conflict between my Google authentication and the IRS system that was causing the silent failure. The steps that worked: 1. Sign out of ALL accounts in your browser (Google, Microsoft, etc.) 2. Clear cookies specifically for irs.gov and any freefile domains 3. Restart your browser completely 4. Go directly to the official Free File site through IRS.gov (not bookmarks or search results) 5. Try logging in with a fresh session It sounds simple but this combination fixed my issue when nothing else would. All my previously entered tax data was still there waiting for me - what a relief! I also learned that the Free File system doesn't play well with certain password managers during the authentication process. If you use one, try typing your password manually instead of auto-filling it. Don't give up! Your data is safe and there's definitely a solution that will work for your specific setup. This thread shows how many different technical factors can cause the same symptom, but also that everyone eventually finds their way back in.