Skip to main content

Legal

Tax & Accounting

Trade & Supply

Risk & Fraud

News & Media

Books

Developers

Determination

ONESOURCE Determination 2023.1 Release Notes

Release highlights

Published: February, 2023
  • Additional support added within One Stop Shop (OSS) to differentiate between Union and Non-Union OSS.
  • The Low Value Goods tab was added to the EU OSS and LVG page to facilitate the input of the threshold value per currency.
  • Brazil updates.

New features

The topics below describe features added with this release.
Union and Non-Union OSS (478536, 570056 and 570060)
There are three types of One Stop Shop (OSS):
  • Union OSS
     - Union OSS is applicable to B2C goods and services transactions within the EU. The VAT registration number starts with the country code of the country where the OSS is opted for. This supports the following transaction types: Goods, Electronic Services, and Physical Performance.
  • Non-Union OSS
     - Non-Union OSS is applicable to B2C services transactions that are provided from non-EU countries. The VAT registration number for Non-Union OSS starts with the EU prefix. This supports the following transaction types: Default Services, Customer Location Services, Electronic Services, and Physical Performance.
  • IOSS
     - IOSS is applicable to B2C goods transactions that are provided from Non-EU countries. The VAT registration number for IOSS starts with an IM prefix. This supports the transaction type of Low Value Goods only.
Prior to this release, Determination supported only OSS and IOSS. Union and Non-Union OSS were grouped under OSS. With this release, additional support within OSS was added to differentiate between Union and Non-Union OSS. Union and Non-Union OSS types are setup on the EU OSS and LVG page (formerly, the EU OSS page). To access this page, select
Companies
, select the applicable company, then select
EU OSS and LVG
.
Low Value Goods Threshold Setup and Its Comparison (334644, 408359, 493925, 511719 and 537168)
The expected tax treatment for low value goods, which is applicable to Australia, the European Union (EU), New Zealand and the United Kingdom (UK), can be achieved by assigning a Transaction Type of LV (Low Value Goods) to the applicable transactions. However, there was no provision in Determination to define the threshold limits per currency and to compare the threshold limit with the line gross amounts in the document to achieve the desired results. This is now addressed.
The
LVG thresholds
 tab was added to the EU OSS and LVG page (formerly, the EU OSS page). To access this page, select
Companies
, select the applicable company, then select
EU OSS and LVG
. The
LVG thresholds
 tab facilitates the input of the threshold value per currency. Multiple entries are not allowed for the same currency unless the previous entry is end dated.
The threshold comparison functionality works for invoices that have a transaction type of LV at the document level or line level. This transaction type can be passed as input data from the source system or it can be assigned by a TransEditor. For transactions with the LV transaction type, the transactional currency is compared with the currencies maintained on the LVG threshold tab. If a matching currency is found, then the gross amount of all the lines in a document with the LV transaction type are aggregated and compared with the currency threshold setup. The following actions are performed as an outcome of comparison:
  • If the total gross amount is less than or equal to the currency threshold, then LV transaction type is retained.
  • If the total gross amount is greater than the currency threshold, then LV transaction type LV is changed to GS (Goods).
If the transactional currency does not match with any of the currencies maintained in the
LVG threshold tab
, but the same is provided with an exchange rate, then Determination compares the translated currency with the currencies on the
LVG threshold tab
. It performs the above steps if a matching currency is found. If there is no matching currency, then no action is performed.
Brazil - ICMS-ST Type - None Should Not Have Limit Credit - All Segments (352070)
When the ICMS interstate or intrastate rate is higher than ICMS-ST rate, Determination recalculated a new ICMS for deducting from the ICMS-ST tax amount (known as a credit limit). This validation is no longer applicable for the ICMS-ST Type - None.
This formula also works according to the ICMS-ST taxable basis percent provided in the rule.
If the ICMS-ST tax amount result is less than 0.00, the Determination displays the ICMS-ST tax amount as 0.00.
Brazil - Desonerado for Intrastate and Interstate Scenarios with Company Option - Brazil Alternative Taxable Basis (457106, 457126, 457139 and 492989)
This feature covers Desonerado calculations for the standard calculation method when the
Brazil - Alternative Taxable Basis
 company admin option is set to
