Agree, but sometimes the CSV import file has an error and big import files are ugly to deal with notepad. Because then, you have to be extremely careful.

We do tons of importing, and our one suggestion and we don't need a calendar for this idea, is be consistent with the ability to do imports with the formats shown as available. A specific example is bank statements in BankRec. Many banks and credit card downloads now offer XLS and some offer XLS instead of CSV. Or we can use OFX. And the XLS import format does not work.

We are installing BankRec to reconcile Credit Card statements which is one of the reasons we would like to see XLS as one of the working import file types.

So if the drop down option for import file format says you can do Excel, then the program should be able to do Excel. Please don't waste our time planning and creating an import template file in XLS or offering up specifications to a 3rd party developer that we can take in XLS or CSV because the program import suggests that you should be able to do XLS, and then only offer CSV with a nice error message when you save the import template with XLS file format.

And yes, we can pre-test every import document type to see if the XLS actually works. but we're looking for efficiency here.

Thanks,
Brian