I went through this exact same situation with my mother's estate about two years ago. The IRS kept sending Form 1041-ES vouchers even though we had properly closed the estate in 2020. What worked for me was sending a certified letter to the IRS with copies of the final Form 1041 (clearly marked "Final Return"), the court order closing the estate, and a brief explanation that the estate had been fully distributed and closed. I included the estate's EIN and my contact information as executor. The key thing is to act quickly - don't let these sit around. The IRS automated system will start generating penalty notices if it thinks estimated payments are being missed. It took about 6-8 weeks after I sent the documentation, but I eventually received a letter confirming they had updated their records and would stop sending the vouchers. Keep copies of everything you send and use certified mail with return receipt so you have proof they received it. This is definitely fixable, just needs the right paperwork to get their system updated.

This is a really common issue that happens when the IRS's computer systems don't properly sync with the final estate closure. I'm a tax professional and see this regularly - you're definitely not alone in dealing with this frustration. The most important thing is to respond promptly with documentation proving the estate was closed. Here's exactly what I recommend sending via certified mail: 1. A cover letter explaining the estate closed in 2019 2. Copy of the final Form 1041 with "Final Return" clearly marked 3. Any probate court documentation showing estate closure 4. Include the estate's EIN and your current contact info Send this to the address shown on the Form 1041-ES. The automated system will stop generating these vouchers once their records are properly updated, but this usually takes 4-8 weeks to process. Whatever you do, don't ignore these - the system will start assessing penalties for "missed" estimated payments even though the estate doesn't exist anymore. I've seen clients get hit with thousands in automated penalties that take months to resolve. If you need the forms analyzed or help drafting the response letter, there are services that can walk you through this specific situation. But the key is acting quickly before penalties start accruing.

I work with a lot of clients who hold commodity ETFs, and there's a shortcut for handling these tiny expense transactions in tax software. In TurboTax: 1. Enter the info exactly as shown on your 1099-B 2. When asked for cost basis, enter the same amount as the proceeds ($0.28 in your case) 3. For "Sales expenses not included in proceeds" enter $0 4. For acquisition date, use your original purchase date This creates a $0 gain/loss transaction, which is the most accurate way to report these. Some tax experts argue you could technically calculate a tiny gain/loss based on your average cost basis, but the amount is so negligible it's not worth the effort.

Just to add another perspective on this - I've been dealing with SLV for several years now and the headache factor really depends on your tax software and how many other investments you have. If you're using basic tax software and SLV is your only "complicated" investment, it's manageable once you understand the pattern. But if you have multiple commodity ETFs, REITs with complex distributions, and other special situations, these micro-transactions can really add up to a lot of manual entry work. One thing I learned the hard way: keep good records of your original SLV purchase dates and amounts. When you have multiple purchases over time and these tiny expense allocations happening annually, it can get confusing to track which shares correspond to which original purchase for the acquisition date reporting. I now keep a simple spreadsheet just for tracking this. The silver lining (pun intended) is that once you've done it a few times, you'll be able to handle these transactions quickly each year. Just remember that the IRS gets copies of these 1099-B forms, so you definitely need to report them even though the amounts are tiny.

Has anyone had issues with their employer FSA administrator not processing reimbursements quickly? My daycare costs are due at the beginning of the month, but my FSA takes 3-4 weeks to reimburse me, creating a cash flow problem.

This is such a common confusion point! I went through the same thing last year and here's what I learned from my CPA: The key thing to remember is that you CAN use both benefits, but you cannot claim the same expenses twice. So with your $21,000 in childcare costs: 1. Use your $5,000 FSA first (this saves you taxes on that $5,000 based on your tax bracket) 2. You have $16,000 remaining expenses 3. For 2025, you can claim up to $3,000 of those remaining expenses for the Child and Dependent Care Credit (since you have one child) 4. The credit percentage depends on your AGI - it ranges from 20% to 35% So you'd get the tax savings from the FSA PLUS a credit of 20-35% on up to $3,000 of additional expenses. This is definitely not double dipping - it's exactly how the system is designed to work. One tip: make sure you keep detailed records of all your childcare payments and your provider's tax ID number. You'll need this for Form 2441 when you file. Also, some states have their own childcare credits that might stack on top of these federal benefits, so it's worth checking your state's rules too.

Does anyone know if you can still do a backdoor Roth for 2024? I thought I heard something about the government closing this "loophole" but I'm not sure if that actually happened or was just proposed.

This is exactly what happened to me last year! The 1099-R showing the full amount as taxable is completely normal and expected for backdoor Roth conversions. Don't panic - you're not doing anything wrong. The key thing to remember is that the 1099-R is just the brokerage firm's way of reporting the distribution to the IRS. They have no way of knowing whether your original contribution was deductible or non-deductible, so they default to showing the entire amount as potentially taxable. When you file Form 8606, you're essentially telling the IRS "Hey, I already paid taxes on this money when I earned it, so the conversion shouldn't be taxed again." The form calculates your basis (the after-tax money you put in) and shows that the taxable portion of the conversion is $0. Make sure you keep good records of your Form 8606 - I learned the hard way that the IRS doesn't always automatically match everything up in their system. But as long as you file it correctly with your return, you'll be fine!

I've been dealing with this exact same TaxAct saving issue and wanted to share what finally worked for me after trying everything mentioned in this thread. After reading all the technical suggestions here, I realized I needed to approach this systematically. What solved it was combining multiple fixes: I switched from Chrome to Firefox, disabled my ad blocker completely, added TaxAct to my trusted sites, and most importantly - worked during early morning hours (around 6am) when server load is lighter. The difference was incredible! I also discovered that my Kaspersky antivirus was blocking some of the save requests - once I temporarily disabled the web protection feature, the perpetual "saving" message finally disappeared. It's frustrating that it took so many steps, but at least I was able to finish my return without starting over. For anyone still struggling, don't lose hope! The data really is being saved in the background even when the interface freezes. I was terrified of losing my 1099 entries and W-2 information, but everything was still there when I finally got it working. The deadline stress is real, but there are definitely solutions that work if you're willing to troubleshoot systematically.

I've been lurking on this thread because I'm having the exact same TaxAct saving nightmare! After reading through all these incredibly helpful suggestions, I wanted to contribute something that might help others who are still stuck. I work in customer service for a different software company, and we see similar issues during high-traffic periods. One thing that hasn't been mentioned yet is clearing your browser's local storage specifically for TaxAct (not just cache and cookies). Sometimes corrupted local storage data can cause these infinite saving loops. To do this: Go to your browser's Developer Tools (F12), find the Application/Storage tab, locate TaxAct's local storage, and clear it completely. Then log back in fresh. Also, if you're using any browser password managers or auto-fill extensions, try disabling them temporarily. Sometimes they can interfere with form submissions in tax software. I'm planning to try the early morning + wired connection approach this weekend based on all the success stories here. This thread has been a lifesaver - it's so reassuring to know I'm not the only one dealing with this and that there are actual solutions that work!