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.

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.

Our latest release focuses on strengthening integration capabilities and improving day-to-day workflow efficiency across the platform.

New API endpoints have been added to give better visibility into contract billing and maintenance history, along with safer, more controlled ways to remove events and budget adjustments when needed. A previous issue affecting bulk event creation has also been resolved, making batch processing more reliable and transparent.

On the user-facing side, quoting has been enhanced with clearer visibility into on-road charges, scheduled billing now offers more flexible filtering between Fleet and Novated contracts, and a new Trust Center link makes it easier to find information on security, privacy, and compliance.

🔌 New API Release

We've introduced four new APIs in this release:

• getContractBilling & getContractBillings — return a Contract's posted Billing/Invoice line items in the same detail shown on the Billing/Re-Print screen

• deleteContractEvents — removes a Contract Event using the same soft-delete behaviour as the legacy Events screen

• getContractMaintenance — returns a Contract's maintenance history without going through the Approvals workflow

• deleteContractBudgets — removes a pending Adjustment or Credit budget line under the same rules as the legacy Lease screen's Delete button

getContractBilling & getContractBillings

For each billing record, the API returns:

• Invoice Type

• Invoice Number and Batch Number

• Billing Period (from and to dates)

• Net Amount, GST Amount, and Gross Amount Received

• Invoice Date and Posted Date

• Status and Credit Note Flag

To ensure results are meaningful and easy to consume:

• Deleted billing records are never returned, regardless of any filters supplied.

• History-only, pending, and posted records are all included — there's no status filter to configure.

• Results can be filtered by contract, client, invoice number, batch number, invoice type, and invoice date range, and are paginated for larger result sets.

The API also includes validation to ensure:

• The specified billing record or contract exists.

• The caller has the required Contract Billing:Get permission.

These new APIs provide a reliable source of contract billing history for integrations and automated processes, making it easier to reconcile invoicing data without going through the Billing/Re-Print screen.

deleteContractEvents

To keep event data safe when deleting, the API also:

• Consolidates the deletion into a single soft-delete update — the record's status is set to deleted and it's never physically removed.

• Cascades the deletion to any linked attachment, and to any pending or failed mail for mail-class events, without affecting mail that's already been sent.

• Rolls back all related changes together if any part of the deletion fails, so nothing is left half-deleted.

The API also includes validation to ensure:

• The event isn't currently locked by another user or process — if it is, no changes are made.

• The caller has the required Contract Events:Delete permission.

This new API gives integrations and automated processes a reliable, permission-checked way to remove Contract Events without needing to go through the legacy screen.

getContractMaintenance

To ensure results are meaningful and easy to consume:

• Deleted maintenance records are never returned, regardless of any filters supplied.

• Results can be filtered by contract, posting class, client, supplier, and invoice number — filters are combinable and results must match all of them.

• Results are paginated, defaulting to 25 records per page.

The API also includes validation to ensure:

• The specified contract, posting class, client, or supplier exists.

• The caller has the required Contract Maintenance:Get permission.

This new API gives integrations and automated processes a reliable way to retrieve a vehicle's maintenance history directly from Catch-e.

deleteContractBudgets

To keep budget data safe when deleting, the API also:

• Writes a single audit record for the deletion, matching legacy audit behaviour.

• Protects against two concurrent operations on the same contract corrupting data — one call succeeds, the other is safely rejected with no changes made.

The API also includes validation to ensure:

• The targeted line isn't a Periodic line — these can only be adjusted to zero via updateContractBudgets, not deleted.

• The targeted line is still pending — lines that have already progressed can't be deleted.

• The caller has the required Contract Budgets:Delete permission.

This new API gives integrations and automated processes a reliable, rule-checked way to remove pending budget adjustments without needing the legacy Lease screen.

🐞 Bug Fix: More Reliable Batch Creation for createContractEvents API

We've fixed an issue with the createContractEvents API where submitting more than one contract event in a single request could fail with a generic server error instead of the actual cause of the problem.

Batch requests to create contract events now behave as follows:

