Solved known issues and recommendations about upgrades, Q1 2022

AAROs recommendation on Upgrades – AARO & AARO Lease IFRS 16:

• We at AARO always recommends you as a customer to upgrade to the latest version (Major and CPV), this to ensure that you take advantage of the latest bug fixes, as well as new functionality.
• An upgrade to AARO23 CPV1 is our strong recommendation. In AARO23 we have new functionality that is not available in AARO22 and AARO21.
  • New AARO Lease IFRS 16 logic, available from July 1, 2022. We are currently developing a revised period mgmt logic for AARO Lease IFRS 16, which will lead to an alignment to how the rest of the AARO logic works. Due to this our recommendation is that no upgrades of AARO Lease IFRS 16 are scheduled until after 1st July.

Please note that with the release of AARO23 we no longer maintain AARO21, meaning we do not fix found issues.

Version 23 CPV1
AARO and AARO Lease IFRS 16

• AARO is integrated with Services.
• Opening rates setup is automated.
• Divest button is reimplemented.
• New account type ’HistoricValue’ for reporting equity changes with a historic rate directly in input form.
• Button ’Revert All’ allows to revert the whole selection of completed items.

Issue: If an associated company is owned by two or more parents belonging to different subgroups then this company is expected to be assigned to different subgroups in the legal subgroup logic. Currently we have an issue where the company is treated as subsidiary in the default legal group (MainGroup), which is correct, since the ownership in total is larger than 50% but in the legal subgroups logic the associated company is not assigned to any legal subgroup, but to “ELIM”.

Release note: Now, when using the new priority functionality (see ref 10068), the associated company appears in the relevant subgroup where it is prioritized.

Two issues remain:
* When using priority the subsidiary shall always be prioritized to the legal subgroup that parent in the prioritized relation belongs to. If a relation is prioritized where the parent company of the relation is not connected to any subgroup the subsidiary should be placed in group “other”. This is however not the case if the non-prioritized relation belongs to a specified legal subgroup. In this case the subsidiary will be placed in the non-prioritized relation.
* Similar if no relation is prioritized, the subsidiary is expected to belong to subgroup “other”. This will not be the case if one of the relations can be placed in a specified legal subgroup. The subsidiary will in that case be placed in the specified legal subgroup as dimension, and not group “other”.

Ref. No: 10663.

Issue: There is an issue with journals copied incorrectly. When ’None Recurrent’ recurrent type is selected in the Copy Period dialog, recurrent journals only are copied. When ’Only Recurrent’ option is selected then recurrent and non-recurrent journals are copied.

Release note: Now journals are copied according to the selection made:

• non-recurrent journals only when ’None Recurrent’ option is selected.
• recurrent journals only when ’Only Recurrent’ option is selected.

Ref. No: 11183.

Issue: There is an issue with running AARO Excel add-in in multiple Excel instances causing the access violation error to appear in different places. Excel instances can be run by different applications and exist as a process only.

Release note: Now you can have several Excel instances running when working with AARO Excel add-in.

Ref. No: 10003.

Issue: Updating (running, changing parameter values, expanding) a drilldown report saved in previous AARO Excel add-in versions (AARO20, AARO21) fails with an error message.

Release note: Now you can update reports saved in previous AARO Excel add-in versions.

Ref. No: 11641.

Issue: There is an issue with wrong calculation of Depreciation and Interest accounts from the contract termination period till year end if the contract is terminated via Import and the previous remeasurement was made within the same year as termination.

Release note: Now the calculation of accounts is correct.

Ref. No: 11287.

Issue: If the contract remeasurement includes end date change within the year, then the remeasurement calculation does not continue till year end after the contract end date that also affects other accounts.

Release note: Now remeasurement calculation continues till year end.

Ref. No: 11199.

Issue: There is an issue with missing values for Depreciation and Interest accounts from contract termination period till year end, in the case when a contract is terminated manually or through the bulk edit, and the previous remeasurement was made in a different year than termination.

Release note: Now the calculation of accounts is correct.

Ref. No: 11071.