OneOffice
Release 16.3.5.0 delivers the A2A Claims Portal Migration.
How this version will be released
This update 16.3.5.1 should be downloaded by your trained DPS Supervisor\Developer who can apply it to your system. The update will be made available on our Customer Portal.
PLEASE NOTE: If you are a hosted client this will automatically be applied to your system by one of our technicians, if you are a non-hosted client and have an SLA, we will be in touch to arrange an update at a convenient time.
What is changing and why?
The A2A Claims Portal integration — used for RTA and ELPL personal injury claims within OneOffice — is being updated as part of a change mandated by CRIF, the Claims Portal operator. CRIF is retiring its current communication method (SOAP) and switching exclusively to a new standard (REST) by the end of June 2026. This is not optional: after that date, any system still using SOAP will no longer be able to connect to the Claims Portal.
We have completed the development work required to support the new REST standard and will be rolling out the update to all customers ahead of the deadline.
What does this mean for your day-to-day work? Nothing changes for your users. The claims workflow in OneOffice remains exactly the same — submitting claims, managing settlement packs, handling notifications, and processing attachments will all continue to work as they do today. The change is entirely in the underlying technology. |
What do you need to do?
There are two things required from your side before your migration can be scheduled:
Step 1 — Apply for your REST API credentials from the Claims Portal
Each organisation must obtain new REST API credentials (a Client Id and Client Secret) directly from the Claims Portal. These are different from your existing SOAP credentials and must be in place before we can complete your migration.
To request your credentials:
1. Download and complete the REST API credentials request form from the Claims Portal website:
2. Email the completed form to: [email protected]
3. Use the following subject line exactly: "Access OneOffice - REST API - requesting new PRODUCTION credentials"
Important — Software House ID When completing the form, use the following Software House ID for OneOffice: SH1042 |
Note on credential naming If you were previously using a value called "Client ID" in your SOAP configuration, please be aware this is actually the Software House ID — the naming was misleading. Your new REST credentials will include a new Client ID and Client Secret, which are separate values issued specifically for REST access. The Software House ID itself (SH1042) does not change between SOAP and REST. |
Step 2 — Contact our Support team once you have your credentials
Once you have received your REST API credentials from the Claims Portal, please get in touch with our Support team. They will be able to advise you on the next steps and guide you through the rest of the process.
Please do not wait once your credentials arrive — the sooner you contact Support, the more time we have to complete your migration comfortably ahead of the June 2026 deadline.
If you have bespoke customisations
If your OneOffice system includes any bespoke changes or customisations, please be aware that these may need to be re-applied following the update. Please ensure you have a record of any customisations before your migration is scheduled. Our Support team can advise you on this when you get in touch.
Key dates
Now | Apply to the Claims Portal for your REST API credentials (see Step 1 above). |
On receipt of credentials | Contact our Support team — they will advise on next steps and guide you through the migration process. |
End of June 2026 | CRIF deadline — SOAP endpoint is decommissioned. All customers must be on REST by this date. |
How to Add Your Client ID and Client Secret in OneOffice
Prerequisites
You will need your Client Id and Client Secret from the Claims Portal Developer Portal. These are issued by the MoJ Claims Portal team and are specific to your organisation. If you do not have them, contact the Claims Portal support desk to request OAuth 2.0 client credentials, following the steps above.
Steps
1. Open the DPS SQL Config.
2. Navigate to Web Accounts in the left-hand tree.
3. Select the A2A/MoJ tab.
4. In the A2A Account Details group:
Enter your Client Id in the Client Id field (this is a GUID value).
Enter your Client Secret in the Client Secret field (the text will be masked with asterisks).
Verify the As User field contains the correct login-as identity for your organisation (this is the same value you used previously).
5. Click OK to save.
Your credentials are encrypted before being stored in the database. The application decrypts them automatically when connecting to the Claims Portal.
Please Note: For EmailAgent polling used with A2A integrations (where the Enable MOJ checkbox is selected), the files included in version 16.3.5.0 and later are required.
To install the update:
Extract 16.3.5.0.exe.
Stop the EmailAgent service.
Copy all files and folders from the extracted 16.3.5.0 folder.
Paste them into the existing EmailAgent installation folder, allowing any existing files to be overwritten.
Restart the EmailAgent service.
This update is required for A2A integrations with EmailAgent polling when the Enable MOJ option is enabled.
Questions or need help?
If you have any questions about the migration, need help with the credentials request process, or are unsure of your next steps, please reach out to our Support team. We are here to make this transition as straightforward as possible.