I've been following this thread with interest since I recently had to deal with a similar situation for some family loans from 2014-2019. After trying several of the resources mentioned here, I found that the most reliable approach was actually combining multiple sources for verification. I started with the Treasury Department's AFR archive (thanks Lucas for that link!) to get the bulk data in Excel format, then cross-referenced key periods with Publication 1212 as Aisha suggested. For a few months where I found discrepancies - turned out to be my own transcription errors - I used Claimyr to get through to an IRS agent who helped clarify the correct rates. One thing I learned the hard way: if you're dealing with loans that had rate adjustments or were refinanced during the period, make sure you're applying the AFR that was current at the time of each transaction, not retrospectively. The IRS is very particular about using contemporaneous rates for imputed interest calculations. For a $175K dispute, I'd definitely recommend the multi-source verification approach. It takes a bit more time upfront, but having that level of documentation accuracy could save you significant money if this goes to litigation. The combination of official Treasury data, IRS publication guidance, and professional verification really strengthens your position.

For what it's worth, I went through a similar nightmare last year trying to compile AFR data for a family business loan audit. After reading through all these suggestions, I ended up using a combination approach that worked really well. I started with the FRED database that Mia mentioned - it's incredibly user-friendly and you can download everything in Excel format. Then I cross-referenced the critical periods with Publication 1212 that Aisha recommended, especially for the business loan categories and compounding examples. The key thing I learned is that for business disputes involving significant amounts like yours, you really want multiple official sources backing up your calculations. I used the Treasury Department archive as my third verification point, and when I had questions about how to handle a loan modification that occurred mid-period, Claimyr actually got me through to an IRS specialist who walked me through exactly how to split the calculation periods. One practical tip: create a master spreadsheet with columns for each source's AFR data so you can quickly spot any discrepancies. In my case, I found two transcription errors that could have cost thousands in incorrect interest calculations. For $175K in disputed loans, that extra verification step is absolutely worth the time investment. The combination of FRED for bulk data, Publication 1212 for methodology guidance, and Treasury archives for official documentation should give you bulletproof calculations that will hold up in any dispute resolution process.

Another option nobody mentioned - if you're using TurboTax, you can actually import your stock transactions directly from many brokerages. I have accounts with Fidelity and was able to import everything automatically. This way your return is fully electronic with no need to mail anything. You just need to connect TurboTax to your brokerage account through their secure connection. It pulls all the transactions and categorizes them properly. Saved me hours of data entry!

Quick tip from someone who's dealt with this exact situation for years: When you mail your Form 8453 package, write your Social Security number on EVERY page of the attached trading records. Also include a copy of your Form 8949 and Schedule D that you e-filed. The IRS processes these attachments separately from your electronic return, and having your SSN on each page helps ensure everything stays together and gets associated with your return correctly.

I've been following this thread and wanted to share another potential solution that worked for me after trying most of the suggestions here. My TaxAct submission was freezing at the final screen, and it turned out to be related to PDF generation settings. When TaxAct tries to generate the final return PDF for submission, sometimes it gets stuck if you have certain PDF viewers or plugins installed. I noticed my browser was trying to open PDF files with an outdated Adobe plugin instead of the built-in browser viewer. Here's what fixed it for me: Go to your browser settings and change the PDF handling to "Download PDFs" instead of "Open PDFs in browser." Then attempt the submission again. Once it completes successfully, you can change the setting back if you prefer to view PDFs in-browser normally. Also, make sure you have enough free space on your hard drive - TaxAct creates temporary files during submission that can cause failures if your disk is nearly full. I cleared about 2GB of space just to be safe. The combination of this PDF setting change plus following Malik's advice about disabling browser extensions got me through the submission process after three days of frustration. Sometimes it really is these obscure technical conflicts that cause the most mysterious problems!

This thread has been incredibly helpful! I wanted to add one more potential cause that I discovered after dealing with a similar TaxAct freezing issue - date and time settings on your computer. I know it sounds weird, but if your system clock is significantly off (even by just a few minutes), it can cause SSL certificate validation issues during the submission process. TaxAct's servers are pretty strict about timestamp verification for security reasons. I spent hours trying all the browser troubleshooting steps, cleared my cache, disabled extensions, checked my banking info - everything mentioned here. Finally, I noticed my computer clock was about 10 minutes fast. After syncing it with an internet time server (you can do this in Windows by going to Date & Time settings and clicking "Sync now"), my submission went through immediately on the next attempt. It's such a simple thing to check, but can cause these mysterious connection timeouts during the final submission step. Worth verifying your system time is accurate before diving into the more complex troubleshooting steps, especially if you're on an older computer where the internal clock tends to drift. Thanks to everyone who contributed solutions here - between all these suggestions, I think we've covered pretty much every possible cause of TaxAct submission freezing!

Has anyone tried just calling the IRS and asking them to add the W-2 rather than going through the amendment process? My sister did this when she forgot a 1099 and they told her they could just add it to her return.

I went through something very similar last year - forgot my husband's second W-2 from a part-time job on our joint return. Here's what I learned from the experience: First, definitely wait until you receive your refund before filing the amendment. This makes the process much smoother and gives you funds available if you end up owing money after adding the missing income. Second, TurboTax does charge for amendments (I paid about $55), but it was worth it for me because they guided me through the whole process step by step. The software automatically calculated how the additional W-2 would change our tax liability and walked me through exactly what needed to be corrected. One thing to keep in mind - depending on how much your husband earned and what was withheld, you might end up owing money back to the IRS. In my case, we had to pay back about $1,100 of our refund because his second job didn't withhold enough taxes. But honestly, it's better to correct it voluntarily now rather than have the IRS catch it later through their document matching system, which could result in penalties and interest. The whole amendment process took about 20 weeks to get processed last year, so be patient. But don't stress too much - this is a common mistake and the IRS handles these situations routinely!

My daughter was a first-time filer this year. Claimed two dependents. No verification needed. Return processed in 16 days. Refund deposited directly. No issues at all. System worked smoothly. Never had to call. Just made sure all information was accurate. Used quality tax software. Double-checked everything before submitting.

The verification requirements can be unpredictable, but here's what I've learned from helping clients through this process: The IRS uses multiple data points beyond just "first-time filer with dependents." They cross-reference SSNs against previous filings, W-2 wage reporting, and even address history. If your daughter's information is consistent across all these databases, she'll likely process without issues like Sadie's daughter did. However, if there are any discrepancies - maybe she moved recently, changed her name, or her employer reported wages differently than expected - that could trigger verification regardless of filing status. The key is having all supporting documents ready (Social Security cards, birth certificates for dependents, photo ID) just in case, but not assuming verification is inevitable.