Employer Paid Benefits (Non-taxable vs taxable)

126 views
Skip to first unread message

Gary Roach

unread,
Dec 8, 2024, 4:04:13 PM12/8/24
to Beancount
Hi all,

I'm working on importing my paycheck and I'm not sure how to handle employer paid benefits. I have 3 employer paid benefits: imputed life insurance (taxable), life insurance (non-taxable), and medical insurance (non-taxable).

For the taxable imputed life insurance, I think it makes sense to have an income and an expense leg on the paycheck entry since this does count as taxable income for me and the expense was paid on my behalf. 

2024-12-01 * "Hooli Paycheck"
  Income:Hooli:Salary                          -2000 USD
  Assets:Bank-Account                           1250 USD    
  ;; Employer Paid Benefits
  Income:Hooli:Imp-Life                          -50 USD
  Expenses:Hooli:Imp-Life                         50 USD
  ;; Before Tax Deductions
  Expenses:Pre-Tax:Medical                        50 USD
  Expenses:Pre-Tax:Dental                         50 USD
  Assets:Pre-Tax:401K                            100 USD
  Assets:Pre-Tax:HSA                             100 USD
  ;; Taxes
  Expenses:Taxes:Income                          250 USD
  Expenses:Taxes:Medicare                         50 USD
  Expenses:Taxes:Social-Secuirty                  50 USD
   ;; After Tax Deductions
  Assets:Post-Tax:ESPP                           100 USD

I believe the above entry is correct from a tax perspective. Income:Hooli represents Gross Income and Income:Hoolie - Expenses:Pre-Tax - Assets:Pre-Tax represents Taxable Gross Income.

However, this doesn't include the remaining employer paid benefits for which I'm not liable for from a tax perspective. This has the problem of not representing the true compensation from the employer as well as underrepresenting the true cost of health insurance.

My first thought was to add them in a similar way as the imputed life insurance benefit. 

2024-12-01 * "Hooli Paycheck"
  Income:Hooli:Salary                          -2000 USD
  Assets:Bank-Account                           1250 USD    
  ;;Taxable Employer Paid Benefits
  Income:Hooli:Imp-Life                          -50 USD
  Expenses:Hooli:Imp-Life                         50 USD  
  ;;Non-Taxable Employer Paid Benifits
  Income:Hoooli:Life                             -50 USD
  Income:Hoooli:Medical                         -225 USD
  Expenses:Pre-Tax:Hooli:Life                     50 USD
  Expenses:Pre-Tax:Hooli:Medical                 225 USD
  ;; Before Tax Deductions
  Expenses:Pre-Tax:Medical                        50 USD
  Expenses:Pre-Tax:Dental                         50 USD
  Assets:Pre-Tax:401K                            100 USD
  Assets:Pre-Tax:HSA                             100 USD
  ;; Taxes
  Expenses:Taxes:Income                          250 USD
  Expenses:Taxes:Medicare                         50 USD
  Expenses:Taxes:Social-Secuirty                  50 USD
   ;; After Tax Deductions
  Assets:Post-Tax:ESPP                           100 USD

Income:Hoolie - Expenses:Pre-Tax - Assets:Pre-Tax still represents Taxable Gross Income, but the employer paid benefits are now counted towards my Gross Income. Which I guess it is, but my W-2 doesn't usually include that in Gross or Taxable Gross. I guess I could still calculate Gross with Income:Hoolie - Expenses:Pre-Tax:Hooli to remove the non-taxable employer paid benefits, but this seems a bit off to me. I'm curious what everyone else is doing here?  

Timothy Jesionowski

unread,
Dec 8, 2024, 4:12:06 PM12/8/24
to bean...@googlegroups.com

What I do is have a separate currency like CUSD (Corporate-USD) for money flows that are about me but aren't my money. Works just as well for travel expenses.

Mostly this just makes the Income balances more immediately legible.


--
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+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/beancount/8e20a919-b660-429d-8f9a-9b8bf7024bf2n%40googlegroups.com.

Red S

unread,
Dec 9, 2024, 12:58:31 AM12/9/24
to Beancount

Many ways to peel this orange. One way is thee other reply you’ve gotten so far.

When in this situation, I find it helpful to ask myself: “what set of end results do I want out of my accounting system?” In your case, it could be:

  1. Numbers that match with the tax authority (in this case, consistent with IRS, 1040, and W2, perhaps?)
  2. consistency with your employer’s paycheck entries (for easy verification?)
  3. determining true cost of health insurance
  4. Something else?

My personal take:
(1) I’ve found to be valuable and fairly easy to accomplish. See my writeup here. I use metadata to match accounts to a W2. This allows me to record what I want (eg: true health insurance premiums) without worrying they’ll affect my W2:

1821-01-01 open Income:Employment:Benefits:Employer-401k USD taxable-income-box1: "False"

I also use my rename_accounts plugin to rename accounts on the fly (eg: move Income:Employer:Health-Insurance to Equity:Employer:Health-Insurance), when needed primarily so I can use some of Fava’s features that are not available via queries.

(2) is easy to accomplish with the above

(3) is also easy to accomplish with the above. Or you could choose to simply not involve your accounting system, since that’s usually just one number per year to track separately

Hope that helps. If it’s something else you’re seeking, feel free to share.

Gary Roach

unread,
Dec 10, 2024, 12:03:10 AM12/10/24
to bean...@googlegroups.com
On Sun, Dec 8, 2024 at 4:12 PM Timothy Jesionowski <timothy.n....@gmail.com> wrote:

What I do is have a separate currency like CUSD (Corporate-USD) for money flows that are about me but aren't my money. Works just as well for travel expenses.

Mostly this just makes the Income balances more immediately legible.

Nice! That definitely makes it easy to see the income you actually have at your disposal, but still track the total employer compensation.

On Mon, Dec 9, 2024 at 12:58 AM Red S <redst...@gmail.com> wrote:

Many ways to peel this orange. One way is thee other reply you’ve gotten so far.

When in this situation, I find it helpful to ask myself: “what set of end results do I want out of my accounting system?”

The main reason I decided to adopt the system was to better track provider billing and insurance claims. Now I'm really just exploring other use cases. 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)

On Mon, Dec 9, 2024 at 12:58 AM Red S <redst...@gmail.com> wrote:

My personal take:

(1) I’ve found to be valuable and fairly easy to accomplish. See my writeup here. I use metadata to match accounts to a W2. This allows me to record what I want (eg: true health insurance premiums) without worrying they’ll affect my W2:

That's an awesome writeup! I hadn't seen your capital_gains_classifier plugin yet. I'll definitely check that out. Thank you for sharing.

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. 

 

Red S

unread,
Dec 10, 2024, 12:38:36 AM12/10/24
to Beancount
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 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.


Reply all
Reply to author
Forward
0 new messages