• All events in a batch are created together as a single transaction — they're only saved once every event in the request has passed validation.

• If any event in the batch fails validation or hits a database constraint, the entire batch is rolled back, so no events from that batch are created (including any earlier events that were individually valid).

• The response now returns the actual validation or database error that caused the failure, rather than a generic, unhelpful error.

Additional Details

• Requests containing a single event are unaffected by this fix and continue to behave as before.

• Successful multi-event requests continue to return all created records in the response.

📊 Total On Road Charges Subtotal on Quotes / Vehicle screen

Users can now see a new Total On Road Charges subtotal on the Quotes / Vehicle screen, giving a clear, single figure for the government charges within a vehicle quote.

This is available when:

• A vehicle variant has been selected on a quote.

• Luxury Car Tax, Initial CTP, Initial Registration, Premium Plate, and Purchase Stamp Duty values have been calculated for that quote.

Additional Details

• The subtotal is shown as Net, GST and Total (gross) columns, positioned directly below Purchase Stamp Duty on the Vehicle screen.

• Only Initial CTP carries a GST component in this subtotal — the other four charges don't attract GST here, matching the existing calculation model.

• The Total On Road Charges figure is a component of the existing Total On Road Price, which continues to include the quote's other vehicle cost components as well.

• The subtotal updates automatically whenever a change to the vehicle variant or optional equipment affects one of the underlying charges — for example, changing the vehicle variant recalculates Purchase Stamp Duty, and adding or removing optional equipment recalculates Luxury Car Tax.

• If the vehicle is cleared (by changing make, model, variant or year), the subtotal — and the Total On Road Price — reset to $0.00.

• This is a calculated, display-only figure; it isn't stored against the quote and is recalculated fresh each time the quote is loaded.

🔍 Contract Group Filter for Scheduled Billing

You can now filter Combined Billing and Periodic Billing scheduler jobs by Contract Group, so Fleet and Novated Lease contracts can be invoiced on separate automated schedules without manual intervention.

This is available when:

• You are creating or editing a scheduled Combined Billing or Periodic Billing job.

Additional Details

• New jobs default to "-- All --" (no filtering), so nothing changes for existing jobs unless you explicitly choose Fleet or Novated.

• "Novated" includes only contracts classified with posting map group "novated" (e.g. Novated Lease, Novated Finance Lease); "Fleet" includes every other classification (Lease, Fleet Managed, Insurance, Salary Packaged, and non-billing arrangements) — Fleet and Novated are exact complements of one another.

• Contract classification is evaluated each time the job runs, using the contract's current posting map — not the classification at the time the job was configured or last saved.

• You can run separate jobs with different Contract Group values on independent schedules — for example, a monthly Fleet job on the 1st, and a Novated job that runs periodically throughout the month — and each is unaffected by the others.

• Existing scheduled jobs saved before this change continue to run exactly as before, behaving as "-- All --".

• The saved Contract Group value is retained when you reopen a job for editing.

🔒 New: Catch-e Trust Center Link

We're making it easier to access important security and compliance information.

The Trust Center provides a central location for information about our security practices, privacy commitments, compliance certifications, and platform reliability.

What you can find in the Trust Center:

• Security and compliance information

• Privacy and data protection resources

• System reliability and operational practices

• Answers to common security-related questions

📍 Where to find it: Bottom-left corner of the Catch-e Help Centre.

This release brings a wave of new API capability to Catch-e. A full Approvals and Claims suite gives you control over Fleet Maintenance Approvals and Contract Claims end to end, backed by new reference data endpoints.

On top of that, the Whole of Life Driver Report now captures ECM amounts billed after a contract's end or suspend date for more accurate Employee Contributions and FBT, patchQuote handles Inclusion rules automatically on Contract Type changes, fuel cards can be created straight from the contract screen, and Adjustment Period budgets can now be managed through the API.

🚗 Whole of Life Driver Report Enhancement

We've improved how Post-tax Collected (Employee Contribution) is calculated and displayed on the Whole of Life Driver Report.

