July 9th, 2026
Changelog
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.
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.
PermissionsPostingClasses:Get permission has been introduced to control access to these endpoints.
Updated API Documentation
Find the full API Swagger documentation here.
patchQuote and createQuote API Client Margin ValidationWe'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.
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.
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.
Having recently announced an “Early Access” period for our new Contract APIs, we are please to advised they are now available in Production.
getContract
getContracts
createContract
patchContract
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.
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.
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.
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.
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.
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.
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.
We've enhanced the Driver Portal tyre reimbursement process to ensure tyre claims accurately record the number of tyres selected by the driver.
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.
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.
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.
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.