Matching as a Service is file-based entity resolution handled by Credit Benchmark. You send names, we resolve them, and we return a matched feed file. Use it when you want Credit Benchmark to own the resolution work. Use the API when you want ranked candidates returned directly to your systems.Documentation Index
Fetch the complete documentation index at: https://docs.creditbenchmark.com/llms.txt
Use this file to discover all available pages before exploring further.
Matching Options
| Decision | Matching as a Service | Matching API |
|---|---|---|
| Who resolves? | Credit Benchmark. | You. |
| Use when | You want to offload review and receive a resolved file. | You want candidates inside your own workflow. |
| Output | Matched CBId file. | Ranked candidates with confidence scores. |
| Trade-off | File handoffs and slower turnaround; Credit Benchmark owns resolution. | Faster, but you own resolution decisions. |
Matching as a Service Process
Agree the input and output format
Confirm the file layout, cadence, delivery channel, and output fields during onboarding.
Send the input file
Transfer the file to Credit Benchmark through the agreed secure channel, usually SFTP or CB Secure.
Credit Benchmark resolves entities
Credit Benchmark matches the submitted names to internal entity records, reviews exceptions where needed, and assigns
CBId values where a match can be made.Input File
At minimum, each row must include the entity name to be matched. Additional identifiers improve match quality and reduce manual review.| Field | Required | Notes |
|---|---|---|
| Entity name | Yes | Legal or commonly used entity name. |
| Country | Recommended | Helps distinguish entities with similar names. |
| LEI | Recommended if available | Enables deterministic matching where the identifier is available and valid. |
| Industry or entity type | Optional | Useful for resolving ambiguous names. |
| Client identifier | Optional | Used to preserve your internal row, portfolio, or system reference in the output. |
| Custom client fields | Optional | Up to two agreed fields can be passed through to the output. |
Submission Patterns
Choose one pattern during onboarding.| Pattern | How it works | Output behaviour |
|---|---|---|
| Append new names | Send an initial universe, then send only new names in later files. | Output includes the accumulated universe. |
| Replace universe | Send a full updated universe each period. | Output includes the latest submitted universe only. |
| Separate lists | Send each file as a separate group of names. | Output includes the most recent list, unless a different layout is agreed. |
Cadence and Deadlines
| Output type | Timing |
|---|---|
| Time-sensitive match file | Returned on an agreed operational schedule. |
| Detailed month-end feed | Submit input by the 20th of the month. Output is returned on the last Friday of the month. |
Output File
Output fields are agreed during onboarding.| Output field | Notes |
|---|---|
| Submitted entity name and client identifiers | Preserves the input reference. |
Matched CBId | Credit Benchmark identifier for the resolved entity. |
| Matched entity name | Credit Benchmark entity name. |
| Match status or confidence information | Included where agreed during onboarding. |
| Selected consensus data fields | Included where the feed includes consensus data. |
| Third-party identifiers | Available identifiers such as LEI or national registry identifiers. |