Change Log 2023-11-23

Report builder improvements make it easier to switch between reports, either in your bundle or just while exploring to find similar reports.

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

Improved: Report Builder

Following on from the latest changes to the report library layout we've continued to improve the reporting experience. Now when configuring reports in the report builder you can explore other reports without returning to the library. Similarly, when configuring reports in a bundle, you can easily switch to other reports in the bundle without leaving the builder.

The report builder layout is consistent in both cases with the primary actions to refresh or save the report. If the report is not yet saved to a bundle the save action prompts to save to a bundle. Additionally, for reports with multi-period and multi-column variations, we have moved these directly into the report criteria. No longer do you need to go back to the template library to select a different number of report periods.

See the following help article and videos for additional details.

New: Transaction Sync

We're continuing to work on improved sync logic for our Xero, MYOB & QuickBooks integrations. This new sync logic is based on transactions , here are some of the main reasons why we are making this change:

  • Faster Sync on updates: After the first sync, which gets all the transaction data, you only need to sync the changes that occurred since the last sync. Previously we ran reports in all periods to detect changes.

  • More robust method for syncing combinations (Xero and QuickBooks): We have developed a new algorithm that can handle complex tracking category combinations and ensure accurate data transfer between systems.

  • Balance sheet movements synced on tracking categories without additional sync time: No additional requests to Xero are required to build balance sheet movements.

  • More features in the future will rely on transaction data: For example, Aged Payables/Receivables reports on consolidated groups and transaction details are just 2 of many ideas for the future.

We'll continue to add progress updates in these change logs when key milestones or changes are made.

Progress Updates

Xero

After a successful beta testing period we've now begun converting all Xero organisations to the new transaction sync mode. Most of you won't notice this change as your daily sync will continue to happen on the daily schedule and your regular reporting will remain unchanged. Essentially, we're just syncing and building the data in a different way. There is however one key change to the way we handle Unrealised Gains/Losses and Bank Revaluation.

Unrealised Gains/Losses & Bank Revaluation

Since Xero do not record a transaction for currency revaluation, we need to perform supplementary syncing steps to reconcile key accounts related to currency revaluations. To optimise the required sync time, Calxa allocates all currency revaluations to the Unassigned Tracking Category option.

What this means for your reports:

  • An Organisation Trial Balance will reconcile to Xero.

  • Consolidating all Tracking Categories will reconcile to Xero.

  • Individual Tracking Category options will not have Unrealised Gains/Losses & Bank revaluations recorded in Calxa reports.

Note: πŸ’¬ if you require currency revaluations to be reported at the tracking category level, please let us know via the chat in the bottom right of this page.

MYOB

The bulk of MYOB development is complete and we're now looking for beta testers or early adopters to migrate to the new transaction sync process. One additional benefit for MYOB users who enable transaction sync is you'll now have the ability to report on data where no Job has been assigned. For the transaction sync we've implemented a special job called Unassigned which can then be used for reporting.

πŸ’‘Early Access Available: if you're interested in gaining early access let us know via the chat in the bottom right of this page.

QuickBooks

QuickBooks Online is currently in the early development stages for a transaction based sync.

Did this answer your question?