July 27th, 2026
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.
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.
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.
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.
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.
These endpoints support approval lifecycle management, including maintenance line creation and updates.
These APIs allow approvals to be validated, posted and reversed programmatically while maintaining existing business rules and controls.
These read-only endpoints provide access to the reference data used when creating and maintaining approval records and maintenance lines.
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.
These endpoints support claim lifecycle management, including maintenance line creation and updates.
These APIs allow claims to be validated, posted and reversed programmatically while maintaining existing business rules and controls.
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.
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.
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.
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.
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.
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.
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.
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.