Everytime I enter my national guard pay(once a month), it magically matches to a transaction that wasn't there, but then it was. Example: I just entered my September deposit for ~$358. It then matched this transaction to a $411 deposit dates January 20, 2015. It changed my entered date to January as well, so when I unmatch it, the transaction I entered has a date of January. The mystery transaction that keeps popping up, is always the same amount and same date. I have deleted it multiple times.

What is going on here, and how do I fix it?

Someone must have an idea about this?!?

I just entered another entry 2 minutes ago, and it immediately "matched" with this mysterious 411.11 transaction. The values I entered was 447.64. Where is this rogue transaction coming from, and how do I stop it? And while it has the date of Nov 20 in the Date column, the bank entry that shows up for 411.11 has a date of Jan 20, 2015, and it changed my entry to a date of Jan 21, 2015.

This stupid transaction just made a comeback. Anyone have any ideas?

KMyMoney does what you tell it to do. You probably defined something somewhere which explains this behavior. Check your matching definitions. As an example of unexpected behavior, see this post.

EDIT: also see the manual:

Code: Select all

Specifically with OFX or HBCI, it is important not to delete the imported transaction, because you will find that the next time you import your transactions, the deleted transaction shows up again. This is because modern import formats like OFX and HBCI use a “Transaction ID” to identify transactions. When you delete the imported transaction, the transaction ID goes with it, so the importer has no way to know this transaction was already imported.

But I don't know of any way of figuring this out. I can't see a transaction ID, and the supposed transaction is from January 2015, over a year ago. Which is far older than anything my bank is sending me during an OFX update. And I have certainly not deleted the 411.11 transaction, I can see it in my ledger.

I will check out that post though.

I read that post you referenced, which led me to look into my Payees and matching. I found the Payee trying to "Match on Payee name" and I am unable to delete this Payee (which is named by my bank, I have another Payee set to match to the same name), and there are no visible transactions with the payee.

This would all seem to be tied together I guess.

Same issue as this thread:
viewtopic.php?f=69&t=97791

I selected "No Matching" for the bank named transaction. Hopefully that helps.

Nice find. I hope it solves your problem, though I'm not sure we understand everything. Match on name seems like the right setting. As to the problem that you cannot remove the payee, the reason is that it is still used somewhere in another context. The page you mention explains this very well, and I agree it's a bug. If you're brave, you can unzip your KMM file, track down the payee, and replace it manually. Do not try this unless you know exactly what you are doing, and hold on to your original file until you are sure the corrected version is OK.

I was never able to resolve the issue. The same transaction kept trying to match with new transactions, so I've started a new file to get rid of this thing.