We’ve completed the first phase of our PEXA integration inside Atto X, our conveyancing product.
It brings selected PEXA workspace tasks into the matter where the team is already working, with a practical aim: less repeated data entry and a closer connection between matter preparation and the PEXA workspace. Lodgement and financial settlement remain in PEXA.
Workspace
Less repetition between the matter and the workspace
For Australian conveyancing teams, preparing a matter can involve moving between practice software and PEXA. Where those tools are separate, information such as a title reference or a client’s details may need to be entered again. The extent of that work varies from firm to firm, but each repeated entry is another step for the team to complete and check.
Fewer repeated steps can also mean fewer opportunities for transcription differences. That is the problem this first phase addresses: reusing selected information already held in Atto, while keeping the practitioner responsible for checking it.
What the first phase supports
For supported matters, with the necessary configuration, connected PEXA subscriber account and authority, the integration supports these tasks from within Atto:
Check title status
Use the matter’s title details to request information from PEXA, including electronic lodgement eligibility and relevant existing workspace use. The response helps inform the next workspace step; it does not replace the practitioner’s title review.
Create or link a workspace
Create a PEXA workspace using selected saved matter details, including the jurisdiction, matter reference and title reference. Where authorised, link an existing workspace or request to join one, keeping the workspace associated with the Atto matter.
Invite participants
Search for a PEXA subscriber and send a workspace invitation for a supported role. The appropriate participant and role still need to be selected, and workspace access remains subject to PEXA’s requirements.
Enter supported parties
Use relevant saved client details to prefill supported party-entry fields, then review and complete the required information before confirming submission. Required fields vary by jurisdiction, role and party type.
The scope is deliberately specific. These capabilities do not mean every firm, jurisdiction or transaction has access, and they do not replace the work that must be completed in PEXA.
A practical benefit, with review still in place
Consider a conveyancer preparing a supported purchase matter. The jurisdiction and title reference are already saved in Atto. Instead of beginning a separate workspace-creation process by typing those details again, the conveyancer can start from the matter, review the relevant options and use the information already held there.
Keeping the workspace linked to that matter also gives the team a clear connection between its matter record and the PEXA workspace. It reduces the need to treat workspace setup as a separate piece of administration disconnected from the file.
Reusing saved data is not the same as proving that data is correct. The integration does not automatically transfer every contract field or guarantee that every detail is identical in both systems. Source documents, client details and transaction requirements still need appropriate review.
Thank you to PEXA
This milestone reflects close collaboration between Atto and the PEXA team. Thank you to everyone at PEXA who has worked closely with us during this first phase. We appreciate that collaboration and the attention given to connecting the systems around practitioners’ day-to-day work.
The feedback we’ve received has been encouraging, including “game changer”. For us, that is a reminder that reducing repeated administration matters: it helps teams concentrate on the work that needs their judgement, rather than entering the same details again.
Getting started
Interested in bringing supported PEXA workspace tasks into your matter workflow?
Join the Atto waitlist to register your interest. Existing Atto firms can speak with the team about their configuration and access requirements before starting.
A PEXA subscriber account, the relevant user connection and the required authority remain necessary. Registering interest is not confirmation that access has been enabled.