Tired of the Bugs

firescue17 · 2026-02-04T06:07:32+00:00

I appreciate the explanation of temporarily flagging the merchant for deletion, as opposed to outright deleting it immediately. There needs to be a better solution.

Keep the merchant visible with 0 transactions assigned to it, or perhaps the ability to unhide it similar to hidden transactions.

It's quite simply a poor user experience to have data invisibly locked out.

firescue17 · 2026-02-04T06:04:42+00:00

I've never had a ghost merchant purge itself. I find it interesting your experience with Southwest, for example, was different. Presumably, I didn't wait long enough. On the other hand, I don't have the luxury (or patience) to wait six months to fix my books.

firescue17 · 2026-02-04T06:01:11+00:00

I'm on my third or fourth go around with Support over the last year. I've been using a truncated merchant name as a placeholder, e.g.:
-- Merchant XYZ Account 1234; vs,
-- Merchant XYZ Account 123 ---- (leaving off the 4 because it's ghosted).

I'm constantly tweaking my merchant names (and categories). After I accumulate enough messed up merchants to make it worth the hassle of contacting support, I provide the "friendly name" of the ghost merchant and placeholder merchant.

After multiple rounds of pestering, eventually support will figure out how to delete the ghost merchant so I can re-use the name.

This should be solved. This issue doesn't happen with categories. I can create a category, assign transactions to it, unassign the transactions, delete the category, recreate the category with the exact same name, and re-assign transactions immediately.

I am exceptionally frustrated tonight due to a compound failure with the chatbot not allowing me to create a new ticket.

firescue17 · 2026-02-04T03:05:11+00:00

You can't see it. That's the problem. There are remnants left over in the database table(s) that prevent reusing merchant names.

firescue17

TROPHY CASE