124,200 Annual Job Openings vs 55,000 Graduates—The Math Doesn't Work: Is Plain Text Accounting Part of the Solution or Part of the Problem?

I’ve been following the accounting talent shortage situation, and the numbers are getting harder to ignore. 124,200 annual accounting job openings but only about 55,000 graduates entering the field each year. The AICPA reports that 75% of current CPAs are nearing retirement, creating an estimated 136,400 annual openings through 2034.

Meanwhile, undergraduate accounting enrollment has declined by one-fifth since 2018, and in 2022, bachelor’s and master’s degrees in accounting dropped 7.8% in a single year—the steepest decline in over 30 years.

As someone who’s been using Beancount for 4+ years (personal finances + consulting work), I’ve been thinking about a question that I haven’t seen discussed much in the community:

Is Plain Text Accounting Part of the Solution… or Part of the Problem?

The “Solution” Argument

The optimist in me sees this:

  • Why the shortage exists: 62% of finance leaders report hiring/retention challenges, and a big reason is burnout from tedious manual work
  • What Beancount offers: Automation that turns 15-20 hours of monthly reconciliation into 90 minutes with Python importers
  • The opportunity: If the 76% shift toward “creativity and communication over pure technical skills” is real, then automation frees accountants to do advisory work instead of data entry
  • The premium positioning: Talent shortage + technical differentiation = higher rates, fewer hours, sustainable practice

The “Problem” Argument

But the pessimist in me sees this:

  • Job postings reality: Every single one says “QuickBooks required” or “Xero experience preferred.” Zero mention Beancount or plain text accounting.
  • The hiring disconnect: New graduates struggle to land roles not because of lack of openings, but because firms want people who can use existing tools without training
  • The scaling challenge: If you want to grow your practice and hire, where do you find Beancount talent? The pool is microscopic.
  • Industry recognition: Only 1.4% of college students chose accounting in 2023 (down from 4% a decade ago)—and none of them are learning plain text accounting in school

The Data That Makes Me Wonder

From recent reports:

  • 82% of public accounting firms report retention challenges
  • The disconnect isn’t about overall demand; it’s about experience with industry-standard tools
  • Firms are solving the shortage by raising salaries (average 3.7% increase for tax/audit roles) and adding benefits—not by seeking people with automation skills
  • 70% of finance leaders plan to use more contract talent to manage workload

The Questions I Can’t Fully Answer

For practitioners using Beancount professionally:

  • Has it made you MORE valuable (charge premium rates, work efficiently) or LESS hireable (niche skillset that mainstream firms don’t recognize)?
  • If you want to scale and hire, have you found the talent shortage makes it impossible to find Beancount-literate staff?

For aspiring accountants/career switchers:

  • Should you learn QuickBooks (what 99% of employers want) or Beancount (what might make you 3x more productive)?
  • Does technical automation differentiate you positively… or mark you as someone who won’t fit into traditional firm workflows?

For the community:

  • Are we building a better way to do accounting that will eventually solve the burnout-driven talent shortage?
  • Or are we creating a parallel ecosystem that’s incompatible with how 95% of the industry operates?

My Personal Experience (Mixed Signals)

Some of my consulting clients don’t care what tool I use—they care that books are done on time and I can explain their finances clearly. I’ve used Beancount successfully for years.

But when I talk to traditional CPA firms, there’s zero interest in “I can write Python importers and automate reconciliation.” They want “I know QuickBooks and can start billing clients immediately.”

I’m genuinely curious: What’s your experience been? If you’re using Beancount professionally, has the talent shortage worked in your favor or against you? If you’re learning plain text accounting, has it helped or hurt your career prospects?

Looking forward to hearing diverse perspectives on this.

This hits home for me as someone who came from software development to get serious about personal finance and accounting.

I’ve been wrestling with exactly this paradox for the past 6 months. I’m a DevOps engineer with 5 years of experience, and when I discovered Beancount, it felt like finally someone built accounting software the way developers would: plain text, version control, scriptable, auditable.

Here’s My Controversial Take

I think we’re asking the wrong question. The talent shortage isn’t about Beancount vs QuickBooks—it’s about people who can think in systems vs people who can click buttons in software.

From what I’ve observed (disclaimer: I’m NOT a professional accountant, just a personal finance nerd):

The Real Differentiation

  • QuickBooks expertise = replaceable: There are thousands of QuickBooks-certified bookkeepers. If one quits, you hire another. They’re commodity labor.
  • Beancount + automation skills = rare: If you can write Python importers, build custom reports, and automate reconciliation, you’re not competing with QuickBooks users—you’re competing with financial systems engineers.

But There’s a Catch

The catch is that very few small businesses need a financial systems engineer. They need someone who can categorize transactions and generate a P&L for their banker.

