Skip to main content

Access PaySuite DDCMS 10.4.11 - Maintenance Release

A maintenance release for our Direct Debit Product

M
Written by Matt Harris

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.11 is a maintenance release. It addresses a range of defects across the platform including fixes to ARUDD processing, collection report generation, file processing, bank detail validation, user permission handling, AUDDIS processing, and customer setup flows.

Enhancements

There are no enhancements in this release.

Fixes

Bank reference update: 0C cancellation instruction not sent for old reference

ADO #1866087

When a bank reference was updated, the 0C cancellation instruction was not being generated for the previous reference. This has been corrected to ensure the 0C is sent as required.

Unapplied ARUDDs where Direct Debit reference contains an apostrophe

ADO #1887172

Where a payer's Direct Debit reference contained an apostrophe, the platform was not matching the ARUDD return correctly. Bacs returns the reference with the apostrophe replaced by a space, and the platform was not recognising this as the same payer. The matching logic has been updated to handle this correctly. This fix applies to ARUDD processing and other return file types. There is no visible change in the user interface.

Disbursals incorrectly generating collection reports

ADO #2067138

Disbursal transactions were incorrectly triggering the generation of collection reports. This has been resolved and collection reports are now generated only for the appropriate transaction types.

Collection report pagination displaying incorrect results

ADO #2119536

Pagination on the collection report was returning incorrect results, causing records to be missed or duplicated across pages. This has been resolved.

Customer title field displaying '---select---' instead of saved value

ADO #2323389

In certain scenarios the customer title field was displaying the placeholder text '---select---' rather than the saved value. This has been corrected.

Ad hoc letter communications generated with raw HTML in the body

ADO #2331348

Ad hoc letter communications were being generated with raw HTML markup visible in the document body rather than rendered content. This has been corrected.

Cross-client schedule selection error on customer setup flow

ADO #2366582

During the customer setup flow in a grouped client scenario, it was possible for a payment schedule belonging to a different client to be selected, causing an error. The schedule selection has been corrected to enforce client-scoped results only.

File upload: First Name incorrectly enforced as mandatory

ADO #2378446

During bulk customer file upload, the First Name field was being enforced as mandatory even where the contract type permits it to be optional. The validation has been corrected to align with the Create Customer rules.

Quick search logging out View Only and Add Only users

ADO #2456563

Users with View Only or Add Only permissions were being forcibly logged out when using the quick search function. This has been fixed and those users can now search without being logged out.

ARUDD not applied where contract reference had changed

ADO #2461684

An ARUDD return was not being applied to the correct contract because the contract reference had changed since the original payment was submitted. The matching logic has been updated to handle this scenario correctly.

Archive and Send 0Cs stuck at processing

ADO #1996931

For a specific client configuration, Archive and Send 0C instructions were becoming stuck in a processing state and not completing. This has been resolved.

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 22 September 2026 between 06:00 and 07:00 BST. No downtime is expected.

Did this answer your question?