In terms of my paycheck import, the things that most immediately come to mind are being able to
- track my employers total compensation so that I can compare employment opportunities - verify the information on my employer provided W2 - ensure that I'm withholding enough throughout the year to avoid tax penalties - eventually automatically import my beancount data into turbotax (or at least present it in a way that allows me to enter it quickly) I do literally all of the above, and have done so for years using Beancount :). It generally works very well. Simply importing your pay check into a reasonably well designed account hierarchy takes care of most of the above. W2 generation can take just a bit of effort to get right, and you can see how I do it with my writeup and code in the tax article. Actual insurance premium costs are not included in most pay stubs. For those, typically it's a fixed amount, or a multiplier of the employee-paid premium, so it's trivial to get right and automate if you so wish. Everything else is straightforward. That's an awesome writeup! I hadn't seen your capital_gains_classifier plugin <https://github.com/redstreet/beancount_reds_plugins/tree/main/beancount_reds_plugins/capital_gains_classifier>yet. I'll definitely check that out. Thank you for sharing. Welcome! I'm a bit on the fence as to whether I want to organize my account hierarchy for tax purposes or not. I'm not opposed to it if there's not another way to accomplish tracking tax liabilities, but it would be cool if there was a way to do this via bean-query and tags (taxable, non-taxable, long, short) instead of having a lot of nesting within my accounts. I would really only want to check tax implications once a quarter, so a report for this would be ideal. You can organize your hierarchy however you want, there are really no restrictions. My metrics are a) does it simplify obtaining the aggregations that I frequently want to see? and b) is it simple enough that fiddling and maintenance are unnecessary? I didn't organize my account hierarchy for tax purposes. Rather, I had it organized for my other needs, and from there, a couple minor modifications made it work very well for tax purposes. For me, I already wanted to be able to see and quickly drill down into what my capgains/losses are any time in the year, and by account. Fava's tree display serves my purposes very well, so the hierarchy works for me. Figuring out my frequent workflows was the biggest input into my hierarchy design. -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/beancount/331b6da4-38a3-4c2c-a24d-7e87025db26an%40googlegroups.com.
