Financial reference data infrastructure

Reference data should not cost you a team.

Across Tunisia the same PDFs are re-keyed, the same scrapers rebuilt, the same corporate actions chased — inside every bank, broker and asset manager, at full cost. No institution has ever won a client because of it.

Cendratis carries that layer for the whole market, so your people go back to the work only your institution can do: pricing, advising, deciding, serving clients.

Being built with partner institutions — 2026
Canonical record · ATL 2025-1as of 2026-08-07
isin
TNHOASGSR955
name
ATL 2025-1 9.65% 29/08/2030
issuer
Arab Tunisian Lease · SA
listing
BVMT bond market · AT251 · TND
next_event
Amortisation + coupon · 2026-08-29
source_doc
CMF visa n°25/1157 · 07/07/2025

FISN and CFI are still unconfirmed against the depository's admission notice — so the record says so, rather than guessing.

The problem

Everyone pays for the same plumbing. Nobody competes on it.

Financial information in Tunisia exists — it is simply scattered, published as documents rather than data, and formatted differently by each institution that issues it. So every bank, broker and asset manager funds the same ingestion work privately, and none of them is chosen by a client because of it.

01
Scattered sources

Listings, identifiers, disclosures, rates and statements each live with a different authoritative institution, in a different shape.

02
Documents, not data

Most of what matters arrives as a PDF, a notice or a web page. Getting it into a system means a person reading and re-keying it.

03
Duplicated cost

Each institution staffs its own ingestion, its own mapping, its own corrections — paying in full for work its competitors are paying for too.

04
No common identity

Without shared identifiers, two systems can hold the same instrument under two identities, and only reconciliation reveals it.

From private pipelines to a shared reference layer.

Today
  • An analyst watches announcements and re-keys them by hand.
  • Corporate actions are discovered late, sometimes after the fact.
  • Each system holds its own version of the securities list.
  • “Where did this number come from?” is answered from memory.
  • Historical figures are rebuilt for every new analysis.
With a reference layer
  • Structured records arrive through one integration.
  • Events are captured at the source and dated consistently.
  • One canonical identity per instrument, per issuer.
  • Every fact links back to the document that established it.
  • History is versioned — you can query what was true then.
What we are building

Reference data domains, designed with the institutions that use them.

Explore the platform
Security Master

One canonical record per instrument, with identifiers reconciled across sources.

In design with partners
Issuer Master

Legal entities, name history, group and subsidiary relationships.

In design with partners
Corporate Actions

Dividends, splits, capital increases — captured, dated and structured.

In design with partners
Financial Statements

Published figures as structured, comparable series rather than PDF tables.

Research
Document Library

Prospectuses, reports and notices kept as evidence behind every fact.

In design with partners
Indicators & FX

Rates and monetary indicators, with revisions and publication dates preserved.

Research
Bond Reference Data

Coupon, maturity, schedule and day-count conventions in one place.

Research
Developer APIs

One integration, stable contracts, formats your core systems already accept.

In design with partners

How we hold ourselves to account.

These principles are not marketing. They are the constraints we design against, and the terms on which an institution should judge us.

  1. 01
    One canonical representation per entity

    An instrument or issuer has a single record, not a per-source copy that drifts.

  2. 02
    Every fact has an authoritative source

    Nothing enters the platform without a traceable origin. We do not create financial information.

  3. 03
    Documents are evidence

    Source documents are preserved alongside the structured knowledge extracted from them.

  4. 04
    Trust before speed

    Reference data feeds regulatory and client-facing work. Being right matters more than being first.

  5. 05
    Infrastructure, not applications

    We build the layer your systems consume — we do not compete with the systems above it.

What Cendratis is not.

The boundary matters. We sit below the market, not inside it — and the institutions that publish authoritative information are sources we build on, not competitors.

Not an exchange
Not a broker
Not a trading platform
Not a bank
Not a clearing house
Not a portfolio manager

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.

Book a call