The IRS Lost 25% of Its Workforce: How Plain Text Accounting Reduces Dependency on Broken Systems

General
1

Last week, a long-time client called me in a panic. “Tina, where is my refund? I filed in January, it is March now, and the IRS website just says processing.” I tried calling the IRS practitioner line on her behalf. Three hours on hold. Never got through.

This is the 2026 tax season reality: the IRS started 2025 with 102,000 employees and finished with 74,000. That is a 27 percent workforce reduction heading into one of the most complex filing seasons in years.

What This Crisis Means for CPAs and Tax Preparers

As an IRS Enrolled Agent and former IRS auditor, I have watched this agency from the inside and outside. Here is what we are facing:

  • Budget cuts: FY2026 budget is 11.2 billion dollars, down 9 percent from last year
  • Inexperienced staff: Only 50 new hires onboarded for return processing (2 percent of authorized level)
  • Massive backlogs: 294,052 paper returns waiting as of December 2025
  • Impossible phone support: Customer service reps reduced by 22 percent
  • New tax law chaos: Tips, overtime, auto loan interest, senior deductions all new for 2026

The bottom line: When clients ask questions about refund delays, amended returns, or IRS notices, the IRS cannot help you anymore. You are on your own.

Why Plain Text Accounting is a Resilience Strategy

I have been using Beancount professionally for three years to help clients maintain audit-ready records. The 2026 tax season has proven something I always suspected: local-first accounting is not just a philosophy, it is a survival strategy when institutions fail.

Here is what Beancount gives me that cloud accounting cannot when the IRS is broken:

  1. Instant Data Access - No External Dependencies

Client calls asking about a Q3 2025 business expense? I open the beancount file and find it in 30 seconds. No waiting for QuickBooks Online to sync. The data is right there, locally, instantly.

  1. Complete Audit Trail - When IRS Systems Are Unreliable

This year, a client received an IRS notice about unreported 1099-K income six months after filing. The notice was vague and the IRS portal showed incomplete information.

With Beancount I had every Venmo PayPal transaction categorized and documented. Balance assertions proved the reconciliation was complete. Git commit history showed exactly when we entered the data. I exported a clean PDF report showing the income WAS reported, line by line.

The IRS took another 8 weeks to confirm we were right. But my client was not panicking because I could prove our position immediately.

  1. No Dependency on IRS E-File Portals

When IRS systems go down, my records do not disappear. When refund processing is delayed, I can show clients exactly what we filed and when. Plain text files are always readable.

  1. Client Confidence in Chaos

The psychology of this matters. When clients are stressed about refunds or audits, being able to immediately pull up their complete financial history without logging in or hoping the internet works is powerful.

Real Scenarios Where This Saved Me

Scenario 1 - Unexpected 1099-K: Client received a 1099-K for 8,400 dollars from PayPal they did not remember. I searched the ledger and found every transaction. Turned out it WAS business income we had already reported. Took 5 minutes to resolve what could have been an audit trigger.

Scenario 2 - Delayed Amended Return: Client needed to amend 2024 return in February 2026. IRS processing time? 16 plus weeks. I exported a complete transaction report showing the corrected figures and gave them peace of mind.

Scenario 3 - Refund Took 18 Weeks: Client filed early, still waiting in May. I pulled up the exact return we e-filed, showed them the confirmation. When the refund finally arrived, we could prove the delay was 100 percent on the IRS, not our filing error.

The Control Factor

Here is what I have realized: when government systems fail, owning your data means you are not helpless.

The IRS might lose your return. Their phone system might be unreachable. But your Beancount ledger backed up locally, version-controlled in git, encrypted on your drive will always be there.

This is not about distrusting technology. It is about understanding that resilience comes from owning your infrastructure, not renting access to someone else overloaded servers.

What Is Your Plan?

For fellow CPAs, EAs, and tax preparers: what is your strategy when the IRS cannot help your clients?

Are you maintaining self-sufficient records that do not depend on external systems staying functional? How are you handling client anxiety about refund delays and processing errors?

I would love to hear how others are navigating the 2026 tax season chaos. Because it is not getting better anytime soon.

Tina Washington EA, Phoenix AZ, Former IRS auditor using Beancount for client record-keeping

2

This really resonates with me, Alice. While I am not a tax professional, this hits home as someone who tracks everything in Beancount for personal finances.

I want to share a story from my 2025 tax filing that perfectly illustrates what you are talking about.