Previously, ECM amounts from billings dated after a contract's end or suspend date were excluded from Employee Contribution calculations, even though those amounts were still billed against the lease. This could result in Employee Contributions being understated and FBT liabilities appearing higher than expected.

What's changed?

• Employee Contribution calculations now include ECM amounts from billings that occur after the contract end or suspend date, where those billings relate to the lease.

• This enhancement applies to ECM values sourced from both contract events and non-contract events.

• FBT days available continue to be calculated using the actual contract end or suspend date and are not extended by the inclusion of later billings.

• The Whole of Life Driver Report now more accurately reflects the total post-tax contributions collected over the life of the lease.

Benefits

• More accurate Employee Contribution values.

• Improved alignment between FBT calculations and actual lease billings.

• More accurate Whole of Life reporting for post-tax contributions.

• Reduced risk of overstated FBT liability calculations.

No action is required. This enhancement automatically applies to Whole of Life Driver Report calculations and ensures post-tax contributions are reflected based on all relevant lease billings, regardless of whether they occur before or after the contract end date.

🔌 New Approvals / Claims API Suite

We've released a new suite of Approvals / Claims APIs, providing programmatic access to create, manage, validate, post and un-post approvals through the Catch-e API. This enhancement modernises approval management and enables seamless integration with external applications and automated workflows.

Approvals APIs

Approval Management

These endpoints support approval lifecycle management, including maintenance line creation and updates.

Approval Processing

These APIs allow approvals to be validated, posted and reversed programmatically while maintaining existing business rules and controls.

Reference Data APIs

These read-only endpoints provide access to the reference data used when creating and maintaining approval records and maintenance lines.

Benefits

• Enables integration partners and internal applications to manage Fleet Maintenance Approvals through APIs.

• Supports automation of approval workflows.

• Provides validation capabilities prior to posting approvals.

• Delivers secure permission-based access to approval processing functions.

• Establishes a modern API foundation for future integrations and enhancements.

The new API suite includes support for approval validation, posting, un-posting, maintenance line management, reference code lookups, configurable business rules and role-based permissions. Existing approval functionality within Catch-e remains unchanged for users continuing to work through the standard application interface.

Claims APIs

Claim Management

These endpoints support claim lifecycle management, including maintenance line creation and updates.

Claim Processing

These APIs allow claims to be validated, posted and reversed programmatically while maintaining existing business rules and controls.

Benefits

• Enables integration partners and internal applications to manage Contract Claims through APIs.

• Supports automation of claims workflows.

• Provides validation capabilities prior to posting claims.

• Delivers secure permission-based access to claims processing functions.

• Establishes a modern API foundation for future integrations and enhancements.

The new API suite includes support for claim validation, posting, un-posting, maintenance line management, batch creation, configurable business rules and role-based permissions. Existing claims functionality within Catch-e remains unchanged for users continuing to work through the standard application interface.

✨ New API: getContractPayRunDates

We've introduced a new getContractPayRunDates API that returns the available pay run dates for a contract, providing a simple way for integrations to retrieve billing periods and payment schedules associated with Salary Packaging contracts.

For each pay run, the API returns:

• Pay Run Date

• Billing Period

• Billing Period Item Number

To ensure results are meaningful and easy to consume:

• Duplicate budget records created by multiple posting classes are automatically consolidated into a single pay run entry.

• Budget rows with uninitialised dates are excluded from the response.

• Results are returned in billing period order.

The API also includes validation to ensure:

• The contract exists.

• The contract is linked to a valid Salary Package Item.

• The caller has the required Contract:PayRunDates permission.

This new API provides a reliable source of contract pay run information for integrations and automated processes, making it easier to retrieve key payroll scheduling data from Catch-e.

📄 API Update: getContractBillingStatus

getContractBillingStatus can now return billing status information for a specific contract.

The endpoint provides detailed billing insights, including billing periods, life budget balances, rental billing summaries, lease structure information, and billing configuration details. This enables external systems and integrations to more effectively monitor billing activity and forecast upcoming contract billings.

Typical Use Cases

• Determine whether billing has commenced for a contract.

