Protecting Your Bank Account Data on Oracle Textura Payment Management

To protect your bank account information on the application, adhere to the following best practices:

When the bank account data on Oracle Textura Payment Management (TPM) is changed all users with the Enterprise Administrator role are notified via email and SMS or Voice (for landlines).
It is recommended that you always have more than one active Enterprise Administrator account for your organization. Creating multiple Enterprise Administrators with different email addresses and verification phone numbers makes it more difficult for a malicious user to modify bank account numbers undetected.
If you only have one Enterprise Administrator in your organization, TPM will display a warning at the top of the page. From the warning, you can choose to create a new Enterprise Administrator, promote an existing user to an Enterprise Administrator, or silence the warning for 90 days.
Enterprise Administrators are required to use a Two-Factor Authentication (2FA) through their verification phone number to make bank account changes.
Do not share the phone used for verification messages. Do not forward or share verification codes sent to your verification phone number.
General Contractors can enable organization-level payment holds when a Subcontractor on one of their projects changes their bank account information. This feature is described under the Place Organization Hold When Subcontractor section on the My Organization Settings page.
Oracle will never ask you for a verification code sent to your phone.
All Enterprise Administrators for your organization will also be presented with a banner at the top of Oracle Textura Payment Management upon logging in indicating the bank account was changed. It displays for 30 days after the change is made.

For more information on security, see the Security Best Practices for General Contractors topic.

Next: Managing User Access