This release introduces a range of enhancements focused on improving accuracy, control, and operational efficiency across the Catch-e platform.

Key updates include more flexible lease inclusion management, stronger salary packaging validations to help prevent duplicate billing, improved visibility of employee contract information, enhanced pay run invoice delivery options, greater transparency when sending emails, and expanded API access to support integration with external systems.

Together, these improvements help streamline administration, strengthen data integrity, and provide a more seamless experience for customers managing leasing, payroll, communications, and business integrations.

📋 Lease Inclusions by Contract Type

Administrators can now set, for each Contract Type, which Lease Inclusions are added to quotes automatically and which can't be used. This stops quotes from carrying Inclusion products that don't apply to their Contract Type.

This is available when:

• Editing, creating or copying a Contract Type in Fleet › Controls › Accounts › Contract Types › Details, using the new Lease Inclusions section.

Additional Details

• Each Inclusion can be set to one of three types:

  • Available (the default): users can select it manually.

  • Preselected: added automatically to new quotes.

  • Unavailable: not offered on quotes.

• Unavailable rows are highlighted pink. Suspended and inactive Inclusions are shown greyed and can't be changed.

• Copying a Contract Type carries its Lease Inclusions settings over, and you can adjust them before saving.

• When a quote's Contract Type changes:

  • Preselected Inclusions are added.

  • Any selected Inclusion that is Unavailable for the new type is removed, with a warning naming it.

  • Removing an Inclusion clears its Plan and pricing and can change quote totals where the Inclusion isn't financed.

• On an existing quote, an Unavailable Inclusion that's already selected stays selected until you remove it.

• Copying a quote doesn't apply the settings, and existing quotes aren't changed when a Contract Type's settings change.

• Changes are recorded in the Contract Type's View Edit History.

✅ Salary packaging Items: Vary no longer accepts a Next Date that has already been billed

Administrators can no longer vary a salary packaging Item onto a Next Date that has already been billed. This prevents duplicate billing periods and duplicate deductions from an employee's pay.

This is available when:

• Varying a salary packaging Item from the Employee's Item screen, where the Item's Contract has already posted billing.

Additional Details

• The Next Date must be later than the last posted billing date. Dates on or before it are refused with "The specified next date must be later than the last posted billing record".

• Pending adjustment entries no longer let a settled date through.

• If an Item already has a duplicated billing date and you leave the Next Date unchanged, you'll see a confirmation instead of the refusal:

  • OK saves your other changes and leaves the duplicate in place.

  • Cancel saves nothing.

• The Next Periodic field on the Contracts / Billing screen isn't affected.

✅ Employee Contracts tab no longer lists salary-packaged items

The Contracts tab on an employee/driver record now excludes salary-packaged items, showing only genuine vehicle contracts — correcting a case where packaged items could appear on the tab as if they were vehicle contracts.

This is available when:

• Viewing an employee's Contracts tab under an internal or client-restricted login. (No change for an employee's own login — the driver-restricted scope already excluded salary-packaged items, so nothing changes there.)

Additional Details

• An employee whose only driver-linked contracts are salary-packaged items will no longer be offered the Contracts tab at all, since it would otherwise open empty.

• Packaged items remain fully available via the Current Packages, Item and Transactions tabs — nothing becomes unreachable.

• Corrects the tab for contracts reached either by an incomplete driver event or by a contract being retyped to a packaged item after carrying a legitimate vehicle driver link.

📧 Pay Run Reports job: new email-only mode

Administrators can now set the Pay Run Reports job to email pay run invoices that have already been created, without invoicing them again. Invoices can be created and reviewed first, then emailed in a separate pass later the same day.

This is available when:

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

• The pay run meets all of these conditions:

  • it is dated today

  • it is at Pending status with a posted invoice

  • its client's delivery type is Email

  • it hasn't already been emailed.

Additional Details

• Invoice defaults to Yes, which keeps the existing invoice-and-email behaviour. Existing saved jobs keep running as before, with no need to re-save them.

• When Invoice is set to No:

  • the Run Date parameter is hidden

  • the Delivery parameter has no effect.

• Pay run invoice emails now record which pay run they were sent for, whether they were sent by the job or from the Pay Run screen. The email-only pass uses this to skip pay runs that have already been emailed, including those emailed from the Pay Run screen earlier the same day. This applies to emails sent from this release onward.

• If an emailed pay run is later un-posted and re-issued, it isn't emailed again automatically. Re-send it from the Pay Run screen.

• If one email fails to send:

  • the rest of the pass continues

  • the failed pay run is named on the exception report

  • it stays eligible for a later pass.

• The pass doesn't run while invoicing is in progress anywhere in your system. It reports this once and can safely be run again later the same day.

📨 Mail Queue: Send confirmation and sender shown in User column

Pressing Send on the Mail Queue now shows a confirmation before any email goes out. It shows how many pending emails will be sent, a breakdown by Type, the oldest email's creation date and age, and the number of recipients.

It also suggests filters to use if you want to send fewer.

Once an email is sent, the User column shows the person who sent it rather than the person who created it.

Cancelling sends nothing, and you can still send a mixed selection in one action.

🌐 Expanded external API access

A number of existing API permissions have been made available for external access across client environments. For the current list of APIs available externally, refer to the API documentation: https://api.catch-e.com/docs/

Qualifiers

• Review the available permissions and enable the permissions you need.

• Only APIs with a checked permission will run successfully.

• Limit your permissions to the required APIs to optimise your system's security.

How to access and enable permissions

1. Go to System / Roles.

2. Select the 'web_services' role.

3. Navigate to Roles / APIs.

4. Review the available permissions.

5. Edit and check the permissions you need.

🆕 New Features

🔓 Clear System Locks — self-service management of system locks

Admin users can now view and clear stale system locks directly from a new System → Clear Locks screen, without needing to contact Catch-e support for most stale-lock situations.

This is available when:

• You're logged in with the Admin role — no other standard role can see the menu item or the screen

Additional Details:

• The screen sits under System, directly below Workgroups and above Change Password

• Filter the current lock list by User Login and/or Table Name (Table Name includes process-style entries, not just database tables), then click Go to refresh the list

• Ticking one lock automatically selects every other lock held by the same session, so a user's full set of locks can be cleared in one action

• Certain critical locks — locks on an entire table, and locks tied to billing or system configuration records — are highlighted; they can't be deleted from this screen, so contact Catch-e support if one needs to be cleared

• If the table behind a selected lock is affected by a long-running database query, deletion is blocked until the query clears; if it needs to be cleared urgently, contact Catch-e support

• If a selected lock has already been cleared by someone else (or expired) by the time you click Delete, you're shown an alert rather than the request silently failing or partly succeeding

• Every deletion is recorded in an audit trail noting who originally held the lock and who deleted it; deleting an active session's lock signs that user out immediately

📋 New "Resources" menu

Internal users can now access Catch-e's Feedback, Roadmap, Changelog, Status, Developers and Trust pages directly from a new Resources dropdown menu, without leaving the app.

This is available when:

• The user's role is an internal role — the menu is not shown to external/client-facing roles.

Additional Details

• The Resources menu sits alongside System in the top navigation.

• Each link (Feedback, Roadmap, Changelog, Status, Developers, Trust) opens in a new tab.

⬆️ Enhancements

🏦 Configurable financier margin rates for quotes

Quotes can now apply a configurable interest rate margin — an increase or a discount — to the financier's base rate, in addition to the existing Client Margin. This replaces a piece of older, client-specific discount logic with a generic mechanism that Catch-e can configure by financier, and optionally by make, model or variant.

This is available when:

• A margin rate has been configured that matches the quote’s financier (and, where applicable, its make, model or variant)

• The quote's Variant, Quote Date, Client Code or Contract Type changes — the margin is re-resolved on each of those triggers (a Term change alone does not re-derive it)

Additional details:

• The Financier Margin field sits on the Quote → Finance tab, directly below Client Margin: a discount shows in red, an increase in black

• Financier Rate is now calculated as Base Rate + Client Margin + Financier Margin

• Where more than one configured rate could match a quote, only the single most specific one applies — margins are never added together

• A related fix: Client Margin now rounds to 2 decimal places before it's added into the Financier Rate, correcting a rare rounding/precision issue

• Every Financier Margin change — made in the UI or via the API — is recorded in the audit trail

• The API also now returns the resolved financier_margin_rate on quote create/update responses (the legacy create-quote endpoint used by some older integrations does not include it)

🔧 patchQuote updates

The patchQuote API can now accept seven additional fields, delivered across two updates.

Finance details

• Early Termination Fee

• Budget Financed

• Residual Rate — editable on novated quotes only; on non-novated quotes any submitted rate is ignored and it continues to be derived from the Residual Amount as before

Additional fee fields

• REVS/PPSR Fee

• Fuel on Delivery Fee

• Delivery Fee

• Other Brokerage

All seven fields accept zero and are validated to reject empty, negative, non-numeric or over-precision values. Early Termination Fee, Budget Financed, and Residual Rate on novated quotes hold whatever value is explicitly set, including through later changes to the quote.

The four additional fee fields work a little differently: an explicit value wins when sent alongside another change in the same request, but — matching how these fields already behave on the Quotes screen — a separate, later request that recalculates the quote can still reset one back to zero.

Existing quotes and patch requests that don't reference any of these fields continue to save exactly as before.

💸 Salary-packaging transactions now update as soon as a receipt is posted or un-posted

Posting or un-posting a receipt batch now updates the linked salary-packaging transactions straight away, instead of waiting for a background update.

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. If a receipt is later un-posted and the billing is no longer fully receipted, those transactions move back to Pending, at the moment the receipt is un-posted.

For employees this means packaging transactions appear on their statement, and count towards their balance brought forward, as soon as the funds behind them are actually received — and disappear again, just as promptly, if a receipt is un-posted.

For finance teams it means packaging status reflects funds received in real time, in both directions.

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

This release delivers targeted enhancements to Employee Package Item management, including improved financial reporting, streamlined FBT year analysis, and more accurate variation processing, while also introducing new capabilities to simplify contract event maintenance and support data integrity across the platform.

🔌 New API - patchContractEvent

We've introduced a new patchContractEvent API that lets you update an existing contract event in place, giving integrations and automated processes a way to correct or adjust event details without needing to delete and recreate the event.

For each contract event, the API lets you update:

• Event Date and Due Date

• Description (or the linked Description record, which the API will use to set the Description text for you)

• Value (or, for Value records linked by id, the API will use that record's text for you)

• Amount

• the linked Cost Centre, Division or Driver record

• Action

• Completed flag

To ensure results are meaningful and easy to consume:

• Only the fields you supply are changed — anything left out of the request is untouched.

• Where an event is linked to a Cost Centre, Division or Driver record, its value is always recalculated from that record, and any value sent directly is ignored.

• If the event you're editing is the contract's most recent event of its type (Registration Number, Cost Centre, Division, Driver or Location), the contract's own details, its Cost Centre / Division / Driver allocation history, and any linked Salesforce record are automatically kept in sync.

The API also includes validation to ensure:

• The contract event exists and hasn't already been deleted.

• The Contract and Posting Class linked to the event can't be changed.

• A linked Cost Centre, Division or Driver record must belong to the same client as the contract (a Driver record may also belong to another client in the same client group).

• A linked Value or Description record must belong to the same posting class as the event.

• The caller has the required ContractEvents:Update permission.

This new API gives integrations and automated processes a reliable way to keep contract event details accurate and up to date, without needing to delete and rebuild an event for a simple correction.

Employee Package Item updates

Enhancements have been made to Employee Package Items to improve financial visibility and accuracy. Summary figures now display GST-inclusive totals, users can review budgets and disbursements by individual FBT years, and Item Variations now use live contract data while preventing unintended schedule changes when no variation has been made.

Item Summary figures now display totals including GST

This is available when: viewing the Item Summary section of any Employee Package Item.
Additional Details: Life Budget, Life Disbursements and Variance now display totals including GST, under a "Total Inc. GST" label in place of "Net".

Life Disbursements has also been corrected to count only settled transactions — amounts not yet posted are no longer included, and amounts held as history now are. Because of that correction, Life Disbursements and Variance may be lower than before for some Items.

FBT Year Ending selector

This is available when: viewing the Item Summary section of an Employee Package Item.
Additional Details:

1. The selector defaults to '--All--' (whole of schedule) every time the screen opens.

2. Selecting a year windows Life Budget and Life Disbursements to that FBT year only — Final Disbursement Due and the Vary fields aren't affected.

3. Edit/Vary is unavailable while a year is selected; return to '--All--' to edit.

Varying an Employee Package Item

This is available when: varying an Employee Package Item.
Additional Details:

1. Remaining Cycles and Deduction Per Pay now reflect the Contract's actual current figures. Saving without changing the deduction no longer alters the pending schedule.

2. A misaligned billing schedule is corrected to the pay-cycle calendar on save, and you'll be asked to confirm if the save would remove pending adjustment records.

3. For claim-to-budget Items, Deduction Per Pay is read-only and only the cycle count can be extended.

🚧 Coming Soon

Admin users will soon be able to view, manage, and delete system locks directly from a new Clear Locks screen under the System menu — no more needing to contact Catch-e support to have a lock released.

This will be available when:

• You're logged in as an Admin user.

• You use the new filters (User Login, Table Name) to find the lock you're after.

Additional Details

• The list shows which user is currently holding each lock, alongside the locked table.

• Every deleted lock will be recorded, including who removed it and when — closing the current gap where lock removals aren't tracked anywhere.

• A small number of system-critical tables will remain protected from deletion via this screen.

Still in development — exact behaviour may be refined before release.