Mapping CommPay Policies to Clients Overview

Viewing your clients' unmapped CommPay policies

To view your clients' unmapped CommPay policies:

1. Go to XPLAN > Administration Functions > CommPay
   
   
   
   
2. From the menu on the left-hand side, go to Mapping > Client Map
   
   
   
   
3. In the Filters panel:
   
   
   
   
   1. Select the required Adviser from the drop down list.
   2. Select other filters, as required (e.g. Client Name,Account).
   3. Click Search (in the top right-hand corner of the screen).
      
      
4. A list of clients with unmapped CommPay policies will be displayed in the CommPay Clients panel.
   
   If a client’s CommPay policies are displayed in the CommPay Clients panel, these revenues will not be disclosed on their FDS when it is merged at the end of their service arrangement period. The client’s CommPay policies must be mapped to their XPLAN client record for disclosure on their FDS.
   
   
5. To view a client’s unmapped CommPay policies, click on the expand icon to the left of their name:
   
   
   
   The client’s unmapped policies will be displayed:
   
   
   • This may assist in mapping the CommPay policy to the correct XPLAN client by using the policy number as an identifier. This will be most helpful where you may have numerous clients with the same or similar names.
     
     

Mapping CommPay policies to XPLAN clients

How do I map CommPay policies to XPLAN clients?

Mapping one CommPay policy to an XPLAN client To map a client’s CommPay policy to their XPLAN client record:

1. Follow Steps 1 to 4 above for How do I view my client’s unmapped CommPay policies?
   
   
2. In the CommPay Clients panel, locate the CommPay policy to be mapped. Tick the client/policy, and then click on the down arrow icon to the left of the client’s name and select Seek Match:
   
   
   
   
3. The XPLAN database will be searched for clients with the same surname as the CommPay policy. The list of possible XPLAN client matches will be displayed in the XPLAN Clients panel.
   
   
   • Note: The CommPay surname data quality is entirely dependent on the format and quality of the revenue statement provided to Wealth Axis by the product provider.
     
     
4. If the client’s record is displayed in the XPLAN Clients panel:
   
   
   • Tick the client record the CommPay policy is to be mapped to.
     
     
     • For jointly-held policies, it is recommended you select the master client (or entity).
       
       
       
       
   • Click Match (at the top right-hand corner of the screen).
     
     
5. If the client’s record is not displayed in the XPLAN Clients panel:
   
   
   • In the CommPay Clients panel, click on the down arrow icon to the left of the client’s name and select Search:
     
     
     
     
   • The Lookup Client search interface will be displayed. Search for and select the required client record.
     
     
   • Tick Match Immediately and click Ok.
     
     
     
     
6. Once mapped, the CommPay policies will no longer be displayed in the Client Mapping page (at Mapping > Client Map > CommPay Clients). The CommPay policies and the underlying revenues will now be displayed in the client’s XPLAN record at Fees > CommPay.

Mapping multiple CommPay policies to an XPLAN client

To map two or more of a client’s CommPay policies to their XPLAN client record:

1. Follow Steps 1 to 4 above for How do I view my client’s unmapped CommPay policies?
   
   
2. In the CommPay Clients panel, locate the CommPay policies to be mapped. Tick the clients/policies, and then click on the down arrow icon to the left of one of the ticked clients/policies and select Search:
   
   
   
   
3. The Lookup Client search interface will be displayed. Search for and select the required client record and click Ok.
   
   
   • For jointly-held policies, it is recommended you select the master client (or entity)
   • The Match Immediately option should be left unticked
     
     
     
     
4. The client’s record will be displayed in the XPLAN Clients  panel.
   
   
   • Tick the client record the CommPay policies are to be mapped to.
   • Click Match (at the top right-hand corner of the screen).
     
     
     
     
5. Once mapped, the CommPay policies will no longer be displayed in the Client Mapping page (at Mapping > Client Map > CommPay Clients). The CommPay policies and the underlying revenues will now be displayed in the client’s XPLAN record at Fees > CommPay.

CommPay policies that can't be mapped to an XPLAN client

There are a number of reasons why a CommPay policy can’t be mapped to an XPLAN client.

Your options are:

1. Create a “dummy” client in XPLAN to which you can map these CommPay policies.
   
   
2. Indicate (or flag) the CommPay policy doesn’t require mapping. No Mapping Required signifies that the CommPay client/policy does not need to be mapped to an XPLAN client, and will hide it from the Client Mapping page (at Mapping > Client Map > CommPay Clients).

How do I flag a CommPay policy as No Mapping Require?

To flag a CommPay policy as No Mapping Required:

1. Follow Steps 1 to 4 above for How do I view my client’s unmapped CommPay policies?
   
   
2. In the CommPay Clients panel, locate the required CommPay policy. Tick the client/policy, and then click on the down arrow icon to the left of the client’s name and select No Mapping Required:
   
   

How do I reset a CommPay policy flagged as No Mapping Required?

To reset a CommPay policy previously flagged as No Mapping Required, to enable you to map it to an XPLAN client:

1. Follow Steps 1 to 4 above for How do I view my client’s unmapped CommPay policies?
   
   
2. In the Filters panel, tick Inc. No Mapping Required and then click Search (at the top right-hand corner of the screen):
   
   
   
   
3. In the CommPay Clients panel, locate the CommPay client/policy to be reset. Tick the required policy, and then click on the down arrow icon to the left of one of the ticked clients/policies and select Reset No Mapping Required:
   
   
   • CommPay policies flagged as No Mapping Required will be displayed in italics
     
     
     
     
4. This will reset the CommPay policy back to mapping required, and allow it to be mapped to an XPLAN client.

Troubleshooting Tips

I’d like to know more about the FDS Fee Categories assigned to CommPay policies

Contact your Brokerage Team

Can I map only selected revenues (or transactions) for a CommPay policy to an XPLAN client record for FDS disclosure?

No – you are only able to map CommPay policies. After mapping a CommPay policy to an XPLAN client record, all revenues for the policy (already received and future revenues) will automatically be mapped to the client.

My client’s revenues are missing on their merged FDS

There are a number of reasons why a client’s revenues are not disclosed on their FDS, including:

CommPay policy has been mapped to the wrong XPLAN client

For step-by-step instructions on how to re-map the CommPay policy to the correct XPLAN client, in XPLAN go to Practice Management > Revenues > CommPay Policies mapped to the wrong client

Revenue was paid to your Practice outside of a Product or Platform account

Brokerage Team offers the Quickstream and BPay facilities to enable your clients to pay your fees – such as initial advice fees, contribution fees and ongoing advice fees – outside of a Product or Platform account. If your Practice utilises these facilities, the revenues will be available in CommPay for mapping to the XPLAN client.

If your Practice doesn’t use Quickstream and BPay (e.g. the fees are paid directly by your clients to your Practice), they will not be available in CommPay. Subsequently, you’ll need to manually update the client’s FDS after it has been merged to ensure the fees are disclosed.

To find out more about Quickstream and BPay facilities, contact your Brokerage Team

CommPay policy had previously been mapped to the client’s XPLAN record

From time to time Brokerage Team changes the way a supplier’s revenues are uploaded and processed in CommPay. This may cause CommPay policies previously mapped to XPLAN clients to be reset to mapping required. Consequently, they will need to be remapped to XPLAN clients before merging their FDSs.