ICMS_EXCLUDE
.
The Brazil ICMS Desonerado authority amount is the sum of the authorities’ tax amount determined according to the type informed as QUALIFIER in the rule under the Brazil ICMS Desonerado authority. The following table shows the qualifier that must be used in the rule to trigger the Desonerado according to its type, the composition of it and the impact on PIS and COFINS taxable basis:
Brazil ICMS Desonerado (Qualifier)
Description of the Taxes to Be Discharged in the Operation
Gross Amount that Will Be the Taxable Basis for Calculating the Following Taxes
New Gross Amount (After Deducting Desonerado Discount) that Must Be Considered as Taxable Basis for Calculating the Following Taxes
PIS and COFINS taxable basis if the Brazil - Alternative Taxable Basis company admin option is set
DESONERADO_TYPE1
ICMS and FCEP II tax value compose ICMS Desonerado amount
Intrastate operation: ICMS and FCEP II
Intrastate operation: IPI, PIS, COFINS, ICMS-ST and FCEP ST
The new gross amount must be considered for PIS and COFINS (since ICMS and FCEP II are already part of Desonerado discount)
DESONERADO_TYPE2
Only ICMS tax value compose ICMS Desonerado amount
  • Intrastate operation: ICMS
  • Interstate operation: ICMS
  • Intrastate operation: FCEP II, IPI, PIS, COFINS, ICMS-ST and FECP ST
  • Interstate operation: ICMS-DIFAL, FCEP, ICMS-ST, FCEP-ST, IPI, PIS and COFINS
From the new gross amount, reduce the FCEP II from PIS and COFINS taxable basis as only ICMS was part of Desonerado
DESONERADO_TYPE3
ICMS, DIFAL and FCEP tax value compose ICMS Desonerado amount
Interstate operation: ICMS, ICMS-DIFAL and FCEP
Interstate operation: IPI, PIS and COFINS
The new gross amount must be considered for PIS and COFINS (since ICMS and FCEP II are already part of Desonerado discount)
DESONERADO_TYPE4
ICMS and DIFAL tax value compose ICMS Desonerado amount
Interstate operation: ICMS and ICMS-DIFAL
Interstate operation: FCEP, IPI, PIS and COFINS
The new gross amount must be considered for PIS and COFINS and FECP should be deducted also (since ICMS is already part of Desonerado discount)
DESONERADO_TYPE5
DIFAL and FCEP tax value compose ICMS Desonerado amount
Interstate operation: ICMS and FCEP
Interstate operation: ICMS-DIFAL, IPI, PIS and COFINS
From the new gross amount, reduce ICMS from PIS and COFINS basis as only FCEP was part of Desonerado
DESONERADO_TYPE6
Only DIFAL tax value compose ICMS Desonerado amount
Only Interstate operation: ICMS-DIFAL
Only Interstate: ICMS, FCEP, IPI, PIS and COFINS
In addition to Desonerado discount, both ICMS and FCEP are reduced from PIS and COFINS basis
For Brazil PIS and Brazil COFINS authorities, Determination starts the calculation from the new net or gross amount calculated after the Desonerado reduction.
If the Brazil - Alternative Taxable Basis company admin option is not set or is blank, the taxable basis will be the new net or gross amount calculated.
If the Brazil - Alternative Taxable Basis company admin option is set, the existing logic of some other authority reduction is kept unless the same authority was part of the Desonerado composition to avoid duplicate deduction.
For an interstate operation with pharma commodity and the Brazil ICMS Desonerado authority, if the Brazil ICMS Repasse all states authority is triggered, then the Brazil ICMS Desonerado is calculated considering the new net amount, discounting the Brazil ICMS Repasse amount.
Brazil - Optional Element Added to Output for Services to Indicate whether PMC, PMPF, or IVA was used for the ICMS-ST Calculation (536333 and 568971)
This feature addresses the need to show the attribute out of PMC, PMPF or IVA that contributes to the ICMS-ST tax calculation.
CALC_BASIS_MODE is an optional element, which was added under the ICMS-ST tax block in output to hold one of the following values:
  • PMP
  • IVA (the default)
  • PMC