So the question becomes: are you positioning yourself for the commodity small business bookkeeping market (huge, but race-to-the-bottom pricing) or the high-complexity financial automation market (tiny, but premium pricing)?

My Experience as an Outsider

I chose to go deep on Beancount for my own finances (tracking rental property, investments, multi-currency transactions) specifically because I’m NOT trying to get hired by a CPA firm. I’m building the technical foundation to eventually consult on financial systems integration—where “knows how to write a Python importer” is exactly what the client needs, not a liability.

If I wanted a job at a traditional accounting firm? I’d probably learn QuickBooks and keep Beancount as a personal productivity secret.

The Uncomfortable Truth

The 124,200 job openings aren’t for “people who can automate accounting workflows with plain text systems.” They’re for people who can use QuickBooks, talk to clients, and produce tax returns.

The talent shortage exists despite massive automation potential, because the industry wants more humans doing the same work, not fewer humans doing 3x the work.

Does that mean Beancount skills are worthless professionally? No—but they’re valuable in a different game than the one most accounting firms are playing.

Mike, you’ve articulated the paradox perfectly, and Sarah’s point about “different games” is spot-on. As a CPA who runs my own firm and has been deep in the hiring challenges for the past year, let me add the practitioner’s perspective on this.

The Talent Shortage is Worse Than the Numbers Suggest

Everyone’s talking about 124,200 openings vs 55,000 graduates, but the quality gap is what keeps me up at night. Here’s what I’m seeing:

The Hiring Reality in 2026

I posted a job opening 8 months ago for a staff accountant. Here’s what happened:

  • 93 applications in the first week
  • 12 qualified candidates who met basic requirements (accounting degree, some software experience)
  • 3 interviewed who I actually wanted to hire
  • 0 accepted offers (all went to firms offering $10K+ more)

The talent shortage isn’t “we can’t find anyone.” It’s “we can’t compete on salary with Big Four firms, and the candidates we can afford lack the skills we actually need.”

What I Actually Need vs What Job Postings Say

Here’s the uncomfortable truth: When I write “QuickBooks required” in a job posting, what I really need is:

  1. Someone who understands double-entry accounting (not just clicks buttons)
  2. Someone detail-oriented who can catch discrepancies
  3. Someone who can communicate with clients about their finances
  4. Someone who won’t quit after 18 months because they’re burned out on tedious reconciliation

QuickBooks is a proxy for “has accounting software experience.” But it’s a terrible proxy, because most QuickBooks users are just following rote procedures without understanding why.

Why I Switched (Some Of) My Practice to Beancount

I started experimenting with Beancount 2 years ago for a few specific clients:

  • Tech startup founder who insisted everything be in git for transparency
  • Real estate investor with complex multi-entity structure that QuickBooks butchered
  • Nonprofit that needed fund accounting QuickBooks couldn’t handle well

What happened:

  • Month-end close went from 6 hours per client to 90-120 minutes
  • Custom reports that used to take me 2 hours in Excel now generate in 30 seconds
  • Client satisfaction went up because they could see their numbers in real-time via Fava instead of waiting for my monthly report

The Staffing Problem This Created

Now I’m in a weird position:

  • I can’t hire “QuickBooks-experienced staff” because half my practice is Beancount
  • I can’t hire “Beancount-experienced staff” because that pool is maybe 200 people worldwide
  • I need to hire because I’m turning away clients due to capacity constraints

So what did I do?

I hired a recent accounting grad with zero Beancount experience BUT:

  • Top 10% of her class
  • Frustrated with how clunky QuickBooks felt during internships
  • Comfortable with technology (not a programmer, but comfortable)
  • Detail-oriented and curious

Training timeline:

  • Week 1: Beancount syntax, basic transactions
  • Week 2: Reconciliation workflow, importers
  • Week 3: Month-end close process, client communication
  • Week 4: Shadowing me on client calls

Result: She’s now managing 6 clients independently (4 QuickBooks, 2 Beancount) and prefers Beancount because “I can actually understand what’s happening in the accounts.”

The “Solution or Problem” Question

Mike asks if plain text accounting is part of the solution or problem. My answer: It depends on your business model.

If your goal is to work for a Big Four firm or regional CPA firm:

  • Beancount is probably irrelevant
  • Learn QuickBooks, learn audit software, pass the CPA exam
  • Automation skills won’t help you because the firm’s model is “bill hours, not outcomes”

If your goal is to run your own practice or work with progressive clients:

  • Beancount is a competitive advantage
  • You can handle 2-3x more clients in the same hours
  • You attract tech-savvy clients who appreciate the transparency
  • You can charge premium rates because you deliver better results faster

The Real Talent Shortage Solution

The accounting shortage exists because:

  1. The work is tedious and burnout-inducing
  2. Pay is mediocre compared to tech/finance
  3. Young people see it as a “boring career”

