One reference layer, eight domains.
Cendratis aggregates, normalizes, enriches, versions and distributes reference data originating from authoritative institutions. Each domain below is being specified alongside the teams that will consume it.
- 01Security MasterIn design with partners
The canonical list of instruments: identifiers, classification, listing status and lifecycle. Identifier resolution maps whatever code a source uses back to one canonical instrument, so two of your systems can stop disagreeing about the same security.
- 02Issuer MasterIn design with partners
Legal entities as first-class records — legal name and its history, sector, group structure, parent and subsidiary links. Answers the question of whether “company X” in one file is the same entity as in another.
- 03Corporate ActionsIn design with partners
Dividends, splits, capital increases and other events captured from the announcement, structured, dated, and delivered with enough lead time to act on. Each action carries the notice it came from.
- 04Financial StatementsResearch
Published statements turned into structured, comparable series with consistent line items across periods — so figures stop being re-keyed by hand from PDF tables for every analysis.
- 05Document Library & SearchIn design with partners
Prospectuses, annual reports, reference documents and notices, indexed and searchable, preserved as the evidence behind every structured fact. When an auditor asks where a number came from, the answer is a link.
- 06Indicators, FX & RatesResearch
Reference rates and monetary indicators with publication dates and revisions preserved, so a late or revised value is visible rather than silently overwriting history.
- 07Bond Reference DataResearch
Fixed-income terms — coupon, maturity, payment schedule, day-count conventions — assembled in one structured place instead of being reconstructed from documents per issue.
- 08Developer APIsIn design with partners
One integration for all of the above, with stable contracts, predictable versioning and formats your core systems already accept.
Delivered the way your systems actually work.
A clean API is only useful if the team on the other side can plug it in without a fight with IT or procurement. We are designing distribution around what core systems accept today.
- REST API with stable, versioned contracts
- Bulk files for systems that ingest overnight
- Spreadsheet and CSV exports for teams working by hand today
- Alignment with established messaging standards where it helps integration
Built for people who have to defend the number.
Reference data feeds regulatory reporting and client-facing work. That sets the bar: it is not enough for a value to be right — you have to be able to show why.
- Provenance on every field, down to the source document
- Full version history — query what was true on any past date
- Corrections recorded as revisions, never silent overwrites
- Validation rules and human review before publication
We are building this with institutions, not for them.
Tell us what reference data costs your team today — the hours, the breaks, the workarounds nobody has time to fix. That is what decides which domains we build first.