SafeSend logins are moving to Thomson Reuters Accounts! This change is set to take place on April 25th, 2026.
This will create one unified account for all your Thomson Reuters products.
Benefits of SafeSend Migrating to Thomson Reuters Accounts:
SafeSend will be on the same single sign-on/multi-factor authentication system as the rest of the Thomson Reuters products.
One single login can be used across most Thomson Reuters products.
Expanded options for two-factor authentication: Text, phone, biometrics & more.
Options for large firms with unique needs, such as federated single sign-on.
Support for 3rd party apps that allow for simplification across the firm.
Convenience and Security.
FAQ
Will firms lose their SafeSend accounts?
No. Everything will stay the same. Your existing SafeSend login (username and password) will no longer be used. Instead, all users will have a Thomson Reuters login, which they will use to log into SafeSend. Only the sign-in method will be updated. There will be no impact on the existing SafeSend user accounts or products. (SafeSend User group, Tier, Product Settings, etc.).
Will this affect Taxpayers?
No, the SafeSend taxpayer experience will be completely unaffected by this change. It will only affect the firm-side application and only the login mechanism. Taxpayers will face no change and will see zero difference in their experience.
How will our existing users get these accounts?
All customers will immediately get a Thomson Reuters login. No action is required for firms logging in with usernames/passwords. We will transfer credentials for all firm users.
When users log in after the release on April 25th, they will put in their normal email address, and we will redirect them to the Thomson Reuters login page. They will put in their password to authenticate, then choose a multi-factor authentication option.
See the following articles for information about setting up multi-factor authentication.
Two-factor authentication for a Thomson Reuters account
Set up two-factor authentication for your Thomson Reuters account
If users already have an existing Thomson Reuters account, that will be used.
Will there be any pricing changes for SafeSend related to this migration?
No, the pricing structure for SafeSend will stay the same. There will not be an additional charge per user for this account migration.
There is a fee for getting Single Sign-On set up with the Professional Services team.
What will happen to the current SafeSend account functions?
SafeSend functions that manage and dictate account settings will be removed as they can all be maintained by Thomson Reuters. These items are:
- Multi-Factor Authentication
- Password Policies
- Single Sign On (SSO) - As currently implemented, firms can still SSO, but will go through a slightly different process. See below.
Thomson Reuters account management has its own Multi-Factor Authentication and Single Sign On features. These options will be removed from the Product Settings > Security section in SafeSend and will not be manageable at the SafeSend firm level.
When customers are migrated to a brand new Thomson Reuters Account, who is the account owner, and what are the multifactor authentication and password policy defaults?
Thomson Reuters Accounts do not designate an account owner. Instead, security is defined for all users; there is no “account manager” in that regard. Users simply login with a multi-factor authentication account that is enforced by the Thomson Reuters Account. The firm does not need to adjust password policies or multi-factor authentication settings any longer.
What about firms that are using Single Sign On (SSO)?
Firms that use SSO will need to take an extra step. SafeSend is not able to do a straight migration on behalf of the firm because they use Microsoft to authenticate, and we do not have access to those credentials. What we will do is create a Thomson Reuters Account for them, but give them a random password. Firms then have two choices:
- No longer use SSO: When you log in to SafeSend, you will need to reset your password, and you can log in as normal.
- Continue using SSO: You will need to connect your SSO account with your Thomson Reuters Account before or after the migration. Please refer to the following article for instructions: Single Sign On (SSO) Migration Guide. Any system admin at the firm can set this up in a few minutes.
If SSO is not configured before April 25th, 2026, users can reset their password and use a username/password to log in until SSO configuration is complete. They should set up SSO in their Thomson Reuters Account ahead of time to continue their firm's SSO process without interruption.
Will this affect APIs?
Yes, to call any endpoints, users will pass their username and password to the login API, and upon the final transition, we will no longer have passwords. We will be updating our Login API to instead take a Client ID/client secret that is derived from the SafeSend account. All APIs will require one extra header argument to be passed as well. A detailed guide on the new API structure guide is attached at the end of this article. This should be shared with all API developers at the firm so they can prepare for updates.
Will there be a migration window?
There will not be a migration window for the standard logon to the application or for single sign-on.
There will be a migration window for the APIs. The APIs will still support the SafeSend email and password (old method) until July 25th, 2026. During this transition time, we will support the new Thomson Reuters Account authentication and the old SafeSend authentication for the APIs (this is outlined in the API article above). After July 25th, 2026, firms MUST use the new CIAM auth method for all API calls.
What are the Timelines of this Transition?
We will create a Thomson Reuters Account for every firm on April 25th, 2026.
On July 25th, 2026, we will make the final change to our APIs to only use the new Thomson Reuters Account authentication method.
Will users need to uninstall/reinstall Mail Merge, Secure File Transfer, or TicTie Calculate version 6?
For Secure File Transfer and TicTie Calculate version 6, these applications will automatically adopt the new Thomson Reuters Account flow without requiring an uninstall/reinstall.
Mail Merge supports two login methods:
1. Username and Password:
After the migration, users can continue to log in and update Mail Merge as normal.
2. Single Sign On (SSO):
The SSO login function will no longer be available, so users who rely on SSO will not be able to log in to Mail Merge. These users will need to uninstall Mail Merge and then download and install the application from the Product Settings > General section of SafeSend.
How will this affect Tax Software Integrations?
The tax software integrations will continue to work until the July 25th deadline, as they use the SafeSend API calls that will remain unchanged until that time. Our integration partners are working on updates to their applications to support the new Thomson Reuters Account login by that time frame.
Comments
Article is closed for comments.