• Retrieve previous and upcoming billing periods and dates.

• Review life budget values, including billed and remaining amounts.

• Access rental billing summaries for initial, previous, next, and final billings.

• Validate billing schedules and billing structures for reporting and integration purposes.

• Support customer service and operational teams with real-time billing status information.

Benefits

• Increased visibility into contract billing activity.

• Simplified integration with external reporting and financial systems.

• Improved forecasting through access to upcoming billing dates and periods.

• Faster troubleshooting and reconciliation of contract billing queries.

• Reduced manual effort when monitoring contract billing progress and budget utilisation.

🚀 Add Fuel Cards Directly from a Contract

Creating fuel cards is now faster and easier.

When viewing an eligible contract that does not already have a linked card, users will see a new Add Card link directly on the Contract screen. Selecting the link opens the Cards screen in create mode, automatically populates the Contract ID, and places the cursor in the Supplier Code field so card creation can begin immediately.

The Add Card link is available when:

• The contract is associated with Posting Class Code F (Fuel).

• The Contract Type is Accruals or Expenses - Approvals.

• No card is currently linked to the contract.

• The contract is being viewed in read-only mode.

This enhancement helps:

• Reduce manual copying of Contract IDs.

• Speed up card creation.

• Minimise navigation between contracts and card management screens.

Existing behaviour remains unchanged for contracts that already have a linked card, with the existing card hyperlink continuing to display.

🔄 Enhanced Inclusion Validation for Contract Type Changes via patchQuote API

We've strengthened how the patchQuote API manages Inclusion products when quotes are updated, ensuring Inclusion selections always align with the configured rules for the selected Contract Type.

With this enhancement:

• Unavailable Inclusions can no longer be added to a quote. If an API request attempts to add an Inclusion that is configured as unavailable for the selected Contract Type, the request is rejected with a validation error.

• Unavailable Inclusions are automatically removed when a Contract Type change makes them ineligible for the quote. Audit records are created to track these updates.

• Preselected Inclusions are automatically added when a Contract Type change occurs and only a single valid plan exists for the Inclusion.

• Contract Type changes are prevented if a required Preselected Inclusion has multiple plan options and cannot be automatically resolved. The API returns a validation error, allowing a plan to be selected before the change proceeds.

• All validation is enforced regardless of the override_warnings_flag, ensuring Contract Type and Inclusion rules remain consistent across all quote updates.

This update improves data integrity, reduces manual intervention, and ensures Inclusion products remain compliant with Contract Type-specific business rules throughout the quote lifecycle.

🐞 Bug Fix: Support Updating Adjustment Period Budgets via Contract Budget APIs

We've resolved an issue where the updateContractBudgets API could only update the original budget entry for a billing period (billing_period_item_no = 1), making it impossible to update budgets associated with Adjustment Period entries.

As part of this fix:

• The updateContractBudgets API now supports an optional billing_period_item_no parameter, allowing budget amounts to be updated against a specific billing period item.

• The insertContractBudgets API now supports an optional billing_period_item_no parameter, enabling callers to create budget entries using a specified item number when required.

• Validation has been improved to prevent duplicate item numbers within the same contract and billing period, returning a clear 422 validation error instead of a database error.

• Existing integrations remain unaffected, with both APIs continuing to default to the original behaviour when billing_period_item_no is not supplied.

This fix enables Adjustment Period budget entries to be inserted and updated correctly through the API, addressing a limitation reported by Positive Salary Packaging.

Welcome to the latest Catch-e release! This is a big sprint for our API suite, with major upgrades to Quoting, Contracts and Card Services, plus a set of quality-of-life improvements and new integrations. Here's everything that's landed.

Quoting

Smarter field updates in patchQuote

Selected fields in the patchQuote API have moved from SET to OVERRIDE behaviour. Previously, a value sent as SET could still be overwritten by the system's default strategies (for example when a variant change re-triggered defaults). Fields declared as OVERRIDE now take precedence over system-calculated values, so the figure you send is the figure that sticks.

The updated fields by section:

