According to Internal Revenue Manual 21.4.1.3, cycle codes are assigned based on the processing center and submission pathway. The change you're experiencing is consistent with your return being routed to a different processing queue, possibly for manual review as indicated by your 570/971 codes. Per IRS Publication 5344, this is standard procedure when certain verification protocols are triggered. While this may extend processing time, it doesn't necessarily indicate an audit or significant issue with your filing.

I went through this exact same scenario last year! My cycle code switched from 0520 to 0620 overnight, and I was convinced something terrible had happened to my return. Like you, I was desperately waiting for that refund money for some urgent expenses. The cycle change ended up being completely normal - my return was just moved to a different processing batch. It did add about 10 days to my timeline, but everything processed fine in the end. The waiting is definitely nerve-wracking when you need the money, but try not to stress too much about the code change itself. Keep checking your transcript for any new developments, and hopefully you'll see movement soon!

I think we're overcomplicating this. The rule is simple - if it's personal, it's not a corporate expense, period. It doesn't matter if you call it non-deductible on M-1, it's still a distribution to the shareholder. The only legitimate non-deductible expenses are things that benefit the corporation but aren't deductible under tax law (life insurance premiums, certain penalties, 50% of meals, political contributions, etc). I tell my clients there are only 3 ways to get money out of a C-corp: 1. Salary for services actually rendered 2. Loans (with proper documentation) 3. Dividends Anything else is just dividends in disguise, and the IRS isn't stupid.

This is exactly the kind of situation that drives me crazy as a tax professional. You're absolutely right to push back on the previous accountant's approach. The fundamental test isn't whether an expense is deductible - it's whether the expense has ANY legitimate business purpose. Personal expenses like family vacations and tuition have zero business purpose and should never touch the corporate books, even as M-1 adjustments. I've seen too many practitioners use the M-1 approach as a lazy way to avoid difficult conversations with clients. But you're setting up both yourself and the client for problems down the road. The IRS has gotten much more aggressive about constructive dividend audits, especially with closely-held C-corps. My advice: bite the bullet now and clean this up. Reclassify the personal expenses as dividends (or loans if there's proper documentation and repayment ability). Yes, it'll create some additional tax liability, but it's better than dealing with an IRS audit that could go back multiple years with penalties and interest. The client may not like it initially, but they'll thank you when they're not facing a massive IRS bill later.

This is really encouraging to hear! I filed my LLC return on 2/3 and have been anxiously waiting since my transcript still shows "N/A" for 2024. Based on your timeline and what others are sharing, it sounds like the IRS might actually be processing business returns much more efficiently this year. The fact that your deposit hit the same day as the transcript update is incredible - that never happened in previous years. I'm going to stop obsessing over WMR and just wait for my transcript to update. Thanks for sharing the detailed timeline, it really helps set expectations for those of us still waiting!

This is exactly what I experienced too! Filed my Schedule C return on 2/1, transcript showed N/A for weeks, then suddenly updated with 846 code on 2/25 and deposit hit my account the SAME DAY. WMR still showed "being processed" even after I had the money in my account! What really surprised me was that my regular W-2 employee friends who filed later are still waiting, but us business filers seem to be getting processed much faster this year. I think the IRS may have streamlined their business return verification process. The old timeline of 6-8 weeks for Schedule C returns seems to be obsolete. One tip for others waiting - I noticed my transcript updated on a Friday morning around 6 AM EST, and the deposit hit by 2 PM the same day. Seems like they're doing batch processing on Fridays now instead of the old Tuesday/Wednesday pattern.

Has anyone here used TurboTax to report a lemon law settlement? I'm trying to figure out where to even put this on my tax forms and the software isn't clear about it.

Based on what everyone's shared here, it sounds like you really need to get clarity on what your $17k settlement was specifically compensating you for. The fact that your paperwork just says "settlement amount" without breaking it down is going to be problematic. I'd recommend a two-pronged approach: First, contact your attorney immediately and request a detailed breakdown letter specifying what portions of the settlement were for vehicle value recovery versus other compensation. Most lemon law settlements are primarily for diminished value (which isn't taxable), but without documentation, the IRS could assume it's all taxable income. Second, if you can't get your attorney to respond, consider using one of those document analysis tools people mentioned or getting professional tax advice. Don't guess on this - a $17k mistake could cost you thousands in unnecessary taxes or penalties if you get it wrong. The key thing to remember is that you're still making payments on the truck, so this isn't a completed sale transaction where you could claim a loss. The settlement and your ongoing loan are separate issues for tax purposes.

This is exactly the kind of situation that makes startup HR so challenging! I went through something very similar last year with our NSO exercises. One thing that helped me was creating a simple spreadsheet to track all the moving pieces - employee name, exercise date, number of shares, strike price, FMV at exercise, total spread (taxable income), and then columns for each tax component (federal income, state, Social Security, Medicare, any local taxes). This made it much easier to see where the discrepancy was coming from. In our case, we discovered that Carta was using a flat 22% supplemental wage rate for federal withholding, but some of our higher-earning employees should have been subject to the 37% rate since their total annual income exceeded certain thresholds when combined with the NSO income. Also double-check if your state has any special rules for equity compensation - California, for example, has some quirky requirements that can throw off calculations. The key is getting both platforms to show you their exact calculation methodology line by line. Don't let them just give you totals - demand the breakdown. Once you have that, the discrepancy usually becomes obvious. Good luck! This stuff is unnecessarily complex but definitely solvable with some persistence.

I'm dealing with a very similar situation right now! One thing that helped me get clarity was requesting the detailed tax calculation worksheets from both platforms. Don't just accept their final numbers - ask them to show you exactly how they arrived at their withholding amounts. In my case, I discovered that Carta was calculating state withholding based on our company's incorporation state (Delaware) rather than where the employee actually works and pays taxes (Texas). This created a significant discrepancy since Delaware has state income tax while Texas doesn't. Also, make sure you check if the employee has any existing payroll tax withholding elections (like additional federal withholding or pre-tax deductions) that might affect the calculation. Rippling might be factoring these into their calculation while Carta treats the NSO exercise in isolation. One more thing - document everything in writing with both vendors. I created a shared email thread with both Carta and Rippling support so they couldn't pass the buck back and forth. Sometimes you have to force them to work together to solve the problem rather than letting them blame each other. The $2,800 difference you're seeing is definitely fixable, but you'll want to resolve it quickly before your next payroll run to avoid compounding the issue.