In July 2025, I got an IRS notice claiming I had unreported income from a 1099-K. The notice was vague just said there was a discrepancy and I needed to respond within 30 days or face penalties. The IRS phone number on the notice? Went to a recording saying wait times were over 2 hours, then disconnected me.

Here is what I did: I opened my Beancount ledger and searched for all Venmo and PayPal transactions from 2024. Took about 15 minutes to generate a complete report showing every single payment I received, how I categorized it (business vs reimbursement vs gift), and the exact line on my tax return where business income was reported.

I exported a PDF, wrote a response letter, and mailed it with the documentation. The IRS took 8 weeks to respond, but they confirmed I was right the 1099-K income WAS properly reported. They had just made an error in their matching system.

But here is what struck me: What if I had been using QuickBooks Online or some other cloud platform?

I would have needed to log in and hope the cloud service was responsive. Maybe the data from Q2 2024 was archived and I would need to request a restore. Maybe I would have hit a browser compatibility issue or my subscription would have lapsed. Maybe the export feature would not give me the granular detail I needed.

With Beancount, it was instant. Open the file. Search for the keyword. Generate the report. Done.

Why Local-First Matters Even More Now

The IRS is making more mistakes because their systems are overloaded and their staff is inexperienced. That means MORE burden on taxpayers to prove things.

When you get a notice, you need FAST access to your complete financial history. Not “let me call support and see if they can restore my backup” or “I hope the API is working today so my third-party tool can pull the data.”

You need your data RIGHT NOW, offline if necessary, in a format you can search and analyze without depending on someone else infrastructure.

The Resilience Mindset

Plain text accounting is not just about saving money on software subscriptions. It is about being antifragile when institutions fail.

The IRS might be understaffed. Cloud providers might have outages. Software companies might go out of business or change pricing. But a .beancount file encrypted on your hard drive and backed up to an external drive? That will outlast all of them.

Thank You for Sharing This

I am forwarding this thread to my CPA so she understands why I insist on maintaining my own Beancount records alongside whatever she uses for official tax filing.

When government systems are this unreliable, self-sufficiency is not paranoia. It is prudent risk management.

And honestly? Knowing I have complete, instant access to my financial history gives me peace of mind that no amount of “cloud convenience” can match.

3

Alice, this thread could not have come at a better time. I have 20 plus small business clients and literally every single one has asked me about refund delays or confusing IRS letters in the past month.

The Client Impact is Real

Last week, a restaurant owner client called me panicking. She got a CP2000 notice claiming 15,000 dollars in unreported income from a payment processor. The notice gave her 30 days to respond. She tried calling the IRS number on the notice five times over three days. Never got through to a human.

I had to become the de facto IRS liaison. And you know what? That is not in my service agreement. But what am I supposed to do, tell her good luck figuring it out yourself?

The Time Sink Problem

Here is what nobody talks about: When the IRS cannot provide timely answers, bookkeepers absorb that workload.

I spent 6 hours last week on hold with the IRS for that same client. SIX HOURS. Never got through. That is billable time I cannot fairly charge because I accomplished nothing. But I also cannot just ignore my client who is terrified of penalties.

This is not sustainable. The IRS workforce crisis is directly impacting small bookkeeping practices like mine because we are filling the gap they left.

How Beancount Helps Me Survive This

Here is my workflow now:

Monthly PDF exports: Every client gets a PDF snapshot of their books at month-end. Stored offline. Even if my server crashes or my Fava instance goes down, they have a permanent record.

Metadata everywhere: Every transaction has notes, receipt links, and detailed categories. When the IRS sends a vague notice like “discrepancy in income reporting,” I can search the full history in seconds and find exactly what they are talking about.

Git version control: I can show clients and the IRS exactly what was recorded when. No “I think we entered that in Q2” - I can PROVE it with commit history.

The Self-Sufficient CPA Philosophy

With the IRS this unreliable, we cannot just be tax-form-fillers anymore. We have to be complete record-keepers who can operate independently of government systems.

That means:

  • Maintaining audit-ready records that do not depend on IRS portals staying online
  • Being able to instantly pull transaction histories without waiting for cloud syncs
  • Having local backups that we control, not some third-party vendor

My Concern for Less Technical CPAs

Here is what worries me though: Not everyone can use Beancount and git. A lot of older CPAs or solo practitioners rely entirely on QuickBooks Online or Xero.

Are they going to suffer disproportionately because they depend on cloud platforms that might go down during peak tax season? What happens when their vendor has an outage and they cannot access client data to respond to an IRS notice deadline?

