You need a new Direct Import Provider
After weeks of issues with your Direct Import Provider being able to import from some of the largest banks I'm putting forth the idea that it's time to reconsider your Import Provider. In short, they are failing to deliver on the product as intended.
Similarly, YNAB is failing to deliver on their product as advertised. While bank importing has been around for years, your current implementation is largely a failure and you have to either, reconfigure your pricing to reflect a reduction in services available for reconsider the relationship you have with the Direct Importers.
Considering that Direct Import is a rather common offering, advertising this and failing to deliver is an indication that, as a company, you have your attention elsewhere or lack the resources to address a core functionality. This doesn't look good.
This is beyond annoying. If you simply removed the expectation that Direct Import could happen it would be far simpler for the customer to come to terms with that and act accordingly.
We're closing out Bank Importing threads in the forum to make sure these issues are better resolved.
Replies in this thread have been turned off, but you can still suggest new banks (even international banks) in the app, if you haven’t already!
If you’re having trouble connecting to a bank in the US or Canada, please fill out this form and our Direct Import team will help you get things back up and running!
Hi Cadet Blue Nomad ! I'm moving this over to our Bank Importing section for a better fit.
When we launched the online version of YNAB, we had one Direct Import partner. We have since added two more in order to provide more stable support for a wider range of financial institutions, improve connection stability, and improve response times.
I'm sorry to hear you've been having connection troubles. There are many moving parts with direct import and any little (or big!) change from the banks can cause disruptions in the connection. If you'd like us to look closer at a particular connection of yours, please let me know.
While direct import is a really amazing feature (especially when it's working!), we feel our method is strong enough that your budget can still work very well without it. In fact, lots of YNABers don't use direct import at all and they're still able to have and use an awesome budget.
That said, we are actively working to make this less of a pain point for users (and for us too, since we're all YNABers ourselves!). We're constantly exploring options with existing and new data providers to help with that. Direct import is something we do want to provide as a dependable feature!
Let me know if you have any questions!
My direct import has been solid for a very long time. I currently have capital one requesting a code on a regular basis but that is capital one's issue and not ynab's. Seriously all the direct import whiners should move to the service they think has that great direct import capability with no problems. Oh yeah...that's right, i think i know why they'd rather just whine on here.
Herman You are incorrect. I'm trying out two competing products to YNAB and neither are experiencing any import issues. The two other products are from larger companies which might be one reason however I agree with Cadet Blue Nomad that something needs to change. I've been singing praises about YNAB for 5+ years but the import issues alone will drive me to a competing platform unless things get better.
It has been almost a month since my institution was able to sync which has effectively made YNAB worthless. I would hope that YNAB could offer some sort of reimbursement to offset the fact that we just paid them for nothing. Also, why is there no way to import transactions manually? This is one of the simplest solutions to have as a backup when issues come up and it was in the original app version but not the online version. I have had to spend almost 10 hours this month manually adding every transaction so I can actually see where my budget is at. I love the product but there is something seriously wrong with the import providers because either you or they are in breach of SLA contracts. You better hurry up before this turns into a class actionable issue.