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 adds an optional Payment Type column to the New Represents file upload template. Client Admins can now choose, row by row, whether to represent the regular payment or the represent payment. Rows no longer fail when two payments on one contract share the same due date.
Enhancements
Optional Payment Type column on the New Represents template
ADO #2798537
Clients can now add an optional Payment Type column to a New Represents template in the Template Designer. The column states, for each row, which payment to represent. The accepted values are "Regular" and "Represent". The values are not case sensitive.
The column is optional. You can save a template without it.
The Payment Type value for each row is shown on the File Upload row details page.
Existing saved templates, the existing columns and other file upload types are not changed.
Choose the payment to represent when two payments share a due date
ADO #2798538
Before this release, a row failed with the error "Multiple payments found for row" when a regular payment and a represent payment on one contract had the same due date. The upload now uses the Payment Type in each row to choose the payment to represent.
Payment Type is "Regular": the regular payment is represented. The represent payment is not changed.
Payment Type is "Represent": the represent payment is represented again. The regular payment is not changed.
Payment Type is blank and more than one payment is due on the Due Date: the row is rejected and a message explains that the Payment Type is required. No payment is changed.
Payment Type is blank and only one payment is due on the Due Date: the row works as it does today.
No payment of the chosen type exists on the Due Date: the row is rejected with a message that no payment of that type was found. No payment is changed.
Payment Type is not "Regular" or "Represent": the row is rejected with a message that explains the accepted values. No payment is changed.
The choice is made per row. There is no setting at upload level. Existing checks stay as they are, including the Represent Due Date check against the contract schedule, the Bacs date rules and the remaining retries check. Files and templates without the Payment Type column keep working with no change. This applies to all clients that use the New Represents template.
Fixes
There are no fixes in this release.
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 27 October 2026 at 07:00 GMT.