• Vehicle Details: warranty_kms, warranty_mths

• Pricing Details: bonus_amount_net, dealer_discount_net, dealer_rebate_net, discount_net, margin_net, rebate_net

• Registration/CTP Details: reg_initial_net, ctp_initial_net, plate_year, premium_plates_net

• Vehicle Trade Details: trade_in_amount_net, deposit_net, disposal_fee

• FBT Details: fbt_business_use, previous_fbt_value

If you integrate with patchQuote, values you supply for these fields will now reliably override system defaults rather than being recalculated over the top of. No payload changes are required, the fields behave more predictably, exactly as most integrations already expect.

Contracts & Payments

New Contract Payments API suite

Five new endpoints let you read and manage contract payment structures and their payment schedules via the API, no more needing to work through the UI for payment variations:

• GET /fm/contract/payment-structures — list payment structures for a contract, with optional filters for payment_type (finance, comprehensive-insurance, finance-principal-interest, management-fee, roadside-assistance, sundry-payment) and status_flag (defaults to active)

• GET /fm/contract/payment-structures/{id}/vary — retrieve a single payment structure

• PATCH /fm/contract/payment-structures/{id}/vary — vary a payment structure, including schedule timing (periods_deferred, first_payment_due, payment_interval, due_day), placing payments on hold, and setting stop dates

• GET /fm/contract/payment-schedules — paginated schedules for a payment structure, with optional payment_period_no filter

• PATCH /fm/contract/payment-schedules — bulk-edit schedule payment_date, amount_net and amount_gst in a single batch

Additional Details

• Four new permissions control access: ContractPaymentStructures:Get, ContractPaymentStructures:Vary, ContractPaymentSchedules:Get and ContractPaymentSchedules:Edit.

• All changes write audit records, and batch schedule edits are all-or-nothing, so if any row in a batch fails validation, the whole batch rolls back so your data stays consistent.

• Posted and history-only schedules are protected and can't be edited via the API.

New getContractEvents API

A new GET /fm/contract/events endpoint returns a paginated list of contract events, with optional filters for:

• contract_id — events for a specific contract

• posting_class_id — events for a specific posting class

• table_name — one of fm_drivers, fm_client_cost_centres or fm_client_divisions

• status_flag — active or deleted (defaults to active)

Filters can be combined and pagination is supported via page and page_size. Access is controlled by a new ContractEvents:Get permission, and responses follow the standard HAL format you'll know from our other collection endpoints. Ideal for audit trails, syncing contract activity into your own systems, or triggering downstream workflows.

FBT fields added to the Contracts API

The getContract and getContracts endpoints can now return a full FBT summary for a contract, bringing the API to parity with the FBT tab in Catch-e. A new opt-in embed=fbt parameter returns an _embedded.fbt object containing:

• fbt_year_ending — the FBT year the figures are calculated for

• start_of_year_date — start of the FBT year for the contract

• fbt_year_days — days in this FBT year

• gross_up_rate

• tax_rate

• budget_statutory_rate and actual_statutory_rate

• budget_fringe_benefit and actual_fringe_benefit

Additional Details

• The FBT fields are opt-in via embed=fbt on both GET /fm/contracts/{contract_id} and GET /fm/contracts. If you don't request them, your existing responses are completely unchanged — no integration changes required.

• An optional fbt_year_ending=YYYY parameter calculates the fields for a specific FBT year, defaulting to the current FBT year when not supplied.

• FBT fields are returned for contracts with an applicable FBT benefit type (operating, statutory or exempt). Contracts that can't support the calculation are silently skipped rather than breaking the response.

• On the collection endpoint the FBT calculation runs per eligible contract on the page, so expect longer response times when using embed=fbt on lists. Swagger has been updated with the new parameters and response shape.

Card Services

New bulk import APIs for Cards

A full batch-based card import workflow is now available via the API. Upload a CSV of cards for a selected supplier and Catch-e validates every row, classifies each as create, update, invalid, duplicate or unauthorised, processes the valid rows, and gives you downloadable reports:

• Upload & Validate — creates an import batch, validates all rows, and returns summary counts before anything is committed

• Process — creates new cards and updates existing ones, returning a summary of created, updated, failed and skipped rows

• GET /fm/cards/imports/{importBatchId}/errors — download an error CSV of invalid, duplicate or unauthorised rows

• GET /fm/cards/imports/{importBatchId}/result — download a result CSV with the final outcome of every row, including the card_id for successful rows

Additional Details

• Create vs update is determined automatically by supplier + card number, and each row must include a contract_id or reg_no.

• Duplicate rows within the same file are detected and rejected with a clear reason, and blank optional values on updates won't overwrite existing data.

• The workflow respects your Cards:Create and Cards:Update permissions independently — missing one won't block the other — and every successful create or update writes normal card audit history.

• Frontend UI for managing bulk import for Cards is coming in the next few weeks.

Other enhancements

Residual Basis default at Client level

You can now set a default Residual Basis at the client level, with support in both the Catch-e UI and the API.

New quotes and contracts pick up the client's default Residual Basis automatically, reducing manual selection and keeping residual treatment consistent across a client's portfolio. Swagger documentation covers the updated API behaviour.

Automated LCC clearing with a client-level retention flag

Luxury Car Charge (LCC) clearing is now automated, and a new client-level retention flag lets you control whether LCC is retained or cleared for each client.

This removes a manual clearing step from your workflow. Set the retention flag once per client and Catch-e handles the rest.

Banking

Three new financial institutions for Driver/Employee bank accounts

Three financial institutions have been added, so Driver and Employee bank accounts with these BSBs can now be created and updated without validation errors:

• BSB 671-000 — Cuscal Limited (People First Bank)

• BSB 772-772 — Revolut Payments Australia Pty Ltd

• BSB 840-303 — Zepto Payments Pty Ltd

Previously, attempting to save a bank account with one of these BSBs failed with a "financial institution not found" style validation error. These institutions are now available across all relevant screens and APIs, and existing BSB validation is unaffected.

Integrations & Data

New JATO vehicle data integration

Catch-e now integrates with JATO, a leading global provider of vehicle specification and pricing data. Reach out to us if you need help with this.

G-NAF address database updated to May 2026

Catch-e's address validation now runs on the May 2026 release of the G-NAF (Geocoded National Address File) database.

The May 2026 release adds around 41,000 addresses nationally, bringing the total to over 15.9 million Australian addresses, and retires roughly 7,000 invalid lot-numbered addresses in Queensland. Address lookups and validation in Catch-e now reflect this latest data.

Lily Improvements

Thank you to everyone for adopting Lily! We have continued to improve Lily’s base training dataset, improving over 20 articles in the past 2 weeks. We will continue to improve Lily’s training context and start rolling out new features over the coming months.

Questions

If you'd like more detail on any of these changes or want a hand with the new APIs, contact us through Lily. We’re more than happy to help. Don’t forget to check out our new customer portals:

support.catch-e.com.au

help.catch-e.com.au

feedback.catch-e.com.au

🔌 New API Endpoints: Posting Classes

We've expanded the Catch-e API suite to include Posting Classes, providing API consumers with direct access to posting class reference data alongside existing Posting Maps functionality.

✨ What's New

getPostingClasses
Retrieve a collection of Posting Class records.

getPostingClass
Retrieve a specific Posting Class using its unique posting_class_id.

Enhanced Validation
Request validation has been added for collection filters and posting_class_id lookups, ensuring consistent API behaviour and responses.

Permissions
PostingClasses:Get permission has been introduced to control access to these endpoints.

Updated API Documentation
Find the full API Swagger documentation here.

🛠️ Improved patchQuote and createQuote API Client Margin Validation

We've enhanced the patchQuote and createQuote APIs to provide stronger validation of the client_margin_rate field, ensuring client margin values comply with configured business rules.

🔄 What's Changed

Validation for client_margin_rate Updates
These APIs now validate the client_margin_rate field whenever it is included in a request payload.

