Contract streams now display "First Due" and "Next Due" dates instead of "Start Date," making it clearer when payments are actually due to be collected. When editing a schedule version, the label "Date of Change" is used in place of "Start Date" to distinguish version changes from the original contract activation.

The edit schedule screen now offers an "Adjusted Payment" option (previously "Next Payment") which, for schedules where collections occur every 3 or 6 months, recalculates the future collection cadence from the adjusted date. A new optional "AdjustedPaymentDate" column in file upload provides the same capability via bulk updates.

The contract stream displayed "Start Date" on the payment schedule row, which could be confused with the payment collection date. The Start Date is the date the schedule becomes or became active — from which, your profile settings (first direct debit and look-forward days) determine when payments can be taken.

What Happens Now:

"Start Date" has been moved to the Direct Debit line, where it continues to represent the date from which your profile settings determine when payments can begin. The payment schedule row now displays "First Due" showing the actual first payment collection date and "Next Due," showing the next scheduled collection date consistent with the schedule pattern. Both dates accurately reflect the dates based on your schedule configuration.

When creating a new contract stream, the field is labelled “Start Date.” When creating or editing a contract stream versions on an existing stream, the field is now labelled “Date of Change” to clearly distinguish the effective date of a version change from the original contract start date.

The edit schedule screen used the label “Next Payment” for adjustment options. For contracts with a collection frequency where “Every” was greater than 1 (e.g. monthly every 3 or every 6), it was not possible to change the collection date month; the system always retained the original collection cadence, even when a different collection month was needed.

What Happens Now:

“Next Payment” has been renamed to “Adjusted Payment” across the section header, question text, and field labels within the edit schedule screen.

When editing a contract with an “Every” value greater than 1, selecting “Yes” to adjust the payment now displays a note: “Do you want to adjust the next payment date or amount? Note: this will recalculate future collection cadence.” This recalculation note does not appear when “Every” equals 1.

Adjusting the payment date on contracts where “Every” is greater than 1 now correctly recalculates the future collection cadence from the adjusted date. This resolves the issue where clients were unable to change the collection month for schedules such as monthly every 3 or every 6.

A new optional column, “AdjustedPaymentDate,” is now accepted in file upload templates. When provided future collection dates are recalculated from the adjusted date based on the frequency and “Every” value. If the column is not included, the file remains valid and the existing next payment date is retained.

The update will be applied to everyone on our SaaS platform on 06/05/2026.