YNAB Status

Welcome, YNABer!

Here’s what we know right now about any financial institutions with widespread issues (learn more about these Watchlist Institutions). If your bank lands on this page, there’s no need to hug the stress pillow. Just subscribe for updates and you’ll be the first to know!

Truist - Inflow/Outflow Swapped
Incident Report for YNAB
Resolved
After monitoring Truist’s connection for the past few days, we’ve confirmed that the issue is resolved!
Posted Feb 02, 2023 - 16:12 UTC
Monitoring
Our Direct Import provider has resolved the issue with Truist transactions! 🎉 Transactions dated on or after today should import correctly, however if you are still running into issues, please remove and re-add the connection. We’ll continue to monitor the situation for the next few days, but if you need more help, write in to [email protected]!
Posted Jan 31, 2023 - 04:18 UTC
Identified
We've identified the cause of the issue with Truist tranactions importing incorrectly, and we're working with our Direct Import provider on the next steps. We'll continue to keep you updated as things progress! Thank you for your continued patience!
Posted Jan 27, 2023 - 00:15 UTC
Update
We're still investigating this issue with our Direct Import provider and we'll continue to keep you updated as things progress. Don't forget—if this is wreaking too much havoc on your budget, you can unlink the affected account(s) and use our other transaction entry methods to keep your budget up to date.
Posted Jan 10, 2023 - 20:02 UTC
Investigating
We are investigating a spike in transactions importing incorrectly with Truist. We're working with our Direct Import provider to learn more, and we'll post updates here as we have them. In the meantime, switch the amounts for any transactions that have already imported with inflows/outflows swapped. If this is wreaking too much havoc on your budget, you may want to unlink the affected account(s) and use our other transaction entry methods to keep your budget up to date!
Posted Dec 28, 2022 - 14:09 UTC
This incident affected: Direct Import Providers (MX).