is broken…should I keep going?

So I thought I could live with despite the fact that it renames every electronically paid bill as ‘BP’, and categorizes it as ‘Fuel’. As you might imagine, this screws up our budget a little.

First I sent the following bug report:

All of my electronic bill-pay transactions have descriptions that start with BP. Mint has decided that all of them must be fuel charges, i.e. BP the gas station.

How can I fix this?

They offered this reply:

Here’s how:

1. Log in to
2. Click the Transactions tab at the top of the page.
3. Click the transaction you want to rename and/or re-categorize.
4. At the bottom of the box that appears around this transaction, click Edit Details.
5. In the Description column, you can type a new name for this transaction. In the Category column, you can click the pull-down menu to view and select from other categories to re-categorize this transaction. To add your own completely new category, click Add/Edit Categories at the end of any of the category lists.
6. Check the box under “Rules” if you’d like to permanently apply the new name and/or new category to this type of transaction.
7. Click I’m Done.

Here’s the problem. Their rules are a very simple text replacement. So if I make a rule to replace, say, ‘BP’ with ‘Thunderhoot’, it’s going to change every one. Never mind that some of those BP transactions are daycare payments, and others went to the mortgage. All it has to go on when making the replacement is BP. So I respond:

Hi Mary,

Thanks for responding. Unfortunately, renaming doesn’t work because
ALL of my electronic bill pay transactions get renamed as BP. When I
make a rule for one, they all get changed.

Am I being obtuse? Seriously, sometimes I write things that seem clear but aren’t…maybe this is one of those times:

In order to investigate & troubleshoot bugs, we need to know the following:

1. Browser and Operating system you’re working with.
See link for supported browsers:

2. The specific steps (if any) that caused you to encounter the error.

3. A screen shot and description of the error. A file should be .jpg or .png format. *Directions for Windows users:
*Directions for Mac users:

Important Note: All requested information are crucial for fixing the bug.

I sense this is the ‘Give the customer some busy work and hope he’ll get tired and go away’ reply. Seriously, they actually think the browser is going to affect how their website processes data? Maybe my operating system? Just for the record, I’m using Firefox, or sometimes Safari. Normal versions, not special developer versions. I’m also using Snow Leopard, again a normal version.

For those of you who are curious, the misnamed transactions behave the same way regadless if it is Firefox or Safari, Mac or Windows XP, or even my iPhone.

It seems that the suggestions Damon (from wrote back on November 8, 2007, with concise instructions on what to supply aren’t correct. I posted a followup so others would know what is required.

Anyway, before these replies had shown up I had started contacting with the specific transactions that are misnamed, as requested in this post. It’s not easy to do, because even though has the correct transaction name (they include it in the properties of the HTML item for the transaction) there’s an extra step or two required to cut and past it into their contact form. Today I got the same browser/os/screenshot reply.

Putting together a complete screen-shot sequence of all the steps required to show their product doesn’t work is, well, a lot of work. The thing is I’m not the first person to notice it. I mean, this Lifehacker post from 2007 describes the problem pretty well under ‘Drawbacks’. My intuition tells me if they wanted to solve this problem, they’d have solved it. Or at least added a ‘Do not translate transaction names’ checkbox to the options page.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s