Overview

This article is a reference guide for Bank Direct Connect (BDC) questions, troubleshooting, and bank management tasks. It covers frequently asked questions about BDC behavior and configuration, provider-specific troubleshooting steps for Plaid, Yodlee, Salt Edge, and Financial File Import, and a full walkthrough of how to delete a bank and re-add it, deregister an aggregation provider, and migrate from one provider to another.

In this article:

• Bank Direct Connect FAQ
• Provider Specific Troubleshooting
  • Plaid
  • Yodlee
  • Salt Edge
  • Financial File Import: removing a Financial File Import entry from the FIA picklist
• Managing Bank Connections and Provider Migrations
  • Remove and re-add bank: overview
  • What happens when you remove a bank
  • How to remove a bank
  • Re-adding a bank after removing
  • How to deregister an aggregation provider
  • Migrating from one provider to another
• Bank Transaction Download Error Logs

Bank Direct Connect FAQ

Is there a way to effectively reset the connection and start fresh? Is that a better option than troubleshooting an existing setup?

In many cases, starting fresh is a perfectly valid approach. To do so, delete your current connections and reconnect from scratch. If you run into issues during that process, submit a support case and the team can assist you.

Is there a maximum number of bank accounts you can have connected?

No, there is no set maximum number of accounts that can be connected through BDC.

Can you update the name of a connected bank account?

No. The connection name comes directly from your bank and is passed through to Accounting Seed as-is. It cannot be manually edited.

Can BDC be set up in a sandbox environment for testing?

Yes, BDC can be configured in a sandbox. After refreshing or creating your sandbox, check the Remote Site Settings in Salesforce Setup and confirm that the BDC-related remote site entries are active.

If you would like to test Plaid in sandbox mode, submit a case and grant admin access for one week so Accounting Seed Support can enable this for you.

Salt Edge and Yodlee can be self-configured in a sandbox:

Step 1: Activate Remote Site Settings

1. Go to Setup > Quick Find > Remote Site Settings.
2. Scroll to the Remote Site Name: Salt_Edge_API.
3. Click Edit, select the Active checkbox, then click Save.

Step 2: Activate Trusted URLs

1. Go to Setup > Quick Find > Trusted URLs.
2. Locate the SaltEdge API entry.
3. Click Edit, select the Active checkbox, then click Save.

Step 3: Verify Permissions

Confirm BDC users have one of these permission sets:

• AS Full Admin
• Accounting Manager
• Cash Out & Banking (or confirm the custom permission "Import BDC Transactions" is assigned for custom permission sets)

Step 4: Register Yodlee or Salt Edge as Provider

1. Go to Accounting Home > Create Entries > Banking > Bank Direct Connect > Bank Settings tab.
2. Click Manage Providers.
3. Swipe right to enable Salt Edge, click Save, then click Yes.

What should you do if your bank returns an error saying the institution is not supported? Can you manually add the information?

Yes. If your bank is not supported by BDC's aggregation providers, you can still import transactions manually using a file in OFX or QFX format.

What criteria does BDC use when matching a transaction to a source record?

BDC matches on two fields: amount (must be an exact match) and date (the transaction date must fall within a defined +/- day range of the date on the source object). If more than one match is found, BDC displays all matching records so you can select the correct one. Vendor/payee information may or may not be included on the bank transaction, so it is not used as a matching criterion.

Is there a way to create Cash Disbursements directly from BDC, for example recurring automatic bank debits that already have recurring payables set up?

Yes. You can use Bank Rules or the Pre-Populate Account option to assign a payee and GL Account to transactions that meet certain criteria. Once assigned, you can use the Add action to create the Cash Disbursement directly from the BDC interface, without needing to navigate elsewhere first. Setting up rules for your recurring debits upfront significantly streamlines this workflow.

Is there a way to automatically post Cash Disbursements created through BDC?

Yes. The easiest method is to use the Automated Jobs feature and configure a scheduled Post job. You can set it to post all Cash Disbursements in Approved status, and schedule it to run multiple times per day.

Why is there a statement ending date but no statement start date in Bank Reconciliation?

