Manage Connections

You can use the Manage Connections feature to set up new Direct Import connections or link a new account under an existing connection. It's also a place to help troubleshoot pesky connection issues or remove connections that are no longer needed. 

In This Article


Remove a Connection

1
Click your budget name (top-left) and choose Manage Connections from the drop-down menu.
2
Remove the connection to the financial institution giving you trouble. You'll need to confirm you'd like to disconnect the account(s), and then select Done (or Cancel). 

Removing a connection will not impact your transaction history in your account registers, and it doesn't require you to delete any accounts. It'll disconnect all accounts you have connected to that financial institution, but getting those reconnected is easy peasy!

Once you've removed the connection, it's time to create a fresh one and relink your accounts! However, we strongly recommend reconciling your accounts before adding a new connection. It's possible to receive different data than what came through the previous connection type, and since this data looks brand new to YNAB, duplicate transactions from the past 31 days may import.

1
Hover over an account you'd like to link, click the edit icon to the left, and choose Link Account in the window that pops up
2

Choose Add New Connection, search for your financial institution, and follow the prompts.

3
Once that account is connected, make sure to relink any other accounts associated with these credentials, too. You'll do so by repeating step one but when you get to step two, select the connection you just created!

Each connection represents a unique set of login credentials for a financial institution. If you have more accounts you'd like to add and they're under a different set of credentials, you'll need to add a new connection.

Pro-Tip: Always make sure you're using the primary account holder's credentials for the best import experience!

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.