SafeSend migration to Thomson Reuters accounts
SafeSend migrated firm-side sign in authentication to Thomson Reuters Accounts on April 25, 2026. Thomson Reuters Accounts provide a unified sign-in experience across Thomson Reuters products, including single sign-on and multi-factor authentication options.
About the migration
SafeSend now uses Thomson Reuters Accounts for firm-side user authentication. This migration creates a unified account that you can use across most Thomson Reuters products.
The migration changes only the SafeSend sign-in method. Existing SafeSend user accounts, user groups, tiers, product settings, and product access remain unchanged.
Benefits of Thomson Reuters accounts
Thomson Reuters Accounts provide the following benefits:
- SafeSend uses the same single sign-on and multi-factor authentication as other Thomson Reuters products. This provides a more convenient and secure authentication experience.
- Use 1 sign in across most Thomson Reuters products.
- Select from expanded two-factor authentication methods, including text message, phone call, biometrics, and other available options.
- Large firms can use options that support unique security requirements, including federated single sign-on.
- Firms can use supported third-party applications to simplify account management across the organization.
Firm user accounts
SafeSend firm users retain their existing SafeSend accounts. Users no longer sign in with their SafeSend username and password. Instead, they sign in to SafeSend by using a Thomson Reuters Account.
SafeSend transferred credentials for firm users who previously signed in with a username and password. Firms didn't need to take action to create these accounts.
When you sign in to SafeSend, you'll enter your normal email address. SafeSend redirects you to the Thomson Reuters sign-in page. Enter your password and select a multi-factor authentication method.
Those that already had a Thomson Reuters Account use that existing account to sign in.
For information about configuring multi-factor authentication, refer to the following articles:
Taxpayer experience
The migration doesn't affect SafeSend taxpayers. Taxpayers continue to use SafeSend without changes to their sign in process or overall experience.
The migration affects only the firm-side SafeSend application and its authentication method.
Pricing
The SafeSend pricing structure remains unchanged. Thomson Reuters doesn't charge an additional per-user fee for the account migration.
Security and account settings
Thomson Reuters Accounts manage authentication and security settings that SafeSend previously managed at the firm level.
The following settings are no longer available in in SafeSend:
- Multi-factor authentication settings
- Password policies
- Single sign-on settings, except as described in the SSO transition information
Thomson Reuters Accounts don't assign an account owner or account manager for security administration. Thomson Reuters Account policies enforce password and multi-factor authentication requirements for all users. Firms no longer need to manage these settings in SafeSend.
Single sign-on transition
Firms that currently use SafeSend single sign-on (SSO) can continue using SafeSend SSO during the migration window. There is no immediate change to the current SafeSend SSO sign in process.
Firms will need to move to Federated SSO with Thomson Reuters in the future. Thomson Reuters hasn't announced an end date for the SafeSend SSO migration window.
API authentication changes
SafeSend updated API authentication to support Thomson Reuters Account authentication. API integrations now use a client ID and client secret derived from the SafeSend account instead of a SafeSend username and password. API calls also require an additional header argument.
The API transition period ended on July 25, 2026. As of July 25, 2026, firms will need to use the new client ID authentication method for all SafeSend API calls.
Share the API authentication guide with all firm API developers so they can configure their integrations for the new authentication structure.
Refer to SafeSend API authentication guide for technical implementation details.
Migration timeline
Date | Event |
|---|---|
April 25, 2026 | Thomson Reuters created Thomson Reuters Accounts for firms that didn't use SSO and moved firm-side SafeSend authentication to Thomson Reuters Accounts. |
July 25, 2026 | SafeSend completed the API authentication transition. All API calls now require the new Thomson Reuters Account CIAM authentication method. |
Mail merge, secure file transfer, and TicTie Calculate version 6
You don't need to uninstall or reinstall Secure File Transfer or TicTie Calculate version 6. These applications automatically use the new Thomson Reuters Account authentication.
Mail Merge supports the following sign in methods:
- Username and password - After the migration, you can continue to sign in to and update Mail Merge as normal.
- Single sign-on - Mail Merge supports SSO during the SafeSend SSO migration window.
Tax application integrations
Tax application integrations used the SafeSend API authentication method through July 25, 2026. Integration partners needed to update their applications to support Thomson Reuters Account authentication before that deadline.
Tax application integrations will need to use the new authentication method for client identity for all SafeSend API calls.