This was an intentional design decision. A start date was found to exclude uncleared transactions that still need to be cleared in the current reconciliation, which caused reconciliation issues. By removing the start date, all uncleared records are included in the Bank Reconciliation so they can be properly cleared.

If you have a large backlog of old uncleared transactions, you can do a "catch-all" Bank Reconciliation record first so they are excluded from your active reconciliations going forward. For more information, submit a support case or search the Knowledge Base.

Why did I see duplicate Bank Transactions from my Plaid-connected bank?

In earlier releases, a Plaid-connected bank could occasionally show the same transaction twice, once as originally matched or added, and again days later as a new, separate Bank Transaction with a different provider ID. This was caused by a limitation in the way Plaid's API worked with Bank Direct Connect which had no way to tell that a transaction had simply changed status rather than being genuinely new.

As of Winter '27, Bank Direct Connect uses Plaid's updated Sync API, which explicitly reports when a transaction has been modified or removed instead of reporting it as newly added — preventing this type of duplicate going forward. If you still see an unexpected duplicate transaction from a Plaid connection after upgrading, submit a support case so the team can investigate. Ensure that Allow Activities and Track Field History is selected on the Bank Transactions object. See configuration changes for details on how to do this.

Note: This applies to Plaid connections only. If you're seeing duplicate transactions through Yodlee or Salt Edge, see the Provider Specific Troubleshooting section below.

Provider Specific Troubleshooting

Plaid

A Plaid Connection error message may appear on the Bank Transactions tab or the Bank Settings tab, either at the top of the page or in the FIA Status column.

Steps to resolve this:

1. Click Refresh Credentials. This launches the Plaid wizard.
2. Enter your username and password, then click Submit.
3. Click Continue. The Success message displays and Bank Settings refreshes.

Error: This Currency is not supported for (bank name): (currency name). Please add the currency

Description: This error appears when you try to connect to a bank account that uses a non-default currency that has not been added to your org.

Steps to resolve this:

1. Click the Gear icon and select Setup.
2. Search for Company Information in Quick Find, then click Company Information.
3. Click Currency Setup, then click New.
4. Select the Currency Type from the drop-down list.
5. Enter the Conversion Rate from your corporate currency to the new currency.
6. Verify the Decimal Places field (0-6 digits). This overrides the decimal places setting on all currency fields for users with this currency.
7. Click Save.

Error: You cannot connect to foreign bank without multi-currency enabled. Please contact your Accounting Seed Customer Success Manager to enable multi-currency.

This error appears when you attempt to connect to a bank with a foreign currency and multi-currency is not enabled in your org.

To resolve this, contact your Accounting Seed Customer Engagement Manager to enable multi-currency.

Yodlee

Error: "Action Required - Additional user authentication information is needed" shown on FIA Status on the Bank Settings tab.

Or warning displayed on Bank Transactions tab: "Financial Institution Account failed to connect, additional action is required. Please navigate to the Bank Settings tab."

Description: This is displayed when a Financial Institution Account cannot be updated or if it fails to connect.

Reasons this is shown:

• Credentials have expired and need to be refreshed
• A security question or token has expired
• A technical issue with Yodlee, or an incorrect username/password

Steps to resolve this error:

1. Go to the Bank Settings tab.
2. Select the Financial Institution showing the message from the drop-down list.
3. Click Refresh Connection to update your MFA (multi-factor authentication).
4. Confirm the status changes to "Connection successful - no action required."
5. Return to the Bank Transactions tab and click Update All to download transactions.

Note: After your current authentication expires, click Refresh again to clear the message and download Bank Transactions.

Error: "Action Required - FIA failed. For more information, review our Knowledge Base" shown on FIA Status on the Bank Settings tab.

Or warning displayed on the Bank Transactions tab: "Financial Institution Account failed to connect, additional action is required. Please navigate to the Bank Settings tab."

Description: This message appears due to invalid credentials or a technical issue with Yodlee.

Steps to resolve this error:

