| Version |
Ref |
Solved Known issue (KI) and new or extended functionality |
|
21 CPV3.4 AARO
|
|
New Functionality and patch for bug fix!
In 21 CPV3.4 we have released new functionality to support electronic reports submitting to authorities that complies with ESMA ESEF (European Single Electronic Format) reporting. In this CPV we have also include the fix with reference 10221.
The patch 21 CPV3.4 is replacing any previous 21 CPV3.X in planned upgrades for both AARO and AARO Lease IFRS 16. Should you have 21 CPV3.X and experience the referred to fixes as a problem contact our support to replace with 21 CPV3.4. |
| 10221 |
Fix added in 21 CPV3.4 (KI in 21 CPV3.X)
Fixes the issue where reports with Source:INPUT with multiple columns or rows behaved differently due to a temporary bug in (21 CPV3.X). 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. |
|
21 CPV3.2 AARO
|
|
The 21 CPV3.4 also include the content from the previous patches 21 CPV3.2 and 21 CPV3.1. |
| 10151 |
Fix added in 21 CPV3.2 (KI in 21 CPV3.1)
Fixes the issue where it was not possible to change status for a journal with status Prepare to status Saved in Data Entry Journals nor in Process Journals. The problem was for journals with accounts that does not have Proforma Type as input field (the new possible functionality from 21 CPV3). |
| 10147, 9898, 9892, 9957 |
Fix added in 21 CPV3.2 (KI in 21 CPV3.1)
The fixes referred to concerning Cashflow in periods with isolated average translation was not entirely fixed in 21 CPV3.1 but in the patch 21 CPV3.2 it is fixed.
Isolated average translation
- Fixes the issues where the calculations of Depreciation (DeprDepr) was incorrect for periods with isolated average translation for GWIDs which you make changes for over time, in year 2 and later.
- Fixes the issue for cash flow in periods with isolated average translation for a Cash flow set up where you have part of the cash flow to historic rates and the rest following calculation to average rate (the isolated average translation logic in this case applied). Our usual logic expects an average translation of the whole Cash flow and there we do not have this problem. We now consider the specific situation mentioned for CF calculations for periods with isolated average translation.
- Fixes the issue for Cash Flow in periods with isolated average translation where the OB/CB chain for the cash flow includes journals with InvType=Acquired. In this case the calculations were not correct. InvType Acquired is used for bookings related to the acquired balance sheet and are not included into match reports.
|
| 10065 |
Fix added in 21 CPV3.2 (KI in 21 CPV3.1)
Fixes the issues with import consolidations that takes longer than 2 minutes to perform. The repeated attempts to order import due to time outs are removed to not fill the import queue with not relevant orders and the default time outs are increased and is also possible to override in SETTING_SETTINGS for very large imports. |
| 10127 |
Fix added in 21 CPV3.2 (KI in 21 CPV3.1)
Fixes the issue using the allocations functionality in AARO. The procedure ’Alloc’ ’Allocations’ is activated in CONS_LOOP if this is implemented and used by you. The problem was that consolidations of all types were failing when ’Alloc’ is activated. |
|
21 CPV3.1 AARO
|
|
New Functionality!
Support have been added to allow export of data from the module Company Information. The export can be done by:
– new retrieve formula ABSGetCompanyInfo.
– Paste data in Paste from AARO.
– AARO Connector. |
|
New Functionality!
It is now possible to specify Accounting Type and Proforma Type in Data Entry Legal. This provides the possibility to handle an acquisition as Proforma and parts of an acquisition could be handled with different accounting types e.g. K3/IFRS. With this you get a better overview of legal bookings directly in the acquisition register. |
|
Extended functionality!
We are extending the input reporting functionality to report on Proforma type directly in input previously only supported in Data Entry/Journals to apply in the consolidated result by journals. Supported for Input, Match and Matrix forms and for Normal, Compact, Matrix, Match reports for reporting in AARO Web Client. Logic also apply to save on defined default input value if the Proforma Type is not added to report definition. |
|
Extended functionality!
We now support defining Accounting Type and Proforma Type in file specifications for the unlicensed text file import to be able to import values other than default Accounting Type or Proforma Type for forms defined with Accounting Type and Proforma Type as input fields. |
| 9782 |
Fixes the issue where we did not apply the logic for saving on default input value for Accounting Type in match reports for match forms where you have Accounting Type defined as input field. The parameter Accounting type was required in the report definition always. |
|
New Functionality!
We have extended the functionality when acquiring groups where we previously did not have support to present both the acquired Subgroup correctly eliminated and at the same time have MainGroup correct. Only one of them could be presented correctly. By a new field ‘Acquiring parent’ it is now possible to define an acquiring parent for different Past Equity IDs on acquired companies in the acquired group and with that determine how the eliminations logic is to be applied in calculations to present both Subgroup and MainGroup correctly. In the upgrade the closest Parent Co will apply as Acquiring Parent for all PE IDs. The upgrade itself will not change this. After the upgrade you can then apply the new logic by defining applicable acquiring parent for the Past Equity IDs in the acquired groups companies and reconsolidate the period. |
| 9885 |
Fixes the issue where Input Function was not applied correctly when ordering an import of a form in Web Import. If the form and the user is defined with the same Input Function but other than ’All’ the Import would still not be performed. |
| 9776 |
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. |
| 9385 |
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 also what the temporarily deactivated Dispose button would 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. |
|
21 CPV3.1 AARO Lease IFRS 16
|
9697 |
Extended functionality!
Fixes the issue where the use of isolated average translation for periods was not supported for Lease |
|
New Functionality!
Introducing an improved model for cost effect distribution of payments. The new model allows for a much more accurate and automated calculation of contracts that have payment dates in the middle of the month. The old model remains as an alternative for existing contracts and some elementary contracts and is the model that will be applied still in the technical upgrade.
In the periodic schedule for payment plans you now have possibility to define if cost effect distribution should be calculated based on a “Scheduled Date” or “Start of Month” with possibility to offset the calculations by a “number of days” in relation to scheduled date. The Start of Month is the old model which based calculations for whole months and that is for some situations too rough could cause unwanted result effects. The new improved model using Scheduled Date will have a much more accurate distribution. Existing contracts can be changed to apply the new model but then effects of the differences that will occur need to be handled. Please refer also to the Configuration notes for information. |
|
New Functionality!
There is a new functionality to handle adjustments of a contract which may be required for mergers and external disposals of companies where our automatic transactions require adjustments. It can also be used for adjustments if contracts in AARO give different data from what has been presented in annual reports before AARO was implemented. You find the functionality under a new button ‘Adjustments‘ in Contract view. An adjustment can be booked to a specific Accounting Type that need to be set up according to the ordinary administration routines for Accounting Types used for Lease. The adjustments are made in TransAmount and translated to LOC using the contracts historic rate . Since historic rate is used you must derive the applicable TransAmount that is to be used for a correct LOC and group value if the contract is registered in a currency differing from the companies reporting currency. Please refer also to the Configuration notes for information. |
| 9572 |
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. |
| 9698, 9017 |
The previous limitation in the Periodic Schedule functionality where payments did not cut off at the contract end date is now handled automatically by the new additional model for cost effect distribution of the payments where such a contract should be set up with a payment plan where you define the Effect distribution using ‘Scheduled Date’. It is an alternative to the previous only model (‘Start of Month’) that looks at whole months and assume that you make a payment in the month that the contract ends with an adjustment for periodic offset used in prepayments or accruals. This means that if a contract ends a date in a month before the payment date there will be an extra last payment affecting Present Value of the contract. The correct model for such contract would be to set up with Scheduled Date. The best practice to handle the KI was to add a row for the last (extra) payment with Payment 0 in periodic schedule or to use manual schedule and delete the last payment so had a way to handle the extra payment in existing contracts. |
