Compliance Analytics Dashboard

1. Glossary
2. Compliance flag statuses
3. Accessing the reports
4. Getting to know the Compliance Analytics Reporting dashboard

Glossary

• Sender address: Related to the remitters cryptoaddress
• Receiver address: Related to beneficiary cryptoaddress
• Flagged client: Related to the actual client that has been flagged in a specific transaction
• Transaction ID: Unique combination of number and letter pertaining to a transaction 
• Amount: The transaction amount sent
• Created at: Date the transaction was created

Compliance flag statuses

• Pending: No action taken yet by the relevant compliance officer
• Escalated: The actual transaction/underlying client profile is now being investigated by a relevant compliance officer
• Solved: A conclusion has been reached with the altering of the relevant thresholds amounts

Accessing the reports

As a member of the compliance team you will have access to the Compliance Analytics reporting dashboard, to access the reporting views, you will use the link within the compliance dashboard itself and therefore need no further login credentials.

There are two ways to access the Compliance Analytics Dashboard: 

1. Click on the “Analytics” button in the top right hand of a client details page
   1. Provides a filtered view per client.
2. Click on the “Report” section of the main dashboard (on the lefthand side) and then click on “Compliance Analytics”.  
   1. Provides a holistic view of all activity.

Via the “Reports” section, you will also have access to the “Network Analytics” dashboard. There is only one way to access the “Network Analytics” dashboard. This dashboard allows a Compliance team member to: 

1. View all mint and burn transactions within your Network 
2. View the balances of different clients
3. View details related to transaction volume and total digital asset supply

Getting to know the dashboard

Dashboard view

The image below represents the “Compliance Analytics” table. This table displays data about sent and received transactions. There are also customisable visualisations on this table. 

Filter types

There are three types of filters available on Analytics. These filters are;

• Sender/receiver client
• Date Range
• Timeframe Range

Client filter

The controls depicted below have a drop down option where the user can select for the actual sending (Sender) or receiving (Receiver) client themselves. In order to reset the filters to indicate all existing information, you can select the three dots (above the input field) and a reset option will appear.

Date range

The date time range control allows filtering by 2 routes; route one is actually the dates themselves (and respective times) and the second route is selecting the unit itself (day, week, month, year etc.) and backcasting from the current date. Please see image to the right to illustrate this functionality.

Timeframe range

Looking at the visual below the filters can show data relative to a timeframe (even selecting a custom number of months like 1 as in the visual). All the relevant visuals that use the control filter will change.

Data Export

An instance may arise where the user may require further analysis to be done on another platform like Microsoft Excel or Google sheets. Our Compliance Dashboard offers the ability to export your visualisations results to Excel (where the data is tabular), or CSV (comma separated value) files where needed.You can download or export filtered or unfiltered data results by clicking on the three buttons next to a table and clicking on “Export to Excel” or “Export to CSV”. Visualisations will normally be able to only be exported to “CSV”.    

Understanding filters

All filters like the ones mentioned in this Section will have an information logo attached next to them (see image below). This filter helps the user understand more about the specific filter itself and what the filter is trying to accomplish.

Sender and receiver client logic

The sender and receiver client filters are present for looking at transactions from certain perspectives. In the examples given below, if the user is only interested in a certain party as a sender, then the receiver filters have to be all removed and vice versa the other way. In the images shown below, the client 'Chris’ as a sender is required as such, the receiver filters are all removed. The results show ‘Chris’ as a sender only to better comprehend the compliance rules and flags raised. We can see in this example ‘Chris’  has triggered a flag in the first transaction, the compliance team can check the relevant transaction in the compliance tab of io.vault to cross-reference the activity arising.