nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

IDEA for Quicken: Support import of transactions from XLS

basegad

I've regularly run across institutions (i.e., HSA administrators) that do NOT supply financial transactions in QIF or other Quicken supported formats.

I'm SICK and TIRED of the manual entry or cut/paste and do not understand why Quicken doesn't have a couple of smart interns write an import utility into the program that allow a user to map an XLS/CSV file to their required inputs. This would be something I'd use vs. the 3rd party shareware that converts CSV to QIF…

This is a VERY common feature of a lot of products and keeps users like me from getting frustrated and dumping Quicken!

Find more posts tagged with

File Import

Comments

nmestanas

You should post this idea in the proper subforum here:

https://community.quicken.com/categories/windows-ideas

mshiggins

@basegad you are not the only one who tired of not being able to import Excel or CSV files into Quicken.

https://community.quicken.com/discussion/7100667/faq-a-program-to-add-the-account-name-and-type-to-qif-files-so-that-quicken-will-import-them

Chris_QPW

It has always been my impression, the Quicken management sees this something or little value to them at best, and a threat on the other side of the coin.

When Intuit owned Quicken, they definitely had monetary reasons not to support something like this and push for customers to push financial institutions to support Quicken where they would make some money off that. These days with Quicken Inc it gets a lot cloudier of what the story might be. They definitely don't directly get money from financial institutions, but their "only aggregator" that they pay for downloading transactions is Intuit, which might push them one way or another not to support other formats. But in truth I think the main reason, is Quicken Inc just doesn't want to support this because it isn't as cut and dry as people tend to make it out to be.

Excel/CSV format only describes "columns of data". There isn't any standardization of the data in those columns. That means that one way or another it will be up to the user to tell how the mapping of the data is, which isn't too hard for non-investment accounts, but is quite difficult for investment accounts. And once it is "supported", it is Quicken Inc that will have to field all the questions/problems on it.

They have a hard enough problem trying to maintain all the financial institutions "they support" (really mostly Intuit supports) without having to directly deal with the customer directly trying to access/convert data.