Best Practice for Managing User Groups
Hi Network 👋 Keen to tap into your collective wisdom on best practice strategies for managing user groups in Xplan. For practices that outsource administration and paraplanning, and need to grant third-party access to their Xplan site—what key considerations should be kept in mind when adding or removing clients from user groups to ensure appropriate access and data security? Thanks in advance for sharing your insights 🙏17th July AMA: I'm Kenny Foo, Xplan expert, Ask Me Anything!
If you want a genuine competitive edge, streamline your operations and serve more Aussies; accurate data isn’t just a nice-to-have – it’s non-negotiable. But are you following data best practices when it comes to Xplan? For example, are you segmenting clients properly? Are file notes orderly and retrievable? Do you have zero client email bounceback? If not, join me here on Thursday, 17 July from 3pm to 4pm AEST. I’ve worked with many practices to optimise processes and boost everyday efficiencies. If it’s about establishing solid data foundations, there’s a good chance I can help you do so with Xplan. I’m here to help. Don't miss out – post your questions in the thread now! 💬 This AMA is text-based so I’ll answer your pre-submitted questions in the scheduled time. 📆 Click here to save the date in your calendar. 🔔 Don’t forget to hit the bell in the top right corner to be notified. 🎙️ Let us know what you thought of the AMA and what topics you would like to see next here.🤓 Xplan Hint: Don’t let yourself be the last to know
Did you know you can subscribe to the release notes in Xplan? If you didn’t know, or if you did know but haven’t bothered yet, you’re missing out! By subscribing, you’ll get an email in your inbox with the latest release details so you’ll never have to say, “Oh, I didn’t know that”, ever again. There are some very cool things being released, and while the larger enhancements get exciting announcements, some of the smaller improvements, that can actually make a big difference to your everyday, can get overlooked. It takes less than a minute to subscribe. Don't let yourself be the last to know - subscribe now! 💡There’s actually something that I think is very cool coming in the next release….so keep your eyes peeled. 👀🤓Xplan Hint: Supercharge your Searches with Syntax
Did you know you can use search syntax in Xplan to create powerful and specific advanced searches—beyond what the basic interface allows? With just a few lines of code, you can target contact details, user fields, adviser roles, and even partner relationships. It’s a game-changer when you need ultra-targeted search results—especially for reporting, segmentation, or compliance checks. Let’s unpack what’s possible. 🧠What is Search Syntax? Search syntax allows you to write logical search queries directly using Xplan’s internal field references. This unlocks additional fields that aren't always available via the standard Advanced Search screen—think adviser roles, contact fields, and even partner data. The general format looks like this: <:let result = $entity.compare('field_path', 'operator', 'value'):> And you enter it here 💡 Practical Examples You Can Try Cleaning up data gaps - Find clients where Date of birth is blank Client Partner Find clients with a service adviser named Jack Smith OR done as multiple lines You can also use these adviser roles: client_adviser_service client_adviser_paraplanner client_adviser_investment …and more! 🧪 Pro Tips Syntax search is case-sensitive—double-check spelling! You can mix syntax and standard search criteria for hybrid searches. Saved Syntax can be reused across searches, reports, and bulk actions. Have a go at writing your own syntax—or try tweaking one of the examples above to fit your client data. 👇 Already using search syntax like a pro? Share your favourite syntax use cases in the comments—we’d love to see them in Advance Search with Search Syntax Search Syntax: User Fields Search Syntax: Address and Contact
Risk Researcher - How can I update the owner to super fund for super-owned cover?
Hi brain trust, When I click REC button in Premium Estimates section, this product appears on Recommendations section. However, ownership for super-owned policy is the client's name. How can I set it up to 'Superannuation' automatically?
🤓Xplan Hint: Datafeed provider balances
Did you know you can now see if the balance in your clients’ portfolio accounts matches the balance sent to Iress by the datafeed provider right within the client portfolio screen? You no longer need to navigate to the datafeed reconciliation reporting screens - you can view the provider balances (as sent to IressNet) right there in Xplan alongside the current balance. You can choose to see the existing portfolio data, the provider's balance data, or both at the same time, centralising where you work and removing all that screen-hopping! You'll need to enable the "platform" columns to see them, as they're not on by default, but then you can customise and save your view so you can load in provider balances anytime you want. There is no data in the above platform columns as there are no live datafeeds in this site. There's a brand-new report called “Portfolio Valuation - Platform Balances” in case you want to report on the balances, and for those of you who love Xmerge, there's a new holdings data source called “holdings2025” that supports this new data. 💡Tip: Always enable the "Platform Data Date" column so you know exactly when that provider data was last updated, especially since the system will show you the latest available data if there's nothing for your chosen date. Check out the Iress Community for more info on configuring your Portfolio grid columns But what if it looks wrong? We've got you covered! Check out our FAQ's for tips on how to troubleshoot if the data is not as you expect! Or any one of our Datafeed Reconciliation or Datafeed Reporting guides in the Iress Community.🤓Xplan Hint: DBFO consent comes to Xplan Risk Researcher
Did you know Risk Researcher now enables you to document client consent for insurance commissions? As many of you know, from 9 July 2025, advisers providing personal advice on life insurance will need to obtain informed client consent before implementing advice or receiving commissions. (Delivering Better Financial Outcomes (DBFO) Act 2024,) Now, you can easily record client consent using the new Insurance Commission Consent (ICC) column in Risk Researcher’s recommendations screen. It allows you to indicate whether consent has been received for each product you recommend. And yes, there’s new merge syntax available so you can include the details in your documents. This update was the result of conversations with several of you. Many shared that consent would typically be captured in their Advice documents (e.g., ATP) or other consent forms. For more information, check out the community article Meeting DBFO informed consent requirements in Xplan. Now that Risk Researcher supports consent tracking, and lets you include it in your documents, we’re also thinking ahead. Are there other ways you’d like to use this data? We’d love to hear your thoughts around any other use cases you see for insurance fee consent. Let us know in this thread!
