Skip to main content

Changelog - 16 November 2026

Our release introduces enhancements to both APIs and reporting.

The Driver API now performs duplicate-driver checks during create and update requests to help prevent duplicate records, while the createContractPaymentSchedules API now blocks updates when contract payments are being edited on screen to avoid conflicting changes.

Additionally, screen reports can be made available from the Contracts Insurance tab, making it easier to generate and configure insurance-related reports without development effort.


🗓 Upcoming release schedule change

Our next sprint will run for three weeks instead of the usual two. A two-week sprint would have placed the release over month end, which is a busy processing period.

Extending the sprint avoids any disruption during this time.

The next release is scheduled for 07/12/2026.


🔌 Duplicate driver warnings now apply to Driver API create and update

The Driver API now checks for duplicate drivers the same way the Driver Contact screen does, giving integrations a consistent way to avoid creating the same person twice at a client.

When creating or updating a driver, the API now checks for:

  • A driver at the same client with the same given name and surname

  • A driver at the same client with the same employee number

To ensure results are meaningful and easy to consume:

  • A duplicate is returned as a warning, not a hard refusal, since two different people can share a name. Resend the request with override_warnings_flag set to yes to proceed.

  • Where both a duplicate name and a duplicate employee number are found, both are reported together and one override clears both.

  • In a list, each driver carries its own override, and a refused driver is reported by its position in the request.

  • A refused list is never part-saved: nothing in the list is created or updated.

  • Updates are checked on the driver as it will be after the change, so any update to a driver who already shares a name at the client needs the override, even for an unrelated field.


🔌 createContractPaymentSchedules now waits while payments are being varied or inserted on screen

Adding a payment line through the createContractPaymentSchedules API is now refused while someone has Vary or Insert open on that contract’s Contracts / Payments tab, in the same way it already is during Payments Edit. This stops a line added through the API from being changed or removed when the on-screen Vary is saved.

This applies when:

  • Vary, Insert or Edit is open on Contracts / Payments for the contract

Additional Details

  • The API returns 423 (Locked) and adds nothing. Retry once the on-screen form has been saved or cancelled.

  • Editing only the Contracts / Finance tab does not block the API.

  • Vary, Insert, Edit and Delete on the Payments tab work as before, and the lock is released on Save or Cancel.


📊 Screen Reports now available on the Contracts Insurance tab

You can now run Screen Reports from a contract’s Insurance tab, the same way as on the Order, Finance, Lease, Payout and FBT tabs. Insurance-related reports can be added through configuration rather than development work.

This is available when:

  • Viewing the Insurance tab of a contract (not in edit mode)

Additional Details

  • A new Report selector sits before the Format selector. Insurance Declaration is listed first and selected by default, followed by any active Screen Reports set up for the Insurance tab.

  • The Format selector changes to match the selected report.

  • Insurance Declaration’s content, layout and file name are unchanged.

  • Until a Screen Report is set up for the Insurance tab, the selector lists Insurance Declaration only.