I am genuinely concerned that the IRS crisis is going to expose how fragile cloud-dependent workflows are.

Question for the Group

For those of you using Beancount professionally: Do you maintain parallel records in QuickBooks for client comfort, or do you go all-in on plain text?

I am still running dual systems for most clients (Beancount for me, QuickBooks for them) because they want the familiar interface. But honestly, the Beancount records are what save me when things go wrong.

How are you handling that transition with clients who are scared of “just text files”?

4

I want to add a different angle to this excellent discussion: the security implications of the IRS workforce crisis combined with cloud accounting platforms.

Alice mentioned the 27 percent workforce reduction, but there is another stat that terrifies me: accounting firms face an average of 300 cyberattacks per week, spiking to 900 plus during tax season. That is a 300 percent increase since 2020.

Let me explain why this matters in the context of IRS dysfunction.

The Attack Surface Problem

Cloud accounting platforms are high-value centralized targets for attackers. Think about it:

  • Millions of tax returns with full SSNs, addresses, income data
  • Payment information and bank account details
  • Centralized databases that, if breached, expose thousands of clients at once
  • Integration with IRS e-file systems creates additional attack vectors

Meanwhile, the IRS itself is running on ancient computer systems that are vulnerable. Their workforce is inexperienced and overwhelmed. Security is probably not their top priority right now when they are just trying to keep basic operations running.

What Happens When Major Tax Software Gets Breached?

Let me paint a scenario that keeps me up at night:

It is peak tax season April 10, 2027. A major cloud accounting platform used by thousands of CPAs gets breached. Attackers gain access to client tax data for the past 5 years.

Now what?

  • CPAs have to notify potentially thousands of clients about the breach
  • Multi-state breach notification laws kick in (some require notification within 72 hours)
  • Clients panic and blame their CPA, not the software vendor
  • The IRS is too understaffed to help with identity theft resolution
  • Lawsuits start flying

And here is the kicker: as the CPA, you may be liable even though it was the vendor platform that got hacked. You are the trusted advisor. The client does not care about your vendor contract fine print.

The Beancount Security Advantage

Now contrast that with the Beancount approach:

Local encrypted files: Client data lives on YOUR encrypted hard drive, not in someone else cloud. No centralized database to breach.

Air-gapped backups: You can keep offline encrypted backups on external drives. Physically disconnected from the internet. An attacker would need to physically break into your office.

Git commit signatures: Every change is cryptographically signed. You have an audit trail of who changed what and when that cannot be forged.

No cloud attack surface: If attackers compromise a cloud provider, your client data is not there. It was never there.

The Trade-Off: You Are Responsible for Your Own Security

Here is the reality check: with Beancount, YOU are responsible for security. That means:

  • You have to manage encryption (GPG, disk encryption, etc)
  • You have to maintain secure backups (and test them regularly)
  • You have to control access (who can decrypt the files?)
  • You have to have an incident response plan if your laptop is stolen

But here is my argument: I would rather be responsible for my own security than trust that a SaaS vendor with thousands of CPAs as customers has perfect security.

With Beancount, my security posture is only as good as MY practices. With cloud platforms, my security posture is only as good as the WEAKEST client of that vendor.

Question for Tax Professionals

When you explain security to clients, do they understand the difference between “your data is in our cloud” versus “your data is in encrypted files on my drive that I back up to a physical device in a safe”?

I have found that high-net-worth clients and business owners actually PREFER the latter once you explain the attack surface difference. They understand physical security better than they understand cloud security abstractions.

The IRS Crisis Makes This Worse

Here is why the IRS workforce reduction amplifies the security risk:

If there is a breach and client tax data is stolen, the IRS cannot help clients resolve identity theft quickly. Their phone lines are jammed. Their systems are slow. Their staff is inexperienced.

You, as the CPA, become the ONLY resource your client has to prove their identity and resolve fraudulent tax filings. And if you are using a cloud platform that just got breached, you might not even have access to clean historical data to help them.

But if you have local Beancount files backed up offline? You have a pristine copy of their financial history that was never exposed to the internet. You can help them prove their real financial situation even if attackers stole data from a cloud provider.

Final Thought

Security through simplicity. Security through ownership. Security through air-gapping critical data.

That is the Beancount advantage in 2026: when both the IRS and cloud vendors are unreliable, local-first plain text accounting is not just a philosophical preference. It is a risk management strategy.