Automation doesn’t solve #2 or #3. But it solves #1. And solving #1 means:

  • You can retain staff longer (not burned out)
  • You can work fewer hours yourself (sustainable practice)
  • You can focus on advisory work instead of data entry (more interesting)

The industry won’t change overnight. Big firms won’t adopt Beancount en masse. But you don’t need the whole industry to change—you just need to build a practice that works for you.

My Current Position

I’m not anti-QuickBooks. I still use it for 70% of my clients. But for clients where Beancount makes sense (tech-savvy, complex structures, want transparency), I use it—and my quality of life is better for it.

The talent shortage is real. But if you’re waiting for “more Beancount-trained accountants to enter the workforce,” you’ll be waiting forever.

Hire smart people frustrated with traditional tools. Train them on Beancount. Build a practice that doesn’t depend on grinding through manual reconciliation.

That’s my solution to the talent shortage.

Mike nailed it with the “what clients think they want vs what they actually need” point, but I want to add the ground-level reality from someone who manages 20+ small business clients.

The Talent Shortage Feels Different Depending on Where You Sit

I’m a self-taught bookkeeper (came from restaurant management 10 years ago), and I’ve been converting my clients to Beancount over the past 2 years. Here’s what the talent shortage looks like from my perspective:

The Math Everyone Ignores

Yes, there are 124,200 job openings. But let’s break that down:

  • Big Four firms: Need people with 150 credit hours, CPA track, willing to work 60-80 hour weeks during busy season. They’re competing for the same 55,000 graduates.
  • Regional CPA firms: Need experienced staff who can handle complex tax returns, audit work, advisory. They’re competing for the already employed talent pool.
  • Small business bookkeepers (like me): Need reliable people who show up, reconcile accounts accurately, and communicate with clients. We’re competing with… everyone else offering $50-60K for entry-level roles.

The shortage isn’t evenly distributed. There are plenty of people who could do bookkeeping. There aren’t enough people who want to do it the way traditional firms want it done (manually, in QuickBooks, for mediocre pay).

Why I Switched to Beancount (and Why It Matters for Hiring)

I switched to Beancount not because I’m some automation genius—I barely know Python—but because I was drowning in manual reconciliation work.

With QuickBooks:

  • Month-end close for a typical client: 6-8 hours
  • Fixing duplicate transactions because the bank feed glitched: 2 hours
  • Generating custom reports the client actually wants: “Sorry, QuickBooks doesn’t do that, here’s a spreadsheet”

With Beancount:

  • Month-end close: 90 minutes (Mike’s number is spot-on)
  • Fixing duplicates: Impossible—my importers deduplicate automatically
  • Custom reports: Python script, done

This matters for the talent shortage because: When I eventually hire someone (which I need to do because I’m at capacity), I’m not looking for “QuickBooks experience.” I’m looking for:

  1. Someone detail-oriented and reliable
  2. Willing to learn a new system
  3. Frustrated with the tedium of traditional bookkeeping

The Real Question: What Game Are You Playing?

Alice, you asked if Beancount makes you more valuable or less hireable. I think you’re conflating two different questions:

“Am I hireable by a traditional CPA firm?”
Answer: Probably less so, because they want plug-and-play QuickBooks users who can start billing clients on Day 1.

“Am I valuable to clients and able to build a sustainable practice?”
Answer: Absolutely more so, because you can deliver better results in less time, which means higher margins and happier clients.

The Staffing Model Nobody Teaches

Here’s what I wish someone had told me 10 years ago: You don’t solve staffing shortages by hiring more warm bodies. You solve them by:

  1. Automating the low-value work so each person can handle more clients
  2. Hiring for aptitude, not existing skills because smart people learn faster than you can hire experienced people
  3. Building systems that work so you’re not dependent on heroic individual effort

I can’t find someone who “knows Beancount” if I want to hire. But I can find someone who’s smart, detail-oriented, and sick of QuickBooks. And I can train them on Beancount in 3-4 weeks.

Meanwhile, if I stayed in the QuickBooks world, I’d be competing for the same shrinking talent pool as every other bookkeeping firm, offering the same mediocre pay for the same tedious work.

The Uncomfortable Opportunity

The talent shortage is real. But it’s also an opportunity for people willing to work differently.

If you can:

  • Automate reconciliation
  • Close books faster
  • Produce better reports
  • Work with distributed/remote talent (because plain text files live in git, not locked in a local QuickBooks company file)

…then you’re not competing in the “124,200 openings, 55,000 graduates” bloodbath. You’re operating in a different market entirely.

The talent shortage in traditional accounting is not your problem. It’s a symptom of an industry that refuses to modernize. If you’ve learned Beancount and automation, you’ve already opted out of that game.