PermID Matching Service - Inconsistent results

I am using the PermID Record Matching service (https://permid.org/match) in order to match my portfolio's positions to reuters permIDs. I have inconsistent results when I am using Ticker + name of the company as inputs vs using only the name of the company. I would have expected to get better result (and not wrong) when I provide more information as input (ticker + name vs only name).
Exple
Input
LocalID,Standard Identifier,Name,1,,Zhen Ding Technology,2,Ticker:4958,Zhen Ding Technology,Output
ProcessingStatus,Match OpenPermID,Match OrgName,Match Score,Match Level,Match Ordinal,Original Row Number,Input_LocalID,Input_Standard Identifier,Input_Name,Input_Country,Input_Street,Input_City,Input_PostalCode,Input_State,Input_WebsiteOK,https://permid.org/1-5037082477,Zhen Ding Technology Holding Ltd,49%,Possible,1,2,1,,Zhen Ding Technology,,,,,,OK,https://permid.org/1-4295879381,T.Hasegawa Co Ltd,100%,Excellent,1,3,2,Ticker:4958,Zhen Ding Technology,,,,,,The second company (where I provided ticker and name) is matched to a japanese company (with the same ticker as When Ding). The process seems to ignore the name completely and only matches on the ticker. I am doing something wrong or is it the expected behavior of the service?
Best Answer
-
Hello @rocosandey,
Please find the response from the product expert:
"The matching tool is behaving as expected. When name and ticker are provided, results with higher match level/score have been provided. When the ticker (4958) is included there are two exact matches as two entities have exactly the same ticker (T.Hasegawa Co Ltd and Zhen Ding Technology Holding Ltd), and this is why both entities are returned in the results with a match level of “excellent” / score of 100%. When only the name is provided, the lower match level of “possible”/score of 49% is returned (as there is more than one match with a similar name and no other credentials on which to base match results)."
0
Answers
-
Hello @rocosandey,
We have referred your report to the appropriate team for investigating.
Thanks for your patience,
-AHS
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 688 Datastream
- 1.4K DSS
- 624 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 692 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 10 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