These changes were made to services, including the SOAP 2020 service, the REST API, and the XML invoice. The SOAP 2011 service was changed in the in the 2022.6 release.
Brazil - Rounding of New Gross (After Repasse Discount) to Remove Penny Difference in Rounded Taxable Basis of PIS and COFINS (690623 and 708865)
Determination now rounds up the Repasse discount amount before calculating the new gross amount.
New gross amount = Gross amount (given) - Rounded Repasse discount
Repasse is one of the discounts applied in Brazil transactions. Desonerado and the discount amount directly input from other authorities are not currently considered.
Transactions when both the Repasse and Desonerado are triggered are not affected. In such a case, only the Repasse rounded amount is subtracted from the gross amount.
For certain cases, there was an extra penny added to the COFINS amount. To address this discrepancy, Determination subtracts the truncated difference of ICMS Repasse from the sum of truncated differences of all authorities before calculating the penny difference that would be adjusted.
New Search and Filter on Products and Services Page (409220)
To improve the user experience and enhance the performance, a search and filter box was added to the
Standard Mappings, Conditional Mappings and Custom Product
 Categories tabs on the Products and Services page. These options allow you to search and filter records by creating filter tags. You can search and filter the records based on multiple company selections.
Performing a Search and Filter
To perform a search and filter:
  1. In the menu bar, select
    Configuration
    ,
    Mapping
     then
    Standard Mapping
    .
  2. Select your search-by criteria (for example,
    Company
     or
    Product group
    ) from the first drop-down list.
  3. Enter your search term in the field or, if you selected
    Company
     or
    Product group
     from the first drop-down list, select the search term value from the second drop-down list. For each search term, a filter tag is created and displays below the search and filter box. A filter tag is a combination of the search-by criteria and the search term.
  4. Select
    Search
    . The records are searched and filtered. Matching records display in the main grid on the Products and Services page. Applied filter tags display in dark gray and unapplied filter tags display in light gray.
Removing Search and Filter Tags
To remove a search and filter tag, select the cross sign shown in the filter tag. Each time an applied filter tag is removed, the records in the main grid on the Products and Services page are refreshed. There are no changes to the records displayed in the main grid when an unapplied filter tag is removed.
Updated the Certificate Admin Role to Have Permission to Access Operating Licenses and Licenses (803718)
Users who are assigned the Certificate Admin user role now have access to the following:
  • Licenses
     - Add, edit and delete
  • Operating licenses
     - Add, edit and delete
  • License types
     - View only
  • Operating licenses type
     - View only
  • Vendors
     - View only
  • Onesource Content
     (accessed by selecting Tools, Tax Tools then Onesource Content)

Fixes

The topics below describe previously known issues fixed with this release.
Cross Contamination of Reporting Data (542253)
An issue was identified in Determination where a transaction from one customer updated the transaction of another customer in a different hosted tenant. This affected only the reporting database tables, not the audited transactions.
Uniqueness of an invoice is based on the combination of HOST_SYSTEM, CALLING_SYSTEM_NUMBER, and UNIQUE_INVOICE_NUMBER. This failed to consider cases where similar values could be contained in the transaction belonging to a customer hosted in a different tenant. A customer hosted in one tenant could have unintentionally updated a transaction for a different tenant and caused the invoice to be reported as a reversal transaction.
To ensure uniqueness in transactions across all tenants, MERCHANT_ID is additionally included as a parameter to uniquely identify transactions within Determination.
Audited Data Missing in Reports if LINE_NUMBER Is Repeated – Revised Error Messaging (508632)
In the previous release, an error message was added that was generated from the tax engine if a line number (<LINE_NUMBER> within <LINE ID = >) was repeated for an invoice. The ERP is responsible to ensure that the LINE_NUMBER in the tax request is unique.
In the previous release, the transaction was blocked from processing by the tax engine if the LINE_NUMBER was repeated. An error message was returned by the tax engine but the message did not clearly identify the invoice. Information that clearly identifies the invoice is now added and should display as follows:
<faultstring>com.sabrix.error.DeterminationRuntimeException: Could not save audit having [Invoice UUID: null, UniqueInvoiceNumber: UNIQUE_INVOICE_NUMBER present in the request or else automatically generated, Merchant ID: Database ID of the company, Merchant Name: company name] as a result of [type: PSQLException, message: ERROR: duplicate key value violates unique constraint "table name"
Detail: Key (invoice_id, line_num)=(Database ID of the invoice, line number that is repeating) already exists.]. Line number line number repeats in invoice number transaction invoice number with invoice date date of the invoice</faultstring>
Tax Amount Rounding Issues with Reverse From Tax Calculations (522792 and 616145)
For the
Reverse From Tax
 calculation method, the invoice already includes the line Gross Amount and the line Tax Amount, and Determination is supposed to recalculate the invoice Total Gross Amount and Total Tax Amount based on those input elements. There was an issue where the input line Tax Amount and the recalculated invoice Total Tax Amount did not match (a penny difference in some cases). This is now corrected.
