Matching as a Service

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.

Matching Options

Decision	Matching as a Service	Entity Resolution 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.

API references: Entity Resolution overview and Accuracy & Coverage.

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.

Receive the output file

Credit Benchmark returns the matched file through the agreed delivery channel. The output can include mapping fields, selected consensus fields, and agreed client reference fields.

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.

If the same entity name can appear with different internal identifiers, tell Credit Benchmark during onboarding. The process can preserve row-level distinction using your identifiers or agreed custom fields.

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.

If no new file is submitted for a monthly run, the output can be generated from the last submitted universe using the latest available Credit Benchmark data.

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.

Volumes

Monthly files commonly contain up to 10,000 submitted names. Larger files can be supported, but processing approach, timing, and commercial terms should be confirmed before onboarding.

Getting Started

Authentication

WebApp

Excel Add-In

Feed File

Partnerships

Matching Options

Matching as a Service Process

Input File

Submission Patterns

Cadence and Deadlines

Output File

Volumes

​Matching Options

​Matching as a Service Process

​Input File

​Submission Patterns

​Cadence and Deadlines

​Output File

​Volumes

Matching Options

Matching as a Service Process

Input File

Submission Patterns

Cadence and Deadlines

Output File

Volumes