Part two of a six-part guide to setting up, monitoring and troubleshooting datafeeds in Xplan.
Article 2: The setup — building a reliable connection
A datafeed setup is a little like bringing on a new team member - intensive onboarding and routine check-ins set them up for success. First, the platform needs to recognise the adviser or firm. Then Xplan needs to know where that adviser belongs, what data should be imported and who is responsible for checking the result.
1. Register with the platform
The first step happens outside Xplan. Many platforms require the adviser or firm to register before data can be supplied. This may involve providing firm details, accepting the platform’s terms, requesting access or setting up credentials. Registration times vary, so allow for this when planning a new datafeed.
Each provider can have different set up requirements - refer to your region-specific Platform summary page for details. Take the time to confirm what the provider supplies - portfolio, insurance, risk, assets and liabilities, documents or other data - because this will influence the options you chose later in the set up process.
2. Map the Adviser ID
Once the platform has issued an Adviser ID, enter it in Xplan. See: Registering for a Datafeed in Xplan - Adviser Mapping. This links the platform’s identifier to an Xplan user and tells IressNet which adviser the data belongs to.
The usual path is Admin > Integration > System Datafeeds > Mappings > Advisers.
Depending on the platform, you may also need to enter a username and password. Where available, use Validate Credentials before saving. If validation fails, check the details carefully and try again. An expired or invalid credential can stop IressNet from obtaining data even when everything else has been configured correctly.
A useful best-practice check is to map the Adviser ID against the same adviser or user that is registered with the platform. If the registration belongs to a business rather than an individual, select the best-fit user and document that decision.
3. Confirm user capabilities
The user completing the mapping needs the right capabilities. An adviser entering their own mapping generally needs View Datafeeds and Modify Own External Adviser IDs. A Datafeed Administrator working on behalf of other users needs Administer External Adviser IDs, along with the ability to view datafeeds.
Review the full list in Managing User Capabilities for Datafeeds, particularly if a user can see the datafeed module but cannot perform a specific task.
4. Activate the platform
Next, activate the datafeed within Xplan. Activation tells IressNet that the site is ready to receive data. At least one Adviser ID must be mapped before activation is available, and activation only needs to be completed once per Xplan site.
If you later need to stop a feed, the same detailed guide explains how to disable it. Remember that disabling a feed is a configuration decision, not a substitute for resolving a data-quality issue.
5. Review Processing Options
After activation, review the Processing Options. Iress provides default settings for each datafeed, and these are the recommended starting point for businesses that are new to datafeeds. More experienced practices can adjust them at site level or create Adviser Overrides for a specific Adviser ID. Always reach out via Iress Connect if you are unsure or want more information on an option.
Pay particular attention to:
- Match Client Data, which can reduce manual mapping;
- Create New Clients, which can create records using information supplied by the platform.;
- Mark account out of balance and Mark position out of balance, which surface reconciliation issues;
- DateLocks, schedules and transaction settings, which affect how historical and future data is managed.
Unless the datafeed is your main source of client information, consider whether automatic client creation is appropriate for your business - you don’t want to end up with duplicate client records!
6. Configure notifications
Finally, use Configuring User Notifications for Datafeeds to make sure the right people know when data arrives and when something needs attention. Notifications can highlight new clients, unmapped accounts, invalid credentials, newly created securities or holdings that are out of balance.
💡 Pro Tip: Before you finish setup, ask a colleague to follow the process using their own login. It is a quick way to find missing capabilities, unexpected visibility restrictions or notification settings that only work for the administrator.
Learn more here: Xplan Datafeeds - Getting Started.
Are your datafeeds set up correctly?
Pick one active provider and trace it end to end: are all Adviser IDs mapped, is the feed activated, are the credentials valid and are notifications configured?
