This release introduces Configurable Represents, a new capability that allows you to re-present ARUDD code 0 (insufficient funds) returned Direct Debit payments directly within DDCMS. You can configure retry timing and attempt limits for your organisation, manually trigger a re-presentation from the payment history for any eligible payment, and use API endpoints to manage settings and trigger represents programmatically.

Once Configurable Represents is enabled for your organisation and your retry settings are configured, payments returned unpaid with ARUDD code 0 (insufficient funds) are automatically represented — no manual action is required. Each retry is scheduled for your configured number of retry delay days (working days) after the return, and the system will make up to your configured number of attempts.

Every automatic attempt must fall within 1 calendar month of the original payment date. If the next attempt would fall outside this window, or all configured attempts have been used, no further retry is scheduled and the payment remains Unpaid with an explanatory note added. Returns for any reason other than ARUDD code 0 are not automatically represented.

Configurable represents, will be available for you to enable via the "View Client details" link in the Quick Search panel. This is available across multiple sections of the system including Schedules, Communications, BACS, and Cancellation Templates. When using the Customers tab, Quick Search is only visible once you have opened an individual customer's profile.

Please note: Configurable Represents is a chargeable feature. A notice confirming this is displayed when you first tick the checkbox to enable this.

Two fields control your retry behaviour:

Both fields must be completed before the Save Retry Settings button becomes available. If your chosen combination of delay days and number of attempts is likely to exceed the Bacs 1 calendar month limit from the original payment date, a warning is displayed so you can adjust your settings before saving.

A Represent button is available on eligible payments in the Payment History tab of a customer record. It appears on payments with a status of Unpaid, provided the Direct Debit Instruction is still active, the payment has not already been represented, and the payment is still within 1 calendar month of the original payment date. Manual represent is available whether or not automatic retries are enabled for your organisation, so you can represent a payment as a one-off.

Clicking Represent opens a Schedule Retry Payment modal showing the payment reference, original due date, and amount, along with a date picker to select a collection date. The last eligible date is shown for reference.

When a non-working day is selected, you should see the below pop up:

Once you select a date and click Submit:

A new Represented Payment appears in the Payment History grid with a status of Pending and your chosen collection date and can be edited/deleted, if necessary, unless you have reached the look forward days.

The original payment status updates to Represented

The retry is automatically included in the next Bacs submission file on the scheduled date — no further action is needed from you

Three API endpoints are available to support Configurable Represents. These allow you to retrieve and update your retry settings, and to trigger a re-presentation for a specific payment programmatically.

Prerequisites

Authentication

All requests must include your API key as a header:

apiKey: {apiKey}

Returns the current retry configuration for your client.

GET /api/v3/client/{clientPrefix}/unpaidPaymentRetrySettings

Parameters

Successful Response (200 OK)

Example response:

{

"AllowRetryFailedPayments": true,

"RetryPaymentsDelayDays": 10,

"FailedPaymentRetries": 2

}

Updates the retry configuration for your client.

PATCH /api/v3/client/{clientPrefix}/unpaidPaymentRetrySettings

Parameters

Request Body (JSON)

Successful Response: 200 OK. Returns the updated retry settings.

Triggers a re-presentation for a specific failed payment. The payment must be eligible: within 1 calendar month of the original payment date, the Direct Debit Instruction must be active, and the payment must not already be in a Pending or Paid status.

POST /api/v3/client/{clientPrefix}/contract/{contractId}/payment/{paymentId}/retry

Parameters

Request Body (JSON)

Example request body:

{

"ProcessingDate": "2026-06-21T00:00:00.000Z"

}

Successful Response: 200 OK.

Error responses:

API Documentation: The full API specification will be published to the DDCMS API documentation site upon deployment: https://api-docs-ddcms-v3.accesspaysuite.com/

The update will be applied to everyone on our SaaS platform on 30/07/2026.