Why don't Mint's Transaction Rules use the REAL transaction name?

One area where Mint should absolutely be best in class is in Rename Rules, but there's one big issue that makes your Rename Rules a huge hassle. Here's my user story.

Take an example transaction from my bank statement:


How does Mint read that?

"L Time Date" (see screenshot 1)

Every transaction from that bank has “L340” somewhere in it. It has “TIME” and “DATE” there, too. Based on a cursory Google search, I'm not the only one whose bank uses these terms in its transactional metadata. And yet this happens all the time in Mint.

Yes, Mint gives me the ability to create a Transaction Rule. I can manually teach Mint that this particular transaction is not from “L Time Date” but is from “Airport Road Family Fare”. I just type in the correct payee and check the box that says “Always rename L Time Date as Airport Road Family Fare" (see screenshot 2)

Wait, what?! If I check that box, Mint’s going to rewrite any transaction called “L Time Date” to “Airport Road Family Fare”. But… there’s no actual transaction called “L Time Date” on my bank statement. That’s just the useless payee that some back-end algorithm has invented. The moment I check that box, Mint starts renaming every debit transaction from my bank. Not helpful at all.

My question to the developers? Why doesn’t that checkbox say:

“Always rename Point of Sales Debit L340 TIME 11:15 AM DATE 06-18 AIRPORTRDFAMILY CHAPEL HILLNC as Airport Road Family Fare and categorize as Uncategorized.”

Use the FULL DESCRIPTION from my bank. Or fix your automatically renaming rules so they're actually useful. It doesn’t seem like that would be too hard to implement, and it would make your rename rules... truly rule.


No answers have been posted

More Actions

People come to Mint for help and answers—we want to let them know that we're here to listen and share our knowledge. We do that with the style and format of our responses. Here are five guidelines:

  1. Keep it conversational. When answering questions, write like you speak. Imagine you're explaining something to a trusted friend, using simple, everyday language. Avoid jargon and technical terms when possible. When no other word will do, explain technical terms in plain English.
  2. Be clear and state the answer right up front. Ask yourself what specific information the person really needs and then provide it. Stick to the topic and avoid unnecessary details. Break information down into a numbered or bulleted list and highlight the most important details in bold.
  3. Be concise. Aim for no more than two short sentences in a paragraph, and try to keep paragraphs to two lines. A wall of text can look intimidating and many won't read it, so break it up. It's okay to link to other resources for more details, but avoid giving answers that contain little more than a link.
  4. Be a good listener. When people post very general questions, take a second to try to understand what they're really looking for. Then, provide a response that guides them to the best possible outcome.
  5. Be encouraging and positive. Look for ways to eliminate uncertainty by anticipating people's concerns. Make it apparent that we really like helping them achieve positive outcomes.

Select a file to attach: