This release introduces a range of enhancements across Catch-e designed to improve efficiency, flexibility, and user experience. Lily now provides a more personalised support experience by recognising authenticated users, while changelogs will be published ahead of deployments to give customers greater visibility of upcoming releases.

Integration and data management capabilities have been expanded with updates to the patchQuote and createContractEvents APIs, as well as the addition of JATO as a supported vehicle data source. Fleet management has also been enhanced through direct bulk card imports, AdBlue capacity tracking for vehicle variants, and the ability to request multiple fuel cards and e-Tags from a single contract.

Salary Packaging processes have also been strengthened with new controls for ad-hoc pay runs, including upfront warnings and mandatory delivery format selection to help prevent report batches from remaining unsent. Real-time transaction updates now ensure packaging transactions are posted as soon as associated receipts are processed, improving visibility for both employees and finance teams.

Further improvements include a new pay run invoicing scheduler that allows invoices to be generated separately from email delivery, giving organisations greater control over their invoicing workflows and enabling invoices to be reviewed before being distributed.

📢 Changelog Publishing Update

To give you more time to prepare for upcoming changes, we’ll now be publishing our Catch-e changelog before scheduled deployments.

While our deployments will continue to occur on Monday evenings, the changelog will be available in advance so you can review upcoming features, enhancements, and fixes before they go live.

This provides early visibility into what's being released, allowing you to plan ahead and be ready to take advantage of new functionality when it's available on Tuesday morning.

💬 Lily now knows who you are

You shouldn't have to introduce yourself every time you ask for help. Lily now recognises you the moment you open it from within Catch-e via authentication with our system; your details, your history, your past requests, all already there. It also means we can see which organisation you're with without asking, so we can get you the right answer sooner.

API Enhancements

🔌 patchQuote Updates

We've extended the patchQuote API response with ten new fields across three areas:

• Broker details — supplier_id_broker, broker_rate, broker_fee

• Lease timing and luxury charge — advance_arrears, months_in_arrears, periods_deferred, luxury_charge

• Insurance premiums — gap_insurance, redundancy_insurance, comprehensive_insurance

All ten fields accept zero as a valid amount and are validated to reject negative, non-numeric, or empty values. These changes give integrations finer control over broker commercials, lease repayment timing, and insurance premiums on a quote, without going through the Catch-e UI.

🐞 Bug Fix: Assign to a Specific User - createContractEvents API

We've fixed an issue with the createContractEvents API so that it now accepts an optional user_id field, allowing a contract event to be created and assigned to a specific user instead of always being recorded against the authenticated account.

The API also includes validation to ensure:

• The supplied user_id matches an existing user in Catch-e.

• If user_id is omitted, or explicitly set to null, the event is assigned to the authenticated (audit) user, exactly as before.

This resolves an issue where including a user_id in the request would cause the entire request to fail, making it easier for integrations to create contract events on behalf of, or assigned to, a specific user.

Fleet Management Enhancements

🚙 JATO Vehicle Data Integration

Administrators can now import vehicle data from JATO and use it as a source for quoting, alongside the existing Glass's Guide and Redbook integrations.

This is available when:

• JATO has been set as your vehicle data source.

Additional Details:

• Vehicle data can be imported automatically on a schedule, or triggered manually from Fleet > Import Data > JATO Data, the same way Glass and Redbook imports work today.

• The import runs in three stages — discover, fetch and import — each with its own independent timeout, so a delay in one stage doesn't affect the others.

• JATO's own suggested wait time is honoured before the first status check, rather than a fixed interval.

• If JATO reports a failure at any stage, the import stops immediately and the reason is recorded — later stages are not attempted.

• On completion, a summary email reports how many vehicle instances were found, fetched, inserted, updated, deactivated and failed, along with start and completion times.

• Existing Glass and Redbook vehicle data imports are unaffected.

🚀 Import Cards (Bulk Import from the Cards Screen)

Users can now bulk import cards directly from the existing Cards screen, without needing a separate import page.

This is available when:

• A supplier and CSV file have both been selected (the Upload button stays disabled until then).

Additional Details

• Only card-capable suppliers appear in the supplier dropdown.

• Create vs update is worked out automatically from the supplier and each row's card number — no need to specify which.

