Loading
HelpCommunityTraining Center

ArticlesAC: How to Fix Plaid Bank Connections That are no Longer Importing Bank Statements

Knowledge Article

AC: How to Fix Plaid Bank Connections That are no Longer Importing Bank Statements

This content outlines procedures for resolving issues with Plaid bank connections that fail to import bank statements. The primary solutions involve rotating Plaid access tokens if a dedicated Plaid user exists. If a dedicated user does not exist, one must be created, and the bank connections must be recreated using this new user. The text also provides steps for cleaning up invalid bank account connections and lists common reasons for import failures.

  • Apr 10, 2026
  • Knowledge

Title
AC: How to Fix Plaid Bank Connections That are no Longer Importing Bank Statements
Summary
This content outlines procedures for resolving issues with Plaid bank connections that fail to import bank statements. The primary solutions involve rotating Plaid access tokens if a dedicated Plaid user exists. If a dedicated user does not exist, one must be created, and the bank connections must be recreated using this new user. The text also provides steps for cleaning up invalid bank account connections and lists common reasons for import failures.
URL Name
AC-How-to-Fix-Plaid-Bank-Connections-That-are-no-Longer-Importing-Bank-Statements

Release Version
All Versions
Additional Notes
  • Creating Bank Account Connection without a Dedicated User is against Salesforce Best Practices for OAuth
  • Bank Connections that are created with a Dedicated Plaid User do not stop working very often if at all. Find out if the existing Bank Connections are still valid before attempting to recreate them. 
  • A significant number of End User Plaid issues are caused by not designating a Dedicated Plaid User and recreating the Bank Connections incorrectly when they stop working 
  • In many cases the Tokens must to be Rotated because there is or was a Password Issue with the Bank. If there is a Password Reset with the Bank reach out to your Administrator and request that the Dedicated Plaid User rotate the Tokens to prevent issues before they happen
  • Known reasons for not being able to Import Statements
    • Special Characters in API names
    • Imports must be done one at a time
    • Logged into the wrong Company
    • The import will fail with an error message if any of the statement lines have dates later than the statement date. If this happens, adjust the statement date and try again.
    • Cache, this can be tested in an Incognito window (with a User that has Permission to Perform the Task)
    • Bank Account does not have Transactions
    • Fields on the Bank Connection are Blank
    • There was a previous Statement that was deleted and uploaded again
    • Bank account must belong to the current company
    • Bank account must be linked to a bank account connection record
    • The selected bank account and its associated bank account connection must share the same currency
    • If no statements already exist for the bank account, the start date and the opening balance must be defined on the associated bank account connection
    • Plaid Tokens need to be refreshed
    • Bank Account Credentials do not work
    • Open Bank Connections are not Successful and do not count
       
Procedure

 

Option 1.  Plaid Dedicated User (i.e. the Username is not Used for any other Task) Exists 

 

Follow these steps if a Plaid Dedicated User is already set up:

  1. Contact your System Administrator (if there is one) and ask them to log in as the dedicated user to rotate the Plaid access tokens.
  2. Attempt to Import the Statements again.
  3. If the issue persists (do not attempt to recreate the Bank Connection), reach out to the Support Team. Request that the Product Team determine if any of the the Bank Connections are valid. Let Support know how long the Bank Connections were working before this incident and who they have a history of working for

 

Option 2. No Plaid Dedicated User Exists
 

If a Plaid Dedicated User has not been created, follow these steps in a Refreshed Sandbox:

  1. Ask the System Administrator (if there is one) to follow the steps in the Setting up the Plaid Bank Integration document to create the Plaid Dedicated User
  2. Contact Support, request that the Product Team determine if any of the Bank Connections are valid. Let Support know how long the Bank Connections were working before this incident and who they were working for. Regardless, if the Bank Connections are still valid, they must be recreated with the Plaid Dedicated User to prevent further issues
  3. Clean up the invalid Bank Account Connections by applying the steps below:
    1. Click the Remove Bank Connection Button on each non-working Bank Account Connection (BAC) and then mark the Obsolete Check Box. 
    2. Delete the Bank Connections Log Details and the Bank Connections Log that are associated with any invalid Bank Connections
  4. Recreate the Bank Connections with the Plaid Dedicated User per the Creating Plaid Bank Connections Documentation
Objective
  • To fix Plaid Bank Connections that are no longer Importing Bank Statements
IntegrationsProfessional Services CloudCustomer Success CloudFinancial Management CloudCash & Bank Management
Was this article helpful?
00
Upload Files
Recommendations
No results for undefined
Loading
Knowledge:AC: How to Fix Plaid Bank Connections That are no Longer Importing Bank Statements