Bank Feeds Now Enforce MFA Token Lifecycle — Reauthentication Required When Tokens Expire

What changed

Bank Feeds connections to financial institutions that require multifactor authentication (MFA, 2FA, or one-time passwords) now actively track the validity state of the MFA token. When the token expires or is invalidated — for example, after a fixed number of login sessions or transactions — the daily bank data import stops until the connection is reauthenticated.

Two new UI surfaces expose the problem:

• Banking Import History page — shows which financial institution connections need reauthentication. Navigate to Transactions > Bank > Banking Import History.
• Match Bank Data page — displays an MFA warning banner for the affected account, with an inline option to renew the connection.

A third path exists for bulk or proactive management: open the institution's format profile, go to Connectivity Configuration > Connections, and click the Refresh icon in the Update MFA column.

Connector coverage

This behavior applies to every supported bank-feeds connector:

• Yodlee — U.S. and Canada
• MX — U.S. and Canada
• Salt Edge (PSD2 / regulated) — Europe
• Salt Edge (non-PSD2) — Europe
• Salt Edge (other countries) — rest of world

What to do

1. Monitor Transactions > Bank > Banking Import History regularly for connections flagged as needing reauthentication. Consider adding this check to your daily or weekly operations runbook.
2. When an MFA warning banner appears on the Match Bank Data page, click through to renew the connection immediately.
3. For institutions whose tokens expire frequently, proactively refresh the MFA token via the format profile's Connectivity Configuration > Connections > Update MFA column before import failures occur.
4. After saving any reauthentication, verify that a new bank data retrieval and import cycle kicks off automatically — no manual import trigger should be needed.

Gaps in the source

Oracle's documentation does not specify which release introduced this behavior, nor does it clarify whether the MFA token status is exposed via SuiteScript records, a saved search data source, or any REST/SOAP endpoint. If you need to automate monitoring of MFA expiry (e.g., sending Slack alerts when a connection goes stale), you will need to test whether the Banking Import History data is queryable through N/search or N/query — this is not confirmed in the current docs.