Rob Taft

Using 999999 with millify should return 1M but it returns 1000k ``` >>> from millify import millify >>> millify('999999') >>> '1000k' ```

Commas in large numbers break parsing

2

A quicken 2016 export with transactions greater than 1000 will export it as 1,000. Parsing throws an exception when encountering this.

Typo with !Type:Ccard

1

The code contains a check for !Type:Ccard, however the spec and my export use !Type:CCard. This errors since qifparse's check for this type is case sensitive.

I have some old memorized transactions that are not active, but still appear in the export. One of the accounts that was originally attached to one of the split lines...

Currently, unsupported types in a qif file will abort the import. Add support for !Type:Price

Currently, unsupported types in a qif file will abort the import. Add support for !Type:Security

The original QIF spec has option headers. A Quicken export includes these, qifparse errors and fails when parsing a file that includes them

This tool does not support !Type:Tag and fails if it encounters any types it does not recognize. !Type:Tag is currently exported from Quicken 2016.