Question for my dearest #accounting and double-entry #bookkeeping nerds:

I want to explicitly track some of my money for periodic subscriptions, e.g. paying for RuneScape membership every six months:

> Expenses:RuneScape EUR 47.99
> Assets:Bank:Liquid EUR -47.99

My idea is to move a sixth of that amount to a savings account every month like this:

> Assets:Bank:Saved:RuneScape EUR 8
> Assets:Bank:Liquid EUR -8

This is fine, but it doesn't track the liability that I have with Jagex to pay the subscription every six months. In my mental model, I should be able to track the cost of the future subscription payment as a liability because it affects my working capital, so I should record the liability with something like this:

> Liabilities:RuneScape EUR -47.99
> ???:??? EUR 47.99

However, I don't know which kind of account I should debit the liability to! Where should this money come from? Debiting equity doesn't feel right and my subscription is not an asset either. My idea is that when I finally pay the subscription, I'll credit the liabilities account with my saved cash:

> Liabilities:RuneScape EUR -47.99
> Assets:Bank:Saved:RuneScape EUR -47.99

But then I'll have to record the liability again for the next period.

I feel like my mental model for this is wrong. Any #help on how I can make this work? Thank you 

#ledger #hledger #beancount

Monatliche Zinsgutschrift auf dem Tagesgeld-Konto. Selber (mikriger) Zinsbetrag wie im letzten Monat. Aber ein Cent (0,01€) mehr Kapitalertragssteuer? WTF???

#beancount

After almost two months, I’ve finished first version of #BeanBeaver: it parses grocery receipts into #Beancount records.

https://github.com/Endle/beanbeaver

I hope I’m not the only person who cares about a grocery-by-item breakdown 🦫

After bouncing around ideas and several experiments, I've decided to launch a new project with the goal of creating CLI tooling that facilitates receipt handling for #plaintextaccounting workflows. LLM based OCR and data extraction has improved to the point that I believe it will be possible to make bulk data extraction useful. If you have ideas, want to contribute, or just want to follow along jump in:

https://codeberg.org/plaintextaccounting/acceptarium

#hledger #ledgercli #beancount #llm #ocr

Made the switch from #ActualBudget to #beancount for my personal finances

The ecosystem is nice
- #fava, #beangulp for imports, #beanahead for recurring transactions, #favaCustomDashboards for charts, and #favaInvestor for portfolio tracking

Also went overboard with custom stuff:
- PDF importers with #ML payee/account prediction
- Custom linters for validation
- Forked #favaEnvelope for envelope budgeting
- #Makefile with 28 targets for price fetching to #FIRE calcs

#plainTextAccounting is great when you can just write #Python to solve your edge cases

#personalFinance #doubleEntryAccounting #CLI #fintech #devlife

Last night, I did monthly1 accounting for my publishing business. And since it was the beginning of the year, I figured it would be an easy2 task to finally stop regenerating my accounting data from source .xlsx and .csv files from 2002 and just close off each year into a final .beancount.

It did not go well2.

I really need to get to the commission, but I'm going to try fixing it for a few hours before giving up until 2027.

#PlainTextAccounting #Beancount