Xplan (Iress) Integration Guide
This guide explains what happens when you push policy data to Xplan from 4admin, for both pension and investment policies. For setup, see CRM Integrations.
Pensions and investments
When you create a new plan you choose Pension or Investment, and 4admin writes the data to the matching record in Xplan:
- Pensions are written to the client's Pension plans.
- Investments are written to the client's Asset plans.
Xplan treats these as two different kinds of record with slightly different fields, so 4admin maps your extracted data to the right place automatically. The push experience is the same for both.
What gets pushed
Plan data
| 4admin field | Xplan field (Pension) | Xplan field (Investment) |
|---|---|---|
| Plan Number | Policy Number | Policy Number |
| Plan Value | Fund Value and Current Value | Current Value |
| Original Investment Amount | — | Initial Value |
| Valuation Date | Fund Value Last Updated On and Current Value Last Updated On | Current Value Last Updated On |
| Start Date | Start Date | — (see note) |
| Provider | Provider and Product Provider | Provider |
| Policy Type | Type | Type |
Xplan records an investment's inception as a Purchase Date rather than a Start Date. 4admin does not write this, so the Start Date toggle does not apply to investment pushes. Set the Purchase Date in Xplan if you need it.
Contributions
Contributions are pushed for both pensions and investments as a CSV document note with columns Date, Type and Amount. The note's subject is ContributionHistory_[Provider]_[Plan Number]. It is only created when contribution data was found.
Documents
Documents are uploaded as document notes, using the Document Type and Subtype from Configure CRM:
- Uploaded policy document(s): the original policy PDF
- Generated checklist document: Word, Excel or both
- 4admin Call Summary: only when the analysis includes calls made through 4admin
Depending on your Configure CRM setting, each file is posted as its own document note or all files go into a single note (Create a separate document note for each attachment).
The push process
Step 1: Sign in to Xplan
Click Push to with the Iress logo on the policy. A new tab opens for Xplan sign-in. Sign in and authorise 4admin.
Step 2: Find the client
Use Search by client name or Search by ID and press Enter. Results show the client name, date of birth and client ID.
Step 3: Select or create a plan
Under Select Plan, pick an existing pension or asset plan to update (shown as provider and policy number), or choose New plan and fill in:
- Select Policy Type: Pension or Investment
- Select Provider: the list matches the policy type you picked
- Select Type: the sub-type list also matches the policy type, for example SIPP or Personal Pension for pensions, ISA, GIA or Investment Bond for investments
- Select Plan Status
4admin remembers whether each existing plan is a pension or an asset and pushes to the correct one.
Step 4: Choose what to push
Each item has a toggle:
- Valuation: plan value as at the valuation date
- Start Date: pensions only
- Plan Number
- Initial value: investments only, from the original investment amount
- Contribution history as a document note
If 4admin couldn't read a date or amount cleanly, that toggle is greyed out with a warning icon and is never pushed.
Step 5: Name your documents
- Uploaded policy document(s): toggle and title
- Generated checklist document: toggle and title; tick Word, Excel or both; use the Page numbers switch to include or exclude citations
Names are pre-filled from your file naming templates. The default is {Provider} - {PlanNumber}.
Step 6: Push
Click Push data. You'll see You're all done! when it completes. Xplan doesn't provide a push summary, so check the record in Xplan if you want to confirm what landed.
What appears in Xplan
Pension plan
| Field | Value |
|---|---|
| Description | [Provider] [Policy Type] |
| Policy Number | From the extracted data |
| Start Date | Plan commencement date |
| Fund Value and Current Value | Plan value in GBP |
| Fund Value Last Updated On and Current Value Last Updated On | Valuation date |
| Provider and Product Provider | Selected provider |
| Type | Selected sub-type |
| Status | Selected status |
Investment (asset) plan
| Field | Value |
|---|---|
| Description | [Provider] [Policy Type] |
| Policy Number | From the extracted data |
| Current Value | Plan value in GBP |
| Initial Value | Original investment amount in GBP |
| Current Value Last Updated On | Valuation date |
| Provider | Selected provider |
| Owner | The selected client at 100% |
| Type | Selected sub-type |
| Status | Selected status |
Document notes
- [Document name].pdf: original policy document
- [Document name].docx: Word checklist (if selected)
- [Document name].xlsx: Excel checklist (if selected)
- ContributionHistory_[Provider]_[Plan Number].csv: only if contributions were found
- 4admin Call Summary: only if the analysis includes calls
Page numbers
With Page numbers on (the default), each value in the checklist shows where it was found, for example "£50,000 (P3)". Switch it off for a clean, client-facing checklist.
Tips
- Pick the policy type first. The provider, type and status lists change to match it.
- Search by the exact name, or use the client ID.
- Check existing plans before creating a new one to avoid duplicates.
- Review the toggles. Anything greyed out needs fixing in 4admin before it can be pushed.
Troubleshooting
- Client not appearing: try a different name variation, or search by ID.
- Plan creation fails: make sure Provider, Type and Status are all selected. For investments, the selected client is set as the owner automatically.
- A toggle is greyed out: correct the value on the policy in 4admin, then push again.
- Documents not appearing: document notes can take a moment to process. Look in the client's Document Notes, not the Documents tab.
- Date format issues: 4admin accepts DD/MM/YYYY, DD/MM/YY and DD-MM-YYYY. A date that can't be parsed is skipped rather than pushed incorrectly.
- Large policy documents: the original PDF is compressed automatically. Very large files (over about 10 MB after compression) are skipped while the plan data still pushes.