1. Log in to your bank's website and confirm or update your credentials.
2. Return to Accounting Seed and go to the Bank Settings tab.
3. Select the Financial Institution showing the message from the drop-down list.
4. Click Refresh Credentials to update your credentials and MFA.
5. Confirm the status changes to "Connection successful - no action required."
6. Return to the Bank Transactions tab and click Update All to download transactions.

Still seeing the error? If "Connection successful - no action required" does not display after updating credentials in Yodlee's Fastlink, contact Accounting Seed Support.

Error: "Bank Update Failed. Connection_1 INVALID_ACCOUNT_ID: one or more of the account IDs is invalid."

Note: The number following "Connection_" is a system-generated identifier and varies by org. Match on the INVALID_ACCOUNT_ID portion of the message.

Description: This error comes from Yodlee, the bank aggregation provider, and means one of the account IDs Yodlee has on file for the connection is no longer valid. This typically happens when an account is closed or deactivated at the bank level, but the connection in Accounting Seed still references it. Because Yodlee ties all accounts under one connection together, resolving this requires deleting and re-adding the entire Financial Institution connection, even if only one account under it is affected.

Important: Before you begin, note the Ledger and Bank GL Account currently mapped to each account under this Financial Institution. Deleting the connection makes its existing mapping inactive, and a new mapping is required after you reconnect.

Steps to resolve this error:

1. Go to the Bank Settings tab.
2. Select the Financial Institution showing the error from the drop-down list, then click Delete. Previously downloaded Bank Transactions are not affected.
3. Click New to re-add the Financial Institution. Have your online banking username and password ready to complete the credential entry through Yodlee's FastLink window. Only accounts that are still active at your bank appear for selection.
4. Set the Initial Start Date. Bank Direct Connect pulls transactions from approximately 14 days prior to this date, so set it to the day after your last successfully downloaded transaction to avoid a gap or duplicate transactions.
5. Select the Ledger and Bank GL Account for each account, using what you noted before starting, then click Save. See Bank Direct Connect - Bank Settings for full details on this mapping step.
6. Go to the Bank Transactions tab and click Update All to confirm transactions are downloading.

For a full walkthrough of this process, see the Remove and Re-Add Bank section of this article.

Note: If you have Bank Rules scoped specifically to this Financial Institution (rather than "All Financial Institution Accounts"), update those rules to point to the newly re-added Financial Institution.

Still seeing the error? If the error persists after re-adding your Financial Institution, contact Accounting Seed Support.

Error: "Refused to connect" error when refreshing a Yodlee connection

The popup window used to refresh a Yodlee connection displays a "refused to connect" error and does not load.

Description: Clickjack Protection is a Salesforce security setting that blocks pages, including popups, from loading inside frames from other sites. This error appears when Clickjack Protection in Session Settings is configured too strictly, which also blocks Accounting Seed's own popup windows, such as the Yodlee connection refresh window.

Note: This fix requires Salesforce Administrator access to Setup. If you do not have access, ask your Salesforce Administrator to complete these steps.

Important: Disabling Clickjack Protection is an org-wide setting. It does not apply only to the Yodlee connection window. Turning it off removes clickjack protection for all customer Visualforce pages in your org. Confirm with your security or IT team before making this change, and consider re-enabling it if a narrower fix becomes available.

Steps to resolve this error:

1. Click the Gear icon and select Setup.
2. Search for Session Settings in Quick Find, then click it.
3. Scroll to the Clickjack Protection section.
4. Deselect both of the following checkboxes:
   1. Enable clickjack protection for customer Visualforce pages with standard headers
   2. Enable clickjack protection for customer Visualforce pages with headers disabled
5. Click Save.
6. Return to the Bank Settings tab and click Refresh Connection again to confirm the popup loads successfully.

Still seeing the error? If the popup does not load after completing these steps, confirm your browser is not blocking popups for this site. If the issue persists, contact Accounting Seed Support.

Salt Edge

Issue: Bank transactions missing from BDC even after Salt Edge shows a successful refresh

Description: Salt Edge may not have aggregated the transactions when the Update All button was clicked to import bank transactions. Update All is also limited to the last 14 days and may miss transactions if aggregation timing is delayed.

Steps to resolve:

