"Hey Siri, Log $45 for Groceries" — Has Anyone Cracked Voice-to-Beancount Expense Entry?

General
1

The other day I was at Trader Joe’s, loaded down with groceries, and thought “I should log this $45 expense.” By the time I got to my car, I’d already forgotten the exact amount. By the time I got home, I didn’t log it at all.

Sound familiar?

Mobile friction is killing my expense tracking compliance. Pulling out my phone, unlocking it, opening a text editor, typing out a properly formatted Beancount transaction—it’s just enough friction that I skip it when I’m busy. And I’m busy most of the time.

What I Want: “Hey Siri, Log $45 for Groceries at Trader Joe’s”

I want to speak my expense and have it magically append to my Beancount ledger. Something like:

  • Voice: “Hey Siri, log 45 dollars for groceries at Trader Joe’s”
  • iOS Shortcuts parses: amount=$45, category=Expenses:Groceries, payee=Trader Joe’s
  • Result appends to my .beancount file or staging location:
    2026-03-27 * "Trader Joe's" "Groceries"
  Expenses:Groceries    45.00 USD
  Assets:Cash

What I’ve Found (2026 State of the Art)

I’ve been researching voice-to-text expense automation, and here’s what’s possible in 2026:

iOS Shortcuts + Siri Integration

  • iOS 26’s Apple Intelligence now supports LLM-based Shortcuts actions
  • People are building voice-controlled expense trackers that talk to Siri, process via n8n, and write to Google Sheets or Notion
  • The “Transaction” automation trigger can capture Apple Pay transactions automatically
  • Voice commands can trigger shortcuts hands-free for immediate logging

Android: Tasker + IFTTT

  • Tasker offers deep device control with custom triggers and parameters
  • IFTTT provides 1,000+ app integrations for cross-platform automation
  • Tasker ranked #1 for Android automation in 2026, IFTTT #2 for ecosystem breadth

The Plain Text Accounting Challenge

  • Most solutions target Google Sheets, Notion, or proprietary apps
  • Very few bridge voice input → plain text .beancount file format
  • Beancount’s human-readable format is perfect for this, but the tooling doesn’t exist yet

The Technical Puzzle

To build this, I’d need:

  1. Voice capture: Siri Shortcuts / Google Assistant / Tasker voice input
  2. Natural language parsing: Extract amount, category, payee from “log 45 dollars for groceries at Trader Joe’s”
  3. Transaction formatting: Convert to valid Beancount syntax
  4. File sync: Append to .beancount file (via Git sync, Dropbox, or cloud service)
  5. Validation: Catch malformed entries before they corrupt the ledger
  6. Review workflow: Staging area for questionable transactions

In 2026, #1 and #4 are solved problems. #2 is possible with LLM-based parsing. #3-#6 are where it gets interesting.

Has Anyone Built This?

I’m throwing this out to the community:

  • Has anyone built a working voice-to-Beancount workflow? Even a hacky prototype?
  • Are there existing projects I should look at or contribute to?
  • What approaches have you tried that didn’t work? (Learn from failures)
  • Would you use this if it existed? What’s your minimum bar for “good enough”?

I’m a financial analyst with decent Python skills and 4+ years of Beancount experience. I can hack together iOS Shortcuts and write parsers. But before I reinvent the wheel, I want to know if someone’s already solved this—or if the community thinks this is even a good idea.

The dream is: Zero-friction expense logging that doesn’t compromise Beancount’s data integrity.

Is that dream achievable? Let’s discuss.