41–50 of 126 posts
Earlier quoted context omitted.
Currently yes. hledger has rudimentary SQL export ( https://hledger.org/hledger.html#output-format ).
It'd be cooler if the quantities didn't come formatted with thousands seperator commas and currency symbols. Then, the numbers could more easily be treated as numbers in SQL.
For Normal People:
Double Entry even though may sound simple, it is quite a difficult concept to grasp. For the sake of double entry we use counter entries that take months to grasp. For example - Amortization, Allowance etc.
More over double entry method strives for standardization of entries. Having a plaintext non-autocompleting solution without accounting for only handful fixed type transactions....I just could wrap my head around it.
Moreover with online connected mobile solutions that are most of the time free why bother using this when the steep learning curve doesn't yield any marginal benefit.
For Accountant:
Excel is god and whatever accounting software the org is using is an acceptable solution
---
Even though the FAQs and the previous discussion has addressed this exact same issue. I really don't know what type of people would use plain text command line solutions except for the sake of using plain text command line solutions.
Slightly off topic, but I finally broke down and paid for YNAB this year and it has literally changed my life. It doesn't feel like accounting anymore, it feels like playing monopoly. Use QB for biz, and tried mint for years, both feel like work. YNAB not only tracks historical categories but makes it fun to plan future expenses.
I have used the old "lifetime" version. How is the new subscription software compared to it? Is it much improved? How?
Recently added budgeting to the mobile app. Most of the user-facing improvements have been cosmetic to UI design, colors, and phrasing.
The reports still are not at feature parity with the old YNAB4. Fortunately there’s an open-source Chrome extension - Toolkit for YNAB that improves reporting and charts. However, I find it disappointing this functionality isn’t built into the App.
Do these scale for multi-user situations? Access controls, segregation of duties, etc?
* Use a version control system - keep journal files in eg a github repo; control access, manage pull requests, audit changes in the usual way.
* Use multiple files - the journal can be composed from multiple files, each with different filesystem permissions/accessibility.
* Maintain files on a server, and run a web UI like hledger-web or fava, perhaps behind a login form, to give read-only or add-only access to remote users.
Earlier quoted context omitted.
I have used the old "lifetime" version. How is the new subscription software compared to it? Is it much improved? How?
The biggest additional feature in the subscription based app is auto-importing transitions. Personally, this is not of interest for privacy / security reasons sharing my banking passwords. Recently added budgeting to the mobile app. Most of the user-facing improvements have been cosmetic to UI design, colors, and phrasing. The reports still are not at feature parity with the old YNAB4. Fortunately there’s an open-sou…
Auto-importing isn't really a point for me, since YNAB has always only supported American banks.
I think I'll reinstall old YNAB these days.
I really don't know for whom this is for. For Normal People: Double Entry even though may sound simple, it is quite a difficult concept to grasp. For the sake of double entry we use counter entries that take months to grasp. For example - Amortization, Allowance etc. More over double entry method strives for standardization of entries. Having a plaintext non-autocompleting solution without accounting for only handful…
PTA tools, some of them at least, can scale well from beginner-level single entry accounting, or even zero entry "accounting" (just a list of dated event descriptions), to fully general double entry accounting that can model any financial event. I always encourage people to start out simple. What usually happens is they learn and become more interested and more sophisticated as time goes on.
So I would say one group of people this appeals to is people who want to get their hands dirty with Double Entry Bookkeeping, with the support of a lively and enthusiastic community, in order to understand it better.
Another is people who are expert with text editors, scripting and programming and want an accounting system where they can bring these skills and insights to bear.
Another is people who want total control and privacy of their financial records.
Another is people who want their financial data to be accessible and usable for a very long time (even without software, if it came to that).
I really don't know for whom this is for. For Normal People: Double Entry even though may sound simple, it is quite a difficult concept to grasp. For the sake of double entry we use counter entries that take months to grasp. For example - Amortization, Allowance etc. More over double entry method strives for standardization of entries. Having a plaintext non-autocompleting solution without accounting for only handful…
Granted using Emacs isn't exactly for everyone, but there are a bunch of tools out there to make editing the text file much easier
I really don't know for whom this is for. For Normal People: Double Entry even though may sound simple, it is quite a difficult concept to grasp. For the sake of double entry we use counter entries that take months to grasp. For example - Amortization, Allowance etc. More over double entry method strives for standardization of entries. Having a plaintext non-autocompleting solution without accounting for only handful…
I just send CSV exports and reports to my accountant.
I'm an independent software developer working on my own. I guess it's useful for people like me.
Anyone have experience with the apps mentioned in the site?
My beancount file is nearly 3 years old now and I love it. Maybe it's overkill for personal finances, but I've tried countless other PF tracking tools and online services and none of them have the flexibility you get from tools like this. For example, tracking RSU vests, my house purchase etc.
Combining beancount with Fava gives you a nice visualisation tool as well which auto updates when it notices the underlying beancount file has changed.
I edit the file in Emacs using the beancount-mode, it's actually the only thing I use Emacs for but I have a bunch of custom elisp functions that add things to the file whilst I'm editing it.
I don't bother with any auto txn importers, which does make it a manual process but it's like 10-15 minutes a week at most. Additionally most of my purchases are generally quite rote so a lot of them are just copy/paste from previous txns and modify the date and amount. This might not scale if I have a partner, but for now just Emacs + vim keybindings + a few custom elisp fns + a little patience works for me!