Introduction
This document outlines all you need to know about this version of the Direct Debit Platform. It provides a brief summary of the changes and, further in the document, more detailed information on each item.
This release is a continuation of live-ticket bug fixes. It addresses a number of issues across the platform including corrections to payment scheduling behaviour, API response accuracy, the customer registration form, and file upload template configuration.
Enhancements
There are no enhancements in this release.
Fixes
Mandatory Custom Questions Ignored When Creating File Upload Templates
ADO #274967
When creating a new file upload template in DDI Setup, mandatory client custom questions were not being enforced. It was possible to save a template without including required questions in the Chosen fields list. This has been corrected; mandatory questions are now validated on save and the template cannot be created without them.
Last Working Day of Month Not Correctly Applied to Schedules and Contracts
ADO #699672 / 1746588
Two related issues have been resolved together. First, when using query parameters to pre-select a payment day on the Direct Debit registration form, passing PaymentDay=99 (intended to select 'last working day of the month') was incorrectly selecting 'last day of the month' instead. Second, contracts linked to a schedule configured with 'last working day of the month' were not inheriting that setting, making it impossible to update those contracts via System Update Contracts with the correct day type. Both issues have been corrected.
API: Empty StatusExplanation Field for Pending-to-Activate Contracts
ADO #1837571
The GET contract API endpoint was returning an empty StatusExplanation field for contracts in a pending-to-activate state. The field now returns the correct explanation text for these contracts.
API: Incorrect Error Response When Updating Adhoc Contract Amount
ADO #2057898
When using the PATCH contract amount API endpoint to update the amount on an adhoc contract, the API was incorrectly returning a validation error stating that the new details were the same as the existing payment schedule version details, even when a different amount was supplied. This has been corrected and the endpoint now processes valid amount updates as expected.
Transaction Summary Report: 'Include Not-Presented' Tooltip Text Updated
ADO #2145327
The tooltip displayed next to the 'Include not-presented' filter on the Transaction Summary Report contained outdated guidance that no longer accurately described the scenarios in which a payment can appear as unpaid and not-presented. The tooltip text has been updated to reflect current platform behaviour following the Frequency Switching work.
Duplicate Title Field Displayed in Registration Form for Existing Customers
ADO #2278448
When creating a new contract for an existing customer via the registration form, the Title field was being displayed twice. This has been corrected; the Title field now appears only once.
API: Start Date and Payment Plan Update Behaviour Corrected
ADO #2311080
An issue was identified in the API where updating a contract's start date and payment plan via a specific API payload was not behaving as expected. This has been investigated and corrected.
Known Issues
There are no known issues in this release.
How This Version Will Be Made Available
This version will be made available to all clients on the SaaS platform on 15 September 2026 at 07:00.