Incorrect Document Rounding for Reverse Charge Transactions (351246)
The Determination tax engine was incorrectly rounding reverse charge lines when a reverse charge line was included along with other forward charge lines in a document. This occurred when document rounding was enabled and impacted both input and output tax blocks of the line(s) subject to reverse charge (RC).
This issue is fixed. Determination now correctly applies rounding to only the forward charge tax amounts.
Related Line Functionality for Exemption Certificates (464958)
When using the Related Line functionality (where a line, such as line 2, is related to another line, such as line 1) the expectation is that the taxability of line 1 is followed by line 2. This should be the same case when an exemption certificate is applied to line 1 (even if it is condition-based) so that the exemption conditions are applied to line 2.
This issue is fixed.
Zone Alias Performance Improvements (511757)
Improvements were made to the Zone Alias functionality where the tax engine reduces the number of database calls made. This results in better performance when the Zone Alias functionality is used in a transaction.
Inclusive_Tax_Indicator Not Working Correctly (334783)
In a transaction, when the value of LINE.INCLUSIVE_TAX_INDICATOR is passed as Yes (Y), or setup as Yes (Y) using configurations, then tax engine should calculate and separate the line Taxable_Amount and Tax_Amount correctly as per applicable tax rates. This was not working and returned incorrect results.
This issue is fixed.
Null Pointer Exception if Country Not Part of Standard Tax Content Support (445499)
If the transaction includes a country name that is not support in the standard tax content (meaning there is no 2 CHAR, 3 CHAR or ISO codes) and the terminate processing check box is also not selected, then tax engine returned a Null Pointer Exception error for those transactions.
This issue is fixed. The transaction will not cause an NPE error even if it failed to return a tax result.
TransEditor Condition to Copy Buyer Registration Number from Invoice to Line Level Was Not Triggered (482815 and 498172)
The following TransEditor was set up to copy a buyer registration number from the invoice level to the line level:
LINE.REGISTRATIONS.BUYER_ROLE = INVOICE.REGISTRATIONS.BUYER_ROLE
It was not triggered within a transaction. This is fixed.
Brazil - Calculation of Brazil ISS Authority for Services Transactions with Brazil - Alternative Taxable Basis (523857)
When the Brazil - Alternative Taxable Basis company admin option is set to ICMS_EXCLUDE, it should not impact the taxable basis for PIS and COFINS for operations different from Goods transactions.
The following fix was made to the factor formula used for calculating the taxes in services transaction: Factor = 100% - PIS rate - COFINS rate - ISS rate
Brazil - Null Pointer Exception when Calculation Direction Switched from Forward to Reverse from Total (499554)
A blank page was caused by a null pointer exception, which occurred due to the gross amount used for the ICMS-ST calculation being zero after switching to a reverse from total. This error is fixed.
Brazil Reduction Basis in ICMS RD Rule Brings Wrong FCEP Tax Amount with Alternative Company Admin Option Set (499765)
A fix was made for the FCEP tax amount for the interstate operation when the ICMS-RD has a reduction basis with Brazil - Alternative Taxable Basis company admin option.
Brazil - Displaying Incorrect FCEP-ST Tax Amount when There Is a Reduction Basis for that Authority (521538)
A fix was made for the FCEP-ST tax amount formula during intrastate scenarios when the FCEP II has a reduction basis percentage.
Brazil - Incorrect Result for ICMS-ST and FCEP-ST when There Is a Reduction in FCEP II and ICMS (Ship From) for Intrastate Scenarios (708913)
A fix was made to correct the ICMS-ST and FCEP-ST tax amounts for intrastate scenarios when FCEP II has a reduction basis percentage added and the FCEP -ST tax amount was incorrect.
FCEP-ST tax amount = (FCEP-ST percentage rate x FCEP-ST taxable basis amount) - ((Gross amount x FCEP II taxable basis percentage) x FCEP II percentage rate)
ICMS-ST tax amount = (ICMS-ST percentage rate x ICMS-ST taxable basis amount) - ((Gross amount x ICMS taxable basis percentage) x ICMS percentage rate)
This fix is for:
  • If the Brazil - Alternative Taxable Basis company admin option is not set or is blank and for the alternative taxable basis and PIS and COFINS taxable basis
  • The inclusive and standard calculation methods
