I’ve been sitting on this post for weeks because I wasn’t sure how to write it without sounding like I’m complaining. But after another 70-hour week during tax season while juggling client reconciliations and debugging an importer that broke because Chase changed their CSV format again, I think it’s time for an honest conversation.
The Numbers Are Brutal
A FloQast/University of Georgia study found that 99% of accountants experience burnout at some point in their careers—24% at medium-high levels. Over 300,000 U.S. accountants and auditors have left their jobs in recent years, a 17% decline. And 51% of accounting and finance team leaders report symptoms of professional burnout.
The profession’s response? “Take breaks. Practice mindfulness. Use your vacation days.”
Individual coping strategies for what is clearly a structural problem.
My Big Four Origin Story—and Why I Left
I spent seven years at a Big Four firm. 71% of Big Four auditors worry about mental health, and I was part of that 71%. The hours were brutal, the culture rewarded suffering as a badge of honor, and the only advice anyone gave was “it gets better after Manager.” Spoiler: it doesn’t.
So I started my own practice. And for a while, it was better. Then I discovered the solo practitioner version of burnout—which is lonelier and in some ways worse, because there’s nobody to even complain to.
Does Beancount Actually Help With Burnout?
When I migrated to Beancount two years ago, part of the motivation was burnout reduction. Here’s my honest assessment after two full tax seasons:
What genuinely helped:
- Automation replaces the soul-crushing tedium. My importers handle 80% of data entry that used to be manual. That’s real hours saved—and more importantly, it’s the most boring hours saved.
- Control reduces helplessness. I built my system. When QuickBooks updates broke my workflows, I felt helpless. When my Python script breaks, I can actually fix it.
- Text files are calming. This sounds ridiculous, but there’s something zen about a clean ledger in a text editor vs. navigating Intuit’s increasingly bloated UI.
- Git gives me an undo button. The anxiety of “did I mess up a client’s books?” dropped significantly when I could just
git diffand see exactly what changed.
What didn’t help (or made things worse):
- I’m now CPA + developer + IT department. My cognitive load didn’t decrease—it shifted domains. Instead of fighting QuickBooks, I’m debugging Python at midnight.
- The “always on” trap intensified. My laptop IS my office. The ledger is always right there. “I’ll just reconcile one more account” turns into two hours.
- Isolation increased. At the Big Four, at least I had colleagues who understood the stress. Now it’s just me, my terminal, and this forum.
The Honest Hours Audit
I tracked my actual hours for a month (because of course I did—I’m a CPA). 57 hours per week average. Breakdown:
| Activity | Hours/Week |
|---|---|
| Billable client work | 28 |
| Importer maintenance & debugging | 6 |
| Ledger reconciliation (non-billable) | 5 |
| Client emails & communication | 4 |
| Learning / professional development | 4 |
| Tax research & compliance updates | 4 |
| “Just one more thing” evening sessions | 3 |
| Community / forum participation | 3 |
The utilization rate tells the story: 49% billable. The rest is overhead that keeps the system running.
The Structural Problem Nobody Talks About
The Journal of Accountancy profiled a CPA who suffered strokes and years of depression before finally addressing burnout. That’s not a personal failure—it’s a systemic indictment.
Here’s what I think the structural drivers are:
- Perfectionism is a job requirement. You can’t be “roughly right” with someone’s taxes. The precision demand is relentless.
- Liability is personal. My CPA license is on the line with every return I sign. That weight never lifts.
- Seasonal compression. No matter how much you automate, April 15 doesn’t move.
- Invisible labor. Clients see the deliverable, not the 30 hours of infrastructure that made it possible.
Questions for This Community
- Solo practitioners: Do you track your actual hours (not just billable)? What’s your real number?
- The Beancount question: Has plain text accounting genuinely reduced your burnout, or just changed its flavor?
- The boundary question: How do you draw the line between “work” and “tinkering with your system”? Is debugging an importer at 10 PM work or a hobby?
- The community question: Should beancount.io have a dedicated “wellbeing” space? Not accounting tips—but peer support for the stress, isolation, and burnout that comes with running a solo practice?
Every time someone posts “I automated X and saved 10 hours!” I want to ask: “…and then did you actually take those 10 hours off, or did you fill them with more work?”
I already know my answer. What’s yours?