Some further research reveals that correct date parsing of QIF imports by financial and accounting programs is a common problem, particularly when:
- Transactions occur early in a month (days 1-12)
- Only one or very few dates are involved (programs have more and less sophisticated algorithms for identifying date sequences)
- Transactions are not listed chronologically in the imported file (the QIF standard does not require chronological order, since each transaction contains its own Date field)
- The file has been opened by Excel—particularly older versions—during the import process (Excel has had changing protocols over the years that attempt to identify dates as conforming to the US standard MM/DD/YY or MM/DD/YYYY formats, without user intervention)
The problem originates with the lack of a definite date format in Quicken’s now-antiquated QIF specification. (Even Quicken eliminated support for QIF files in most of its products a dozen years ago in most regions of the world.) Thus, Manager is not unique in having this problem. Documentation of other financial programs includes strong cautions to manually review—and edit if necessary—dates from imported QIF files.
Personally, I don’t think this qualifies as a bug any more than would the inability to correctly identify a 2-digit year. @whosat, if your bank offers other formats, you might try them and see if you get better results. In my experience, both QFX and OFX are both better.