Ability to make API calls using a Planner Central license
Thank you ever so much for taking the time to respond to my enquiry.
It is deplorable that we cannot make API calls to Xplan using the Planner Central license as we had identified that the biggest workflow improvements would be from our ability to interface directly with Xplan to input client information accurately and efficiently. We will potentially explore other alternatives to Xplan (ie, competitors that allow for API calls to be made to their platform without charging an arm and a leg) so as to present an alternative to the paraplanning organisation's stakeholders.
We are open to any other alternatives and suggestions anyone might have implemented already as to the most efficient ways to enter client information in Xplan.
Thanks again.
Michael
Iress ContributorCan you detail what precisely you are trying to achieve and where the issue sits in your process? If I can understand the use case, then I may be able to give you an alternative to achieve the desired outcome.
Thanks
Andrew
Thank you for your offer of assistance.
In response, we are seeing some time wasted transferring client information from documents provided by financial advisors into Xplan for a number of reasons so we'd like to streamline this process by using an API to create/amend client information into Xplan first time every time.
Also, there are a few emails being exchanged between the paraplanning company staff and financial advisors, asking for further clarification in regards to the sub-products/sub-classifications used. Once the information has been provided by financial advisors, we would like to trigger a process to upload the relevant information into Xplan using API.
In essence, we have identified that there are a number of manual tasks that could be automated/streamlined using API ... hence my original post.
Thank you for your input to address the above conundrum and I hope that your response(s) can help others as well.
Cheers,
Michael
- andrew.wilson
Apologies in advance but I am a little lost.
Focusing on "we are seeing some time wasted transferring client information from documents provided by financial advisors into Xplan for a number of reasons so we'd like to streamline".
By documents are you referring to PDFs, docx, etc? How do you see APIs taking data from these documents? I ask as, if you are currently getting the information from these documents into a useable digital format, could you save as a CSV and do an upload to Xplan.
Cheers
Andrew
Thank you for your prompt response.
I am sorry if I wasn't clear enough as your questions are perfectly valid.
In response:
- I was in fact referring to PDF documents containing typed as well as handwritten notes sent by financial advisors to the paraplanning company. It appears that the financial advisors have their own template that they use to collect client information. Once the template has been completed, they then print it, add handwritten notes to the printed pages before emailing a scanned version of the documents in PDF format to the paraplanning company. So, that's why the PDF documents sent contain both typed and handwritten notes.
- Time spent reading the sent PDF documents and deciphering handwritten notes contained therein, can be time-consuming as it often involves phone calls and email exchanges to clarify., before the client information can be entered into Xplan.
- We have (almost) completed the ability to read the PDF documents sent and decipher the handwritten notes but we would now like to upload the client information that was read from the PDF documents, into Xplan in as efficient a way as possible ... hence exploring the use of API calls to fill in client information, etc in Xplan.
- Saving the PDF document as a CSV is not practical as there are handwritten notes on the PDF document.
Does the above make sense?
Cheers,
Michael
Recent Discussions
Related Content
