As a long-time Quicken user, I'd like to report a bug that I've noticed for many years that still seems to be occuring. I've gotten around it - but's its a PITA.
Here's how it plays out:
- I begin with two accounts - a checking account and a credit card account.
- I set up a transfer at a "future date" between the two accounts, representing a payment from my checking account to my credit card to pay off a balance (for example).
- The bug occurs when the "future date" arrives - and I download transactions from from bank for my checking account that shows this transfer has now been executed (for example).
- Quicken matches the transaction in the checking account - no problem.
- BUT — Quicken DOES NOT match the corresponding transaction in the credit card register - and INSTEAD creates another entry in the credit card register, essentially creating a "repeated entry" in the credit card registry.
- I am now left with a correct match in the checking account - and a double entry in the credit card registry - which essentially screws up its balance.
- The question now is - what to do next?
- I've found that if I delete the now original "unmatched" repeated entry in the credit card registry (my original planned entry) - Quicken deletes the original "now matched" entry in the checking account — causing the checking account balance to be off because the "new entry" in the credit card registry has no match entry in the checking account.
- If I delete the new entry made by Quicken in the credit card account - it also deletes the "matched entry" in the checking account - causing the checking account balance to be off (as above).
- It appears that Quicken allows multiple transactions from the credit card registry to be attached to a single transaction in the checking account registry.
The only way I've able to correct this situation is to delete both entries in the credit card registry (which by default deletes the matched checking account registry entry). I then recreate the transfer transaction from the checking account to the credit card account.
I've worked around this issue for years — but when it occurs (monthly for me) - it's takes a bit of sleuthing to resolve.
Best,
KPT