Time to update your Wells Fargo connection!!
We've done it! -- as part of the ExpensifyApproved! Banks program, we've upgraded our Wells Fargo card feed connection with a new API to provide a more reliable connection for our users! We will be completely removing the old Wells Fargo feed on December 6th, so please check out the instructions below on how to transition to the new connection soon.
Please note that the instructions provided below apply to individual users with personal Wells Fargo cards and companies importing their cards via direct bank connection. If your company cards are imported via a CDF or VCF feed no action is required on your end.
Important Step! Before deleting your old connection please make sure that all the transactions previously imported to your Expensify account are added to reports and submitted. When you delete a card, all unsubmitted expenses from that transaction feed will be deleted. Expenses that have been added to a submitted/closed report will remain in your account.
Personal Card Import
We encourage you to transition to the new Wells Fargo connection before the end of November to avoid any last-minute issues. This way, you can remove this task off your to-do list and enjoy your Thanksgiving holiday!
On the Expensify website navigate to Settings > Your Account > Credit Card Import > Import Card/Bank and choose the Wells Fargo connection. Make sure to start a new connection here as opposed to selecting "Fix":
Once successfully synced, make sure to delete your old Wells Fargo connection to avoid importing duplicate expenses. Just a quick tip here, before deleting your old connection please make sure that all the transactions previously imported to your Expensify account are added to reports and submitted. When you delete a card, all unsubmitted expenses from that transaction feed will be deleted. Expenses that have been added to a submitted/closed report will remain in your account.
Company Card Import
We encourage you to transition to the new Wells Fargo connection before the end of November, to avoid any last-minute issues. This way, you can remove this task off your to-do list and enjoy your Thanksgiving holiday!
The following steps can only be completed by a Domain Admin.
On the Expensify website navigate to Settings > Domain Control > Company Cards > Import Card/Bank and choose the Wells Fargo connection.
Make sure to start a new connection here as opposed to "Assign new cards" or selecting "Fix":
Once the integration is set up you can delete the old Wells Fargo connection to avoid importing duplicate expenses. Then assign the individual cards back to users accounts from the Company Cards page.
Just a quick tip here, before deleting your old connection please make sure that all the transactions previously imported to users Expensify accounts are added to reports and submitted. When a card is deleted, all unsubmitted expenses from that transaction feed will be deleted. Expenses that have been added to a submitted/closed report will remain in users' accounts.
Happy expensing!
Comments
-
Is anyone else having issues updating for the Corporate Card? When I try the Import Card/Bank on the Domain Control, it keeps adding the card as a personal card for me. I don't understand what is happening....
-
Hi @mhaisfield - Let me check on that real quick!
-
@Stevie LaFortune I would appreciate that! I just did the Chase version of the update for a different client and didn't have this issue.
-
@mhaisfield I really appreciate you taking the time to reach out here! We were able to locate the issue and have made the fix. Can you try connecting to the new Wells Fargo connection in the domain settings once more?
-
@Stevie LaFortune Thank you for that update! I'm glad the fix was that simple to locate, because it worked just fine this time. I thought I was going a little crazy there for a moment. :)
-
I've also tried to go through this process, and it adds all cards to my personal account even though I'm going through the Domain Control to add the company card. I just tried this multiple times, but no joy, @Stevie LaFortune I give up for now!
-
@Jake Don't give up - I'm sorry for the trouble with this. Can you refresh your browser and try once more? I would guess that the update didn't get to you since you've been in trying so hard to get it to work properly.
-
Thanks, @Stevie LaFortune ! That did the trick.
-
I updated our connection but now have open expense reports for transactions that have already been coded and synced to QBO. How do I delete those? Prior to updating the connection, I submitted all open reports. Thanks! @Stevie LaFortune
-
Hi @barrce01 - had you selected the transaction start date when assigning cards -
If not, go ahead and unassign those cards - that will remove the unsubmitted transactions that imported with the connection and reassign with the proper start date to avoid duplicates. -
@Stevie LaFortune thank you!!
-
I successfully added in all my checking/credit card accounts on WF and after verifying all transactions moved into reports or deleted, I deleted the old cards. However, I could not create a "new" card for my high yield savings account that also makes some business related payments sometimes....should I just retain the old card for that in Expensify?
-
Hi @My3r5 - I've done some looking on the surface and don't see a reason for this.
Since this is out of the scope of this thread let's work together on this via Concierge. We might need some personally identifiable information that we wouldn't want here.
Please email us at [email protected] so we can look into this. -
I clicked on Import Card/Bank and didn't see a link for Wells Fargo (New and Upgraded) but rather was prompted to log into my Wells Fargo account and check boxes next to credit cards I wanted to sync. My Company Cards page now looks the same as it did before. There is no old connection to delete. Am I missing something?
-
Hi @JustinSM, after clicking Import Card/Bank the Wells Fargo button should link you via the new connection but to be 100% sure, instead of clicking the button, start typing Wells Fargo in the search bar and it will display there. Go through the flow and a new connection should be added to your domain. Let us know if this doesn't happen and we'll be happy to troubleshoot further.
-
This is what I received when I clicked on Wells Fargo after typing it into the search bar.
Bad Request
Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit. -
Ted Harris Expensify Success Coach - Admin, Expensify Team, Expensify Student Ambassador Posts: 359 Expensify TeamHi @JustinSM - I've tested this on a few devices and as long as I'm correct in my understanding that all you're doing is clicking this:
...this sounds like a browser issue.
Are you blocking any pop-ups at all? Are you using any extensions which might be stopping this link from opening up? Try this is a Private/Incognito tab and let us know how that goes! -
It worked in a different browser. I completed everything the same way I did before. I can see there are two different Wells Fargos within the dropdown directly under Imported Cards but there is no way to delete one of them.
-
@JustinSM have you unassigned any cards that were assigned on the old Wells Fargo connection?
-
No. How would I do that? I only know how to unassign them employees. Can you look to see if everything is set up correct?
-
Jason Li Expensify Success Coach - Admin, Expensify Team, Expensify Student Ambassador Posts: 231 Expensify Team@JustinSM - to unassign a card, you'll need to navigate to Settings > Domains > [Domain Names] > Company Cards, and click on the blue settings cog (on the right hand side) to reveal the "Unassign" button.
Before you unassign anything, I would recommend that you ensure that users have submitted the appropriate card expenses, as any unsubmitted card expenses will actually disappear once you unassign that card. -
Got it. I'll then assign the cards again but can back date that assignment to pick up any charges. Is that correct?
-
Rachael Hopkins Expensify Success Coach - Admin, Expensify Team, Expensify Student Ambassador Posts: 904 Expensify TeamHi @JustinSM, that's right - you can assign as of a certain date, and it does not need to be the same for each card, so some could be 2 weeks, some 3 weeks if needed. -
Hi. I'm following the instructions but this isn't working. I connect via Wells Fargo (who send me an email saying I have established the connection) and I get sent back to Expensify inbox and when I go back to company card page I do not see any new cards, it looks exactly the same as before. I've tried this 4 times now. Can you help please?!
-
@RichardWhittow I have the same issue. reached out yesterday but haven't heard back.
-
@Stevie LaFortune , any time I follow this process to connect, instead of resulting in a completed connection, it sends me back to my inbox page, as @RichardWhittow above. Please advise.
-
@RichardWhittowcoltonshaw06 We are having the same issue with our Wells Fargo checking and savings accounts not showing up in the Expensify Imported Cards section, even though they are showing up as successfully connected from our Wells Fargo website account dashboard. Strange. We sent in a request for support today, Saturday.
-
@RichardWhittow @coltonshaw06 @NatashaC @klaario - I did do a bit of digging and see that this has been reported by just a couple of others as well. We have gotten those details to our banking engineers to dig into. I will post an update here just as soon as I have one. Once you've been able to establish the new connection, Wells Fargo will send the past 30 days of transactions, so no need to worry - you should be missing any transactions in the end once this is resolved.
-
I've added more details to a new post regarding updating card connections that you might find useful here -
Updating your Chase and Wells Fargo connections - don't worry if you missed the date!
-
@Stevie LaFortune Thank you for the update. Our concern is this removes our ability to view our spend real-time which reduces our effectiveness dramatically. a 30 day backdate does not solve our problem, unfortunately. what is the ETA on this and a viable workaround?
