filed on 03/29, accepted 03/30, DDD of 04/12 on my transcript, and it hit my CashApp on 04/10 - so 2 days early.

CashApp user here! Got mine 3 days early this year. Filed on 4/8, accepted same day, transcript showed DDD of 4/25, but money hit my CashApp on 4/22. My sister used Wells Fargo and got hers exactly on the IRS date - no early release. From what I've noticed over the years, it really depends on when during the week your DDD falls and how quickly the IRS processes that particular batch. If your bills are tight, CashApp is definitely worth trying, but I wouldn't count on more than 1-3 days early max.

Based on what everyone's discussed here, it looks like you're dealing with a classic capital improvement situation. A $24,500 complete roof replacement definitely falls under capital improvements that need to be depreciated over 27.5 years for residential rental property. While bonus depreciation would be amazing for cash flow, residential rental property improvements like roofs generally don't qualify - they follow the same depreciation schedule as the building itself. Section 179 is also off the table for rental properties. Here's what I'd suggest: set up the depreciation over 27.5 years starting from when the roof was placed in service (likely when completed last summer). This means you'll be able to deduct roughly $890 per year ($24,500 ÷ 27.5 years) for the next 27.5 years. Not as exciting as a big first-year deduction, but it's the correct treatment under current tax law. Given the complexity and the dollar amount involved, it might be worth having a CPA review your return to make sure everything's handled correctly. The depreciation recapture rules when you eventually sell the property can get tricky too.

Just to add one more perspective here - I went through a similar situation with a $18,000 roof replacement on my duplex last year. After consulting with my CPA, we confirmed that the 27.5-year depreciation schedule was indeed the correct approach for residential rental property. One thing that might help with your cash flow situation: make sure you're also capturing any other deductible expenses from the roof project. Things like permits, disposal fees for the old roof, and even the cost of temporary repairs to prevent damage during the replacement process can often be deducted as rental expenses in the year they occur, rather than being added to the capital improvement cost. Also, don't forget that you can start claiming the depreciation from the month the roof was placed in service, so if it was completed in July, you can claim 5.5 months of depreciation for last year (roughly $408 if using the $890 annual figure mentioned earlier). The 27.5-year timeline seems long, but that annual deduction really does add up and provides solid tax benefits each year you own the property.

Has anyone considered the possible legal implications beyond just taxes? Letting someone else use your account on gig platforms usually violates their terms of service. Could she get in trouble with the platform too?

This is a really tricky situation that I've seen cause headaches for people. The key thing to understand is that the IRS computer systems automatically match 1099s to Social Security Numbers, so if Sarah doesn't report that $13,500 on her return, she'll almost certainly get a CP2000 notice (basically an automated "you forgot to report this income" letter). Her dad's promise to "take care of the taxes" doesn't change the fact that the income is tied to her SSN. Even if he somehow managed to pay taxes on it through his own return, the IRS systems would still be looking for that income on Sarah's return. The Schedule C approach mentioned by Carmen is probably the most practical solution at this point - Sarah reports the income, then deducts the full amount as payments to her father for contract services. This way the IRS sees the income reported under the correct SSN, but the tax burden effectively passes to the person who actually earned it. Just make sure there's proper documentation of this arrangement in case of questions later. And definitely learn from this situation - sharing gig accounts creates way more problems than it's worth!

Side note but really important - tell your sister NOT to lie again on next year's taxes thinking she can "balance it out." Each tax year is separate and trying to fix fraud with more weird reporting just compounds the problem. I've seen people dig themselves into huge holes this way.

Your sister needs to understand this isn't just about "getting caught" - it's about doing the right thing. I work in tax preparation and see this kind of situation more often than people think. The stress and anxiety of wondering if/when the IRS will notice often ends up being worse than just dealing with the consequences upfront. A few practical points: First, the IRS has sophisticated matching systems that compare reported income and expenses across different sources. If she claimed Uber expenses but has no 1099s from Uber, that's an automatic red flag. Second, even if she got away with it this year, these things have a way of catching up - the IRS can audit returns up to 3 years later (6 years for substantial underreporting). The amended return route really is her best option. Yes, she'll have to pay back the money plus interest, but that's infinitely better than potential fraud penalties of 75% of the underpayment plus possible criminal charges. The car purchase actually makes this more complicated since she'll need to figure out how to pay back the refund. Bottom line: encourage her to consult with a tax professional immediately and file that amended return. The longer she waits, the worse this could get.

This exact thing happened to my neighbor last year! The CP80 notice can be really scary but it's usually just a processing mix-up. Here's what worked for her: She called her bank and got a copy of the front and back of the cashed check - the back showed it was endorsed by the IRS Treasury, which proved they definitely received her payment. Then she made copies of her entire tax return and wrote a cover letter explaining the situation. The key thing is to respond quickly to the CP80 notice. Don't wait thinking it will resolve itself. Include: - Copy of your complete tax return (mark it "DUPLICATE - CP80 RESPONSE") - Copy of the cashed check or bank statement - Brief letter explaining you filed and paid on time Send everything certified mail to the address on the CP80 notice. My neighbor got a letter back in about 6 weeks confirming everything was straightened out. The IRS even apologized for the confusion! Also, definitely keep trying to call the IRS. Early morning (around 7 AM) seems to have shorter wait times. You might get through eventually and they can sometimes resolve it over the phone if you have your documentation ready.

I actually went through this exact same situation about 8 months ago and it was absolutely nerve-wracking! The CP80 notice made it sound like I was in serious trouble, but it really was just a processing error on their end. What helped me was understanding that the IRS payment processing and return processing are completely separate systems. Your check gets deposited almost immediately, but your actual return can get stuck in various queues for manual review, data entry backlogs, or just random processing delays. Here's what I learned from my experience: - Don't panic about penalties since you paid on time (that's what matters most financially) - The "balance released" language in the CP80 just means they're not holding your payment hostage while figuring out the return issue - Make sure to respond within the timeframe they specify in the notice (usually 30 days) I followed similar advice to what others have mentioned - sent a complete copy of my return with "CP80 RESPONSE" written on top, included my bank statement showing the cashed check, and used certified mail. It took about 5 weeks but I got a letter confirming everything was resolved. The most important thing is to respond promptly and keep copies of everything you send them. This is way more common than you'd think, so try not to stress too much about it!