mastodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance, open to everyone, but mainly English and French speaking.

Administered by:

Server stats:

811
active users

#plaintextaccounting

1 post1 participant0 posts today
Continued thread

As much as I love plain text accounting, there are subtle things about it that make me want to write a program. That's a lot of how I do my book keeping for my publishing company and apparently how I'm handling Partner's babysitting.

The only difference is that this uses Deno instead of Node and I'm trying out hledger verses beancount. Mostly because I wanted to try out puffin which I don't exactly like. But, hledger is more popular than beancount so I might as well let them war in my head for a while before I decide on one or the other.

Replied in thread

@astrophoenix @ellane
I use a depth limit in my default queries.
So if under assets:bank:wf:checking I have assets:bank:wf:checking:tax:2024:us and assets:bank:wf:checking:tax:2025:us, I normally limit balance reports to depth 4 to hide those, eg by adding

[balance] -4

to ~/.hledger.conf. I also hide lot subaccounts this way. My chart of accounts is arranged so that this simple depth limit works for all, but if not I could set per-account depth limits.

Simple really is better, more times than not.

Yesterday I figured out how to track savings goals in Beancount (Fava) by creating a parallel BGT currency. It involves more data entry, but it does the calculation between what's already saved and my goal.

Nice, but unnecessary.

Today I scrapped all that (yay for backups!) and simply added the savings goal to the name of each account. Thanks for the tip on the forum, @simonmic

After 7 months of #plainTextAccounting, insights are starting to flow. Honestly I have no idea how I'd have tracked all this without a) paying a ridiculous amount of $ every month, b) locking myself into an app that doesn't do what I need it to, and c) makes it hard to move somewhere else!

Admittedly the hardest thing about PTA wasn't learning how to use the command line. It was learning the principles of accounting, and how to apply them to my situation.

I've not used #beancount since v3 went stable, and I'm planning on getting my #PlainTextAccounting setup going again.

Is there anything I should know (or a pointer to somewhere I can find out) about any user-visible changes?

I used to have Fava as my main UI, with a few hand-cranked (and awful!) python plugins providing synthetic transaction enrichment (e.g. VAT; CT). Is that workflow still likely to be happy with v3? Might I have to get my hands dirty with python API changes? #ledger #pta

Continued thread

Another super interesting chart for me is this one: accounting loss over time, i.e. things that slip through the radar.

I fill my #hledger journal very thoroughly with ~1500 txns/year that I sort and tag meticulously, including all things cash (this is where things get lost).

What you can see here is: No matter how hard I try, ~1€/day slips through my radar - a lost receipt, some coins change hand on a market, etc. I find the consistency of this very fascinating 😀