Summary: | Would like an option to suppress downloaded transactions for $0.00 | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | george |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | ostroffjh |
Priority: | NOR | ||
Version: | git (master) | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
george
2014-09-16 22:50:30 UTC
Just as a temporary workaround, is there anything at all sufficiently common in the payee field that you can use to attract all those transactions to a "dummy" payee? I do that for many of the transactions I download that do not need a payee (mostly transfers from my checking account for online payment of various credit cards or other accounts.) I still need to edit them, but at least I don't also need to remove the payee every time. (In reply to Jack from comment #1) > Just as a temporary workaround, is there anything at all sufficiently common > in the payee field that you can use to attract all those transactions to a > "dummy" payee? I do that for many of the transactions I download that do > not need a payee (mostly transfers from my checking account for online > payment of various credit cards or other accounts.) I still need to edit > them, but at least I don't also need to remove the payee every time. Yeah, I have a payee called "DELETE THIS" to try and catch them. The big offender is the Discover CC. Now I just caught them sending a zero amount on a legal Payee. FWIW I sent Discover CC a note about it. They even seemed to care. Time will tell. I'm about to file a new wishlist item for an option to prevent the importer from creating new payees, as I find they are much more likely to be bogus, based on irrelevant words in the banks payee or memo fields. So, it seems closely related to this one, but I suspect they serve sufficiently different purposes that they should stay separate. |