Release Notes – v3.2.3-rc1

08 July 2026 (070a4e0)

EFinancials reports time out with "Failed to fetch" on date ranges beyond a few days

V3-228

Fixed an issue where EFinancials reports (EFinancials, EFinancials - With Order Details, and Sales & Income - With Order Details) would fail with a "Failed to fetch" error when run over larger date ranges. The underlying cause was a slow database query introduced in a previous update, which caused the reports to exceed timeout limits. This has been resolved by reverting the problematic query, restoring reliable report generation across all date ranges.

This fix will only address Efinancials in future runs, it does not correct any data in the past.

HRP - V3 Rollout - Variance against an API Booking DVOSUV4WCVS6O

V3-230

This issue was not explicitly fixed but a fix was implemented as a byproduct of V3-228. A full explanation is provided below.

We've traced the variance on order DVOSUV4WCVS6O to an interaction between two recent fixes: one that correctly records a reversal entry when a deferred-invoice (API/trade partner) booking is cancelled, and a separate change that was excluding cancelled orders from the payments side of the EFinancials report. Together, these meant a cancellation's reversal entry could disappear from the payments side while still appearing on the sales side, creating a variance when the report was run for a single day rather than the order's full lifespan. Nothing was wrong with the underlying transaction data or your reconciliation, purely how the report combined these two entries on a given day.

We've reverted the conflicting change as part of the efinancials performance optimisation (FD5275 / Jira: V3-230). The cancellation now correctly produces two entries (the original charge and its reversal) that net to zero, so a single-day EFinancials run for this type of cancellation will reconcile correctly.

I'll add a note to the release notes to make clear that we didn't retrofix this by changing any data, the report simply reports the underlying data more accurately as a result of the fix in V3-230.