Data residency for transactions
Configure Determination Anywhere to write transaction data directly to customer-managed cloud object storage to meet local data residency requirements.
Customers in data-sensitive regions may require that transactional data stays within their local region.
note
Customers who deploy Determination Anywhere can retain transactional data within their own infrastructure by directing it to customer-managed cloud object storage.
Determination Anywhere saves transaction data as Avro files directly to the customer's cloud storage, such as Amazon S3, meeting data residency requirements.
How the tax engine supports data residency
Determination Anywhere can be configured to write tax calculation transactions to customer-managed object storage as Avro files, following a similar upstream transfer to Enterprise Cloud.
note
In a data residency configuration, Avro files are stored in the customer's environment and not sent to Thomson Reuters.
The Avro file contains the same data as the XML or JSON response, but with different field names. It includes a built-in schema so customers can easily read and use the data for their own reporting.
Determination Anywhere can also be configured to support data residency while still syncing transaction data to Thomson Reuters' reporting solution.
note
A future
Log Center
feature will store tax engine request and response payloads (XML or JSON) for customer reporting.Intended use of data residency
Data residency in Determination Anywhere gives customers the data elements needed to build their own reporting or analytical solutions. It is not intended to replicate Thomson Reuters' Reporting and Analytics solution.
note
Some customers choose not to use data residency and instead rely on the tax engine response (XML or JSON) consumed by their source systems. Determination Anywhere supports both approaches.
What Determination Anywhere data residency doesn’t support
Some internal auditing workflows, such as transaction reversal handling, use proprietary logic that is not included in data residency. Customers can use the output data to design their own reversal mechanisms if needed.
The same applies to Line at a Time (LaaT) processing. LaaT-specific logic is not included in the data residency output, but the data contains the elements needed for customers to implement their own handling.
How Determination Anywhere data residency differs from legacy Determination
In legacy Determination, the audit database is embedded directly within the application deployed to the customer's infrastructure. This included:
- The user interface to manage configurations
- The tax engine communicating directly with the content and configuration database
- An inherent audit database
Customers licensed for reporting also required SAP-based components to move audit data into reporting systems. The entire application stack is hosted within the customer's region, inherently satisfying data residency needs.
Determination Anywhere operates differently as an extension of the Enterprise Cloud platform:
- The user interface and core services are hosted in Thomson Reuters' cloud
- Components required to sync content, configuration, and transactions reside within the Determination Anywhere instance in the customer's infrastructure
- Audit and reporting databases are hosted in the cloud
In a data residency configuration, transaction data is saved directly to the customer's own object storage, rather than being transmitted to Thomson Reuters' cloud storage.