Since there are many ways HSA's are managed, here is the method I use for my situation. My employer fully funds my HSA at the start of the year.
![Works Works](/uploads/1/2/5/3/125353317/932234125.png)
![That That](/uploads/1/2/5/3/125353317/840589799.jpg)
Since I haven't contributed this entire amount, essentially they are giving me an interest free loan. If I quit before the end of the year, I'd have to repay any money I hadn't contributed and used. What I do:. Create a Manually tracked Loan for the HSA amount, and set it to 0% interest and 12 months (with payments bi monthly, weekly, etc based on when you make contributions.). Create a Manually tracked Banking account for the HSA expenses (you could also create this as an Asset instead and link it to the Loan, but I prefer just to use a Banking account).
Make the opening balance the balance of the 'HSA Loan' created above. (Optional) Add a pre-tax (or could be post-tax in some cases) item to my Paycheck in Quicken to pay the 'HSA Loan' created above.
This will 'pay down' what you owe each check to your HSA. At the end of the year it will be 'paid off'. Log any expenses or reimbursements from the HSA in the HSA Banking account register. My girlfriend, who's finances I track in Q, also has an HSA. Her's isn't pre-funded, as is dranobob's.
In Quicken, I have one account, call it 'HSA-Investing' listed under investments, and another account 'HSA-Cash' listed under banking. Both accounts tie to the same physical account, but are represented as two separate ones in Quicken. Mar 16, 2017 - I have a new HSA play with Payflex and am using Quicken 2017. Also see this Thread: I was updating my Quicken Premier 2017 PayFlex HSA accounts. One Step update worked just fine this morning as well.
SO, I just set it up as a regular 'Asset' type account with a starting balance as of 1/1/14 (when I started tracking her finances). The 'Transfers In' to the account are set as 'W2- Wages, self' (she has her own Q data file).
Thus the paycheck deposits to the HSA reduce her W2 taxable income. Her employer makes quarterly contributions, which I just record as 'FlexContrib' (it isn't really, but that's a convenient tax line to use). Expenses paid from the HSA go to an 'HSA Expense' expense category, that's used just to keep track of the total amount of HSA expenses. 'HSA Expenses' doesn't have any tax attributes and doesn't appear in any tax related reports.
Attached are two screen shots after a sync to mobile operation. I reopened Quicken 2018 Mac to discover that my main account had around $15,000 extra dollars in it this time.
The screen shots do not show much. I opened up the crash report (which I’v sent around 10 times over the past two months to Quicken) to show details. Unfortunately that was as large a window as I could show. The same thing happens on update all online accounts (I now do all this through manual downloads, which works). Thanks for the help.
I tried that using App Cleaner. Same issues arose, so here: This time I removed Quicken 2018 from my hard drive. Then I did a complete reinstall of Quicken 2018.
Restored my Quicken file from a back-up and opened it. I immediately did 'sync to mobile' and the program crashed again. So to repeat something that has been happening since Febraury 22, 2018 — (1) Select 'Sync to Mobile'; (2) Crash of Program; (3) Account balances are changed with no way to correct except from a back-up. I've sent this in through 3 updates of Quicken 2018. I've called tech support to inform of the problem (they were not so great at understanding me or the problem); Posted the problem in a forum.
Sorry to keep it up, but if Quicken can't fix this, I have to find another software program. Thanks for the note. If you'll look above — I am just now noticing my post from yesterday is not there. Yes, I followed Tyka's advice, created a new admin account, opened the file, did 'Update all Online accounts' and the program crashed again with the same results. I posted in response to Tyka, and uploaded to pictures, but I have since trashed them (as I thought I posted them).
So, I have (1) deleted Quicken from my drive, and did a full reinstall, and the same problem resulted; (2) I opened a new Admin User and opened my file in a new User environment and the program did the same thing. So nothing has worked, and did as the question why Quicken doesn't look at the code for the builds prior to Feb 22, 2018 as it all worked prior to that date for me. I think I installed a new build and the program crased on the sync. I'v done all I can outside of doing a complete install of everything, which I am not going to do. So could some one there help me? I'm sorry my previous response to Tyka is not above. I did it yesterday 4/10.
Yes, I have. That was very frustrating. Here's the ticket number: 01322868 — Quicken 2018 Ticket.
The person didn't even understand the issue from my perspective. I eventually asked him to tell the development dept. I know the issue is in the code, and after all I have done — maybe it is a corrupt data file, but that does not account for why it worked perfectly before Feb 22, 2018 and not after. I have not heard a thing on the ticket, which is why I started posting here. Now I uninstalled, reinstalled, restored from back-up, created a new admin user, and each step creates the same issue.
So I don't think it is with my machine. Unless you know of conflicts with other software, I don't know what to do. An I thought all Mac programs are sandboxed anyway. Sorry you're experiencing this issue. I found the crash reports that you've submitted, and I see that it's an issue we've been scratching our heads about for a while.
Quicken has data validation rules in place for complicated transactions so they can't be changed in ways that cause them to become nonsensical. For example, if you have a linked transfer between two accounts, that ends up creating two different transactions (one in each account) but Quicken ensures that any changes made on one side are automatically applied to the other side. There are also rules in place about transactions with multiple split lines where one or more split line is a linked transfer to another account. The 'other side' of those transfers (the transactions in the remote accounts) have a single split line, even though the 'local side' has multiple split lines. So the normal rules don't apply: Quicken wouldn't always be able to propogate changes made on the single split line to the other side. So those single split line transactions are locked from being edited: if you try to modify them, you're told to go edit the other side of the transfer instead.
Internally, we refer the single split line transactions in this configuration as 'locked child transfer' transactions. Probably more detail about Quicken internals than you care to know.:) The issue you're experiencing is that the sync server is returning data to Quicken which is somehow causing Quicken to attempt to modify or delete a 'locked child transfer' in an inappropriate way, and the data validation rules kick in and crash the program to prevent that. We need to understand the way it's getting into this state in order to figure out the logic problem and correct it. I'm going to reach out to you directly to troubleshoot this issue. The issue has been ongoing for a while, but most of the occurrences we've seen so far are temporary and not reproducible, even after we've reached out to customers to troubleshoot.