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 delivers a series of enhancements and fixes arising from the Frequency Switching (FQSW) programme. It includes improvements to contract reinstatement behaviour, communication queue visibility, bulk file upload processing, API parameter consistency, and a number of regulatory and data accuracy corrections.

ADO #1998193

The System Communications tab now displays queued communications alongside sent communications. Two date columns — Queued Date and Sent Date — clearly distinguish pending items from completed ones. When a queued communication is sent, the existing record is updated rather than a new row being created. The Resend action is disabled for items that are still queued. Historical records that pre-date this change display a dash in the Queued Date column rather than a backfilled value.

ADO #1853912

Custom advance notice letter templates have been updated to include the same enhancements introduced for standard templates as part of the Frequency Switching release. Clients using custom templates will now receive the same improved communication quality as those using standard templates.

ADO #1897547

The FQSW create and edit future version API endpoints now use consistent parameter names aligned with the rest of the DDCMS API. The parameters startDate and numberOfPayments have been augmented with start and numberOfDebits respectively, removing an inconsistency that caused integration complexity for API consumers.

ADO #1912513

Client Admins can now use inline editing to correct date validation errors when a file upload contains 50 or fewer errors. Previously, users were required to download and re-upload the file to resolve date format and invalid date errors. This change allows corrections to be made directly within the platform.

ADO #1954730

The contract payment schedule version history screen now displays the frequency interval (the 'Every' value) alongside the frequency type. Previously, users had to enter edit mode to see the complete frequency details. The version history now mirrors the information shown on the active schedule.

ADO #1986370

When a contract stream is cancelled mid-way through its schedule and subsequently reinstated, DDCMS now restarts the stream using the original payment cadence. The Client Admin is presented with the payment schedule for confirmation and can confirm, cancel, or navigate to create a new version. This ensures the reinstatement process flows logically and preserves the original schedule where appropriate.

ADO #2140497

When DDCMS receives an ADDACS code 3 advice (account transferred to a new bank), contracts now remain in an Active state following the lodgement of the 0N AUDDIS transaction. Previously, the contract was incorrectly set to CreationPending, interrupting collections. Per the Direct Debit Rulebook, the 0N sent following ADDACS code 3 is a lodgement acknowledgement only — the instruction already exists at the new bank via the Current Account Switch Service and collections can continue immediately. This behaviour applies to ADDACS code 3 only; manual bank detail changes continue to set the contract to CreationPending as before.

ADO #2177677

The Bulk Cancel and Archive file upload now permits archiving of a customer where the Direct Debit reference provided is already in a Cancelled state, provided the customer has no other active contracts. Previously, rows with already-cancelled contracts failed validation, requiring manual individual processing. Existing blocking rules remain in place: archiving is still prevented where the customer has future-dated ad-hoc payments or pending Bacs submissions.

ADO #1929198

Retired DDCMS functionality that was previously accessible via bookmarked or direct URLs is now redirected to the appropriate locations in the new user interface. Users attempting to access deprecated pages will be redirected automatically and will no longer be able to access retired features.

ADO #1969123

The contract calendar now correctly displays historical payments for reinstated contracts. Previously, reinstating a cancelled contract caused the calendar to appear empty, even where payments had been collected prior to cancellation.

ADO #2143827

The Gift Aid report now correctly respects the client profile ObfuscateBankDetails setting when displaying account numbers and sort codes. Previously, the report's 'Bank Details' checkbox operated independently of the profile setting, producing inconsistent masking behaviour compared to Custom Reports. The checkbox has been removed and replaced with the same profile-driven logic used elsewhere in the platform.

There are no known issues in this release.

This version will be made available to all clients on the SaaS platform on 6 October 2026 at 07:00 BST.