QB 2014 Bank Feed Transaction List Redesign

Since the release of the 2012 program, I have been trying to convince clients that it is now O.K. to use downloaded transactions, as many of them have been burned by previous iterations of the feature with incorrect matching, strange data and bloated vendor and rule lists.

With the 2014 version, however, I am forced to advise against using this after losing many rows of entered-but-not-added data, in addition to the nuisance of performing mouse-necessary actions (such as adding a memo). I've also encountered a programming bug while using the Shift key when entering Payee names.

The layout is akin to the Batch Enter Transactions screen - in graphical design only. Programming-wise, it is very different. Previously entered payees and accounts disappear after having been clicked or tabbed-through. Entry is not retained after list changes. If you type a capital letter in a Payee field, the keyboard's Shift key becomes the Tab key when released.

The redesign already has the potential of making this a very good feature, and so I hope Intuit can work through these shortcomings - and soon!


The very best Online Banking Center function and layout is the QB 2009-2012 "Side by Side" mode.

It used Renaming Rules instead of Alias, and you have "other transaction Types" so you can select the download is a payment from a customer, link it to invoices; or a Bill payment, link it to open bills; etc.

2014 is a huge step backwards. If your bank doesn't support the Live Feeds, you are back to the old "register" mode that you told everyone to avoid.

Was this answer helpful? Yes No

No answers have been posted

More Actions

People come to Accountants Community 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: