Send a plan to your CRM
Sending a plan writes it back to the client's connected CRM: the plan itself, the funds it holds, its valuations and what is being paid into it. You ask Templi to send it in chat, and nothing leaves Templi until you approve the exact change.
Before you send
Plans are switched on per firm. If a client has no Plans page, ask your Templi administrator to turn plans on.
The plan needs somewhere to go. Templi sends a plan back to the system it came from, and a plan you recorded yourself goes to the CRM its client came from. A client with no connected CRM has nowhere to send to.
Intelliflo Office and Plannr take a plan only as a pension, investment, protection or mortgage. A plan left as Other has no equivalent in either system.
Every client on a joint plan needs a record in the CRM before the plan can go across, so that ownership is recorded correctly.
Send a plan
Get the plan right in Templi first: the send covers the plan and everything on it as one change.
Correct the plan's details, add or amend the funds it holds, and record the latest valuation.
Ask Templi in chat to send the plan to your CRM.
Read the approval request. It lists what has altered since the plan last went across successfully.
Approve it. Templi queues the send and tells you what the CRM took.
Nothing reaches your CRM until you approve that exact change. Turning the request down sends nothing at all.
What each system accepts
All three take the plan itself. What they do with its funds, valuations and contributions differs, and each system's own page carries the full detail: Intelliflo Office, Iress Xplan, Plannr.
What is sent | Intelliflo Office | Iress Xplan | Plannr |
|---|---|---|---|
The plan | Yes | Yes, as a pension, asset or liability. A protection policy has no Xplan record, so it is reported back to you instead of sent | Yes |
Fund holdings | Yes, when the holding has units, a unit price, a valuation date and an ISIN, SEDOL or Citicode | Never. Xplan's portfolio can only be read | Yes, when the holding has units and a unit price |
Valuations | Yes, every valuation Intelliflo does not already hold | The most recent one only, as the record's value | The most recent market valuation only, as the plan's current value |
Contributions | Yes, every contribution Intelliflo does not already hold | One regular contribution on a pension, and none on an asset or liability | Not sent |
What a plan is worth
A plan's value comes from its most recent market, fund, estimated or other valuation. A surrender or transfer figure is what the plan would pay out if it were cashed in or moved on, so it never stands as what the plan is worth.
Record a surrender or transfer figure as its own valuation rather than as the market value. Templi keeps both, and the plan still shows the market figure.
Fund identifiers
A holding keeps its ISIN, SEDOL and Citicode as three separate values, held apart from the provider's own fund code. Type one identifier into a holding and Templi reads its check digit to work out whether it is an ISIN or a SEDOL, and files it as that. Anything that is neither is kept as the provider's code.
Blank identifiers are normal, because a system supplies only the codes it holds. Intelliflo needs at least one of the three before it will match a holding to a fund, so fill one in before sending a holding you recorded by hand.
When part of a plan cannot be sent
Each part of the plan is reported on its own, so one holding your CRM will not take does not stop the plan going across. The result names the reason per row: a missing unit price, a provider your CRM does not recognise, a client with no record in the CRM yet, or a plan type your site does not offer.
Fix what the message names and send the plan again. A second send updates what the CRM already has rather than creating it twice.