Question

How to fix improperly auto assigned data in bank feeds? Help!

Forum|Forum|7 years ago
January 10, 2019
15 replies
110 views

Okay, so yesterday I imported hundreds of transactions into QB pro from Chase Bank via a downloaded web connect file. Because of a move to a location far from a Chase bank location, I switched to using the Chase bank mobile app to deposit customer checks into my chase business account a few months ago. This is the first time I have imported these transactions into QB since this change to the Chase Mobile Deposit system.

Here is my issue. Chase bank reports each mobile deposit as simply; "Remote Online Deposit". So QB sees every deposit I made via mobile deposit as being from the same customer, which for some odd reason it automatically assigned to a single customer name. So now I have 239 deposit transactions sitting in the Bank Feed Manager list as "Changed By Rules" all in the name of one customer.

Now, I keep copies of the checks I deposited via chase mobile deposit, so I have the correct information, but there is a problem associating it with the auto-assigned transactions in the Bank Feeds Manager. I have tried entering the checks manually via the "Enter Sales Receipts" function and then going to the Bank Feed Manager and trying to use the "Match to Existing Transaction" action to tie the appropriate (but misassigned) transaction to the correct customer check that I entered manually, but I am not given the option to match it, because the date of the check and the date of the deposit are not the same, and there is no additional customer data associated with the Chase web connect data other than the amount.

I am at a loss as to how to fix this issue and could really use some help. I have attached a screen-shot to show you an example of what I am talking about.

QuickBooks Desktop

Rose-A

Level 10

Hey there, Victor B.

I appreciate the details you've provided. Let me help you sort this out.

Based on the screenshot you've provided, you have a Renaming Rule that was set up, which is being recognized by QuickBooks. If the assigned name is incorrect, you need to simply edit the rule.

Here's how to modify a renaming rule:

From Banking menu, select Bank Feeds > Bank Feeds Center.
Select Rules in Bank Feeds window.
In the Rules List window, highlight the renaming rule you need to change.
From the Action column, select the drop-down and choose:
- Edit Rule: If you need to change details of the rule. Make the appropriate changes then click Save.
- Delete Rule: If you need to remove the rule. Click Yes when prompted to confirm if you want to delete the selected rule.

You can check out this article for more details: Use renaming rules for Bank Feeds.

However, if you'd like to go through this over the phone, you can call our dedicated team who will be happy to assist you. Our contact details can be found here along with our opening hours:

Go to: https://help.quickbooks.intuit.com/en_US/contact.
Choose your QuickBooks Product.
Select your QuickBooks version.
On the Contact Us page, click a topic.
Click on the Get Phone Number button to see the support number.

Feel free to get back in touch with me if you have other concerns about QuickBooks. I'd love to help.

Victor BAuthor

Thank you for your reply and offer to help. But there may be an issue with your advice that you may have not thought of. The problem is not the rule. The problem is that I have 239 transactions all listed under the same exact name with no other unique identifiers. So yes, I can go in and delete or modify the original rule that caused the problem, but the first time I associate one of these 239 transactions listed as "Remote Online Deposit" with a new customer, QB will then automatically create a new rule and just reassign all remaining 238 transactions to the new rule. So each time, I will have to go back and delete the new rule for each deposit. Am I wrong about this?

A

AldrinS

Level 4

The title of my question is, how, "How to fix improperly auto assigned data in bank feeds?" So far, no one as actually addressed this issue. Rasa-LilaM did tell me how to Match these transactions with existing transactions, but not how to FIX the imported transactions. Just in case you are having difficulty seeing the difference, let me give you a visual example to guide you.

Let's say my question was "How to fix my car (QB) that won't run because the gas station (Chase) attendant (web-connect file) put diesel (improperly formatted data) in it instead of gasoline." To this question, Rasa-LilaM answered; "Leave the diesel in the tank, get out of the car and start pushing it yourself" (Do all your data entry manually).

So yes, Rasa-LilaM's answer gets me down the road, but only at the expense of a ton of EXTRA work that that does not even fix the issue of the corrupt data. Bank feeds serve the same purpose as a car; they are to help us move faster and more efficiently then walking by foot or entering data manually. That is the whole reason for their existence. Having to enter all the data manually to try to feed the improperly formatted data, is the same exact thing as pushing your car down the road to get to the store. Yes, you get to the store eventually, but it would have been a lot easier if you just left the car at home instead of pushing it. Why in the world would I input all the data manually to try to fix the bad data from Chase? LOL! Makes absolutely no sense at all. It is not a solution or troubleshooting. ROFL!

As far as issuing a trouble ticket; I don't have to because I am not the first person to have this problem. Chase is one of the largest banks in the world and millions of people use their mobile deposit system every (I have proof of this if you need it). Many people have gone to Inuit for help with this issue and Intuit support has one answer; "Go to Chase Bank and tell them about the problem with THEIR data reporting". I have been down this road so many times before and it is nothing but a game of "Pass the Buck". Intuit says it is the Banks problem to fix and the Bank says it is Intuit's problem to fix. They play ping-pong with their customers until the customer finally gives up.

Here is the solution. Inuit needs to send it's engineers of to talk with the Chase database administrators and tell them how to properly format their data feeds to work with QB. It really is that simple. Inuit know what QB needs, so it is their responsibility to make sure banks that offer QB support knows how to give what they claim to offer. If I had my way, Intuit would sue every bank for "Failure to Render Advertised Services). In the case of Chase, we are not talking about a simple mistake here. We are talking about a complete lack of any effort what-so-ever to offer QB compatible data. But they are glad to charge $9.95 a month for their Quickbooks service that does not work.

Hi Victor B,

First and foremost, I want you to know that your voice matters and I completely agree with the solution that you provided. Your time is very valuable to me and the last thing I want you to deal with are problems like this.

This isn't the impression that I'd like for you to be left with. The updates and changes to QuickBooks are largely the results of feedback provided by users, just like yourself. That said, I'm making it my top priority that your feedback reaches our engineers and make them understand the urgency of this matter. After all, updates and changes to QuickBooks are largely the results of feedback provided by users.

Please don't hesitate to touch base with me here in the Community if there's anything else I can do for you.I assure you that I'll do my best to help you out.

Sign up

Login with SSO

Let's get you signed in

Login with SSO