What's New
This release changes how the system handles Contract Streams that reach their natural end. Previously, when a Total Number of Debits or End on Exact Date contract stream completed, the contract stream was automatically cancelled. Now, the contract stream remains active after schedule completion, allowing you to add a new payment schedule version directly without needing to restart the contract first. This applies across the UI, API, and file upload, simplifying ongoing collection management on Active Direct Debit Instructions.
Stream End behaviour changes
When a payment schedule reached its natural end — either the Total Number of Debits had been completed, or the End on Exact Date had been reached — the system automatically cancelled the contract stream. This meant that if you wanted to continue collecting payments from the same payer on the same Direct Debit Instruction, it was not possible to simply add a new schedule version to the existing stream. You would first need to restart the cancelled contract before adding a new version.
What Happens Now:
When a payment schedule reaches its natural end, the contract stream now remains in an active state. No further collections are generated beyond the termination point, but the stream is no longer cancelled. This means you can add a new payment schedule version directly to the existing stream — via the UI, API, or file upload — without needing to restart the contract first.
Key changes:
Contract streams now remain active after a payment schedule reaches its natural end (Total Number of Debits completed or End on Exact Date reached)
You can add a new payment schedule version (via UI, API, or file upload) with a future start date directly to the existing stream
When the new version’s start date is reached, the system automatically transitions to collecting on the new version
Manual cancellation (cancel now, scheduled cancel with given notice) and BACS report-driven cancellation remain the only ways to cancel a contract stream
Important Note for Existing Contracts:
For contracts where the stream was already cancelled due to a natural schedule end prior to this release, you will still need to restart the contract first (Step 1) before adding a new payment schedule version (Step 2). This applies across UI, API, and file upload. Going forward, newly completed schedules will not cancel the stream, so this additional restart step will no longer be required.
How To Access This Update
The update will be applied to everyone on our SaaS platform on 07/04/2026.