Handling Client Updates

Your SalesConnect system may include the Client Updates utility. With this utility enabled, changes that you or others make in SalesConnect to key data for officesClosedAn office is a connection in the intermediary business hierarchy, an organization subordinate to a broker/dealer firm. Offices are also sometimes referred to as "branches'; institutional firms have branches in SalesConnect. An office is affiliated with a single broker/dealer firm, and may have one or more reps directly affiliated with it. An office may have associated office contacts, as well. Possibly the most critical information you can track for offices are aliases, also known as trading IDs. Aliases are the IDs that associate transactions with each office. If you need to write queries or reports: The primary data for offices is stored in the Office table. Information about office trading IDs is stored in the Office Alias table., repsClosedA rep is perhaps the most important contact connection in the intermediary business hierarchy. Each rep is an individual who sells funds and is affiliated with an office (and through the office, with a broker/dealer firm). Reps may also be referred to as "financial advisors." Possibly the most critical information you can track for reps are aliases, also known as trading IDs. Aliases are the IDs that associate transactions and assets with each rep. If you need to write queries or reports: The primary data for reps is stored in the Contact and Rep Profile tables. The Rep Alias table stores trading IDs associated with reps. and rep partnershipsClosedA partnership is a contact connection in the intermediary business hierarchy, though it is really a name for a group of reps working together to sell one or more products. A partnership, sometimes called a rep partnership, is treated as a special type of rep: this means that most of the tools for working with reps may be used to work with partnerships as well. Most views of transactions associated with an individual rep generally don't include transactions or parts of transactions that the rep may have cleared as part of a partnership. Instead, these kinds of trades are listed only for the rep partnership. Each member's portion of rep partnership sales data is always based on the percentages currently assigned to each member; no long-term historical information about percentages is maintained. SalesConnect does not store any calculated trade or asset values based on rep partnerships. If you need to write queries or reports: The primary data for partnerships is stored in the Contact, Rep Partnership, and Rep Profile tables. The Rep Alias table stores trading IDs associated with partnerships as well as reps. maintained by Universal Dealer Services (UD) are automatically transmitted to UD for review; you also have the opportunity to request that rep moves be made in the UD system and your own. UD personnel may approve all or part of each change made in your SalesConnect system. When reviewing such changes, UD personnel may either opt to make the same changes to UD's master data or may only accept the change in your system. UD may also opt to reject a change altogether.

You can review these change items in the Client Update queue at any time, to see their status. For items already reviewed by UD, you may be able to retain the changes originally made in your SalesConnect system (knowing that future UD updates may overwrite them) or you can request a Client Sync from UD, to update your SalesConnect system with UD information for that office, rep or partnership.

  1. Using the Data Operations personaClosedA persona is an interface set of menus and dashboard or home view that was designed for a single set of operators who share goals, skills, attitude and behavior patterns. Each persona's interface displays only the content and tools that are relevant for that group., select Client Updates from the Data Management menu. Or, select in the universal menu, and then select Client Updates under Universal Dealer. The Client Updates page appears.
  2. Choose a saved search or create a new search to use to list client updates. Filtering by UD Status may be especially helpful.

  3. Review and handle the updates listed in the table. UD Status values can help you determine which records you may want to review:

    • Pending records have not yet been acted upon by UD. You can review them if you like, but no action is necessary on your part.

    • Accepted records are those for which UD has approved the changes, committing them to the UD master record for as well as to your SalesConnect system. You may want to review these records, since UD personnel may edit values in addition to those that were changed in your system. Client Status for these records is Completed, so no action is needed on your part.

    • Accepted No Action records are those for which UD has approved the changes made in your SalesConnect system, but has opted not to make those changes to the UD master record. You can review these records if you like; the Client Status for them is Completed, so no action is necessary.

    • Partially Accepted records are those for which UD has approved some of the changes made in your SalesConnect system; you should review the details, keeping in mind that UD personnel may have further edited values that had been changed in your system. The approved portion of the changes are now part of the UD master record for the entity. Client Status for these records is blank, indicating that you should review these items to determine how to handle them.

    To review a client update record: Select the link for it in the table, and review information on the displayed Client Update Detail page.

    Tips

    • Be sure to review information in the Notes and Values areas of the page.
    • You can type a note about this update in the Note field, and then select Add Note to add it to the notes table.
    • You can select Keep Client Changes to retain the changes that had been made in your system in your SalesConnect.
    • You can select Sync to UD to request that your SalesConnect system be updated with information from the associated UD master record; your request is queued and will be processed as soon as possible. When your request is processed, data in your system will be overwritten with data from the UD master record.