Support for Configurable Negative Margins
Negative client_margin_rate values are now evaluated against the qt.client_margin_allow_negative_flag global control, ensuring API behaviour aligns with business configuration settings.

Effective-Date Aware Processing
The validation logic respects the effective date of the applicable global control, ensuring the correct business rules are applied based on the quote date.

Improved Error Handling
Where negative client margins are not permitted, the API returns a clear validation message to assist developers in troubleshooting failed requests.

📋 Additional Details

• Positive client_margin_rate values continue to be accepted and processed successfully.

• Negative client_margin_rate values are permitted when the applicable client_margin_allow_negative_flag control allows them.

• Invalid or non-numeric client_margin_rate values are rejected during validation.

• Successful updates continue to recalculate and return related finance values, for example: finance_rate, client_margin_net, finance_pmt_net, finance_pmt_gst

• Existing behaviour remains unchanged when client_margin_rate is not included in the request payload.

🚀 Contract APIs Now Available in Production

Having recently announced an “Early Access” period for our new Contract APIs, we are please to advised they are now available in Production.

✅ Production ready Contract API endpoints

• getContract

• getContracts

• createContract

• patchContract

❤️ Thank You

Thank you to everyone who participated in the Early Access opportunity and provided valuable feedback. Your input has helped shape and refine these APIs for general availability.

Salary Packaging

⚙️ Automated Pay Run Invoicing & Reporting

We've introduced a new automation feature that streamlines the pay run invoicing process by automatically generating invoices and providing visibility of pay run status through a companion review report.

✨ What's Changed

Automatic Pay Run Invoice Generation
Pay run invoices can now be generated automatically using a scheduled job, removing the need to manually create invoices from the Pay Runs screen.

Scheduled Processing
Administrators can configure the frequency, execution time, and report recipients through System Administration → Scheduler Jobs, ensuring invoices are processed consistently and on schedule.

Pay Run Status Review Report
A companion report is generated alongside invoice creation, providing visibility of pay runs that are pending, open, or past due before export to your accounting system.

Flexible Report Delivery Options
Reports can be delivered via email, made available in the Report Queue for download, or generated as a CSV file for further review and processing.

📋 Additional Details

• Reduces manual effort associated with pay run invoice generation.

• Supports proactive review and correction of pay run data before export to accounting systems.

• Updated pay run data can be re-imported and the process re-run to generate an updated invoice batch.

• A Pay Run Invoice Date Review report is available to support data validation and exception management.

🔐 Improved Driver Portal Lockout Recovery

We've enhanced the Driver Portal login experience to make it easier for drivers to regain access to their accounts after multiple unsuccessful login attempts.

✨ What's Changed

Automatic Password Recovery
When a driver reaches the configured maximum login attempt threshold. The system can now automatically trigger the password reset process where a valid email address is registered against the driver account.

Configurable Login Attempt Limits (maximum 8)
The maximum number of failed login attempts is now controlled via a configurable setting, providing greater flexibility for organisations.

Improved User Experience
Drivers now receive clearer messaging when an account is locked and, where applicable, are informed that a password reset email has been sent to their registered email address.

📋 Additional Details

• Existing two-factor authentication (2FA) lockout behaviour remains unchanged.

• Auto-recovery only applies when enabled through system configuration.

• Password reset emails are only sent when a valid email address is available for the driver.

• The existing "Forgot Password" process continues to function as before.

• Enhances self-service account recovery and reduces administrator intervention for driver login lockouts.

🐞 Improved Driver Tyre Claim Quantity Tracking

We've enhanced the Driver Portal tyre reimbursement process to ensure tyre claims accurately record the number of tyres selected by the driver.

✅ Issue Resolved

Accurate Tyre Quantities Recorded
When drivers submit a tyre reimbursement claim, the correct tyre quantity is now recorded rather than defaulting all claims to a quantity of 1.

Improved Tyre Allowance Tracking
Tyre allowances will now be reduced by the actual number of tyres claimed, helping ensure balances remain accurate and up to date.

