KYCv7.14 Standard Demonstration Guide
KYCv7.14 Standard Demonstration Guide
7.14
Trademarks
For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. Other brand or product names
are trademarks of their respective holders.
For information about the third-party software that is delivered with the product, refer to the third-party license
file on your installation media that is specific to your release.
Notices
This publication describes and/or represents products and services of Pegasystems Inc. It may contain trade
secrets and proprietary information that are protected by various federal, state, and international laws, and
distributed under licenses restricting their use, copying, modification, distribution, or transmittal in any form
without prior written authorization of Pegasystems Inc.
This publication is current as of the date of publication only. Changes to the publication may be made from
time to time at the discretion of Pegasystems Inc. This publication remains the property of Pegasystems Inc.
and must be returned to it upon request. This publication does not imply any commitment to offer or deliver
the products or services described herein.
This publication may include references to Pegasystems Inc. product features that have not been licensed by
you or your company. If you have questions about whether a particular capability is included in your
installation, please consult your Pegasystems Inc. services consultant.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or
typographical errors, as well as technical inaccuracies. Pegasystems Inc. may make improvements and/or
changes to the publication at any time.
Any references in this publication to non-Pegasystems websites are provided for convenience only and do not
serve as an endorsement of these websites. The materials at these websites are not part of the material for
Pegasystems products, and use of those websites is at your own risk.
Information concerning non-Pegasystems products was obtained from the suppliers of those products, their
publications, or other publicly available sources. Address questions about non-Pegasystems products to the
suppliers of those products.
This publication may contain examples used in daily business operations that include the names of people,
companies, products, and other third-party publications. Such examples are fictitious and any similarity to the
names or other data used by an actual business enterprise or individual is coincidental.
Pegasystems Inc.
One Rogers Street
Cambridge, MA 02142-1209
USA
Phone: (617) 374-9600
Fax: (617) 374-9620
www.pega.com
This demonstration script showcases the following KYC application and Pega 7 Platform
technology assets:
Demonstration back story: When new customers, accounts and products are onboarded at a
financial institution, due diligence must be performed before the accounts can be transacted
against or before the institution can begin its business relationship with the client.
Among other features, this script demonstrates how the KYC system dynamically selects and
applies regulatory data capture processes when new accounts, products and customers are
onboarded at a financial institution.
Assumption: When demonstrating manual case creation, the assumption is made that customer
and account data already exists in systems of record. The user walks through the process of
selecting pre-existing customer, account, product and related party data required for KYC
evaluation.
The assumption is also made that a single user will be presented all applicable due diligence
requirements for completion. In a production environment, it is expected that multiple cases with
unique KYC requirements will be created and assigned to various operators in one or more
workgroups.
Important: When demonstrating KYC as a stand-alone system, KYC does not demonstrate the
intricate processes and steps required for collecting onboarding data (account setup, product
selection, etc…) for various lines of business such as investment banking or commercial
lending.
It is expected that upon implementation, the KYC system will be extended and/or integrated
with Pega-based and non-Pega based onboarding systems that serve as the entire end-to-end
onboarding and due diligence process.
2. The KYC Analyst Manager portal provides a ‘super-user’ view with access to all charts,
reports, users and cases.
3. The following diagram details each of the key features and tools available on the dashboard
that are critical to demonstrating the system
1. Navigation
− Dashboard – Default view for KYC Manager sign-on
− My Work – Contains worklist of active cases and all workgroup team members with
cases assigned to them when file import case creation is initiated
− Calendar – Useful for explaining how KYC Cases with SLA’s will display in the calendar
to ensure cases are managed and worked in a timely manner
− Reports – Provides pre-configured KYC and FATCA reports available to KYC Managers
for re-use and extension
2. Create +
− Use this action to create manual new business onboarding cases as explained later in
this guide
3. Search and Operator ID
− Search for Profiles, sample customers and cases using Pega’s default search tool
− Indexing tool provided in the Pega developer portal must be run
− Use the Mobile preview to demonstrate Pega’s dynamic UI for mobile devices
4. Dashboard Charts
− Six re-usable and extendable KYC-related charts and graphs are provided to showcase
Pega’s interactive data visualization
5. Demo Tools
− Import .csv files containing sample data to create cases and populate the dashboard
− Demonstrate how the system can retrieve FATCA data and format the data in xml for
IRS reporting
− Demonstrate how due diligence data can be extracted from the database and output to
an Excel file.
− Delete all sample case and Profile data in the database to demonstrate the system from
a ‘clean slate’.
Important: Creating cases and completing KYC Types in advance also helps demonstrate re-
use of KYC data stored at the Profile.
6. A New Business Onboarding case is created with the following KYC Type:
Entity Standard Due Diligence
Note – The displayed KYC Type is a basic due diligence requirement that, for purposes of
demonstration, must be completed when no account or products are present. i.e. – only the customer
is being onboarded
Important - For all KYC Types displayed in a case, each applicable Type will contain only a
single mandatory Item that requires a response. This will facilitate and quicken the completion
process.
10. The case is resolved. Status is changed to Resolved-Approved. Close this work item
Note – The displayed KYC Type is a basic due diligence requirement that, for purposes
of this demonstration, must be completed when no account or products are present. i.e.
– only the customer is being onboarded
Important - For all KYC Types displayed in a case, each applicable Type will contain only one
mandatory Item that requires a response. This will facilitate and quicken the completion
process.
8. Press Finish
9. At the ‘New Business Onboarding Decision’ step, select Approve and press Submit
3. Click Open to access the sample file used for data import and case creation
4. In the Binary File rule form, click Download File and to download and view the csv file
5. The .csv file opens in Excel to display the sample data used by the system to create cases
Discussion points:
Data model, file format and parsing rules included in the KYC for FS application can be
modified to accommodate client’s specific data requirements
Different formats can be used (xlsx, csv, tab delimited, xml, etc…)
File can be maintained by the client and processed by a system agent or other automated
process
Although file import and parsing functionality is ideal for quickly populating the KYC
Manager dashboard for demonstrations, this feature also highlights the system’s ability to
use data for batch/bulk case creation. This has many uses for production implementations
and would typically be run using an automated process.
6. Return to the Dashboard and open the Demo Tools gadget
7. Click the Run button to start the file import process
8. ‘In Progress’ icon will display and when the import is finished, the dashboard will refresh to
show the dashboard charts populated with data.
9. Perform the same steps for the FATCA sample file by navigating to Demo Tools, select the
FATCA file in the dropdown list and click the Run button.
10. The dashboard charts will populate with additional Profile and Case data. If time allows, it is
critical to discuss these charts with the audience as they showcase both Pega 7 chart and
reporting technology as well as pre-configured assets in the application.
11. If you need to refresh the database to clear the dashboard of all cases and data, expand the
Demo Tools gadget and click Delete sample cases button
12. Press Submit when prompted to clear any existing sample work objects and data from the
system
13. The Dashboard will refresh and display no cases or data when complete
Important! – refer to the FATCA demonstration guide for in-depth detail on demonstrating and
explaining FATCA functionality included in the application.
Dashboard
− Each chart has a description detailing its purpose
− Each chart provides ‘Chart Actions’ to open the source report and access and open
Profiles or Cases
- Each report has a filtering condition which allows the conditions to be modified in
real-time
− Pie charts are ‘exploding’. Click any of the grouping values to ‘explode’ the value’s
shape in the chart
− As cases are processed and Items are completed, data will populate the ‘Active cases -
% of completed due diligence’ report
− You can run the file imports again to generate more cases which will set threshold colors
in the ‘Active cases per analyst’ report
My Work
− This is the KYC Manager’s view of all Cases for all team members in the workgroup
− When the file imports are run and cases created, cases are auto-assigned to Team
members
− Click and drag a case from the Urgent Work list to the right and into Diya Cleveland’s
queue. (The transfer will occur when you see case assignment label change to ‘Diya
Cleveland’)
− These are default Pega case management layouts and tools and should be discussed to
showcase Pega’s case mgmt. technology
Calendar
− Assigning work to Diya Cleveland in the previous section makes cases visible in Diya’s
calendar
− The Service Level Agreement (SLA) set for the case(s) (1 day goal) becomes apparent
when the newly assigned cases appear on Diya’s calendar
− This functionality is key when performing due diligence. It prevents work from being
missed
− Double-click any of the items to open the Case
Reports
KYC for FS is shipped with pre-configured, KYC and FATCA-specific reports and charts that are
accessible via the Private categories gadget. The list of reports is a follows:
Profiles (Retail customer risk change assessment) Helps assess impact when risk factor change is required
Profiles (Commercial customer risk change assessment) Helps assess impact when risk factor change is required
KYC Profile - New Customer Profiles by Region (MAP) Interactive chart with drill-down to Profiles from Global/regional
to country view
KYC Reviews - New and in-progress cases Gets newly created and in-progress KYC Review cases
Profiles (Upcoming KYC Review - 30 Day Outlook) Gets customers with upcoming KYC Reviews within the next
30 days
FATCA - Summary of Acct Holders and IRS Reporting Codes Gets account holders and their FATCA IRS reporting codes
from the Profile
Profiles (Opened today in Europe by country) Displays map of Europe with count of new Profiles opened by
country
Profiles (Opened Today by Risk) Distribution of new Profiles opened today by Risk
Profiles (Distribution Opened Today by World Region) Distribution of Profiles opened today by world region
Profiles (opened today - northern Europe) Profiles opened today for northern Europe countries
KYC Cases (In-Progress Due Diligence Cases per Analyst) Gets count of in-progress due diligence cases for each analyst
KYC Cases (Active Cases by Type) Distribution of active KYC cases by type.
KYC Cases - Pct. of Required Due Diligence Data Collected Active cases with % calculation of collected due diligence data
1. Click the KYC Manager Reports link to view the full list
2. To showcase Pega’s chart technology, click the Profiles (All by region, country and risk –
MAP) report link
3. A global map showing count of Profiles opened for the region displays
Customer Search
Important! – Sign on as KYCFSSysAdmin / install to enable and execute indexing prior to using
the search feature. DesignerStudio > System > Settings > Search
1. Use Pega’s default searching features to locate Profiles and Cases by key data values. You
can search by:
Name
Customer ID
Customer Type
Occupation / Industry
Case ID
Profile ID
And many more….
2. In the search field, enter a value and click the magnifying glass icon
3. All Cases and Profiles meeting the search criteria display
Responsive UI
1. KYC manager dashboard accommodates different resolutions and devices via Pega
responsive UI technology
2. You can re-size browser to show how dashboard adjusts to fit content
3. You can also select Mobile preview’ from Diya’s operator ID dropdown selections to
demonstrate Pega’s mobile device compatibility
4. In the Mobile Preview window, select the different devices to preview the different
resolutions and UI layouts
Important - If required to demonstrate the system within a short timeframe, then navigate to the
My Work browser and open any of the cases from a user’s work list to process the case and tell
the KYC and/or FATCA evaluation story. These cases have fewer KYC requirements to
complete. They have no related parties and no child sub-cases and take less time to process.
Important – Use the following matrix as a quick reference to determine which KYC Types are
selected and displayed in a case based on the selected account(s).
Other selected Types are driven by factors such as Customer Type (individual or business) or
by a change in Risk.
US FINRA 2111
US SWAPS with Derivatives
Entity Enhanced Due
Diligence (risk changed to
HIGH)
Account Enhanced Due
Diligence (risk changed to
HIGH)
Account # Account Type Product Location (Country) Selected & Displayed Types
3045000948 Escrow Wire Transfer United Kingdom Entity Standard Due
Diligence
Entity Enhanced Due
Diligence (risk changed to
HIGH)
Account Enhanced Due
Diligence (risk changed to
HIGH)
Escrow Acct FATCA EXEMPT
Account # Account Type Product Location (Country) Selected & Displayed Types
3045000949 Investment Trading United Kingdom Entity Standard Due
Diligence
Investment Profile
EU MiFID
EU EMIR
Entity Enhanced Due
Diligence (risk changed to
HIGH)
Account Enhanced Due
Diligence (risk changed to
HIGH)
FATCA – Taxable Entities
Selecting NO accounts Entity Standard Due
Diligence
Entity Enhanced Due
Diligence (risk changed to
HIGH)
Selecting ALL accounts Applies these 12 KYC Types:
3045000945 Investment Trading Canada Entity Standard Due
3045000946 Investment Mutual United Diligence
Fund States
Investment Profile
3045000947 Investment Credit United
Default States
US DFA SWAPS
SWAP
Canada IIROC
EU MiFID
EU EMIR
US Mutual Fund
Important – When demonstrating the system, the user should determine any specific due
diligence requirements prior to the demonstration to help determine which accounts to select.
Selected accounts will ultimately drive the applicable KYC Types as detailed in the
Account/Type matrix. For this script, all accounts are selected which will drive the selection
and display of all applicable Types.
Important – Depending on time, the demo user can select one party, both parties, or no related parties
for this customer.
Selecting one party creates one sub-case that must be processed (less time required)
Selecting both parties creates two sub-cases that must be processed (more time required). This will
require the demo user to complete due diligence requirements for both related parties.
Depending on which related party is selected, the following Types will display in each child sub-
case:
7. Select Eva Smith as one of the related parties for any one of the accounts > press Finish
8. Parent case for Eurotech is created with a child sub-case for the selected related party
Discussion point:
Press submit to show how case dependencies are enforced. The parent case for Eurotech
cannot be processed until the related party’s sub-case is processed and completed.
9. Click the Collect & Evaluate Requirement Data link to open the sub-case for the related
party.
10. The child case for Eva Smith is displayed
Discussion points:
Note that the due diligence requirements are 50% complete. Assumption is made that initial
due diligence has already been performed for this person (completed in pre-demo setup).
The completed due diligence data stored in the Profile has been re-used.
FATCA Type appears because US Person status must be evaluated for parties related to
onboarding of new accounts that meet FATCA requirements (these accounts are at the
parent case level)
Showing the sub-case with a pre-completed KYC Types demonstrates re-use of completed
and approved due diligence data contained in the customer’s Profile
Cases where required due diligence data is completed and approved can be auto-resolved
for straight-through processing
11. Demonstrate Content Server Integration (CMIS assets) – this requires CMIS integration
configuration. (See Implementation Guide). System will use default documents if CMIS is
not configured.
a. Navigate to the Standard Due Diligence Type
b. Open the Documentation verification group
If CMIS assets are turned ‘on’ (enabled) in the OOB sample application or configured in a
custom-built application as shown below…
… then the system will connect to the content server and display the Content Server pop-up
window for navigation and document selection.
If CMIS assets are turned ‘off’, then the default functionality will search the local instance for
sample documents and display the following dialog window:
Important – By default, the KYC solution and sample application are shipped with CMIS
Integration disabled. The system locates sample files shipped within a sample document
database table installed with the system. For detailed instructions on Content Server
configuration, please refer to the Implementation Guide.
12. Click the info icon next to the status bar to show the calculation of mandatory and complete
Items. This is an OOB asset that will automatically calculate mandatory vs. completed Items
for every applicable KYC Type.
Important – Upon implementation, Item response property values (i.e. – ‘Is PEP?’) can be auto-set to a
value passed from another system that exists elsewhere on a clipboard page by using the
DataTransfrom feature in the KYC Type and Item definition configuration screens.
16. Navigate to the Customer risk tab at the footer of the case. This display shows why the risk
changed to HIGH (High Risk Item response detected)
17. Click on any of the risk icons to open the business rule that defines the risk evaluation
Decision Strategy Manager (DSM) assets are leveraged to utilize scorecard rules for
calculating a risk rating.
18. Navigate to the FATCA – Individuals KYC Type > Select Yes for the first Item
a. A more complex FATCA scenario can be demonstrated when the response is set to No
(Please see the FATCA Demonstration Guide for more detail)
b. Based on the selected responses, the system will ‘drive’ the user to request the
appropriate Form for tax reporting
c. Press the Request button and a window displays to enter the email of the intended
recipient
d. Press Submit.
e. When the screen refreshes, the Item and Type are marked complete
f. By default, outbound email for the associated correspondence rule is not configured and
active. Outbound correspondence is not required for demonstration. Out
correspondence is expected to be configured when the system is implemented in a
production environment depending on specific business requirements.
g. In the case header, select Other Actions > Attachments
h. Open the Attachments window to view copies of the Email and Eform that were “sent”
and saved to the case.
19. Close the Attachments window and navigate to the Enhanced Due Diligence KYC Type.
Complete the single, mandatory Item.
Important – refer to the Eurotech’s account/KYC Type matrix to determine which Types you need to
apply and display in the Case. Remember: Selecting all accounts will apply all applicable KYC Types
which will increase the time required to navigate, explain and complete each Type.
Discussion Points:
Approved / completed KYC Type
− Standard Due Diligence was completed in the pre-demo setup and stored in Profile for
re-use
27. At the New Business Onboarding Decision step > Select Approve > Press Submit
28. The case is Resolved-Approved
Discussion Points:
29. At this stage of the case lifecycle, KYC data is synchronized with the customer’s Profile and
also written to the due diligence data index tables. This processing is pre-configured and
provided in the application’s each case type’s lifecycle by default. It is expected that when
implemented, data will also be communicated to other systems of record according to
business requirements.
30. The application provides service integration (SOAP services) to utilize bi-directional data
communication with both Pega and non-Pega applications
31. If KYC is installed and demonstrated with Pega’s OBFS application (Onboarding for
Financial Services), then both systems are configured to demonstrate bi-directional data
communication – NBB to KYC to NBB (See the KYC v7.14 Implementation Guide for more
detail on application integration)
Follow the ‘create New Business Onboarding Case’ steps detailed earlier in this document for
Eva Smith
1. At the Select accounts step, select all accounts and press Next
2. NO related parties apply to this account > at the Select related parties step > select Finish
3. When the case is created, the US Life Insurance KYC Type and Account Enhanced Due
Diligence Types display and need to be completed. Other Types are marked complete as
they were completed in previous steps of this document.
Note – Profiles can also be opened from any of the Profile-based charts on the dashboard.
Select Chart Actions > Show data
2. From the list of search results, click the Profile ID to open Eurotech’s Profile
3. Eurotech’s Profile displays
Header: Contains basic customer information stored for reference. Note - The Profile is not
intended or designed to replace master system of records. It is used to primarily store due
diligence data.
Customer risk: Displays the most current risk rating information. The risk data stored in the
Profile represents the most recent and approved data that was sourced from the ‘last’ KYC case
synchronized with the Profile.
Due diligence: All approved and current due diligence requirements are stored here for re-use
for future cases. All data is read-only.
Related parties: Every related party associated with a customer’s new business onboarding
case undergoes due diligence evaluation within its own KYC case. When the parent KYC case
is synchronized with the Profile, the system will also synchronize and store a consolidated list of
all related parties in the Profile. Note – The Profile ID is a link that can be clicked to open the
Profile for the related party.
Cases: References active and resolved KYC Cases associated with customer’s Profile.
Important! This feature ensures timely, risk-based reviews are performed for a financial institution’s
client base and streamlines the process by automating KYC Review case creation.
Dynamic system settings are shipped with the application that associate a time period, in years,
with a customer’s calculated risk rating. The default KYC Review date settings are as follows:
You can access the settings to view or customize them by signing on as KYCFSSysAdmin, go
to Explorer > SysAdmin > Dyanmic System Settings. Sort by name to locate the settings
associated with the PegaKYC ruleset
When a case is processed for a customer, resolved and synchronized with the Profile, the risk
value of the case (High, Low) is compared to the dynamic system setting and used to calculate
the ‘Next KYC Review’ value for the Profile.
You can view the ‘Next KYC review’ date in the header section of any Profile.
To demonstrate how the system uses the ‘Next review date’ to auto-create KYC Review cases,
perform the following steps:
2. At the pop-up window, change the date to today’s date and enter the mandatory audit note.
Press Submit
3. The Profile screen will refresh and the Next review date will be updated to today’s date
4. In the background, a system agent will locate Profiles with a ‘next review date’ containing
today’s date and automatically create a KYC Review case for the customer.
5. Navigate to Cases and click the refresh icon
6. A KYC Review case will display in the list of the customer’s cases
This tool uses mxGraph technology which is an open source, JavaScript diagramming
technology supported by Pega. You can learn more about jGraph and mxGraph here:
http://www.jgraph.com
Important – this tool is intended as a model for client implementations only. Functionality is primarily for
demonstration and shows how the concept of the viewer can be used. It is assumed the client will
require customization and will be responsible for all customizations done in the field.
Node Icons
Delete – Used to remove a node from the display. Deleting a Parent node will remove all
associated Child nodes from the display. (Changes to the display are committed to the database
only when the save icon is pressed on the Tools gadget)
Add Child – this icon appears on the bottom of each node where one or more Child
nodes can be added to a Parent node.
Important - If a Child node is added for a client that has its own Profile and relational structure, then the
‘Add Child’ icon will not display.
This will help avoid creation of numerous, relational structures for the same client within multiple
Profiles. A client’s relational structures should be maintained within its own Profile.
Tools Gadget
The system opens the mxGraph relationship viewer and the default view shows the current
customer as the root node (Eurotech) and the related party (Eva Smith).
Related parties may or may not be connected to the root depending on if related parties have
been processed in sub-cases for the client or if a user has previously maintained the data
structure.
Since Eva Smith was identified and processed as a related party, she is displayed as a related
part in the relationship viewer by default. Related Parties associated with an onboarding
scenario are automatically copied to a unique page used by the relationship viewer –
pyWorkParty(Customer). RelatedEntity
4. Or, leave the ‘Add Existing Customer’ box unchecked and manually enter related entity data
a. Name – enter the name of the entity
b. Type – this will determine the icon to use (individual or business)
c. Ownership – ‘Owner of Parent’ points the connector from the child node to the parent
node (UP). ‘Owned by Parent’ points the arrow from the parent node to the child node
(DOWN).
d. Ownership Description – free text that appears on the connector label
7. Since the newly added node is for a non-customer, the ‘Add Node’ icon appears.
8. Note – a green checkmark denotes that the node is for a customer with its own Profile.
Therefore, relational data should not be maintained here. Users should access the profile of
the related entity to add/update relationship data for the entity.
9. To delete a node from the database, click the delete icon and press the Save button to
commit the changes
10. To edit a node’s data:
a. Right-click the node > select ‘edit node’
b. Dialog window opens with the existing fields and data populated
e. You can re-open the Edit Relationships to show how the structure is saved to the
Profile
Important! – A custom ruleset must be added to the application stack in order to create new
Types or copy and update a pre-configured Type.
1. Create a new rule set Create > Sys Admin > RuleSet
2. Set the Validation mode to Application Validation > Press Save
d. Save the KYC for FS application. You are now ready to create new Types and Items for
demonstration.
To demonstrate creation and maintenance of KYC Types, perform the following steps:
3. To demonstrate how new KYC Type rules are created, right-click on any category or on a
KYC Type > New > KYC Type
Important - For a detailed steps and supplemental information on how to create and configure KYC
Type and Item rules, please refer to the KYC Implementation Guide which can be found on the PDN at:
https://pdn.pega.com/products/know-your-customer