Xplan API access: what AFSL practices can actually build

Quick answer: Xplan (Iress’ advice software) does not offer a public, self-serve API you sign up for. Access is real, but it typically sits at enterprise tier and inside AFSL-network / licensee arrangements — which is why most searches for “Xplan API” come up short. Once access is in place, the builds that earn their keep for an advice practice are the same few every time: a branded client portal, AI-assisted document handling, automated annual-review workflows, and clean links to Class Super, Xero and MYOB. Here’s the honest version of what you can and can’t do, drawn from building this for Australian advice firms on Xplan.

Xplan is the practice management system a large share of Australian licensed financial advisers run on — client records, fact-finds, Statement of Advice machinery, ongoing-fee renewal, and the compliance documentation that sits around ASIC’s RG 175 and RG 244. It’s particularly entrenched inside the big AFSL adviser networks, which matters a great deal when you get to the question of integration.

How Xplan API access actually works

If you’ve gone looking for an “Xplan API key” or a developer portal and found only marketing pages, that’s not you missing something. Unlike a Stripe or a Xero — where you self-register, generate a key and read open docs — Xplan’s API access is arranged, not self-served. In our experience at the time of writing:

• It’s an enterprise-tier and licensee-level capability. Direct API access is generally available through enterprise arrangements and within AFSL-network deals, rather than switched on for an individual adviser’s subscription.
• The licensee is often the gatekeeper. Because so many practices operate under a licensee, the network’s arrangement with Iress frequently determines what an individual firm can and can’t connect to. Access questions that look technical are often really licensee questions.
• The documentation comes with the access. The reference you can’t find on the open web is available once you’re inside an approved arrangement — which is exactly why the public internet only shows you the brochure.

The practical upshot: you generally can’t DIY an Xplan integration by grabbing a key over the weekend. The access path runs through Iress and, usually, your licensee — so most firms have a partner handle the access conversation and the build together. It’s very doable; it just isn’t an open API.

What you can build once access is in place

The gating is on access, not on ambition. Where an arrangement allows integration, these are the patterns that consistently pay back for an advice practice — and where the API is genuinely constrained, a secure branded portal layer (reading from Xplan and presenting to clients) does much of the same work without needing deep write access.

1. A branded client portal that reads from Xplan

The single most common build. A white-labelled portal where clients see their documents, review status and can exchange files securely — pulling from Xplan so the adviser’s team isn’t emailing PDFs or fielding “has my review been done?” calls. For adviser groups and AFSL networks, this becomes a network-wide, white-label asset rather than a one-practice tool.

2. AI-assisted document handling

Inbound client correspondence — statements, ID documents, super rollovers, insurance paperwork — classified and routed automatically instead of manually filed. Done to the right standard (enterprise-tier models with explicit no-training agreements, Australian data residency), this takes a real administrative load off the practice without putting client data anywhere it shouldn’t be.

3. Automated annual-review workflows

The ongoing-fee and annual-review cycle is structured, repetitive, and deadline-driven — which makes it perfect for automation. Structured client outreach, document collection ahead of the meeting, and progress tracking so nothing quietly slips past its date. The workflow does the chasing; the adviser does the advice.

4. Recorded-meeting transcription and fact-find extraction

Client meetings recorded (with consent), transcribed, and turned into structured fact-find updates and file notes — so the adviser is present in the room rather than typing, and the record is captured consistently. A genuine time-saver on one of the most manual parts of the job.

5. Clean links to Class Super, Xero and MYOB

Advice practices rarely live in Xplan alone. Where SMSF administration runs through Class Super, or the practice’s own accounting sits in Xero or MYOB, the integration removes the double-entry and reconciliation friction between them.

The compliance and data bar is the hard part — and it’s non-negotiable

This is regulated territory, and the engineering has to respect that. We build to the technical bar advice work demands — Australian data residency (typically AWS Sydney, Azure Australia East or Cloudflare Australia depending on your existing stack), least-privilege access scoped to only the data a given integration needs, encryption in transit, and audit logging throughout.

Two lines we hold firmly, because they matter:

• AI never authors the advice. Where AI assists — classification, drafting, extraction — the licensed adviser always authorises the advice and the file. The tooling speeds the mechanical work around the advice; it does not make the advice.
• Your obligations stay yours. We build the platform to support your firm and licensee in meeting your RG 175 / RG 244 and privacy obligations. We’re the technical layer — the compliance responsibility remains with the adviser and the licensee, where it belongs. If something in a build would sit awkwardly with your licensee’s standards, that’s a conversation to have before a line of code is written, not after.

When a custom build isn’t the answer

Three cases where the honest advice is not yet:

• Solo or very small practices with contained admin. If the manual load is small, the portal-and-automation build won’t pay back yet.
• Firms mid-way through a licensee change. The licensee arrangement shapes what’s possible — settle that first.
• Practices unsure whether they’re staying on Xplan. If a platform move is genuinely on the table, hold the custom work until the decision is made.

The threshold where this work earns its place is usually a multi-adviser practice (or a network), a real ongoing-review book, and a team already feeling the cost of the manual portal-and-paperwork layer.

A typical Xplan project

Most begin with a short discovery: where the practice’s admin time actually goes, which client interactions cause friction or slip deadlines, and — critically — what the licensee arrangement allows. From there the build stages the highest-friction item first (usually the client portal or the annual-review workflow), then layers document handling, meeting-to-fact-find, and the accounting/SMSF links as appetite allows.

A first Xplan-connected build typically lands in the $25,000–$60,000 (ex GST) range for a V1, depending on how many patterns are in scope and the depth of each — a portal layer or a single automated workflow sits at the lighter end; a network-wide white-label platform with AI document handling and compliance tooling sits at the heavier end. Plan for an ongoing retainer — typically $750–$2,000/month — covering monitoring, hosting, security updates and light support, so someone is watching it as the platform and the rules around it change. (Every figure here is indicative; a real number comes from a scoped, written quote.)

Running Xplan across an advice practice or network and feeling the friction above? That’s usually the prompt to have the conversation — and the first question we’ll ask is what your licensee arrangement allows, because that shapes everything after it.

Common questions

Does Xplan have a public API I can just sign up for? No. There’s no self-serve developer portal or open API key. Access is arranged through Iress at enterprise tier and typically within your AFSL-network / licensee arrangement — see “How Xplan API access actually works” above. Most firms have an integration partner handle the access conversation and the build together.

We’re under a licensee — does that change what we can integrate? Often, yes. The licensee’s arrangement with Iress frequently determines what an individual practice can connect to, so the access question is as much a licensee question as a technical one. It’s the first thing to establish.

Can AI tools be used with Xplan client data? Yes, engineered correctly — enterprise-tier OpenAI / Anthropic / Azure OpenAI with explicit no-training agreements, Australian data residency, and least-privilege access. The licensed adviser always authorises the advice; AI handles the mechanical work around it.

Is Australian data residency available? Yes. We engineer Xplan-connected platforms with explicit Australian data residency — typically AWS Sydney, Azure Australia East or Cloudflare Australia, depending on the existing stack.

What if the API can’t do what we need? A secure branded portal layer — reading from Xplan and presenting to clients — delivers much of the value (document exchange, review status, self-service) even where deep API write access isn’t available. It’s often the right first build regardless.