You can automate PEXA settlement date reminders by pulling the key dates — cooling-off expiry, finance approval, and settlement — out of your matter management system (or a shared spreadsheet) and feeding them into an automation tool like Zapier or n8n, which then sends scheduled alerts to staff and clients at set intervals. The reminders sit alongside PEXA, not inside it. PEXA governs the lodgement and financial settlement itself; it does not manage the weeks of deadlines that lead up to settlement day. That gap is where matters slip, and it is exactly what you can automate.
This article is for Australian conveyancers and small conveyancing teams who are tired of manually diarising every cooling-off date and chasing clients for finance confirmations by hand. You do not need a developer, and you do not need to replace any of your existing systems.
Why PEXA doesn't handle your reminders
PEXA is an electronic lodgement network. It coordinates the settlement event — the exchange of funds and the registration of documents — between the parties, the banks and the land registry. It is very good at the thing it does.
What it does not do is track the critical pre-settlement milestones that make or break a matter: the cooling-off period, the finance approval deadline, the building and pest inspection window, unconditional date, and the countdown to settlement itself. Those live in your contract, your file notes and your head.
PEXA's API access is also limited and tightly governed, so building directly "inside" PEXA is not a realistic option for a small firm. The practical answer is a reminder layer that reads dates from wherever you already record them and acts on them automatically. For the broader picture of what else can be automated around settlement, see our guide to AI for conveyancers in Australia and automating settlement workflows.
Which dates are worth automating?
Not every date needs an automated reminder. Automate the ones where a missed deadline has real consequences — for the client, for the contract, or for your professional liability.
| Milestone | Who gets reminded | Typical lead time |
|---|---|---|
| Cooling-off expiry | Staff + client | 2 days before, day of |
| Finance approval due | Staff + client | 5 days and 2 days before |
| Building & pest deadline | Staff + client | 3 days before |
| Unconditional date | Staff | On the day |
| Settlement date | Staff + client | 7 days, 2 days, day of |
Cooling-off and finance periods vary by state — Queensland, NSW, Victoria and South Australia each have different rules and timeframes — so your reminder templates need to reflect the jurisdiction of each matter. Build the state into your data so the automation knows which rules apply.
How to build the reminder system, step by step
Here is the simplest reliable approach. You can have a first version running in an afternoon.
- Pick your source of truth for dates. This is where each matter's dates live. If you use a practice management system like LEAP, that is your source. If you track matters in a spreadsheet (Google Sheets or Microsoft 365), that works too. The key is one place, consistently filled in.
- Add a clean date column for each milestone. Cooling-off expiry, finance due, settlement date, and so on — as proper dates, not free text like "end of next week". Automation can only act on structured dates.
- Choose an automation tool. For most small firms, Zapier is the fastest to set up; n8n gives you more control and can be self-hosted for tighter data governance. We compare them in n8n vs Zapier for professional services firms.
- Build a scheduled check. Set the tool to scan your matter list once a day (early morning works well) and find any matter where a milestone is a set number of days away.
- Send the right reminder to the right person. Staff reminders can go to a shared inbox, Teams or Slack channel, or an internal task list. Client reminders go by email or SMS — and these must be reviewed templates, not free-form AI output.
- Log that the reminder was sent. Write a note back to the matter or a tracking column so you have an audit trail and never double-send.
That is the whole engine: one source of dates, a daily check, and templated messages out. Everything else is refinement.
Writing the reminder messages
Staff reminders should be blunt and action-oriented: "Matter 1042 — finance approval due in 2 days. Last client contact 6 days ago." No pleasantries, just the next action.
Client reminders need a different tone — clear, reassuring and specific about what you need from them. You can draft a small library of these once and reuse them. A language model is genuinely useful here for getting the wording right across different milestones and states. Our roundup of the best ChatGPT prompts for conveyancers includes prompts you can adapt for exactly this.
One firm rule: the AI drafts the template, a human approves it, and the automation only ever sends the approved version with the matter's details merged in. Never let an AI generate client-facing text live, unreviewed, on send.
Keeping client data safe
The moment a matter reference, a client name or a property address flows through an automation tool, you are handling personal information under the Privacy Act. The OAIC's general guidance is clear that the Act applies when personal information enters an AI or automated system, and that publicly available chatbots should not be fed personal information.
Practical rules for this build:
- Use enterprise or paid API tiers of any tool, where your data is governed by contract and not used to train models.
- Pass only the fields a reminder actually needs — a matter reference and a date are often enough internally; avoid pushing full client records around.
- If a tool processes data overseas, treat that as a cross-border disclosure under Australian Privacy Principle 8 and document it.
- Keep a written data-flow record for the automation: what data moves, where, and why.
For a fuller treatment, read whether AI is safe for client data under the Australian Privacy Act. This is general guidance, not legal advice — check it against your own obligations.
What breaks, and how to catch it early
Reminder automations fail quietly, which is the dangerous part. The reminder that does not fire looks exactly like a day with nothing due. Watch for these failure modes:
- Missing or badly formatted dates. If a date field is blank or holds text, the automation skips it silently. Add a weekly check that flags any open matter with empty date fields.
- Time-zone and date drift. A reminder set for "2 days before" can fire a day early or late if time zones are mismatched. Test with a dummy matter before trusting it.
- Public holidays. Settlement timeframes don't care that it's a Queensland show-day holiday. Build business-day awareness into critical reminders, or review the week's deadlines manually each Monday.
- Duplicate sends. Without a "reminder sent" log, a matter can be alerted every day until the date passes. Always write back a sent flag.
Run the system in parallel with your existing manual diarising for the first few weeks. Trust it only once it has proven itself on live matters.
When not to automate a reminder
Automation is the wrong answer for anything requiring judgement or carrying real risk if it goes wrong. Do not automate the final settlement authorisation, funds confirmations, or any communication that tells a client a condition has been satisfied — those need a human who has checked the file. The reminder should prompt the conveyancer to act; it should never be the action itself.
If your matter volume is low, a well-maintained shared calendar with alerts may be all you need. The honest test is in our article on what admin work you should automate before hiring: automate the repetitive, rules-based chasing — keep the judgement calls human.
Who owns and maintains it afterwards
This is where DIY automations fall into "shadow IT". Decide up front who owns the system, where the login lives, and who fixes it when a tool changes its interface — which Zapier, n8n and the rest do regularly. Document it, list it in your firm's AI and systems policy, and make sure the knowledge doesn't walk out the door with one staff member. A simple one-page runbook describing the data flow and the fix-it contact is enough for a small team.
If you want a structured starting point, our free guide, 10 AI Workflows to Save 10+ Hours a Week, walks through reminder automations and other quick wins you can build around your existing conveyancing systems without replacing a thing.
Common questions
Can PEXA send settlement date reminders automatically?
PEXA coordinates the settlement event itself — funds and lodgement — but it is not designed to manage the lead-up deadlines like cooling-off, finance approval or inspection windows. PEXA's API access is also limited for small firms. The practical approach is a separate reminder layer that reads dates from your matter system and sends scheduled alerts alongside PEXA.
What's the easiest tool to automate conveyancing reminders?
For most small Australian conveyancing firms, Zapier is the fastest to set up — it can scan a spreadsheet or practice management system daily and send alerts by email, SMS or Teams. n8n offers more control and can be self-hosted for tighter data governance. Both let you build a working reminder system without writing code.
Is it safe to put client details through an automation tool?
It can be, if you handle it properly. Use paid or enterprise tiers where data isn't used for training, pass only the fields a reminder needs, treat any overseas processing as a cross-border disclosure under Australian Privacy Principle 8, and keep a written data-flow record. The OAIC's general guidance is that the Privacy Act applies whenever personal information enters an automated system.
Should client reminders be written by AI?
AI is useful for drafting reusable reminder templates, but it should never generate client-facing messages live and unreviewed. The safe pattern is: AI drafts the template, a conveyancer approves it, and the automation only ever sends the approved version with the matter's specific dates merged in. This keeps tone consistent and avoids errors reaching clients.
How do I stop automated reminders from missing deadlines?
The main risks are blank or badly formatted date fields, time-zone drift, public holidays and duplicate sends. Guard against them with a weekly check for empty dates, business-day awareness on critical reminders, a sent-flag log, and testing on a dummy matter first. Run the automation alongside your manual diarising until it has proven reliable on live matters.
Want these ideas working in your firm? We build controlled AI workflows for Australian professional services firms — starting with a free automation audit.