Brazil - Cases with Reduction in Any Authority Provides Wrong Result with Desonerado (477144)
A fix was made for all the cases when a reduction basis percentage is configured in ICMS, FCEP II, ICMS-RD or ICMS-RD ST authorities as part of Desonerado calculations.
Brazil - Model Scenarios Import/Export Functionality - Values in Overrides - Calcs (PMPF, PMC) Are Not Retained (369299)
With this fix, the values of PF, PMPF, PMC or PMVG provided in the line level are retained after exporting the same company to a different environment.
Tax Jurisdiction Flow for Non-U.S. Child Companies (456861)
We updated the flow for adding an establishment for non-U.S. child companies. A warning, which indicates the child company is inheriting data from parent company, displays then the Tax Jurisdiction page of the parent company displays.
Returning User Recently Searched Data (493900 and 493902)
In custom fields and on the Products and Services page where the new search and filter box was added, the applied and unapplied filter tags and the filtered records from the most recently performed search and filter are retained when a user returns to the page from another application page or a tab on the same page.
Performance Improvement on the Tax Jurisdiction Pages (390652, 523007, 523008, 523009, 523010 and 690563)
For many companies, the amount of time that elapsed when displaying results in the user interface was significantly reduced after the logic was optimized in the tax engine code and the API calls associated with the Tax Jurisdiction pages.
Performance Improvement on Users Pages (520732, 522999 and 660073)
With this release, performance improved on the Users and Roles page (which lists users) and the Assign and Manage Roles page (which is used for editing users) by optimizing the code and the API calls.
Performance Improvement on the Model Scenario Page (521834)
As part of the performance enhancements implemented with this release and to enhance the user experience, the amount of time that elapsed when loading the Model Scenario page (which lists the Model Scenarios) was significantly reduced.
Performance Improvement for Mappings (810625)
As part of the performance enhancements implemented with this release and to enhance the user experience, the amount of time that elapsed when loading the
Standard Mappings, Conditional Mappings and Custom Product Categories
 tabs was significantly reduced.

Known Issues

The topics below describe known issues in this release.
Error while Mapping a Product (666852)
An error is received in the following scenarios:
  • Scenario 1:
     A customer adds a duplicate product code with the same product category and a different start date and no end date.
  • Scenario 2:
     A duplicate product code with the same product category and different start dates and different end dates is added.
  • Scenario 3:
     A duplicate product code with a different product category and different start dates and no end dates is added.
  • Scenario 4:
     A duplicate product code with different product categories and different start dates and different end dates is added.
Solution:
  1. Select
    Configuration, Mappings then Standard Mappings
    .
  2. Select
    Add Standard Mapping
    .
  3. Select any company.
  4. Add the same product code for the product category as the ones already existing with a different start date and end date that is after the start date of the existing product code.
Tax Jurisdiction - Authorities and Save button enabled even when the User Has An Error on any one of the Authorities for both Registrations and Establishments (568507)
Solution:
 All the authorities and the SAVE button are unavailable when a user has an error on any one of the authorities for both registrations and establishments.
Tax Jurisdiction - Blanket De-Establishing all U.S. States Does Not Save the Changes (812391)
Solution:
 Clear the Established in all states & territories check box de-establishes the entity in all the U.S. states and territories.
Default Products Added for all Product Groups for New and Existing Companies (813351)
Users see only the product groups added by the user and no default groups are added for new or existing companies.

This article applies to:

  • PRODUCT: ONESOURCE Determination,ONESOURCE Indirect Tax

Related Content