This release introduces enhanced schedule version and temporary change (patch) management functionality within the Direct Debit and Credit Management System (DDCMS). This feature focuses on improving the validation, restrictions, and user interface for managing patches and contract stream versions.

You can now edit start dates for future schedule versions directly through the user interface, providing consistency with API functionality, and greater flexibility in managing payment schedule changes. There’s no longer any need to delete and recreate schedule versions when only start dates need changing.

There’s an additional field after selecting Edit Schedule Version in the Actions dropdown for any future schedule versions:

If Yes is selected, you’re presented with a date picker to choose the new date:

The system automatically prevents selection of dates within the BACS amendments notice period:

Before confirming, you can review how the start date change affects your payment timeline with a detailed grid showing collection dates and amounts.

All start date changes are automatically logged with full audit details:

Enhanced patch editing capabilities now provide consistent restrictions across all access methods, ensuring data integrity whilst giving appropriate control over different patch types.

New comprehensive validation rules prevent schedule conflicts and maintain payment timeline integrity by blocking incompatible frequency switches and patch operations:

When future patches exist on a contract, the system automatically blocks the creation of new frequency switch contract stream versions that would overlap with or disrupt existing patches. This intelligent validation occurs before any changes are committed, providing clear error messaging that indicates conflicting patch dates and advises on resolution steps. The protection applies consistently across UI operations, file uploads, legacy API endpoints, and new FQSW API endpoints, ensuring a unified experience.

The system prevents patches from being applied or extended when the patch end date would extend beyond any existing future contract stream version start date, regardless of how the change is initiated. This ensures that patch end versions correctly revert to the appropriate contract stream version and future schedule changes are not disrupted by overlapping patches. Payment schedules remain predictable across UI, file upload, and API operations through comprehensive validation that applies to patch creation and modification operations.

Where a future schedule version has an associated patch (temporary change version), it is not possible to delete the version until the patch itself is deleted.

The update will be applied to everyone on our SaaS platform on 18/02/2026.