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.