Support for Multi-Tyre Claims
Claims submitted for multiple tyres (such as 2 or 4 tyres) will correctly record the corresponding quantity against the maintenance record.

Existing Claim Processing Preserved
Fuel claims and all non-tyre reimbursement claims continue to behave as they do today, ensuring no impact to existing claim processes.

🖥️ Updated Contract Types Details Screen Layout

We've refreshed the Fleet → Controls → Accounts → Contract Types → Details screen to provide a cleaner, more consistent, and easier-to-use experience without changing any existing functionality.

🔄 What's Changed

Posting Map ID Now Visible
Previously, the Contract Type's numeric identifier was not displayed on the Details screen. A new read-only Posting Map ID field is now shown near the Status field, making it easier to reference Contract Types for support, administration, and integration purposes.

Data Fields Expanded - Left column
Several fields in the left-hand section of the screen were previously narrow and difficult to work with, particularly when viewing longer values. Text entry fields within the main Contract Type details area, have been widened to make information easier to read, review and maintain. e.g.: Map Code

Order Address Flags Relocated
The Order Address Flags section (Invoice To, Delivery For, Registration To, and Registration Notification To) previously occupied the top-right section of the screen. These fields have been moved to the bottom of the left-hand column, creating a more logical layout and making better use of available screen space.

Quote Request Email Field Enhanced
The Quote Request Email To field has been moved from the middle of the screen to the top-right section and expanded in width, making email addresses easier to view and edit.

Cleaner Screen Alignment and Spacing
Inconsistent field spacing, alignment issues, and blank gaps between sections have been removed to provide a more streamlined and professional-looking layout.

📋 Additional Details

• No changes have been made to underlying functionality or business processes.

• No database or API changes were required.

• The update focuses solely on improving usability, readability and screen consistency.

• Existing Contract Type data and behaviour remain unchanged.

Luxury Car Tax (LCT) 2026/27 Update

The Australian Taxation Office (ATO) has updated the Luxury Car Tax thresholds and car cost limits for the 2026/27 financial year.

These new values will automatically apply to all quotes with an effective date on or after 1 July 2026.

For more information please visit;

• Help Centre reference - Luxury Car Tax Limits

• ATO reference - Luxury car tax rate and thresholds

PAYG Tax Rate 2026/27 Update

The Australian Government has introduced updates to the PAYG income tax rates for the 2026/27 financial year.

These changes will automatically apply across all relevant tax tables and withholding schedules from 1 July 2026.

For more information please visit;

• Help Centre reference - Tax Rates

• ATO reference - 2026 Pay as you go (PAYG) withholding tax tables

We’re introducing a new set of Contract APIs! These endpoints are available to trial in Staging, giving you an early opportunity to explore and provide feedback as we continue to refine them.

✨ What’s included

• getContract
  Retrieve a single contract by its ID for quick access to detailed information.

• getContracts
  Fetch a list of contracts, enabling efficient browsing, filtering, and bulk operations.

• createContract
  Create new contracts programmatically to integrate contract creation into your workflows.

• patchContract
  Apply partial updates to existing contracts without needing to replace the entire record.

⚠️ Important

• These APIs are not yet production-ready

• Functionality may change as we continue development

• We encourage you to test and trial in Staging only

💡 Why try it now?

Early access allows you to start shaping your integrations and provide feedback that helps us deliver a more robust final release.

🚧 Coming Soon: Contract Payments APIs

We’re working on a new set of Contract Payments APIs, currently still in development. These endpoints are not yet available, but will be released soon—so stay tuned for further updates.

✨ What’s planned

• getContractPaymentStructures
  Retrieve payment structures associated with a contract.

• getContractPaymentSchedules
  Access detailed payment schedules, including timing and amounts.

• varyContractPaymentStructures
  Update and adjust contract payment structures as needed.

• editContractPaymentSchedules
  Modify payment schedules to reflect changes in payment arrangements.

⚠️ Status

• Currently under development

• Not yet available in Staging or Production

• Details and functionality may evolve ahead of release

👀 Watch this space

We’ll share another update as soon as these APIs are ready for testing.