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 version clears a further backlog of defects. It improves Advance Notice Letters, Bacs report history, schedule reinstatement, the SD API, 0N advance notice payment checks, payment submission after an account change and Direct disbursals. This release contains fixes only. There are no new features.

There are no enhancements in this release.

ADO #2660477

If the schedule of a contract was changed before the contract started, and the customer's bank details were then changed, the Advance Notice Letter (ANL) for the bank details change was not created. The ANL is now created.

ADO #2808563

When a contract on a Take Number of Debits schedule had collected all of its payments and was then reinstated, the completed schedule ran again. This happened when the contract was reinstated from the portal and when it was reinstated by ADDACS code R. The contract is now live with no schedule after it is reinstated. Restart Schedule on a completed Take Number of Debits schedule is rejected with the message “Number of payments must be between 1 and 999 for this Termination type.” Schedules that were only partly collected keep their remaining payments.

ADO #2808722

A charge file status request by filename returned HTTP 404 when the filename ended in .csv. This applied to the charge_file and v1.1/charge_file endpoints. The request now returns the status of the most recent upload that matches the filename. Lookup by import ID is not changed.

ADO #2820900

Sending the same update call to the SD API again created a new contract stream version and showed “Payment Schedule Version amended” in the contract updates, even though nothing had changed. Update calls that make no change no longer create a new contract stream version or an amendment notice.

ADO #2834203

A first payment could be marked unpaid with the comment “Due to the Direct Debit being within the 0N advance notice period, the payment was marked unpaid”, even though the 0N had been lodged in time. This happened when a contract was created just before the 13:00 cut-off. The 0N is created a few minutes later and lodged at the 13:10 run on the same day. The 0N blocking window is now counted from the 13:10 run, not the 13:00 cut-off. The 0N calendar displays use the same window.

A 0N raised at or after 13:10 is lodged on the next working day and is counted from then, so a payment that is too close to the 0N is still blocked. Migrated 0Ns, the start date check and the payment comment text are not changed.

ADO #2834823

After an account change, a payment could be marked unpaid without being submitted. An account change is no longer a reason to leave a payment unsubmitted. The payment is submitted to the original bank until the new Direct Debit Instruction has had time to lodge.

ADO #2846724

Some Bacs INPUT report entries with the message “Individual Item Limit Exceeded” are warnings only (type HIGHLIGHT). The item is not rejected and the payment is collected. Direct treated these warnings as failed payments and deducted them from the client disbursal. HIGHLIGHT entries are now information only. The payment is not marked unpaid and nothing is deducted from the disbursal. Items that Bacs rejects, and that appear on ARUDD reports, are still deducted.

There are no known issues in this release.

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