ledger-autosync VS plaintextaccounting

as far as the ledger-cli google groups [1] go, they seem to think it is a proper journal file. It has been fairly tested with OFX imports (https://github.com/ledger/ledger/wiki/OFX-Import) as well bank autosync (https://github.com/egh/ledger-autosync).

In fact, someone also wrote a book on this - https://leanpub.com/personal-accounting-in-ledger/

I will defer if you are indeed building your own competing tool in this space which is better, but holding to the original point of my request - maybe it will be incremental to support your format if ledger-cli format is supported today. versus not supporting any disk format (or inventing a new one).

[1] https://groups.google.com/g/ledger-cli/search?q=double%20ent...

There is also ledger and ledger-import, together with other tools like >, ledger-autosync and emacs.

If you are willing to write personal tools, the very first IME will be a way to import transactions from your bank(s) out of the formats they offer, avoid duplication, handling "history changes" (for instance debit cards in most (all?) countries appear immediately then change when the payment processors gives details to the bank) etc. That can be a nice intro/base https://github.com/egh/ledger-autosync but for stocks is more complicated: much depend of your trading choices: if you do rare put/call bank export + "live" quote from Yahoo Finance might be ok, if you do day trading or scalping you need a more "near-real time" source of data, and that's are not free at least in EU (France/Italy/Sweden AFAIK), there are some SIM that offer rest APIs with various price policies...

ledger-autosync [1] tries to solve this problem, by pulling the data for you from supporting banks. If I understand things correctly, this [2] is the list of banks it can successfully pull data from.

[1] https://github.com/egh/ledger-autosync

I use ledger: https://ledger-cli.org/

I believe this same plain text format is used by other tools, which you can find info about here: https://plaintextaccounting.org/ (In particular a lot of people seem to use hledger and beancount)

The ledger is written using a text editor. The purpose of the software is to add everything up, calculate the balances and make sure everything balances. I keep all of my 12 years of accounting in one file and haven't noticed any slowdown. But a real business would surely have many more accounts and may want to split files by financial year or something.

I use helper scripts to convert the data from my bank CSV downloads into ledger format. It uses machine learning to associate payees to accounts (e.g. "Tesco" gets filed to the account "Expenses:Groceries"). I haven't maintained the ML part although it works for me most of the time. In case it's useful, the code is here: https://github.com/georgek/accounts/

I invite you to hang out in the https://plaintextaccounting.org/#news-discussion -> chats, we like to discuss tactics.

My attempt at solving the same problem https://paisa.fyi. It builds on top of https://plaintextaccounting.org/ principles and is available as a CLI/Desktop App.

ledger, hledger, beancount: https://plaintextaccounting.org/

Gnucash

Firefly III

The plain text accounting options are by far the best if you're willing to give up automatic pretty navigation and graphing.

Same: see also https://plaintextaccounting.org/

...the gist is "ledger.exe" (crufty-old-C-program) is the "perl" of plain-text-accounting. The implementation _is_ the specification.

"HLedger" (haskell) is the mostly-compatible ("now you have 15 standards!") which cleans up a bit of the crufty accidents and is considered more "pure" and "correct".

Mess with it for funsies, and consider using `hledger-ui` for browsing. It's really really powerful!

Specifically this part is super cool: https://ledger-cli.org/doc/ledger3.html#Commodities-and-Curr...

...and: https://ledger-cli.org/doc/ledger3.html#Currency-and-Commodi...

Implied exchange rates, arbitrary commodities/inventory. It gets into really heady territory pretty quick.

Does anyone know of in the spirit of something like plain text accounting (https://plaintextaccounting.org/) but adapted to integrate the complexities of a wealthy family? I intend to implement something myself, but was interesting if there was anything else out there.

The point would be to design something that substitutes for Addepar but with a sensibly organized sqlite db and csvs as "first class" sources of truth (and scripts to handle a variety of common functionality).

So it is really an exercise in understanding the correct architecture of various hierarchies, relationships, and categories in the context of a wealthy family.

All the major software out there just does not seem very good, have a principled handle on the fundamental and primitive relationships and operations that describe a family's financial affairs (everything done on an ad hoc basis). And because of this, entail complete data/platform lock-in.

I use Beancount; learned at https://plaintextaccounting.org/.

I use ledger (https://plaintextaccounting.org/) to manage my transactions in plain text and then generate reports. I copy/paste the transactions from pdfs received monthly in an Emacs Org file and then convert them to ledger format using ob-lc (https://github.com/jayrajput/ob-ledger-convert). There is a steep learning curve, but the results are awesome.