


Ask the community...
Does anyone know if the adoption tax credit is still non-refundable for 2024 filings? I'm planning to adopt next year and trying to figure out how this will impact our taxes.
Thanks for starting this thread, Liam! The adoption tax credit carryforward rules can definitely be confusing. Just to add some clarity to what's already been shared: You're correct that the 5-year carryforward period includes the original year you qualified (2020). So your deadline to use any remaining credit is indeed 2024 - this is your final year to claim it. One important thing to keep in mind: make sure you have enough tax liability to absorb the credit. Since it's non-refundable, you can only use it to offset taxes you actually owe. If you don't have sufficient tax liability in 2024, any unused portion will unfortunately expire. I'd also recommend keeping detailed records of how much you've used each year. The IRS doesn't automatically track this for you, so you'll need to calculate your remaining balance yourself when filing. Form 8839 is required each year you claim any portion of the credit, including carryforward amounts. Good luck with your 2024 filing!
This is really helpful, Maria! I'm in a similar situation and wondering - if someone doesn't have enough tax liability in their final carryforward year to use up all the remaining credit, is there any way to generate more tax liability? Like maybe doing a Roth conversion or something like that to create taxable income? It would be such a shame to lose thousands of dollars in credits just because of timing.
I'm experiencing the exact same issues with FreeTaxUSA today! Started trying around 10am and it's been completely unreliable - sometimes it loads partially, other times I get timeout errors. Really frustrating since I also planned today specifically for tax filing. Based on what others are saying here, it sounds like this is pretty normal for tax season and the site should work better during off-peak hours. I'm going to try again tonight around 10pm or early tomorrow morning. For what it's worth, I used FreeTaxUSA last year and had a great experience once I actually got on the site - their interface is clean and the price can't be beat. I think it's worth being patient rather than switching to something more expensive like TurboTax just because of temporary server issues. Thanks everyone for sharing your experiences and workarounds! This community is really helpful during stressful tax season.
I'm glad I'm not the only one dealing with this! I was starting to think it was something wrong with my setup. I've been trying to access FreeTaxUSA since early this morning and getting the same timeout errors and partial loading issues. Your plan to try again tonight makes sense - seems like that's when most people here had success. I might try the early morning approach too since I'm usually up early anyway. Really appreciate everyone sharing their experiences and tips in this thread. It's reassuring to know this is just a temporary traffic issue and not something more serious with the platform. Definitely beats paying the extra fees that TurboTax charges!
I've been having the same exact issue! Started trying to access FreeTaxUSA around noon and it's been nothing but error messages and timeouts. Really glad to see it's not just me - I was starting to worry there was something wrong with my internet connection. Based on everyone's experiences here, it sounds like this is just peak season server overload. I'm going to try the late evening approach that several people mentioned worked for them. Has anyone tried reaching out to FreeTaxUSA directly on social media for status updates? Might be worth checking their Facebook or Twitter for real-time information about when their systems are running normally again. I really don't want to switch back to TurboTax after all the good things I've heard about FreeTaxUSA's pricing and features.
I just checked FreeTaxUSA's Twitter (@FreeTaxUSA) and they posted about 2 hours ago acknowledging the server issues and saying they're working to resolve them. They mentioned that traffic is about 300% higher than normal today, which explains all the problems we're having. They also suggested trying to access the site during off-peak hours (early morning or late evening) and recommended clearing browser cache if you're still having issues. Based on what others have shared here, it really does seem like waiting for lower traffic periods is the best approach rather than switching platforms entirely. I'm definitely going to stick with FreeTaxUSA - the cost savings compared to TurboTax are just too good to give up over what's clearly a temporary technical issue.
Another approach that worked for me last tax season - check if H&R Block has a "Review" or "Summary" section before you file. Many tax software programs generate a comprehensive review document that includes all your entries in a more accessible format. In H&R Block, look for something like "Review Your Return" or "Tax Summary" - this often creates a consolidated view of all your forms and schedules. Sometimes this review format is more copy-friendly than the individual input screens. Also, if you're comfortable with it, you might try using browser developer tools if you're using the online version of H&R Block. Press F12, go to the Console tab, and sometimes you can access the underlying data that way. It's a bit technical but I've seen people extract form data this way when normal copy functions are blocked. The combination of these suggestions from everyone should definitely save you from having to manually type all 51 transactions!
The Review/Summary section is brilliant advice! I wish I had known about this earlier. Just found it in my H&R Block - it's under "File" then "Print/Save Returns" and there's an option for "Tax Return Summary" that shows everything in a much cleaner format. Still testing if I can copy from there, but even if not, it's definitely going to be way easier to work with for screenshots or OCR than the cluttered input screens. You've potentially saved me hours of formatting headaches!
Just wanted to share another potential workaround that saved me last year - if you have access to the actual 1099-B forms from your broker (Fidelity in your case), you might be able to download them directly from their website in a more Excel-friendly format. Most major brokerages like Fidelity, Schwab, etc. allow you to download your tax documents as PDFs, and some even offer CSV or Excel exports of your transaction history. Log into your Fidelity account and look for a "Tax Documents" or "Year-End Documents" section. The advantage is that this data comes straight from the source and won't have any transcription errors that might occur from copying between software programs. You can then use this to verify what you've entered in H&R Block rather than trying to extract it from the tax software. I found my broker's export was actually more detailed than what the tax software showed, which helped me catch a few small discrepancies. Worth checking before going through all the screenshot/OCR steps!
This is excellent advice! I actually forgot that I could go directly to the source. Just logged into my Fidelity account and found they have a "Tax Forms & Information" section where I can download all my 1099-B data as both PDF and CSV formats. The CSV export is exactly what I needed - it has all the transaction details in neat columns that I can directly import into Excel. This is probably the cleanest solution since it eliminates any potential OCR errors or formatting issues. Thanks for reminding me to check the source first before wrestling with the tax software!
I've been following a similar strategy for about 2 years now, overpaying by roughly $18K annually. One thing that's given me peace of mind is working with a tax professional who helped me establish a defensible estimation methodology. What we do is create quarterly projections that account for variable income scenarios - like potential bonuses, freelance work, or investment gains that might materialize. I document these projections each quarter, showing how I arrived at my estimated payment amounts. Sometimes the income materializes, sometimes it doesn't, but the important thing is having a reasonable basis for each payment. The processing fees (around 1.9%) are definitely worth it when you're hitting signup bonuses that can be 15-20% returns in just a few months. Just make sure you're not putting all your overpayments on one card or making it too obvious that you're manufactured spending. My advice would be to treat this as legitimate tax planning first, credit card optimization second. Keep good records, vary your amounts somewhat year to year, and make sure you can articulate why your estimates led to overpayments if ever asked. The IRS isn't going to penalize you for being conservative with your tax planning.
This is really helpful advice! I'm just starting to consider this strategy and the emphasis on treating it as legitimate tax planning first makes a lot of sense. Quick question - when you say "vary your amounts somewhat year to year," do you mean the total overpayment amount or the quarterly distribution? I'm trying to figure out the best way to make this look natural while still being able to hit the credit card bonuses I'm targeting.
@Emma Thompson Great question! I vary both actually - some years I might overpay $15K, others $20K, depending on my actual income projections for that year. For quarterly distribution, I also mix it up - sometimes front-loading more in Q1 if I expect higher income later, other times spreading it more evenly. The key is having legitimate business reasons for the variations. Like this year I m'expecting some consulting projects to wrap up in Q3, so my Q2 and Q3 payments are higher to account for that projected income spike. Last year was more evenly distributed because my income was steadier. This natural variation makes it look like genuine tax planning rather than a systematic scheme, while still giving you flexibility to time your credit card applications around when you need to hit minimum spend requirements.
I've been considering this strategy myself and appreciate all the insights here. One additional angle I'd suggest is looking at safe harbor rules for estimated taxes. If you pay either 100% of last year's tax liability or 110% (for higher income earners), you're automatically safe from underpayment penalties regardless of how much you actually owe. This gives you a legitimate framework for "conservative" estimates that could result in systematic overpayments. You could base your estimated payments on projections that ensure you hit these safe harbor thresholds, and if your actual income ends up lower, the overpayment becomes a natural byproduct of following IRS safe harbor guidelines. The beauty of this approach is that you're literally following an IRS-recommended strategy for avoiding penalties. It's hard for them to question a methodology they explicitly endorse, even if it results in consistent overpayments when combined with credit card optimization. Just make sure to document your safe harbor calculations each year to show you're following established tax planning principles rather than arbitrary overpayment amounts.
Cassandra Moon
Just wanted to add my perspective as someone who's been dealing with 72(t) distributions for about three years now. The 1099-R coding issue is unfortunately very common - I've had to get corrected forms from Vanguard twice now for the same reason. One thing I haven't seen mentioned yet is that you should also make sure your tax software is set up correctly to handle the 72(t) exception. Even if you get a corrected 1099-R with code 2, some tax software programs will still flag early distributions for review. In TurboTax specifically, there's a section where you need to explicitly indicate that your distribution qualifies for the 72(t) exception. Also, for future years, consider reaching out to Fidelity proactively each January to remind them about your SEPP status. I started doing this with Vanguard after the second coding error, and they've been much better about getting it right the first time. They can add notes to your account that help prevent these mistakes. The stress of dealing with this isn't worth it when there are simple preventive steps you can take. Good luck getting it sorted out!
0 coins
Fatima Al-Sayed
ā¢Cassandra, this is such valuable advice! The proactive approach of contacting the brokerage each January is genius - I never would have thought of that. It makes perfect sense though, especially since these coding errors seem to happen so frequently with automated systems. Your point about TurboTax needing explicit confirmation of the 72(t) exception is really important too. I've been assuming that if I get the corrected 1099-R with code 2, everything would flow through automatically, but it sounds like I should double-check that the software properly recognizes the exception regardless of which approach I end up taking. I'm definitely going to set a calendar reminder for January of next year to contact Fidelity proactively about my SEPP status. Having them add account notes to prevent future coding errors could save so much time and stress down the road. It's one of those simple preventive measures that's worth way more than the few minutes it takes to make the call. Thanks for sharing this longer-term perspective on managing 72(t) distributions - it's exactly the kind of practical wisdom that comes from real experience!
0 coins
Aaron Boston
I've been following this thread with great interest as I'm planning to start my own 72(t) SEPP distributions next year. The consistency of this 1099-R coding issue across multiple brokerages (Fidelity, Vanguard, Schwab, E*Trade) is really eye-opening - it seems like this is more of a systemic problem with how these firms handle automated tax reporting for SEPP distributions. What strikes me most is how well-established the workaround solutions are. Between getting corrected 1099-Rs from the tax operations departments and using Form 5329 with exception code 02, it's clear the IRS is very familiar with this scenario. The fact that multiple people have successfully used both approaches without audit issues gives me a lot of confidence. I'm particularly grateful for Cassandra's proactive approach suggestion about contacting the brokerage each January. That seems like such a simple way to prevent the headache entirely. I'm also planning to keep extremely detailed documentation of my SEPP calculations and methodology after reading Natasha's cautionary tale about the strict compliance requirements. Thanks to everyone who shared their experiences - this thread has become an incredibly comprehensive guide for handling 72(t) distribution tax reporting issues!
0 coins
Grace Lee
ā¢Aaron, you're absolutely right that this seems to be a widespread systemic issue! As someone who's relatively new to understanding 72(t) distributions, I'm amazed by how common these coding errors are across different brokerages. It really highlights the importance of understanding the rules yourself rather than relying completely on the financial institutions to get it right. Reading through everyone's experiences, I'm struck by how the IRS seems to have anticipated these exact problems - having Form 5329 with specific exception codes ready to handle brokerage reporting errors shows they know this happens regularly. It's actually reassuring that there are such established procedures for dealing with it. The proactive January contact strategy that Cassandra mentioned is definitely something I'll remember if I ever set up a SEPP plan. It seems like such a small investment of time that could prevent major headaches later. And keeping detailed documentation of calculations seems absolutely critical given the strict compliance requirements. This whole discussion has been incredibly educational for someone just learning about 72(t) options. Thanks to everyone for sharing such detailed real-world experiences!
0 coins