clacct: Multiple user, multiple account finances

clacct took a little effort to get working, but in the end, it was worth it.

Very straightforward, no interface to speak of, and line-by-line account management. For multiple users and accounts too, apparently.

Like clipf, there doesn’t seem to be a way to edit transactions once you’ve entered them, but the account files are hand-editable, so that shouldn’t be a big problem.

clacct can handle IOUs, which seems unusual among console banking tools. It’ll transfer money between accounts, show recent transactions or a full account history, and a few other things.

And if the home page is to be believed, you can set up rules for regular transactions, like paychecks or automatic bill payments. I’ll be honest: I didn’t dig that far into clacct.

clacct isn’t new; the timestamp on the tarball is 2004, but it seems to work fine for me in Arch. If you decide to try it, you might need to install perl-date-calc, or the equivalent in your distro.

Happy accounting. 😉

chkbk: Simpler than some others

I’ve found a few personal finance tools in the past year, most recently brinance and clipf. Here’s another one: chkbk.

chkbk isn’t in Arch or AUR and doesn’t appear in Debian either, which is a shame because it’s not a bad little program.

It behaves much like you might expect, keeping an account for checking and another for savings.

You can make deposits and withdrawals from either, show balances and account histories.

Supposedly printing is possible too, although I don’t have a printer so I haven’t tried it.

If you have very simple banking needs, or if don’t care to learn the complexity of something like clipf, this might be an option.

brinance: Simple command-line accounting

No interface on this one, folks. But it still has the potential to be quite useful. Here’s brinance:

To read the history of brinance, it sounds like a reaction to the relative complexity of things like GnuCash, when the writer just wanted something for personal accounts.

And that sounds about right. brinance can handle credits and debits, multiple accounts and transfers between them.

But if you want recurring credits or debits, interest calculation or something a little more complex, you’ll have to do some footwork.

Having said all that, I should note that there is a tk interface for brinance, written by a different author and designed to run against version 3. It does make brinance a little more accessible, in some senses. Don’t forget to install perl-tk if you want to try it out. 😉

clipf: Cryptic, but powerful

From the customer suggestion box comes clipf:

clipf is a personal finance manager, and one that takes a little getting used to. Of course, that might just because I do my finances in a spreadsheet. With sc. Because I am an action movie star. 🙄

I have relatives that swear by Quicken or whatever le app du jour is. A spreadsheet usually does the job for me.

So shifting to clipf is a bit like learning to park a boat. It requires a change in your approach. I fear change. 😯

Not really. But there doesn’t seem to be much documentation on actual use of clipf, aside from what’s here.

My advice is first to set the account with whatever name you like (I chose “Home” in the screenshot there), then start adding categories with prod add.

clipf allows you to declare subgroups via dot-names, which means you can group milk and cheese and so forth under dairy., if you like.

Convenient in that sense. Because later, when you make reports, you get a breakdown by category.

Make adjustments against your account with the op add function. Use can use tab completion (thank goodness).

Finally reports with rep. There are some other functions, and you can set dates and so forth with flags against each command.

So really, clipf is a lot like a specialized shell, that works primarily as a financial manager. Kind of cool.

One thing I should mention is that this is a python2 program. I tried to run it against the current python3 package and got errors. (Also, for Arch users, the AUR package seems somehow empty. It installed nothing that I could find on my computer. 😕 )

The only other quirk I should mention is that once you enter an operation, you can’t delete it. You have to reverse the operation to nullify it.

So if I make a typo I have to make a step backwards to zero it out, then start again with the error still in my report? Seems odd, and slightly inconvenient. 😐

Probably I would just hand-edit the database file, to get it out.

Regardless, I think I will spend a little more time with clipf, and see what it can do for me. That a 30-year-old spreadsheet program can’t, that is. …