Cbc VS plaintextaccounting

Taking a look at pulp it just seems to be a solver abstraction API and all the real work is done by solver libraries written in other languages like C++. It looks like the default solver is COIN-OR CLP/CBC, and it looks like that's written in C++: https://github.com/coin-or/Cbc/tree/master/src

Maybe I'm misunderstanding something here and it's the abstraction API causing the problems, but it seems like it's up to the solver implementation to be efficient here?

Hi! I am searching for people who have previously used COIN-OR CBC through it's C++ libraries. I am specifically going to use their lotsize variable type ( Need for Creation of a new type of variable in the CBC Solver (Bucket Variable) · Discussion #516 · coin-or/Cbc (github.com) )

To use CBC (https://github.com/coin-or/Cbc) we need to compile it. Get source code from following address instead of github, this archive include all dependencies as well which will be compiled as well (if missing)

I've looked at it a little bit, but as someone nearing retirement, it is lacking a number of features that I would like.

There are some common tricks that I don't see how to model with ProjectionLab:

1. Do your tax-deferred 401k,403b,IRA saving in a high earning job, state, then move to a low or no income tax state to do the withdrawals in retirement.

2. Retire early so there is some time before taking social security payments to do Roth Conversions. I-ORP[0] turns this into a branch and cut linear optimization problem. User Indyhou at Bogleheads[1] has built a spreadsheet that uses a solver plugin. It may be possible to build a model in CBC[2] and compile it to WASM and run it in the browser.

3. After turning 63, watch the Roth Conversions to make sure you don't trigger IRRMA medicare surcharges.

4. Are you trying to stay under income limits for ACA subsidies? It's not quite the sharp cliff that it was, but can be important for some.

5. Are you trying to balance regular income and capital gains to take advantage of the 0% cap gains rates? You've got to plan ahead on your contributions to the taxable and tax deferred accounts for this to work. Jeremy at Go Curry Cracker has written about using this to pay $0 in US Federal Income taxes[3].

6. Paying full rate for health insurance will likely get you over the 7.5% limit for tax deductions.

7. Social Security claiming strategies can be complex for married couples.

A feature that would be useful during accumulation is life insurance planning for the death of a spouse.

The death of a spouse can throw a wrench in some of the strategies since the single tax bracket is much smaller. Tax law changes can also upset highly optimized strategies. So any highly optimized strategy should also have a monte carlo simulation around a spouse dying and tax law changes to understand what disruptions are possible and maybe accept a non-optimal strategy that is better in these adverse cases.

[0] https://i-orp.com

[1] https://www.bogleheads.org/forum/viewtopic.php?t=365518

[2] https://github.com/coin-or/Cbc

[3] https://www.gocurrycracker.com/go-curry-cracker-2020-taxes/

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.