Transactions in "Kirkland" geography are mistakenly given the [Mint Description] of "Kirkland PCC", and are therefore mistakenly classified.

Hi Mint --  I love your stuff, and have been using it for years.  You have a problem though, which I'd like to see fixed. 

Your [Mint Description] is often computed incorrectly, using a keyword of the geographic area, instead of the merchant.  This causes all transactions in a geography to be lumped to a single (mistaken) classification.  That is, Restaurants, Groceries, Coffee Shops, ATMs, Gas Stations, etc..  are all put into a single mistaken [Mint Description].  And because they are all first classified into a single mistaken [Mint Description], they are therefore mistakenly classified into a single mistaken category.  Furthermore, there is NO WAY for me to fix this by applying a custom rule.

For example:

I live in "Kirkland, WA" USA.  This is a small city near Seattle, WA.  For a lot of the businesses in this area, "Kirkland" is a keyword used in the [Original Description].  Here are some precise examples...

[Mint Description]           [Original Description]


Kirkland PCC       CACTUS KIRKLAND          




 ... As you can see above, all of these get computed as "Kirkland PCC" by Mint.  And because I can only apply a rule on the [Mint Description], there is no way for me to properly classify these.  They all get lumped into "Groceries" in my case, but many of them should be "Coffee" or "Entertainment" or "Restaurants".    There is no single category that fits them all.

This is a systemic problem in Mint.  To fix it, ideally I'd be able to have more flexible control over the rules.  But that's a major feature for Mint I'm sure.  I'd settle for someone at Mint simply fixing my specific "Kirkland" issue in your algorithms.  Other people in “Kirkland” geographies also have this problem.  Here are other posts from others with the "Kirkland" issue..


Please advise,


P.S.  I realize this is a community support forum.  I already submitted a ticket to Mint.  I’m adding my ticket here as well so that others can see it and clamor together if they have the same issue. 

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: