Meeting minutes status: Draft (pending approval)

Table of Contents

Date/Time

8th January 2019, 11:00 AM EST

WebEx and Dial-In

WebEx:https://finos.webex.com/finos/j.php?MTID=mb087705b81d823c6e027176d03cab493
Meeting number (access code): 660 099 386
Host key: 428864

JOIN BY PHONE
+1-240-454-0879 USA Toll
Tap here to call (mobile phones only, hosts not supported): tel:+1-240-454-0879,,*01*660099386%23%23*01*

+44-20319-88141 UK Toll
Tap here to call (mobile phones only, hosts not supported): tel:+44-20319-88141,,*01*660099386%23%23*01*

Global call-in numbers:
https://finos.webex.com/finos/globalcallin.php?serviceType=MC&ED=582460637&tollFree=0

Attendees

Name	Organisation
Ben Sandler	AQR
Pascal Lefrancois	Innovestor
John Matera	FactSet
Sailesh Pandey	Nomura
Mark Andrade	FinTech Sandbox
Anthony Golia	Red Hat
Alvin Shih	Morgan Stanley
Tosha Ellison	FINOS
Rob Underwood (Deactivated)	FINOS

Outstanding Action Items

Agenda

Time	Item	Notes from the Meeting
5 min	Convene & roll call	Done
10 min	Review action items from previous meetings (see above)	During last meeting the group agreed to narrow down to a couple of focus areas.
15 min	Deep dive - Issuer linkage Issues.	The group discussed challenges around linking issuer data from multiple vendors including: Data is available from multiple providers; if you use only one data provider the linkage is okay but when you have two or more feeds (e.g. Bloomberg and Reuters) this is more difficult. It is also possible to use LEI but coverage is sparse. Linking information from one vendor to another can also cause operational errors. Issuer hierarchy can also be problematic given the different ways issuers create notes and identify parents/ultimate parents. A member of the group suggested looking at Open Corporates, which looks extensive although it has no obvious hierarchy and no other IDs. FactSet confirmed they do use “Open Corporates”, and perhaps we could get vendors to map back to this open ID. The community could then perhaps map back the the hierarchy. FactSet does map open corporate symbol to their own symbol and also maintains hierarchy. John Matera offered to look into how FactSet uses Open Corporates (e.g. license) and how good the coverage is. It would be appealing if there is a mapping to say 1 open field so that banks/asset managers can use data from multiple vendors more easily . The group queried whether vendors would add an open ID to their feeds, would this mapping then be bundled in with other fees? The other option is to open source IDs, e.g. FIGI. Someone thought that Bloomberg does have a FIGI at the entity level (to validate). Group discussed why is LEI not more widely used? Not clear. For banks there might be some official identifier required and that could be an opportunity, e.g. SEC CIK filings is something that identifies a legal entity. Central key that the SEC requires for filing. Anyone issuing securities has to have a CIK. CIK is different from TIN and it can be hard to use these because they are mostly US.
15 min	Deep dive - Mapping of CUSIPs to Symbols. Reference to the below use case that was discussed last week - "CUSIP is also commonly used but is extremely expensive and entities on both sides of a transaction have to be entitled. Also potential issues here where compliance uses CUSIP but a trader uses symbol so can cause errors so potentially not even standard usage within a company. Could CUSIP be open source so there is a single identifier that uniquely connects the securities. "
10 min	Summarising the discussion and take away.	Explore the use of Open Corporates.
5 min	AOB & adjourn	None

Decisions Made

Action Items

Browser not supported