Our primary use case for Thomson Reuters ONESOURCE Indirect Tax Determination is indirect tax determination, mainly sales and using it for tax and VAT. We have OneSource integrated with our SAP environment so that tax is calculated automatically as transactions are processed. We also use it for troubleshooting tax results, maintaining tax configurations, and supporting our tax reporting processes. The biggest benefit has been around automation with Thomson Reuters ONESOURCE Indirect Tax Determination. Previously, there was more manual work involved in validating the tax calculations and researching exceptions, whereas now it gives us a centralized tax engine and reduces the amount of manual interventions required from us, both from our tax and IT teams. It has also helped us standardize the way our tax is calculated across the different business processes and jurisdictions.
My main use case for Thomson Reuters ONESOURCE Indirect Tax Determination is to help with indirect taxes. It is easy to identify the company's products, determine how much the tax is, and calculate it easily. On time, we are going to claim the taxes to the government.
I mainly use Thomson Reuters ONESOURCE Indirect Tax Determination for tax determination for other conditions. It is integrated with SAP, and we mainly use it for TransEditor, TCQ purposes, and custom rules, and to write a new TransEditor or TCQ. The main purpose is that. Suppose a situation where an AP processor tried to process an invoice from SAP, and SAP is integrated with Thomson Reuters ONESOURCE. While processing the invoice, the AP team has an issue. Maybe they are not able to process the invoice due to a Sabrix error. We go and check the issue and we put in the data and we check the logs of the out-data and we found that there is an error in the TransEditor. We go to that particular group of the TransEditor and fix it. I mostly use the product mapping, TransEditor, custom rules, and TCQs. These are the main uses and the use case.
Learn what your peers think about Thomson Reuters ONESOURCE Indirect Tax Determination. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
Thomson Reuters ONESOURCE Indirect Tax Determination facilitates precise tax calculations for businesses, enabling compliance with global tax regulations. It integrates seamlessly with existing systems and enhances efficiency in managing indirect tax obligations.Deploying advanced algorithms, ONESOURCE Indirect Tax Determination stands out in the landscape of tax technology. It automates the tedious tax calculation process, adapting to frequent legislative changes. This adaptability supports...
Our primary use case for Thomson Reuters ONESOURCE Indirect Tax Determination is indirect tax determination, mainly sales and using it for tax and VAT. We have OneSource integrated with our SAP environment so that tax is calculated automatically as transactions are processed. We also use it for troubleshooting tax results, maintaining tax configurations, and supporting our tax reporting processes. The biggest benefit has been around automation with Thomson Reuters ONESOURCE Indirect Tax Determination. Previously, there was more manual work involved in validating the tax calculations and researching exceptions, whereas now it gives us a centralized tax engine and reduces the amount of manual interventions required from us, both from our tax and IT teams. It has also helped us standardize the way our tax is calculated across the different business processes and jurisdictions.
My main use case for Thomson Reuters ONESOURCE Indirect Tax Determination is to help with indirect taxes. It is easy to identify the company's products, determine how much the tax is, and calculate it easily. On time, we are going to claim the taxes to the government.
I mainly use Thomson Reuters ONESOURCE Indirect Tax Determination for tax determination for other conditions. It is integrated with SAP, and we mainly use it for TransEditor, TCQ purposes, and custom rules, and to write a new TransEditor or TCQ. The main purpose is that. Suppose a situation where an AP processor tried to process an invoice from SAP, and SAP is integrated with Thomson Reuters ONESOURCE. While processing the invoice, the AP team has an issue. Maybe they are not able to process the invoice due to a Sabrix error. We go and check the issue and we put in the data and we check the logs of the out-data and we found that there is an error in the TransEditor. We go to that particular group of the TransEditor and fix it. I mostly use the product mapping, TransEditor, custom rules, and TCQs. These are the main uses and the use case.