When a Direct Debit contract had already taken some payments and a user tried to edit the schedule back to its original number of payments (for example, extending a contract that had taken 5 of 10 payments back to 10), the system incorrectly blocked the change with a "cannot be the same as the current version" error. This has been fixed so the schedule can be edited back to its original value as expected.

When a customer signed up through Eaziweb, answered custom questions, and then selected the Gift Aid option, their custom question answers were not saved against the new customer record. This has been fixed so custom question answers are retained regardless of whether Gift Aid is selected.

0N Bacs submissions were only including Direct Debit instructions created up to an earlier cut-off point each day, rather than all instructions created right up until the submission job ran. In some cases this left insufficient time for the Direct Debit instruction to lodge before the first payment date. This has been fixed so Advance Notices include instructions created up until the submission job runs.

When viewing payments related to a disbursement report and sorting by a column (for example amount), the chosen sort order was not carried through when the data was exported to XLS or CSV. This has been fixed so the sort order is retained in the exported file.

In the file upload template library, dragging a field into the selected columns area when creating a new template did not work — the field was released immediately rather than being held for dragging. This has been fixed so fields can be dragged into place as expected.

When changing a schedule’s frequency type (for example from Monthly to Fortnightly), the "Every" field remained at its default value of 1 instead of updating to match the newly selected frequency, which could result in a schedule being configured differently from what the user intended. This has been fixed so the "Every" field is set correctly when the frequency type is changed.

For clients where the Welsh language / bilingual Direct Debit form feature is not enabled, files downloaded from File Upload → Uploaded Files incorrectly included an additional LanguagePreference column that was not present in the original uploaded file. This has been fixed so the downloaded file matches the original for clients without this feature enabled.

A contract could be created against the wrong client when the customer belonged to a different client within the same shared client group, meaning the contract could be found via search but would not open against the customer record for further action. This has been fixed so contracts are created against the correct client.

Certain new-debits import files were failing with an unexpected error, affecting some files on some clients — the issue did not occur once a file was reduced to under 100 rows. This has been fixed so larger files import successfully.

There are no known issues in this release.

This version will be made available automatically to all clients via our cloud infrastructure on 1 September 2026. No action is required.