MFA or Security Token Not Working in Treasury Services

Troubleshoot expired one-time passcodes, soft token sync errors, hardware token failures, and MFA push approval delays in treasury platforms.

What usually breaks MFA

Treasury authentication can fail for several reasons: the wrong token type is selected, the device clock is out of sync, the hardware token battery is weak, push notifications are delayed, or the user account is no longer mapped to the correct authentication method.

Check time sync first

Time-based codes only work when the clock on the phone or computer is accurate. Turn on automatic time and time zone settings, then reopen the authenticator app. Even a small clock drift can produce invalid code errors.

Push approval problems

If push approval does not arrive, check whether the app is logged in, notifications are allowed, and the device has internet access. Some users have multiple registered devices and approve the wrong request or wait on an old phone that is no longer active.

Hardware token failures

For physical tokens, check whether the display is dim, unresponsive, or generating codes that fail repeatedly. Some enterprise tokens eventually need replacement. If only one user is affected while others can authenticate, the token itself is often the source.

Resets and re-enrollment

When codes consistently fail after a phone migration or app reinstall, the safest path is usually an MFA reset and clean re-enrollment by an administrator or support team. Capture the steps already tried so the reset is not delayed by repeated basic troubleshooting.

Practical checklist

• Capture the exact wording of the error
• Test a second browser or private window
• Confirm whether coworkers are affected
• Review role and entitlement changes
• Document timestamps before escalating