1. Go to Accounting Home > Setup > Automated Jobs.
2. Select Scheduled Bank Download and click Run Now.
3. This force-imports all transactions back to the Initial Start Date and checks for duplicates.
4. If transactions are still missing after this step, contact Accounting Seed Support.

Issue: Update All only pulls data once per day / no transactions on first import

Description: Salt Edge limits actual data refreshes to once per day for compliance. This is outside Accounting Seed's control. The very first import always behaves like the Download button and pulls from the Initial Start Date, which can take many hours due to Salt Edge API rate limits (30 GET calls per minute, 100 transactions per batch).

Steps to resolve:

1. For the first import, allow several hours for the job to complete. This is expected behavior for large transaction volumes.
2. To trigger an on-demand refresh outside the daily cycle, go to Accounting Home > Setup > Automated Jobs > Scheduled Bank Download > Run Now.
3. Use the Download button (not Update All) for historical imports or to recover missed transactions.

Note: Sandboxes have tighter processing limits and may behave differently from production orgs.

Tip: Update All is designed for incremental daily syncs. For initial setup or catching up on missed transactions, always use the Scheduled Bank Download job.

Error: Initial start date must be less than today's date

Description: The Initial Start Date on the Bank Settings tab cannot be set to a future date. The system requires it to be today or in the past.

Steps to resolve:

1. Set the Initial Start Date on the Bank Settings tab to your actual go-live date (today or a past date).
2. The system automatically pulls up to two weeks of prior transactions from that date.
3. Any early or unwanted transactions can be deleted or ignored during reconciliation.

Error 403 when attempting to Refresh Connection or Refresh Credentials. Bank feed has stopped updating.

Description: The underlying bank connection has returned to an "Action Required" state. Additional user authentication is needed to re-establish the feed.

Steps to resolve:

1. Go to the Bank Settings tab.
2. Locate the Financial Institution showing the error.
3. Click Refresh Credentials.
4. Complete the re-authentication flow using your online banking credentials.
5. Confirm the status returns to "Connection successful - no action required."

Issue: Bank Transaction date in BDC is coming from the "made_on" field instead of the "posting_date" field.

This is expected behavior and is by design.

Reasoning: The system uses the made_on (transaction date) because it more closely matches source record dates used in BDC matching logic. The posting date can vary significantly and reduces match accuracy.

The system applies this date hierarchy consistently across all providers:

1. Date field, if this is provided
2. Transaction Date / Made Date, if Date is not provided
3. Posting Date, only if all above are blank

Issue: Description field on Bank Transactions is blank after connecting with Salt Edge, making it impossible to match transactions to invoices or cash receipts.

Description: Not all bank data fields are mapped to standard Bank Transaction fields. Additional data, including invoice numbers and other reference fields, is available in the Payload field on the Bank Transaction record as JSON.

Steps to resolve:

1. Open the Bank Transaction record and locate the Payload field. If you do not see this field, add it to the bank transaction page layout: Setup > Object Manager > Bank transaction > Page Layout > drag and drop the field onto the layout > Save.
2. Find the relevant data in the JSON (for example: "additional":"FACTURE 400798").
3. Build a pre-save Flow to parse the Payload field and write the desired value to a custom field on the Bank Transaction record.

Important: The Flow must run pre-save. Accounting Seed fields lock on save and cannot be updated afterward.

Issue: Scheduled bank download job runs but imports no new transactions, but running on demand was successful

Description: This is not related to how the job is run, but rather the unpredictability of Salt Edge's aggregation timing. Transactions are only imported when three conditions are all met: Salt Edge has aggregated the transaction, the transaction is in a Posted status, and it has not already been imported.

Salt Edge's aggregation runs at unpredictable intervals. A transaction dated May 27 may not be aggregated until May 28, regardless of when the import job fires.

Steps to resolve:

1. Confirm Salt Edge has had time to aggregate. Aggregation typically runs within 24-36 hours of the transaction date, but timing varies.
2. If transactions are still missing, use the Download button to manually force-import all transactions back to the Initial Start Date.
3. If the issue persists across multiple days, contact Accounting Seed Support.

