Two years into marriage, my wife and I hit a wall. Not over kids, not over careers—over whose money was paying for groceries.
We’d been operating on completely different mental models. She thought “marriage = joint finances = obvious.” I thought “two incomes = proportional splits = fair.” Neither of us had said these assumptions out loud. We just… assumed.
The blowup came over a $2,400 couch. She bought it from our joint checking account (the one we’d opened for “bills”). I freaked out because I thought that account was only for utilities and rent—not furniture. She was hurt because she thought we’d agreed to share everything. We hadn’t agreed to anything. We’d just opened an account and hoped for the best.
The Failed 100% Joint Experiment
We tried the “traditional” approach first: combine everything. One checking account, one savings account, all income flows in, all expenses flow out. Simple, right?
Wrong.
I felt like I’d lost financial autonomy. Every coffee purchase felt like I was “spending our money” instead of my money. She felt like I was nickel-and-diming her every time she bought anything personal. We were both walking on eggshells, which is exactly the opposite of what joint finances are supposed to accomplish.
Three months in, we were fighting more about money than when we’d kept everything separate.
The Beancount Architecture That Saved Us
Here’s where plain text accounting became relationship counseling.
I proposed we build a hybrid model in Beancount—not because I wanted to “win” the separate vs joint argument, but because we needed to make our financial arrangement explicit instead of assumed.
Here’s what we built:
Assets:Joint:Checking ; Shared operating account
Assets:Joint:Savings ; Emergency fund, down payment savings
Assets:Joint:Investments ; Retirement accounts, taxable brokerage
Assets:Fred:Personal:Checking ; My spending money
Assets:Fred:Personal:401k ; My employer retirement
Assets:Wife:Personal:Checking ; Her spending money
Assets:Wife:Personal:401k ; Her employer retirement
Equity:Fred:Contributions ; Track my total contributions to joint
Equity:Wife:Contributions ; Track her total contributions to joint
Every month, we run a “settlement” transaction. We each contribute to Assets:Joint:Checking proportional to our income (I earn 60% of household income, so I contribute 60% of joint expenses). The equity accounts track cumulative contributions over time.
The magic isn’t the account structure—it’s the transparency and version control.
When we disagree about spending, we don’t argue about feelings. We pull up Fava, look at actual numbers, and discuss. When she worried she was “freeloading” during her 3-month career transition (she wasn’t), I showed her the git history: she’d contributed more than me over the previous 24 months. Data settled the argument in 30 seconds.
What We Learned (The Hard Way)
1. The architecture will evolve—and that’s fine.
We started with 70/30 splits (my income was higher). Now it’s 55/45 (she got promoted). We’ve adjusted the Beancount model four times in three years. Version control makes it easy to see how our arrangement has changed.
2. Separate “fun money” accounts are essential.
We each get $500/month deposited into Personal:Checking accounts. No questions asked, no judgment, no tracking. She can buy a $200 purse, I can buy a $150 keyboard—neither of us feels guilty or monitored.
3. Joint goals need explicit tracking.
We have sub-accounts under Assets:Joint:Savings:
HouseDownPayment(targeting $120K by 2028)EmergencyFund(6 months expenses, fully funded)VacationFund(annual trip budget)
Seeing progress toward shared goals reduced 90% of our money stress.
4. The conversation matters more than the code.
We have a monthly “money date”—30 minutes with coffee, reviewing Fava reports together. It’s not about policing spending. It’s about transparency building trust.
Three Years Later
We’re not perfect. We still disagree about spending priorities (she thinks $80/month for premium yoga is essential, I think it’s negotiable). But we don’t fight about money anymore.
The Beancount architecture forced us to:
- Make assumptions explicit (no more “I thought you knew”)
- Track contributions objectively (no more “I pay for everything”)
- See progress toward goals (no more “we’re not getting anywhere”)
We’re on track to hit CoastFIRE by age 38, mostly because we stopped arguing and started optimizing together.
Questions for the Community
How do you structure couple finances in Beancount?
- Fully joint? How do you handle personal spending without guilt?
- Fully separate? How do you avoid resentment over unequal contributions?
- Hybrid like us? What’s your architecture?
And the big one: How do you handle income disparity? We do proportional contributions (60/40 based on income), but I know couples who split 50/50 regardless of earnings. What’s fair?
Would love to see your account hierarchies and hear what works (or spectacularly failed).
P.S. - My wife reviewed this post before I submitted it. She wanted me to add: “The Beancount ledger is great, but the monthly money dates where we actually talk are what saved us, not the software.” She’s right. The tool just made the conversations possible.