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.
Version 10.4.16 clears a further backlog of defects. It improves custom reports, customer registration forms, payment history, the Template Library, file upload validation, Bacs report processing and the API. This release contains fixes only.
There are no new features.
Enhancements
There are no enhancements in this release.
Fixes
Mandatory Multi Check List custom questions are now validated on registration forms
ADO #1867300
A client can set a custom question of type MCL as mandatory. Before this release, a customer could continue to the next page of the registration form without selecting an option. The form now shows an error until a value is provided. This applies to the current and the legacy registration forms.
Custom reports run when a column name starts with a space
ADO #1897542
Renaming a column in a custom report so that it started with a space (for example " DDRef") caused an application error when the report was run. Leading and trailing spaces are now removed from column names and the report runs as expected.
Disbursement contracts no longer appear in Contract custom reports
ADO #2037551
Custom reports based on Contracts included disbursement contracts. These contracts are now excluded. Custom reports based on other record types are not changed.
Creating a contract through the API without paymentDayInMonth
ADO #2069988
A POST request to create a contract on a monthly, quarterly or annual schedule returned an unhelpful 400 response when paymentDayInMonth was not sent. The collection day is now taken from the contract start date. If paymentDayInMonth is sent, the value you send is used.
Direct Debit Guarantee hidden for Direct Credit only accounts
ADO #2101389
The Direct Debit Guarantee was shown on the registration form for client accounts set up as Direct Credit only. The advance notice days in the text were also incorrect. The Guarantee is no longer shown on the registration form or the confirmation page for these accounts. It is still shown for Direct Debit accounts.
Template Library sorts correctly by Created Date
ADO #2109496
Sorting the Template Library by Created Date gave an incorrect order. Templates are now sorted by date, oldest to newest or newest to oldest.
Collections report shows the correct date while the payment job runs
ADO #2120492
While the payment job was running, the Collections report could show a submission date of 01/01/0001. The report now shows the correct date.
Deleting a payment twice no longer causes an error
ADO #2256688
On the payment history page, deleting a payment that was already deleted caused an application error. The delete buttons are now disabled after the first delete request is sent. If the payment is already removed, the page reloads without an error.
SD API: quarterly payers keep their frequency when updated
ADO #2596831
Updating a payer on a quarterly schedule through the SD API changed the payer to monthly, every 3 months. The payer now keeps frequency type Q and frequency factor 1. The frequency_factor value is now also returned in payer details when it equals 1.
SD Direct credit lines accept shorter payment references
ADO #2597098
Credit lines in an SD Direct file failed validation if the reference was shorter than 6 characters. Credit line references can now be blank, or up to 18 characters long. Debit lines still require a reference of 6 to 18 characters.
Long Bacs report messages no longer stop reports being applied
ADO #2604966
A Bacs report record with a long reason message could stop the report being applied. Payment comments are now limited to 200 characters. A shortened comment ends with "..." and keeps the reason code and explanation at the start. The full text is kept in the outcome log. When a payment is represented, the new comment is added to the existing comment and is not repeated.
SD API: get_collection_report shows pending ad hoc payments as rejects after cancellation
ADO #2721164
When a contract with pending ad hoc payments is cancelled, those payments are again shown in the Rejects section of the get_collection_report endpoint only after they have failed to be submitted as a result of the contract being in the cancelled state at the point of payment submission.
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 Tuesday, 13 October 2026 between 07:00 and 07:30 BST.