• After validation, the available buttons adjust automatically:

  • Import only, if everything's valid

  • Error Report then Import, if some rows fail but others don't

  • Error Report then Re-Upload, if none of the rows are valid

• Error Report and Results CSV downloads are available at the relevant stages, and Next/Re-Upload fully reset the tab for another import.

Benefits

• Faster bulk updates — no more relying on generic Import Table Data or one-by-one manual entry for card maintenance.

• Fewer mistakes — every row is validated before anything is committed, and duplicate or invalid rows are automatically excluded rather than silently processed.

• Full visibility — the Error Report and Results CSV give a clear record of exactly what happened to every row, success or failure.

⛽ New Variant Field - AdBlue Capacity

You can now record an AdBlue Capacity value for a vehicle variant, keeping this detail alongside the vehicle's other fuel specifications in Catch-e. This helps fleets track AdBlue capacity for diesel vehicles as AdBlue systems become mandatory on trucks entering Australia from November 2025, without needing to record it outside the system.

This is available when:

• Editing any vehicle variant's Fuel section on the Variant Detail screen.

• Viewing or creating a quote that references a variant with an AdBlue Capacity value set.

Additional Details

• The field is optional — existing variants show it blank by default, and no import or migration populates it automatically.

• Values are stored and displayed to one decimal place (e.g., 1.55 → 1.6).

• Entries that are negative, non-numeric, or greater than 9999.9 are rejected with an inline message.

✨ Enhancement - Add a New Card or e-Tag Directly from a Contract

We recently introduced the ability to add a fuel card from the Contract screen.

Users can now submit multiple new fuel cards and /or e-Tags directly from the same contract.

This is available when:

• This is available when the contract has a Fuel (F) and/or Toll (TOL) budget.

Additional Details

• The "Add Card / e-Tag" link no longer disappears once a card or e-Tag is already linked to the contract — it now stays available regardless of how many cards/e-Tags exist against it.

• Existing linked cards and e-Tags remain visible and unaffected on the contract screen.

• There's no limit to the number of cards or e-Tags that can be linked to a single contract.

• Selecting the link still opens Fleet → Card Services → Cards in Create mode, with the Contract ID pre-populated and the cursor in the Supplier Code field.

Salary Packaging Enhancements

✅ Ad-hoc Pay Run Warning and Mandatory Delivery Format

You can now see an upfront warning when a Salary Packaging pay run will be ad-hoc, and must explicitly choose an Email or PDF delivery format before posting — closing a gap where ad-hoc pay run report batches could get stuck unsent with no warning.

This is available when:

• Posting a pay run on the Salary Packaging Pay Run screen for a client/pay cycle/period combination with no existing regular pay run for that period (making it ad-hoc).

Additional Details

• The warning appears as soon as you select Go, before any records load — not after you've already committed to Invoice.

• Declining the warning loads nothing; Go remains usable and nothing is created.

• The Email/PDF delivery format field starts blank for an ad-hoc pay run instead of defaulting, and Invoice is blocked until a format is chosen.

• Regular pay runs are unaffected — the format still defaults as before and no warning appears.

• Once an ad-hoc pay run is successfully posted, its status now correctly advances from Open to Pending, the same as a regular pay run; a failed post leaves it at Open for retry.

• The existing pay run report review pop-up (list of pending items, Send/Cancel, per-item editing) is unchanged and still appears for Email delivery, including for ad-hoc pay runs

🧾 Packaging transactions update as soon as a receipt is posted

Posting a receipt batch now updates the linked salary-packaging transactions straight away. When the receipts against a pay-run billing add up to the full invoiced amount, the employee's packaging transactions move from Pending to Posted at the moment the receipt is posted, instead of waiting for a background update.

For employees this means packaging transactions appear on their statement, and count towards their balance, sooner. For finance teams it means packaging status reflects funds received in real time.

Every change is recorded in the audit trail against the user who posted the receipt.

🔄 Pay Run Invoicing scheduler job (invoice-only)

You can now schedule pay-run invoice creation separately from emailing.

Pick which delivery types to invoice — Email, Post, or All — and invoices are created on their invoice date, out of hours if you wish.

Emailing remains a separate step, so invoices can be reviewed first.