
When accounting goes unaccounted for. Tips: 202-505-8885 • [email protected]
Joined June 2009
- Tweets32.6K
- Following516
- Followers22.8K
- Likes3.3K
Going Concern retweeted
Great advice from the @AICPA 2026 Tax Ethics Update:
Have an engagement letter & STAY INSIDE IT!
Scope creep can put liabilities on you and your firm. – at Breckenridge, CO
Going Concern retweeted
Microsoft wants to replace 60,000 employees with AI when they can’t even get Teams to recognize that I’m still working just because I haven’t moved my fucking mouse in 3 minutes.
Going Concern retweeted
Normalize cutting the tension in a meeting by ending it with, “We’re all gonna die one day, so none of this really matters.”
Going Concern retweeted
Now that tax season is over and you had a few days to recuperate, get on with firing those clients you know need to go. There will be plenty more to take their place.
The public will soon be able to view Tax Court motions remotely through the Tax Court’s electronic filing and case management system rather than having to file a records request or visit the courthouse. taxnotes.co/4zGm5rA
Going Concern retweeted
Happy 40th birthday to the Internal Revenue Code of 1986, to all who observe!
Going Concern retweeted
Someone sent me this. #TaxTwitter
Going Concern retweeted
It's interesting what AI is doing to hourly advising. I do annual one-hour reviews for clients who ask. Recently, a few clients sent 50+ pages of AI-generated reports on their finances, along with a 15-tab AI spreadsheet and 85 AI-generated questions. They deliver all this the morning of the call "for review prior to speaking." 😂 I'm good, but not that good.
Going Concern retweeted
Pounding my head into a table is more enjoyable than trying to understand how to properly navigate AI usage within 7216 as a small tax firm.
Going Concern retweeted
Okay, I'll say it. The AICPA and IRS are doing serious damage to tax pros as it relates to AI.
Every day there is another "I'm firing my idiot CPA because my frontier model found an error" post.
There is a lot of good, but dated, legislation governing what your tax pro can send to a model.
You, as the taxpayer, do not have that same restriction.
Yes we have client consent processes that can help, but tax pros still need to be using the right tier to protect that data and remain compliant.
The tax code keeps growing, context windows for frontier models keep expanding, and the bar for being a tax pro keeps getting raised.
We're in this weird spot in the profession where our clients have more technology leverage than we do because of bureaucracy.
It's a terrible position to be in and the longer out of touch generations are in charge of making the rules the worse it will get.
Going Concern retweeted
I hope everyone enjoyed their last tax cycle in which AI didn’t nitpick the shit out of every little thing for 9.5 months straight. Yesterday was undoubtedly the day the music died in tax compliance.
Going Concern retweeted
First time?
I guess they’ve never experienced a large acquisition or an ERP change.
Going Concern retweeted
i love being an accountant because every day i get to discover a new way someone has made their financial decisions my problem.
Going Concern retweeted
Got a call from a former client asking the status of their 2025. I resent my disengagement letter.
Not today!
Going Concern retweeted
Someone just asked me if I’m taking appointments for Columbus on Monday. I said, “I don’t have anyone named Columbus on my client list and they better have the extension done”. … lol …
#TaxSeason #TaxHumor
Going Concern retweeted
Curious where general sentiment is here, as I think a lot of folks are afraid of being AI-cancelled
For US tax pros, if you're using an AI assistant that doesn't train your prompts into the model (business plans)
Do you think a signed 7216 consent to disclosure is required?
25%Yes need a signed CTD
36%No signed CTD necessary
38%Results
593 votes • Final results





