Issue: After connecting successfully, Update All triggers long-running Apex jobs with zero Bank Transactions created.

Error: "Too many queueable jobs added to the queue: 2."

Description: Large transaction volumes (tens of thousands of records) can take many hours to import due to Salt Edge API rate limits (30 GET calls per minute, 100 transactions per batch).

Note: The "Too many queueable jobs" error is more likely to occur in Sandbox environments, which have tighter Apex limits than production.

Steps to resolve:

1. Use the Download button instead of Update All for the initial import.
2. Allow several hours for large imports to complete. This is expected behavior.
3. Avoid running large initial imports in a Sandbox environment where possible.
4. If you see the "Too many queueable jobs" error in production, contact Accounting Seed Support.

Financial File Import

Remove Financial File Import Entry from the FIA Picklist

If you used Financial File Import to bring bank transactions into Accounting Seed, that import source appears as a picklist option in the Financial Institution Account (FIA) drop-down on the Unmatched Bank Transactions screen. To remove it, deactivate the associated GL Account Mapping (GLAM) record.

Step 1: Create the GL Account Mappings Tab (if it doesn't exist)

1. From the App Launcher, search for "Mapping" to check whether the GL Account Mappings tab already exists. If it does, skip to Step 2.
2. If it does not exist: from Setup, enter Tabs in the Quick Find box and click Custom Tabs.
3. Click New.
4. In the Object picklist, select GL Account Mappings and choose any tab style.
5. Click Next, Next again, then Save.

Step 2: Add the Inactive Field to the GLAM Page Layout

1. From Setup > Object Manager, search for and click GL Account Mapping.
2. In the left pane, click Page Layouts and select the layout in use.
3. Drag the Inactive field onto the page layout.
4. Click Save.

Step 3: Create a List View for Financial File Imports

1. From the App Launcher, navigate to the GL Account Mappings list view.
2. Click List View Controls, then New, and name the view (for example, Financial File Imports).
3. Change the filter scope to All GL Account Mappings.
4. Add a filter: Source equals Financial File Import.
5. Click the Gear icon > Select Fields to Display and add: Account Name, Financial Institution, Source, Inactive, GL Account, Ledger (and any other columns useful to your org).
6. Click Save.

Step 4: Deactivate the GLAM Record

1. From the list view, locate the GLAM record associated with the picklist value you want to remove.
2. Click on the record to open it, then click Edit.
3. Select the Inactive checkbox.
4. Click Save.

The Financial File Import value no longer appears in the BDC Financial Institution Account picklist.

Managing Bank Connections and Provider Migrations

Remove and re-add bank: overview

There are several situations where you may need to remove or delete a bank from Bank Direct Connect (BDC):

• A bank account is no longer active or needed for reconciliation
• You need to migrate from one aggregation provider to another (for example, Yodlee to Plaid, or Plaid to Salt Edge)
• A connection is broken and cannot be repaired through credential refresh alone
• You want to reset a Financial Institution Account (FIA) to pull extended historical transactions

Important: Deleting a bank from BDC does not delete previously downloaded Bank Transaction records. Those records are retained in Salesforce and remain accessible on the All Bank Transactions tab.

What happens when you remove a bank

Before deleting, review the following impacts:

What Is Affected	What Happens
Financial Institution Account (FIA)	Disconnected from Accounting Seed
GL Account Mapping	Deactivated and no longer visible on the Bank Settings page
Previously downloaded Bank Transactions	Retained in Salesforce, not deleted
Unmatched Bank Transactions	Remain on the Unmatched tab and can still be processed
Bank Rules scoped to the deleted bank	Must be manually updated after re-adding the bank
Bank Rules set to "All Financial Institution Accounts"	Not affected

Note: If you delete a bank and re-add it, the GL Account Mapping needs to be reconfigured. Any Bank Rules scoped to that specific bank (rather than "All Financial Institution Accounts") also need to be updated to include the re-added bank.

How to remove a bank

1. Navigate to Accounting Home and click the Create Entries tab. Under the Banking menu, click Bank Direct Connect.
2. Click the Bank Settings tab.
3. From the Select Aggregation Provider drop-down, select the provider for the bank you want to delete (Plaid, Yodlee, or Salt Edge).
4. From the Select Financial Institution drop-down, select the bank you want to remove.
5. Click Delete.
6. Confirm the deletion when prompted.

Note: After deletion, review your Bank Rules. Any rules configured for that specific bank need to be updated when the bank is re-added.

Re-adding a bank after removing

You can re-add a bank at any time after deletion. Keep the following in mind:

• GL Account Mapping must be reconfigured. Select the appropriate Ledger and Bank GL Account for each FIA.
• Initial Start Date: set this carefully to control how far back transactions are downloaded. BDC typically begins importing transactions 14 days prior to the Initial Start Date.
• Bank Rules: any rules previously scoped to the deleted bank must be updated to include the newly re-added bank.
• Duplicate Transactions: transactions already downloaded before deletion are not re-imported (duplicate Bank Transaction IDs are skipped). It is good practice to review the All Bank Transactions tab after reconnecting.

For full setup steps, refer to the Bank Direct Connect - Bank Settings article.

How to deregister an aggregation provider

Deregistering a provider is a more significant action than deleting a single bank. It disconnects all Financial Institution Accounts associated with that provider and deactivates all related GL Account Mappings.

You may want to deregister a provider when:

• You are fully migrating to a new provider (for example, from Yodlee to Plaid)
• Your organization no longer uses a particular provider

Steps:

1. Navigate to Accounting Home > Create Entries > Banking > Bank Direct Connect.
2. Click the Bank Settings tab.
3. Click Manage Providers. The Manage Aggregation Providers dialog box displays.
4. Swipe the toggle to the left to deregister the desired provider.
5. Click Save, then click Yes to confirm.

Important: Once deregistered, all Financial Institutions and FIAs connected through that provider are disconnected, and their GL Account Mappings are deactivated. Previously downloaded Bank Transactions are retained in Salesforce.

Migrating from one provider to another

Migrating between providers is effectively a delete-and-re-add workflow. Follow the steps below to avoid duplicate transactions and data gaps.

Migrating from Yodlee to Plaid

1. Review the Last Refresh Date in Bank Settings for the Yodlee-connected FIA.
2. Do not map the same bank account to both Yodlee and Plaid simultaneously. This causes transactions to be downloaded twice.
3. Set the Initial Start Date for Plaid to the day after the Last Refresh Date from Yodlee.
4. Connect the bank through Plaid following the standard Bank Settings setup steps.
5. Once connected, click Download from the Bank Transactions tab (under Download Historical Transactions) to pull historical transactions for Plaid-linked FIAs.
6. Review the All Bank Transactions tab for any duplicates. If needed, create a custom tab for the Bank Transaction object to review records directly.

Note: Historical transactions greater than 30 days may take up to 24 hours to become available from Plaid.

Migrating from Plaid to Salt Edge

1. Review the Last Refresh Date in Bank Settings for the Plaid-connected FIA.
2. Do not map the same bank account to both Plaid and Salt Edge simultaneously.
3. Set the Initial Start Date for Salt Edge to the day after the Last Refresh Date from Plaid.
4. Connect the bank through Salt Edge following the standard Bank Settings setup steps.
5. Once connected, click Download to pull transactions. Salt Edge supports up to 365 days of historical transactions from the Initial Start Date.
6. Review downloaded transactions for duplicates before processing.

Note: Salt Edge is available for EMEA and United Kingdom customers only.

Bank Transaction Download Error Logs

Beginning with Spring '26, if an error occurs when using the Refresh or Update All buttons on the Bank Transactions tab, the error is logged and does not interrupt the download process for your other connected bank accounts.

Reviewing Errors

If you notice that transactions are missing or a connection issue is reported on the Bank Transactions tab after a Refresh or Update All:

1. Run the Exceptions Bank Transaction Download report in Salesforce. This report provides the specific error information needed to diagnose the issue.
2. Alternatively, check the related GL Account Mapping (GLAM) record for a task with the error description, such as a connection failure or invalid access token.
3. Share the error details with the Accounting Seed Support Team for further assistance.

Return to top