Renew MFA-Blocked Bank Connections Directly from Match Bank Data

What changed

When a bank connection hits a multifactor authentication (MFA) error, subsequent imports stop. Previously, resolving this required navigating to the format profile's Connectivity Configuration subtab. NetSuite now surfaces an MFA warning banner directly on the Match Bank Data page (Transactions > Bank > Match Bank Data) that lets users renew the connection inline.

Scope

• Applies to bank connections where the most recent import produced an MFA error — including Bank Feeds connections and connections configured without a SuiteApp.
• Currently, the only trigger for the inline renew flow is the MFA warning banner on Match Bank Data. There is no API or scripted entry point documented for this workflow.

How the renewal flow works

1. Navigate to Transactions > Bank > Match Bank Data and select the affected account from the Account dropdown.
2. If the account's last import failed due to MFA, a warning banner appears.
3. If the banner contains a Renew connection link (visible only with the Financial Institution Records permission), clicking it opens a modal that mirrors the connectivity configuration flow from the format profile's Connectivity Configuration subtab.
4. If the connection does not support inline renewal, NetSuite displays a message — possibly with a link to the corresponding format profile — instead of the modal.
5. After completing authentication in the modal, clicking Initiate Import schedules a delayed import 1 hour in the future. If another delayed import was already scheduled within the past hour, no duplicate is created.
6. Clicking Close without Import preserves the renewed authentication but does not schedule an import.

Permission requirement

The Renew connection link only renders when the user's role includes the Financial Institution Records permission. Users without this permission see the banner but must contact an authorized administrator to renew.

What to do

1. Verify role permissions: Ensure that roles responsible for bank reconciliation include the Financial Institution Records permission if those users should be able to self-service MFA renewal from Match Bank Data.
2. Monitor import history: Use Transactions > Bank > Banking Import History to identify accounts with MFA errors before users encounter the banner.
3. Note the 1-hour delay: Post-renewal imports are scheduled 1 hour out, not immediately. If your workflow expects near-real-time data after reconnection, plan accordingly.
4. Non-SuiteApp connections: If your bank connections were configured without a SuiteApp and do not support inline renewal, the fallback is still the format profile. See Oracle's documentation on Configuring a Connection to a Financial Institution (Without a SuiteApp) for the manual path.
5. No scripting hooks documented: Oracle's source does not mention any SuiteScript trigger, workflow action, or REST endpoint for programmatic MFA renewal. If you have automated reconciliation scripts that depend on import availability, add monitoring for MFA-related import failures via Banking Import History or saved searches on import status.

Source note: The release version for this feature is not stated in the Oracle documentation. The exact release in which this capability became available could not be determined from the source URL or page content. Verify against your environment's version and release notes index.