AAROs recommendation on Upgrades – AARO & AARO Lease IFRS 16:
Please note that with the release of AARO22 we no longer maintain AARO20 meaning we do not fix found issues. 20 CPV4.1 is the last available CPV. Our strong recommendation is to upgrade to AARO22 if you are currently in AARO20. |
Version | Solved Known issue (KI) and new or extended functionality. Please see also the Release notes for AARO22 for full presentation of new features in AARO. |
Version 22 CPV3 |
By upgrading to AARO22 you will get the below, and more:
Simplified administration for faster closing by:
Improved analysis for increased transparency in closings by:
Enhanced user experience to make closings easier by:
|
For 22 CPV3 we present bug fixes not fixed in CPVs for AARO21 nor AARO20. 22 CPV3 hold bug fixes performed in parallel and after release of 21 CPV5 but was released before 21 CPV6. Therefore, some of the bugfixes in 21 CPV6 will be fixed with the release of 22 CPV4 in spring 2022. |
|
Version 22 CPV3 AARO and AARO Lease IFRS 16 |
Fixed issues with AARO Lease IFRS 16 contract prepayments calculated incorrectly. We have changed the calculation of the short part of lease liability. Previously we calculated the short part of lease liability as the difference between the current closing balance of total lease liability and what the closing balance of total lease liability would be in 12 months. The calculation of what the lease liability would be in 12 months included the interest (that would increase the lease liability) for the next 12 months. We have concluded that this calculation is incorrect. The new calculation filters out the Payments, Expiration costs and Purchase options happening within the next 12 months and calculate the present value for those. This fixes the issue which was most noticeable where the previous calculation caused a negative short part when you have high inflation with high interest rate and a rapid increase in nominal payments as the previous calculation included a higher “added on” interest increase of the lease liability but a lower payment reduction of the lease liability. Please note that the changed calculation will give a difference in your figures when looking at the distribution between long and short part. Ref. No: 9703, 9679. |
Fixes the issue in match reports for a user having write restrictions on Company. For such user the counter amount was always 0 where the counter company did not belong to user rights. Ref. No: 11304. |
|
Fixes the issue with Accounting Type set up on the account level in Edit Accounts/PE radio button settings being overridden by Accounting Type setup on PEID level in Legal. The logic of booking on a specific Accounting Type in PEID was introduced in AARO21CPV3. Ref. No: 11296. |
|
’ALR Period’ period copy option discontinued The option ’ALR Period’ in the Copy Period dialog, Parameters to Copy area has been discontinued as legacy functionality. It was introduced in AARO20 in order to support standalone Lease customers where relevant tables were grouped under this check box and that they did not have to use the standard AARO check boxes. From now on please use standard check boxes to copy period data. Ref. No: 8596. |
|
Fixes the issue with HEADER and TEXT form layout elements not being visible in reports in Web client. Ref. No: 10984. |
|
Fixes the issue with the LDAP login not working properly with the AARO Excel add-in where Excel retrieve formulas were missing and Excel send formulas didn’t work. Ref. No: 10878. |
|
Fixes calculation of Lease prepayments
Ref. No: 10669, 10660. |
|
Termination of contracts is adjusted
Ref. No: 10586, 10594. |
|
Extended functionality!
Edit contract – check for consolidation of underlying figure data. We have improved the logic when editing Lease contract data to prevent from getting wrong figures if the underlying contract data has not been consolidated. Now a contract is locked for editing with an informational message appearing in the period if the period chain has not been properly consolidated. Before contract editing in a period, the prerequisite is that the period chain including opening balance period, previous period and period in question has to be consolidated in the stated order. Note that all periods with Lease data must be consolidated in the upgrade see AARO Lease IFRS 16 Configuration notes for more information. |
|
Issues with consolidation
Ref. No: 10954, 10714, 10740. |
|
Bookings for EATXX49L concerning LRECEXCHAJ is adjusted.
Are you affected: Issue: When this logic was implemented in earlier versions the bookings were incorrectly set up with the asset class for buildings (LEAS1110S) on all four EATXX49L. Workaround: Manual configuration is required to change Bookings settings to proper codes. Ref. No: 11605. |
|
Report with match difference entered.
Are you affected: Issue: Web match report with an entered match difference setting is not exported to Excel. Workaround: We recommend to clear match difference setting when you need to export the report to Excel. Ref. No: 11354. |
|
Group Bookings journals.
Are you affected: Issue: With the new feature to group Bookings journals in AARO22 on different ContentDesc in Bookings logic some customers have noted differences for bookings that depend on other bookings since these where not included in the first bookings calculations in the consolidation. Workaround: The differences is possible to handle with a manual change in the CONS_LOOP table in earlier CPVs of AARO22 and we will solve this in 22 CPV3. Contact AARO Service Center. Ref. No: 11481. |
|
Legal group delete.
Are you affected: Issue: When a company belongs to multiple legal groups and one of legal groups is deleted in Data Entry/Legal then opening balances for all companies are deleted in all periods after consolidation. Workaround: Don’t delete legal groups on the menu Data Entry/Legal until this issue is fixed. Please contact AARO Service Center for help. If you have already lost opening balances, you should consolidate the chain of periods from the start period. Ref. No: 11456. |
|
Automatic journal identifier.
Are you affected: Issue: When automatic journal identifier is activated then sending journals from Excel add-in shows an error. Workaround: Deactivate automatic journal identifier. Contact AARO Service Center. Ref. No: 11345. |
|
Elimination and journals FIXLOC and GROUP.
Are you affected: Issue: There is an issue with elimination applied to the account value zeroed out by summing up input value and values reported in FIXLOC and GROUP journals that is typically used for reporting acquisitions. Workaround: Do not zero out accounts by using FIXLOC and GROUP journals. Ref. No: 10813. |
|
Parameter Contract Type has no value.
Are you affected: Issue: Lease parameter Contract Type has an empty list of selection values in Web reports in the ’Selection and settings for’ dialog. Workaround: Don’t use parameter Contract type in reports until this issue is fixed. Ref. No: 11204. |
|
Past Equity and Excess Value journals are not sent.
Are you affected: Issue: When sending Past Equity and Excess Value journals from Excel add-in, Excel stops working, journals are not sent. Workaround: Create Past Equity and Excess Value journals in Windows client. Ref. No: 10234. |
|
Eliminations and Intercompany eliminations are calculated separately.
Are you affected: Issue: Eliminations and Intercompany eliminations are done separately that may lead to different results dependent on what form is open in current period. We will adjust the calculations to be done together. Workaround: The differences is possible to handle with a manual change in the CONS_LOOP table in earlier CPVs of AARO22 and we will solve this in 22 CPV3. Contact AARO Service Center. Ref. No: 11418. |
|
In match report descriptions are not exported to Excel.
Are you affected: Issue: At export to Excel of a match report and Show description option only is ticked in the Selection for dialog, then codes are shown instead of description. Ref. No: 11511. |
|
Wrong calculation after end date change.
Are you affected: Issue: If the contract remeasurement includes end date change within the year then the remeasurement calculation (LRAREMNET, LLREMNET, LLREMNET_P) does not continue till year end after the contract end date that also affects accounts (LRADISPOSE, LRDDEPRE, LLINTEREST). Ref. No: 11199. |
|
Missing values for terminated contract.
Are you affected: Issue: There is an issue with missing values for Depreciation and Interest accounts (LRDDEPRE, LREDEPRE, LRDDEP_REM, LLINTEREST, LREINTERES) 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. Workaround: For correct figures, from version 22 CPV 2, terminate a contract via Import. To terminate the contract through the import the contract template in Excel should have: – Remeasurement date = empty – Optional contract end date = empty – Revised depreciation end date = empty – Active contract end date = initial value – Termination date = new value Ref. No: 11071. |
|
InvType ELAcqDiv does not eliminate Cash Flow accounts.
Are you affected: Issue: InvType ELAcqDiv does not eliminate Cash Flow accounts when Average Translation for period is ”Isolated period”, system adjustment for ELAcqDiv is wrongly included into calculation. Ref. No: 11254. |
|
E-mails are not sent.
Are you affected: Issue: Microsoft has deprecated the Transport Layer Security (TLS) 1.0 and 1.1 long time ago, and is now enforcing the decision. TLS is a security protocol for establishing encryption channels over computer networks. Our AARO Products ”Report Subscription” and ”Cash Forecast” are using TLS1.0 for its mailing services and do not work with TLS1.2. We will fix this in coming CPVs. If you are using these products in AARO we recommend that you plan an upgrade to a CPV where this will be fixed. Ref. No: 11286. |
Version | Solved Known issue (KI) and new or extended functionality |
Version 21 CPV5 |
Fixes the issue in ESEF export where sum formulas were not presented for sum accounts in a report with Matrix Layout. Ref. No: 10679. |
Ref. No: 10694, 10676, 10620. |
|
Fixes the issue in Match reports where long comments in the comment field on a counter entry was truncated and not fully visible. Ref. No: 10640. |
|
Fixes the issues where the elimination of past equity on legal Type PE was not handled correctly in the legal subgroup as dimension logic for a company owned by parents belonging to different subgroups. Depending on what version you come from the problems may have been partly solved already but we have now secured that both are fixed with upgrade to 21 CPV5.
Ref. No: 10321 |
|
Improved performance! We have improved the performance of using the Find button in Legal to search for a specific Company. Depending on the size of a Company structure it took a long time before the Find dialogue appeared. This should now be faster. Ref. No: 10308. |
|
Fixes the issue where the ODBC driver was used from Excel with AARO Connector. Values inserted into Excel got corrupted showing not readable characters. This version of the ODBC driver can be used with any AARO version to get around this problem. Ref. No: 10736. |
|
Version 21 CPV5 |
Prepayments not correctly calculated (payment plan changes with remeasurement date within remeasurement period). Fixes the issue where the calculations of prepayments affecting the periods changes was incorrect which in turn effected the result in income statement in different areas. It was also visibly noted in the Preview Payment reflecting the payment schedule where you saw that the effect to date for the payment before the changed payment plan was incorrectly cut off earlier than it should be. The problem was for contracts with prepayments using periodic schedule with either Start of Month or Scheduled date where payment plan is changed with a remeasurement (adding a sequential payment row) and where the remeasurement date is within the period where remeasurement is made. Ref. No: 10669. |
Prepayments not correctly calculated (payment plan changes in original period). Fixes the issue where the calculations of prepayments affecting the periods changes is incorrect which in turn effected the result in income statement in different areas. It was also visibly noted in the Preview Payment reflecting the payment schedule where you saw that the effect to date for the payment before the changed payment plan was incorrectly cut off earlier than it should be. The problem was for contracts with prepayments using periodic schedule with either Start of Month or Scheduled date where payment plan is changed adding sequential prepayment rows within the original period. Ref. No: 10660. |
|
Fixes the issue for contracts that is terminated where the contract has either a remeasurement or decrease of scope has been used within the same year. The current accumulated interest and depreciation, from the termination date until the end of the year, was too low and the interest and depreciation were calculated as if the termination was a remeasurement at the termination date. Ref. No: 10593. |
Version | Solved Known issue (KI) and new or extended functionality |
Version 20 CPV4.1 |
In the patch 20 CPV4.1 which holds also the bug fixes and extended functionality from 20 CPV4 we have included additional bug fixes, please see below. The patch 20 CPV4.1 is replacing the 20 CPV4 in planned upgrades for both AARO and AARO Lease IFRS 16. Should you have 20 CPV4 and experience the 10221 as a problem, please contact AARO Service Center to replace the 20 CPV4 with 20 CPV4.1. |
Fix added in 20 CPV4.1 (KI in 20 CPV4) Fixes the issue where reports with Source:INPUT with multiple columns or rows behaved differently due to a temporary bug in (20 CPV4). When executed, the reports presented a matrix of possible combinations given your selection on the row or column parameters instead of only the combinations with data (unless you activate remove empty rows/columns). If you have ‘All’ selected and you have wide access in AARO this could have created a very large report and in some situations, this would affect the performance of presenting the report. If many users were executing large reports at the same time the reports could hang and in worst case cause the server to go down. Ref. No: 10221. |
|
Version 20 CPV4 |
Extended functionality! We now support moving opening balances values with Legal Type PE and PEInv for dimensions with FromCo as Subdimension when member relation changes between closing and opening periods, also when the dimension is not defined as a Legal Group. Ref. No: 9672. |
Isolated average translation
Ref. No: 9898, 9892. |
|
Fixes the issue where comments were deleted for all companies when you copy legal information for a selection of companies in Data Entry Legal. The copy functionality in Legal should not delete nor copy comments at all. Ref. No: 9776. |
|
Fixes the issue with not correctly reversed depreciations if you retire an Excess value within the same year as it is acquired and the asset is not owned from the start of the year and you reverse the values in Data Entry Legal not in the acquired ID column but create a duplicate of the ID and reverse the values there (which is what the Dispose button will do). After the upgrade a recalculation of the reversed depreciation will give a correct depreciation value in this situation. Our recommendation however is that in this situation you should reverse the values within the same column. Ref. No: 9385. |
|
Fixes the problem where Excel Send converted Accounting Type ID to upper case letter and it was not possible to send data on AcctType other than default unless the AcctType ID was uppercase letters. Now Send formula is case sensitive and will send on ID matching the spelling. Ref. No: 9380. |
|
Version 20 CPV4 |
Extended functionality! Fixes the issue where the use of isolated average translation for periods was not supported for Lease. Ref. No: 9697. |
Changed logic The handling of exchange differences LOC to Group has been inconsequent. To solve possible issues and align the functionality with other exchange difference calculations the technical upgrade will replace translation logic with bookings logic for each asset class. For extra asset classes it must be added manually. For more information please see configuration notes. |
|
Fixes the issue with sequential periodic payment plans where different periodicity and/or offset (prepayment) are set up. The calculation used the last set up payment and not the individual calculations. Ref. No: 9572. |
|
Fixes the issue where importing a contract with changes multiple times in the same period caused incorrect calculation of Deferred Tax. If you have incorrect values remove the revision causing the incorrect deferred tax in the period for that contract and add the changes for the contract manually in the contract view or import again now with the version where this is fixed. Ref. No: 9692. |