Additional reports now support multi-org consolidation, an option to suppress empty rows when exporting budgets and many small fixes associated with update 2.4.2.


Planned Release Date: Sunday, 2 November 2014.


New: Cost Centre Comparison Supports Multi-Org Consolidation

This template now supports multi org consolidations, displaying each organisations budgeted or actual profit and loss side by side with a consolidated total column. This means there are now only a couple more templates to be added to the multi org library and you can expect those in updates coming soon.


Improved: Exclude Empty Budget Rows in Export

In the previous update we added an option to exclude inactive accounts and now we have added an additional option to exclude accounts that don’t have any budget data. Refer to the knowledge base article Exporting and Importing Budgets for more details.


Fix: MYOB Classic Budget Import

In the previous update a problem was introduced where importing budgets from MYOB Classic files required users to subsequently perform an Organisation update to retrieve actuals which had been removed during the budget import. This has been resolved however there is still one know issue with MYOB Classic budget imports which is isolated to importing Job budgets. We are aware of the issue and expect a fix available soon.


Fix: Custom Unspent Budget Reports

Users who have previously customised an Unspent Budget report template experienced issues running these after the previous update. We have identified the cause and resolved this issue.


Fix: Trailing Spaces in MYOB AccountRight Live Accounts

Improvements we made to importing budgets from excel had an undesirable effect for AccountRight Live users who had trailing spaces in their account names. When they tried updating their organisation Calxa required then to remove the spaces in MYOB but this is no longer necessary.


Fix: Unallocating Accounts in an Account Trees Caused Unexpected Results

Some users reported unexpected results when unallocating accounts in their Account Trees. We have resolved this problem.