General Updates
Delete Datasets:
When a user tries to delete a dataset that includes entities the user does not have access to, the following new warning message has been added:
You do not have write access to one or more entities in the dataset and cannot be deleted. No access entities will not be visible in the Returns grid.
Dataset Edit:
Resolved an issue with incorrect period date getting appended in return name after we edit dataset start or end dates, and changing the return name while editing a dataset.
Decimal places customization in the GL Reconciliation report: Updates to allow customization of the GL reconciliation report to adjust the number of decimal places they wish to see in the reconciliation output, to make mismatches in amounts more clear when reviewing the report. The change is supported for both onscreen and Excel formats.
Native language – Report Parameters issue: Resolves issue meaning users can now select the date parameters on the reports screen when running the reports with the UI set to native languages.
Issue with missing data and incorrect user names on the Audit Reports: Resoled issue with Audit map and audit entity manager reports display accurate user names and the corresponding operation(s) performed by the users.
Audit report for DTR adjustments: DTR Adjustments report was created to provide visibility over edits performed on DTR transactions. The report is an excel report and will provide information for each import type separately in individual tabs. The tabs are inserted only if there are edited records under an import type.
Norway Digital: Resolved an issue on scheduled roll forward of returns.
Export to Excel: Resolved an issue where the export to Excel was not considering European localization of amount separators.
An issue parsing files with certain special characters in the metadata using the import wizard tool has been resolved by upgrading to the latest libraries.
For imports which utilize manual exchange rate sources, there are occasionally scenarios where an the rate to be applied to an exchange rate pairing for a given date is undefined. In these scenarios, OIC automatically applies one of the below transformations, to facilitate a successful import:
EUR to USD is mapped with rate 1.10, but USD to EUR is not mapped. The import file contains a transaction needing conversion from USD to EUR.
In this case, a rate of 0.91 (in other words, the inverse of the mapped rate) will be applied, and the following warning will be displayed:
Exchange rates are not mapped in exchange rate source for the date. A reverse rate has been applied.
USD to GBP mapped with rate 0.81, GBP to EUR mapped with rate 1.13, but USD to EUR is not mapped. The import file contains transaction needing conversion from USD to EUR.
In this case, a rate of 0.915 will be applied using GBP mappings as intermediary rates, and the following warning will be displayed:
Exchange rates are not mapped in the exchange rate source for the date. An intermediary rate has been applied.
These warnings will highlight transactions where unmapped exchange rates have been applied. The objective of this functionality is to allow imports to proceed, but flag transactions which may need further review and correction.
Exchange rates & Invoice values can be corrected by filtering to applicable transactions, editing the
TransactionExRate
field and selecting
Recalculate Amount
fields during the edit process.
The functionality to recalculate amounts must be enabled by a database setting.
Filter performance: Filter performance on returns drill down has been significantly improved, and test data patterns updated to reflect scenarios with high volumes of imports.