Skip to main content

Changelog

Follow new updates and improvements to Catch-e.

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.

Changelog - 04 November 2026

Our latest release introduces security improvements, enhanced API quote creation rules, and several automation features, including copying User Defined vehicle variants, automated insurance rate updates, and automatic fuel card creation during fuel imports. These enhancements strengthen platform security, improve consistency, and reduce manual administration across key workflows.

Please note: Due to the Melbourne Cup public holiday in Victoria, deployment will occur on Wednesday, 4 November 2026.


🛡️ Security Update: Recently Disclosed PHP Vulnerabilities

Our engineering and security teams have reviewed the Catch-e platform against the recently disclosed PHP vulnerabilities and have taken the following steps:

  • The Catch-e API and Driver Portal have been updated to a patched PHP release, and the affected PHP functionality has been disabled.

  • Containerised services have been rebuilt on the latest patched PHP releases.

  • The Catch-e application is assessed as not affected by one of the vulnerabilities. It is also protected by our web application firewall, which includes AWS-managed rules that detect and block attempts to exploit these vulnerabilities.

  • Firewall protections are updated automatically as AWS releases new detections.

We’ll continue to monitor these vulnerabilities and update our protections as part of our ongoing security program. Thank you for your patience and continued trust while we completed this work. If you have any questions, please contact Catch-e Support.


🔌 createQuote: Contract Type Inclusion Rules

The createQuote API now applies the Contract Type’s Inclusion settings when a quote is created. This also covers simulate and simulate-and-compare. Quotes created through the API now match the Contract Type’s configuration, and callers no longer need to know which Inclusions are preselected.

  • Inclusions the Contract Type marks as unavailable are rejected, however the request names them.

  • Preselected Inclusions with one applicable plan are added automatically when the request doesn’t mention them.

  • A Preselected Inclusion with more than one applicable plan must be given a plan or excluded, or the quote isn’t created.

  • Inclusions excluded for the client or vehicle are rejected, however they’re named and whether or not they’re marked as included.

Additional Details

  • A request that already includes or excludes a Preselected Inclusion is now honoured as sent. Previously Catch-e overrode it.

  • A Preselected Inclusion that’s excluded for the client or vehicle is no longer added and no longer causes the whole request to fail.

  • Suspended Inclusions and inactive plan versions are never added automatically.

  • The inclusionCodeNotAllowedForContractType error key has been retired.

  • The request and response formats are unchanged. Copying an existing quote isn’t affected.


✨ Automated Insurance Rates updates

Users can now update comprehensive insurance rates and refresh contract premiums and payment schedules to match, using a standard upload and Scheduler job process available to every client.

This is available when:

  • Catch-e has activated the insurance update jobs for your site. They are created for every site as restricted jobs and stay inactive until then, so contact Catch-e Support to have them activated.

Additional Details

  • Rate files now include the insurer’s supplier code. If any row can’t be matched, nothing loads and the Scheduler screen shows why.

  • After a successful rate load, a draft of suggested new amounts for each contract is emailed automatically for you to check and upload.

  • The confirmed amounts are applied overnight with a full audit trail. If the upload has a problem, nothing changes and the reason is shown.

  • Sites already running these processes are unchanged.


✨ Automatic fuel card creation during fuel import

Fleet operators can now have Catch-e create a missing fuel card automatically when an imported transaction’s registration identifies exactly one suitable contract, instead of creating each card by hand from ‘Failed Card’ transactions.

This is available when:

  • The global control feature_auto_create_card_on_fuel_import_flag is switched on for your site. It is off by default. Switch it on in Global Controls if you have access, or contact Catch-e Support.

Additional Details

  • A card is created only where the registration matches exactly one active contract whose Contract Type has a Fuel budget on its Expenses-Approvals tab. Anything less certain stays at ‘Failed Card’ for you to fix as today.

  • Created cards appear on the Cards screen with a note recording when and how they were created.

  • It works when importing a file, running Check, and on scheduled imports.

  • Each transaction still goes through the usual validation checks before it can be posted.


✨ Copy a User Defined Variant

Users can now create a new vehicle variant by copying an existing User Defined variant. This makes it quick to set up each new model year as its own variant, without overwriting the previous one.

This is available when:

  • The variant_copy_enabled_flag control is switched on. It’s off by default.

  • The variant on display is User Defined and in Display mode.

  • The user has access to Edit on the Variant Detail tab.

Additional Details

  • Copy opens a new, unsaved variant with the original’s details filled in. List prices start at 0.00, and Variant Code Previous and Next are blank.

  • The Variant Code must be changed before saving. A copy can’t keep the original’s code.

  • Linked records such as the profile, equipment, discounts, rebates, bonuses and photos aren’t copied.

  • Status is copied as it stands, so copying an Active variant gives an Active copy.

  • Cancel returns you to the original variant, which is never changed.

