Yodlee Format Profile for New NetSuite Accounts

New customers do not receive the U.S. and Canada Accounts (Yodlee) format profile preinstalled. When available preinstalled profiles do not support a U.S. or Canadian financial institution, an administrator can manually create the Yodlee profile using the Bank Feeds SuiteApp standard connectivity plug-in and transaction parser. Existing installations before February 4, 2026 retain the profile.

What changed for the Yodlee format profile?

The U.S. and Canada Accounts (Yodlee) format profile is not preinstalled for new customers. This does not mean Yodlee connectivity is unavailable in every account.

The profile remains available in Bank Feeds SuiteApp versions installed before February 4, 2026. Administrators should therefore inspect the records in their own account rather than assume that an existing Yodlee profile has been removed or that every new Bank Feeds installation includes it.

If the available preinstalled format profiles do not support a U.S. or Canadian financial institution, NetSuite permits the creation of a Yodlee format profile. That manually created profile must use the standard connectivity plug-in and transaction parser from the Bank Feeds SuiteApp.

This is a specific path for the Yodlee profile. Custom format profiles that do not use the SuiteApp standard connectivity plug-ins and transaction parsers can cause errors during setup or upgrades.

Why do format profiles matter for bank feeds?

Financial institution records represent banks, credit card companies, or corporate card companies from which an account retrieves financial institution data. A financial institution record contains format profiles, which provide the settings needed for manual or automatic data import.

A format profile can be configured to import data for either of these uses:

• Bank reconciliation
• Employee expense reports

SuiteApp-provisioned financial institution and format profile records support direct connections to financial institutions for data retrieval. Their profile type, connectivity method, and transaction parser are preselected and read-only.

By contrast, when an administrator adds a format profile to a user-created financial institution record, NetSuite requires selections for the profile type, connectivity method, and transaction parser. The manual Yodlee path therefore requires deliberate use of the Bank Feeds SuiteApp standard connectivity plug-in and transaction parser.

For broader connectivity changes affecting the SuiteApp, review the Bank Feeds SuiteApp connectivity enhancements. Teams that also import statement files should separately evaluate the Auto Bank Statement Import SFTP configuration changes.

Which Bank Feeds records are preinstalled?

The Bank Feeds SuiteApp documentation identifies the following financial institution and format profile records. The Yodlee profile is the exception for new customers: it is not preinstalled for them.

Administrators can access the preinstalled records in Setup > Accounting > Financial Institution > List. Reviewing this list establishes whether the Yodlee profile is already present in the account and identifies the available preinstalled alternatives.

How should administrators handle a missing Yodlee profile?

Use the following sequence when setting up a U.S. or Canadian bank feed:

1. Confirm bank-feed authorization. Contact the financial institution to confirm that the bank or credit card account is authorized for a bank feed connection.
2. Review the available records. Go to Setup > Accounting > Financial Institution > List and identify the preinstalled profiles available in the account.
3. Use an appropriate preinstalled profile when one supports the institution. The U.S. and Canada Accounts (MX) profile is a preinstalled option for financial institutions in the United States and Canada.
4. Create the Yodlee profile only when needed. If the available preinstalled profiles do not support the U.S. or Canadian institution, manually create the Yodlee profile with the Bank Feeds SuiteApp standard connectivity plug-in and transaction parser.
5. Check the connection against the intended institution and account. Bank feeds support only certain bank or payment accounts, and connection reliability can vary by financial institution.

A role must have the Financial Institution Records permission at the Full level to create a financial institution record and an associated format profile. This permission should be confirmed before assigning manual profile setup to a role.

What configuration mistakes should be avoided?

Preinstalled Bank Feeds records participate in SuiteApp installation and upgrade processing. Record names and record pairing therefore matter when maintaining bank-feed setup.

• Do not rename preinstalled Bank Feeds records. The Bank Feeds SuiteApp uses the financial institution record name to apply required updates during installation and upgrades.
• Do not use “Bank Feeds” in the name of a custom financial institution record. NetSuite might skip required updates if a custom record includes that name, and installation or upgrade can fail.
• Do not use preinstalled Bank Feeds format profiles with custom financial institutions. Preinstalled profiles should be used only with their matching preinstalled Bank Feeds records. Otherwise, NetSuite might skip required updates and installation or upgrade can fail.
• Do not substitute arbitrary connectivity components for the Yodlee profile. The manual Yodlee profile uses the Bank Feeds SuiteApp standard connectivity plug-in and transaction parser.
• Do not assume every account type is supported. Loan, mortgage, and investment accounts are examples of unsupported account types for which bank feeds may not work as expected.

Not every financial institution connection works the same way, and the Bank Feeds SuiteApp cannot always access every institution reliably. A failed connection should be assessed in light of the institution’s authorization requirements, the account type, and the available profile options.

What should be checked after setup?

After selecting a preinstalled profile or creating the Yodlee profile, confirm that the configuration is being used for the intended financial institution and bank or payment account. The purpose of these SuiteApp components is to connect directly to financial institutions and retrieve bank data.

Format profiles support import for bank reconciliation or employee expense reporting, depending on the profile configuration. Keep the profile and connection decision distinct from later processing of imported financial data.

For related product changes, see the Match Bank Data experience and the Reconcile Account Statement page.

Who This Affects

• NetSuite administrators: Must determine whether the Yodlee profile is already available and create it only when the available preinstalled profiles do not support the U.S. or Canadian institution.
• Roles managing financial institution records: Need the Financial Institution Records permission at the Full level to create a financial institution record and associated format profile.
• Implementation teams: Should not assume that a new customer account contains a preinstalled Yodlee profile.
• Banking and finance teams: May follow a different initial setup path when a U.S. or Canadian institution requires Yodlee rather than an available preinstalled profile.
• Expense reporting teams: May use imported financial institution data through a format profile configured for employee expense reports.

Key Takeaways

• The U.S. and Canada Accounts (Yodlee) format profile is not preinstalled for new customers.
• The profile remains available in Bank Feeds SuiteApp versions installed before February 4, 2026.
• When available preinstalled profiles do not support a U.S. or Canadian institution, administrators can manually create the Yodlee profile.
• The manual Yodlee profile must use the Bank Feeds SuiteApp standard connectivity plug-in and transaction parser.
• Preinstalled Bank Feeds records should not be renamed or paired with custom financial institution records.