Valuation feeds are crucial, ensuring that client records stay updated with the latest valuation data. This article explains how the process works, when updates are made, and how to troubleshoot common issues with receiving valuation feeds.
Timing and Schedule of Valuation Feeds
Provider | Run time | Feed Type |
Abrdn | 09:00 | Origo Integration Hub |
Aegon ARC | 09:00 | Origo Integration Hub |
Aegon Platform | 09:00 | Origo Integration Hub |
AJ Bell | 05:00 | Direct |
Aviva Platform | 09:00 | Origo Integration Hub |
Fidelity | 08:00 | Direct |
Fundment | 10:00 | Direct |
Hubwise | 12:00 | Finio |
James Hambro | 09:00 | Origo Integration Hub |
LGT Wealth | 10:00 | Origo Integration Hub |
LV= | 09:00 | Origo Integration Hub |
M&G | 12:00 | Finio |
Nucleus | 04:30 | Direct |
Parmenion | 08:45 | Direct |
Prudential | 11:00 & 20:00 | Origo Integration Hub |
Quilter | 10:00 | Direct |
Raymond James | 12:00 | Finio |
Royal London | 01:00 | Origo Integration Hub (Unipass) |
Scottish Widows Platform | 09:00 | Origo Integration Hub |
7IM | 12:00 | Finio |
Soderberg & Partners | 08:45 | Direct |
Standard Life | 06:00 | Origo Integration Hub (Unipass) |
Transact | 07:45 | Direct |
Wealthtime | 12:00 | Finio |
Wealthtime Select | 12:00 | Finio |
Notes
Fundment - The data retrieved corresponds to the prior day's valuations. For example, a valuation file received on the 31st will include valuations from the 30th.
No updates occur on weekends, meaning there are no new valuations for Saturdays or Sundays. Any updates for those days will be included in the next weekday's data feed.
Troubleshooting Common Issues
If you are experiencing issues with receiving valuation feeds, such as after making updates to plan numbers, follow these steps to resolve the problem:
Verify Policy Number Format: Ensure that policy numbers follow the correct format and match what the Provider holds. E.g. does it need a suffix at the end (-001).
Check Provider Name: The provider name in the client’s plan must align with the correct, updated naming convention. For example, if the provider was rebranded (e.g. from Embark to Scottish Widows Platform), ensure that the provider name is updated to reflect the new name. Incorrect or legacy provider names may disrupt data synchronisation.
Check Platform Directly: Ensure the Platform is still showing the same policy number and a valuation for the policy.
Allow Overnight Processing: After making the corrections mentioned above, let the overnight valuation feed process run. Check the data feed again the following day to confirm the issue is resolved.
Troubleshooting Unipass Feed Issues
For our Unipass datafeeds, these sometimes have their own complexities. Here are some common issues and how best to resolve them:
Ensure Unipass certificate is uploaded by the Adviser: This is the most simple way to ensure the Unipass feeds work as intended - as the plans (under the relevant provider) should already be linked to the Adviser. If this isn't the case, then follow the next step.
Ensure "the adviser to use for contract enquiry requests" matches the user that holds the Unipass certificate: If a member of your support team has uploaded the Unipass certificate instead, ensure they're under the 'Adviser' department, in order to select them in the contract enquiry box. This box can be located by going into the relevant plan > plan details > scroll down slightly.
Check the Adviser is correctly registered against the plan with the Provider: Sometimes, the Provider will have a different adviser linked to the policy. Ensure you've checked with them the correct adviser is linked.
Ensure Unipass Certificate is linked to Login: Check the user can log into the relevant Provider, using their Unipass certificate. If they only log in with a username and password, it's unlikely the feed will work as intended. You will need to speak to the relevant Provider to link the two together.
By following these steps, most common issues related to failed or missing valuation feeds can be resolved efficiently. If you're still having issues, then please speak to our support team.