Change Log 2022-03-22

New comparison style reports plus daily sync, billing and performance improvements.

Shem Bogusz avatar
Written by Shem Bogusz
Updated over a week ago

New: Trial Balance Comparison Report

This has been a regular request for those consolidating multiple organisations. This new report, similar to the P&L Comparison and Balance Sheet Comparison allows you to run a consolidated trial balance with individual entities displayed as columns on the one page and a consolidated total.

New: Account Tree & Business Unit Tree on Trial Balance

Both the existing Trial Balance and the new comparison version now also support Business Unit Trees and Account Trees in the criteria.

Business Units Trees can be used to prepare a Trial Balance by Business Unit and prepare a Trial Balance across multiple entities at the department or project level. In addition this functionality will allow users to create consolidated group reports with both detail and consolidated values.

The addition of Account Trees allows you to group and summarise and merge accounts across an organisation group, which is particularly handy if organisations do not have the same chart of accounts.

New: Daily Sync Failure Notifications

All connected organisations in Calxa automatically sync with your accounting data daily. For various reasons it is possible that these daily syncs may fail. Previously you were not made aware of these failures and wouldn't realise the data wasn't up to date until you're signed in and running reports. Now we've introduced failure notifications with configurable options that enable you to enable/disable and or choose who should be notified. We'll notify you when an organisation has failed to sync after 2, 7 and 30 attempts. Check Daily Auto-Sync for configuration details.

New: Pause Subscription

We've now added an option to pause your Calxa subscription. This allows you to pause payments until a future period when the subscription will automatically reactive again.

Improved: Performance Under High Load

In recent months we've had reports of poorer performance during peak periods. It's during these periods that our application infrastructure scales to provide more resources. The idea here is to reduce the impact on customer facing performance. While this scaling has been in place for many years, with recent feedback we've investigated further and identified some parts of the application could not correctly use the additional resources. We've updated these components and tested over a number of trial periods. These changes are now published live and we expect this will have a positive impact on performance during peak load. As always happy to hear your feedback, so drop us a chat message if you would like to share your thoughts, good or bad.

Did this answer your question?