MILabs
Integrations

Client onboarding automation for Xplan with human review

How client onboarding automation works with Xplan. AI prepares intake checks, and a qualified staff member approves each entry before it is saved.

Updated 2026-01-13

Client onboarding automation with Xplan

Onboarding is where a new client's file is most likely to stall. Intake forms come back incomplete, identity evidence arrives as scans, photos and emails, and someone has to decide whether the file is ready to move forward. MILabs is a Sydney agency that works with small and mid-sized businesses on AI, and this page describes one build for teams that run Xplan, the financial advice platform from Iress. The build treats Xplan as the system of record. An automation step gathers the new client's documents, reads them, and proposes the checks and fields that the file needs. A staff member then confirms each proposal before anything is written back. The build starts with a friendly conversation about how your team works in Xplan, then gets to work on the documents, the checks and the fields, so each file reaches your staff member already sorted.

How it works

  1. Intake: new client forms and identity documents are collected through the channel your team already uses and linked to a single file reference.

  2. Extraction: an AI model reads each document and drafts a summary of names, dates, addresses and document types for staff to check.

  3. Matching: the draft is compared with the client record in Xplan, and any mismatch or missing item is listed for review.

  4. Checklist: the onboarding checklist your business has documented is applied, so gaps show before the file moves to the next stage.

  5. Approval: a qualified staff member confirms or corrects each proposed entry, and only approved entries are written back, where your Xplan configuration allows it.

  6. Audit: the build keeps a record of what was proposed, who approved it and when, so the decision trail stays with the file.

good questions, straight answers

Frequently asked questions

Can I start with a part of a client onboarding automation on Xplan?
Yes. Many teams begin with the document step alone, such as reading intake forms and listing what is missing from each file, and leave the write-back to Xplan for later. That keeps the first stage small and lets your staff judge the output before any wider change. Each part can be checked on its own, and the later steps can be added once you have confirmed what your licence and configuration allow.
How does MILabs test a client onboarding automation against Xplan?
MILabs tests the build on representative sample files that contain no live client data. Each file is run through the steps, and the proposed entries are compared with what a staff member would have recorded by hand. Mismatches are logged and the matching rules are adjusted. Testing also checks that every proposed change stops at the review step, and that no entry reaches Xplan without approval.
What does MILabs do after delivering a client onboarding automation for Xplan?
After handover, MILabs can review how the build performs on your real onboarding files, and adjust matching rules and checklist prompts where the results call for it. Changes that follow an Xplan or licence update are scoped with you before work starts. Any agreed change is documented so your team knows what the build does at each point. Further questions can be sent through the enquiry form on this site.
Can a client onboarding automation work with Xplan?
Yes. The design follows what Iress documents for your account, and the staff-led route works from the start: the automation gathers documents, reads them and proposes the checks and fields, and staff enter the outputs themselves. Where direct access is available, the workflow reads and writes through it. The first conversation is about which route suits your setup. Either way, the file reaches the same finish line, with a staff member confirming each result.
What does a client onboarding automation write to Xplan?
Nothing without a staff decision. The build can prepare proposed entries, such as checklist status, document type labels and the client record each file belongs to. Those proposals sit in a review queue. Once a qualified person approves an entry, it can be written to the matching client record, provided your licence and configuration allow that write. Rejected entries are kept out of the record and logged.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.