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 covers the SD API v21 feature set. The majority of items are bug fixes to the SD API integration layer, together with one enhancement to the Future Payments Due Report. Several fixes relate to specific client-reported issues with payment scheduling, amount calculation, and data retrieval via the API.
Enhancements
Future Payments Due Report — Performance and Reliability Improvements
ADO #2403726
The Future Payments Due Report has been improved to address performance and reliability issues. Changes include fixes to the data retrieval loop, prevention of duplicate report tasks being queued, and improvements to the report generation process to ensure accurate and timely results.
Fixes
SD API: Charge File Response Not Delivered to Integrated Client Systems
ADO #2262880
An issue was identified where the charge file response generated by the platform was not being delivered to integrated client systems (such as FinDock). This has been resolved to ensure charge file responses are reliably transmitted.
API Date Filter ('From' Field) Off by One Hour
ADO #2273465
When using the 'from' date/time parameter in API queries, records created up to one hour before the specified time were incorrectly included in results. This was caused by a timezone handling error and has been corrected so that date filtering returns only records created at or after the specified datetime.
Inline Editor: Originating Account Name Truncated at 18 Characters
ADO #2313109
The inline editor applied an incorrect 18-character limit to the Originating Account Name field during file upload error correction. The field now accepts the correct maximum length.
SD API: Debit and Regular Amounts Incorrectly Combined into Initial Amount
ADO #2323940
When creating a variable Direct Debit with both a regular amount and an ad-hoc debit on the start date, the platform was incorrectly adding the two amounts together to produce the Initial Amount. Each amount is now handled independently as intended.
SD API: Amending Regular Amount Caused First Payment to Be Taken Again
ADO #2328653
Amending the regular amount on a contract via the SD API was incorrectly triggering the first payment to be collected again. This has been resolved so that amount amendments do not affect previously scheduled or collected payments.
SD API: Contract Returned Without Version History
ADO #2348463
In certain scenarios, contracts retrieved via the SD API were returned without any version history. This has been corrected to ensure version data is always included in the response.
API: Payments Endpoint Using Incorrect Default Pagination
ADO #2349232
The client payments endpoint was applying an incorrect default page size when no pagination parameters were supplied. The correct default pagination is now applied consistently.
API Date/Time Filtering Error Affecting Specific Clients
ADO #2365813
A date/time filtering error was causing incorrect results to be returned for certain clients when querying records by date range. This has been resolved.
SD API: Change of Collection Frequency or Amount Causing Incorrect Payment Scheduling
ADO #2367802
Changing the collection frequency or amount via the SD API was in some cases causing payments to be scheduled incorrectly. This has been resolved to ensure payment schedules are recalculated correctly following an amendment.
SD API: Weekly Contracts Could Not Be Created with a Weekend Start Date
ADO #2387818
Attempting to create a weekly Direct Debit contract with a Saturday or Sunday start date via the SD API was rejected. The platform now correctly handles weekend start dates by advancing the first collection to the next working day.
SD API: Sending Unchanged Start Date or First Amount Caused an Error
ADO #2390859
When an API request included the existing start date or first amount without changing them, the platform returned an error. Requests that include unchanged values are now handled correctly.
DDCMS Direct: AUDDIS File Rejected When Originating SUN Details Omitted
ADO #2393150
AUDDIS files submitted via DDCMS Direct without an originating SUN sort code and account number were being rejected with a 'No payment lines matched' error. The platform now correctly prompts the user to select the relevant SUN when these details are absent from the file.
SD API: Payment Deleted via API Even After Submission to Bacs
ADO #2398156
The DeleteViaAPI function was incorrectly allowing payments to be deleted even after they had been submitted to Bacs. Submitted payments are now protected from deletion via the API.
SD API: Data Dump Returning Obfuscated Bank Details When Both Options Enabled
ADO #2433775
When both the 'Include Account Details' and 'Obfuscate Bank Details' options were enabled, the data dump endpoint was returning obfuscated (masked) bank details rather than the full account information. The two settings now operate independently and correctly.
SD API: Collection Report Incorrectly Excluding Successfully Submitted ARUDD Payments
ADO #2437188
The get_collection_report endpoint was excluding ARUDD (Automated Return of Unpaid Direct Debits) payments that had been successfully submitted, causing them to appear missing from the report. These payments are now correctly included.
Generated First-Time Payments Not Submitted When 0N Created Close to Payment Date
ADO #2557177
In scenarios where a 0N (new instruction) was created close to the generated first payment date/time, the first-time payment was not being submitted. This has been resolved to ensure first-time payments are submitted correctly in all timing scenarios.
SD API: Successful Collection Report Excluding Payments Affected by 0N Timing
ADO #2594002
The get_successful_collection_report endpoint was excluding payments that were not submitted due to 0N creation timing. These payments are now correctly reflected in the report.
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 08 September 2026 at between 07:00 BST and 07:30 BST.