New features
We've introduced a new
Tax Rate Simulator
feature, accessible through the
Tools
then
Tax Tools
menu. By inputting relevant parameters such as
Ship from
,
Ship to
,
Product code
,
Commodity code
, and
Gross amount
, users can quickly obtain an estimated tax rate and tax amount for the given transaction date.
In the
Ship from
and
Ship to
sections, the simulator supports both the geographical address and latitude and longitude coordinates, automatically adjusting the interface based on entries.
The mandatory field validation ensures accurate data entry, while the
Run calculations
initiates the tax calculation process. Results are displayed in a sortable, paginated table on the
Result details
tab. For a deeper analysis, an
XML
tab provides access to Input and Output XML files, complete with search and download capabilities.
This comprehensive tool improves tax rate calculations, offering improved control and insight into tax scenarios.
Enable selection of the DSL license type from provinces other than state authority
We've improved the
Add Custom Operating License Mapping
workflow by introducing the selection of
Destination State
dropdown before selecting the
Destination Seller Operating License Type
.
You can now select the
DSL License type
from provinces other than the given state authority. Both fields are optional. The
DSL license type
dropdown is turned on only after you've selected the state. These changes apply to both Standard and Custom Authorities and have been optimized for performance.
BR — Standard CST codes (1076125)
The post-tax calculation, based on attributes applied from the rules to the transaction system matches a unique CST code for an authority. This code is populated in the
<cst>
tag under the tax block for the authority. Currently, this is applicable to Brazil IPI, Brazil ICMS, Brazil PIS and Brazil COFINS authorities.
These codes and the corresponding attributes are part of the standard content while determination finds a match after tax calculation to send a unique CST code corresponding to the match found.
Example:
CST code 50 is sent under authority – Brazil IPI for a Seller transaction with Business Supply – Yes in case of a transaction from São Paulo to São Paulo with inclusive calculation where an IPI rule with non-exempt SR rate code with 100% basis gets applied to a taxed transaction.
The Solution is being released into waves according to the Standard Content plan to be populated. We will provide this information in the upcoming Release Letters regarding the LATAM Content.
For this Cloud Release, the IPI codes are matched as table Standard Codes below:
IPI (IN 1.009/2010)
CST Code | CST Description | Standard |
00 | Entry with Credit Recover | - |
01 | Entry taxed at a zero rate | x |
02 | Exempt Entry | x |
03 | Untaxed Entry | x |
04 | Immune Entry | - |
05 | Input with suspension | x |
49 | Other entries | |
50 | Taxed output | x |
51 | Taxable Output at zero rate | x |
52 | Exempt Exit | x |
53 | Untaxed output | x |
54 | Immune output | |
55 | Output with suspension | x |
99 | Other departures | x |
Some tax situation codes (CST) are out of the scope of the standard logic match. Situation codes that require some action from the client in the IDT configuration side will be included in the upcoming Releases and published in their respective Release Notes.
Product standard mapping (1252716, 1256967, 1253442, 1252714, 1221834 and 1256976)
We've added a
Start date
and
End date
under standard mapping and system content for all product groups.
These 2 attributes come with sorting and filtering functionality. There's also an increased character limit for the
Name
and
Description
of product categories up to a maximum of 1,000 characters.
Company registration mask with company option (1257038)
The system considers both simple and full registration masks to apply the VAT registrations (provided in the request or set at company level registrations) to a transaction when Company option
Enables Simple Registrations Such As DE Rather Than Full Number
isn't set to a value or is set to
Y
. Only when this company option is set to
N
will the system match the full registration numbers.
Oil and Gas — New UOM: Drum (1084586)
We've added a new UOM ‘
Drum
’ to support additional functionality in Determination.
Category | From | To | Operator | Factor | Start Date | End Date |
Volume | GLL | DRM | / | 55 | 01/01/2024 | - |
Volume | QT | DRM | / | 220 | 01/01/2024 | - |
Volume | LTR | DRM | / | 208 | 01/01/2024 | - |
Volume | BBL | DRM | * | 0.763636 | 01/01/2024 | - |
Volume | DRM | GLL | * | 55 | 01/01/2024 | - |
Volume | DRM | QT | * | 220 | 01/01/2024 | - |
Volume | DRM | LTR | * | 208 | 01/01/2024 | - |
Volume | DRM | BBL | * | 0.763636 | 01/01/2024 | - |
Coupons in retail industry: New object ‘Related Line Amounts’ added in REST service (1203738, 1239430, 1239472, 1251681, 1251684, 1251685, 1258715, 1258716, 1262573, 1262575, 1272547, 1272653, 1272654, 1272926, 12729300, 1287913, 1287917)
We've introduced a new field to the
REST
services that enables users to add a related line number and split amount. This can be used for Coupons that are applicable in U.S. retail industries.
ONESOURCE Determination currently supports 2 types of coupons: Manufacturing Coupon (Commodity Code 70.170) and Store Coupons (Commodity Code 70.180).
To use the Related Line Amounts, the following are needed:
The
Company
option
Enable Related Line Calculation
needs to be configured for a company. You can find this by selecting
Companies
,
Select Company
,
Tax Logic and Company Admin
,
Options
, then
Enable Related Line Calculation
.
Add a new line with the relevant
Commodity Code
to specify the type of Coupon.
The new structure for the Related Line Amounts for a REST Calculational Service Request is as follows.
"relatedLineAmounts" : [
{
"lineNumber" : 1,
"splitAmount": -2
},
{
"lineNumber" : 2,
"splitAmount":-2
}
The
line number
of
relatedLineAmounts
specified in the request must be valid. Consider an invoice that has 11 lines, where lines 1-10 are retail items and line 11 is the coupon. In line 11, the
relatedLineAmounts
will include a line number and a split amount. The related line number specified in the request should be between lines 1-10.
The split amount must be valid. In the above example, If line 1 has a gross amount of $2, and line 11 is the Coupon, the coupon can be applied to one or multiple lines. When providing an input for related line 1, the split amount can't be larger than $2. If multiple coupons are applicable to line 1, the sum of the coupon split amounts to be applied to line 1 shouldn't be greater than the gross amount of line 1, $2. For instance, line 11 can be a coupon with a split amount for $1 towards line 1 and line 12 can be a coupon with a split amount of $1 towards Line 1.
Two fields are added to the
Line Tax Summary
to include net gross and net tax amounts (refer to the Sample REST Calculation Service Response below).
Net_Gross_Amount
: The calculated net gross amount for each line. Net gross amount = Line Gross Amount Minus Coupon Amount applied to that line.
Net_Tax_Amount
: The calculated net tax amount for each line. Net Tax amount = Line Tax Amount Minus Coupon tax amount (for authorities where coupon reduces taxable basis).
Sample REST calculation service response:
"taxSummary": {
"taxableBasis": "0.00",
"nonTaxableBasis": "0.00",
"exemptAmount": "-2.00",
"taxRate": "0",
"effectiveTaxRate": "0",
"netGrossAmount": "-2.00",
"netTaxAmount": "0.00"
},
Authentication will be required to access SOAP WSDL, XML Schema, and Zone Look Up service [992933, 927212]
The following endpoints are currently available without any authentication. This represented a security risk for Thomson Reuters and therefore we’ve introduced a native user-based authentication. This will be effective starting the upcoming release, ONESOURCE Determination Enterprise Cloud 2025.01 release (UAT in January 2025 / Production in February 2025).
Any services of the following format, for all environments in Enterprise Cloud (UAT and Production) will need the established SOAP (Simple Object Access Protocol) user credentials:
.../sabrix/services/taxcalculationservice/2011-09-01/taxcalculationservice?wsdl
.../sabrix/services/taxcalculationservice/2011-09-01/taxcalculationservice?xsd=TaxCalculationService.xsd
.../sabrix/services/zonelookupservice/2011-09-01/zonelookupservice
This change won't impact the tax engine interfaces. They’ll continue to function in the same way.
Performance improvements observed after enabling company admin option: Fetching Rules with Product Category (1253368)
We've observed significant performance improvements when the following Company Option is enabled for a company. If customers choose to enable this option to leverage the performance improvements, we recommend testing this in a lower environment to ensure this has no adverse impact on tax calculations. An issue was identified with this Company Option at a prior release and has been resolved. (More details can be found in the Fixes section of the release notes.)
To find this option, select
Companies
,
Select Company
,
Tax Logic & Company Admin
,
Options
, then
Fetching rules with Product Category
.
Malaysia service tax enhancement (1049301)
As per the new Malaysian (MY) tax regulations, digital services supplied by foreign (non-MY) service providers to non-registered customers in Malaysia will be taxable in the customer's country. This entails the addition of a new logic in the tax engine for the transaction type of Electronic Services that will consider the customer location — not the country of consumption — and must be applied to the authority of Malaysia Service Tax.
Increase in custom attributes (1172861, 1172862, 1172864, 1172866, 1172867, 1172869, 1280981)
Enhanced the custom attributes functionality in Determination Enterprise Cloud. The number of available custom fields at both the document and line levels has been increased from 50 to 200, offering an additional 150 custom attributes at each level. Which allows for greater flexibility in capturing and processing transaction data that falls outside standard XML elements, providing a more tailored and robust tax determination process.
Multiple changes were made to accommodate the expanded functionality and ensure seamless integration and compatibility across all components of Determination Cloud. Changes include data schema level and services such as, config areas, TransEditors, rule qualifiers, model scenarios, tax calculation services, and others; as well as database level changes for the following tables:
Tb_scenarios_custom_attributes
Tb_invoice_custom_attributes
Consider the new data schema will deploy in the UAT environment before production. As a result, custom attributes created or modified in UAT during this interim period may not be compatible with the production environment. Users are advised to exercise caution when importing or exporting data during this time. Reports and Analytics will reflect and align the changes to accommodate the additional custom fields according to the revised release dates
.
Data migration — Standard mappings individual data export (1262332)
Enhanced the export functionality to create an export file for an individual Standard Mapping records selected by the user. When navigating to the
Standard Mappings
page, users will be able to select 1 or more records by selecting the checkbox. Once the selection is done,
Export
gets enabled and selecting it will generate an export file, which will be imported through the Import Functionality. To go to the
Import
tab, select
Tools
,
Administration
, then
Export and Import
).
Data migration — Conditional mappings individual export (1273442)
Enhanced the export functionality to create an export file for an individual Conditional Mapping records selected by the user.
Data migration — ERP code mappings individual data export (1179267)
Enhanced the export functionality to create an export file for an individual ERP Code Mapping records selected by the user.
Data migration — Custom product categories individual data export (1179268)
Enhanced the export functionality to create an export file for individual Custom Product Categories records selected by the user.
Data migration — Exchange rates and exchange rates sources individual data export (1179262)
Enhanced the export functionality to create an export file for an individual Exchange Rate or Exchange Rates Sources records selected by the user.
Data migration — Allocations individual data export (1273478)
Enhanced the export functionality to create an export file for individual Allocations records selected by the user.
Data migration — Lookup list individual data export (1179264)
Enhanced the export functionality to create an export file for an individual Lookup list records selected by the user.
This release introduces significant improvements to our CSV import functionality, particularly for product zones, custom product categories, and exchange rates.
You can now easily import product zones for selected company and target groups.
We have enhanced the custom product category import process, resolving previous 500 error issues.
We improved the user interface for selecting target groups and custom product categories for a specific company during import
We resolved the issue for the exchange rates import flow, by introducing the selection from
Exchange rate source
for a given company before importing the file.
We implemented better error handling and success messaging.
These updates streamline the data import process, making it more efficient and user-friendly.