v2026.1.1.0 was made available for release from 19 February 2026.
Improvements
| System Area | Improvement |
| PTO Comparison – Japan (JPO Import) | Users can now import official JPO files and compare the Request for Examination Date against their case data in Equinox. When a JPO file is imported via Import JPO File on a JP Patent case, Equinox will:
This enhancement improves accuracy and visibility when validating official Japanese examination request data against internal records. Applicable to systems where:
|
| E-Invoicing | Equinox now supports including a specific Contact Person or Department on exported e-invoices. Some debtors require invoices to be addressed to a named contact or department (e.g. “For the attention of: Accounts Payable”) in order to process them correctly. This information can now be configured and exported in the UBL XML structure. Users can:
When configured, the selected value will be included in the appropriate XML section of the e-invoice. |
| Case Summary | Changes to Case Applicants are now fully logged in the Case Summary tab. This improves audit visibility and provides a clearer history of applicant updates made to a matter. |
| PAVIS Integration | Enhancements have been made to the Equinox–PAVIS integration to improve internal logging and monitoring of scheduled background processing. Where individual case errors occur, these are now logged and skipped without interrupting processing for other cases on the server. This improves overall reliability and ensures one case failure does not impact other renewal processing. |
Fixes
| System Area | Fix |
| PTO Comparison | Resolved an issue affecting the Grant Date populated via the PTO Comparison tool for JP and KR cases. |
| Website | Updated wording in the Equinox bottom toolbar from “IP Services Portal” to “IP Law Portal” for improved clarity. |
Xero Integration | Removed unused permission scopes from OAuth authentication requests, improving alignment with security best practices. |
| Background Processing | Improved background scripts to optimise database connection handling. Queries now reuse a single database connection rather than creating new connections repeatedly, improving overall system performance and efficiency. |
| Database Configuration | A migration to resolved database collation inconsistencies that were generating errors. |