Changelog - 19 October 2026

Our latest release delivers key enhancements across fleet management, integrations, salary packaging, and payment processing. From the upcoming Catch-e Driver App and new odometer API to stronger validation controls and more flexible billing workflows, these updates are designed to improve efficiency, accuracy, and user experience across the platform.

🕒 Coming soon: the new Catch-e Driver App


We’re putting the finishing touches on a new mobile app built for your drivers. It brings the everyday parts of running a vehicle into one place, so drivers spend less time on admin and more time on the road.
What to look forward to:

  • Your vehicle at a glance: lease details, servicing schedules and key dates in one view

  • Simpler fuel and expense logging: capture receipts and odometer readings on the go

  • Timely reminders: prompts for registration, servicing and other upcoming tasks

The Driver App will be available on iOS and Android soon. We’ll share setup guides and rollout details closer to launch.


API Updates

New API - createContractOdometer

We’ve introduced a new createContractOdometer API that records an odometer reading against a contract, providing integrations with the same capability as the Odometer button on the Contracts / Maintenance screen.

For each reading, the API records:

  • Odometer reading (km)

  • Reading date

  • Description (defaults to the FBT VMRS code description if left empty)

To ensure readings are accurate and consistent:

  • A reading outside the contract’s expected odometer range is held back with a warning and saved only when the caller confirms it.

  • A reading identical to an existing one for the same contract and date isn’t saved again, even when sent more than once at the same moment.

  • Each reading is recorded against the authenticated user, or the person who supplied it, in the maintenance record and the audit trail.

The API also includes validation to ensure:

  • The contract exists and is within the user’s client restrictions.

  • The reading is a whole number greater than zero, with a valid date.

  • The caller has the required ContractMaintenance:Create permission.

This new API lets integrations and portals submit odometer readings directly, removing the need for back-office staff to key them in through the Maintenance screen.


Salary Packaging Updates

Confirm Varying an Item When the Next Date Has Already Been Billed

Users varying a salary packaging Item are now asked to confirm before saving when the Next Date they’ve left in place has already been billed. Previously, the save just didn’t complete and no message appeared.

This is available when:

  • You are varying an active salary packaging Item from the Vary form.

  • The Item’s Contract has already started billing.

  • The Next Date has been left as the form supplied it, and that date has already been billed.

Additional Details

  • Selecting OK saves the variation. No additional billing period is created on the already-billed date.

  • Selecting Cancel saves nothing and returns the cursor to the Next Date field, so you can pick a different date.

  • If the same save would also suspend the Item, only the suspend confirmation is shown. Accepting it also accepts the already-billed Next Date.

  • Any other Next Date problem still shows the standard failure message, with no option to continue.

BECS Disbursements Batch Checked Against Your Reviewed Selection

Users creating a BECS Disbursements (ABA) batch are now stopped if the disbursements have changed since the control totals were displayed. This means a batch can no longer include payments you haven’t reviewed.

This applies when:

  • Creating a batch from the BECS / Disbursements (ABA) screen, with an ABA Type of Client or Company.

Additional Details

  • If Control Invoices, Control Items or Control Total no longer match, the batch isn’t created. You’ll see “Problem creating BECS export - the selection has changed since it was displayed. Review the control totals before creating this batch.”

  • A change to any one figure is caught, even if the Control Total stays the same.

  • To continue, reselect by changing the Client Code, Pay Cycle or paying bank account, then review the updated figures. New and changing the ABA Type don’t reselect.

  • If every disbursement has been removed from the selection, you’ll still see the existing “No disbursements found” message.

  • A rejected batch saves nothing and doesn’t lock the general ledger for other users.

Email Pay Run Invoices in a Separate Pass

The Pay Run Reports job can now email pay run invoices that have already been created, without invoicing them again. You can invoice pay runs first, check them, then email them in a later run.

This is available when:

  • The Pay Run Reports job’s new Invoice parameter is set to No.

  • The pay run is dated today, at Pending, with a posted invoice, and the client’s delivery type is Email.

Additional Details

  • Invoice defaults to Yes, so existing jobs keep invoicing and emailing as they do today, with no changes needed.

  • In email-only mode, Run Date is hidden and the Delivery setting is ignored.

  • Pay runs that have already been emailed, whether by the job or from the Pay Run screen, aren’t sent again.

  • If a send fails, or the client has no email recipient, the pay run is listed on the exception report, and the rest of the pass continues. A failed pay run is picked up again on the next run.

  • An email-only run creates no invoices, so it can run during business hours.

Earlier updates