Home/Products/Fund Master
In preview

One source of truth for
fund static data.

Fund Master is the governed master record for everything it takes to set up and maintain a fund — structures, parties, people, benchmarks, documents and the static data every downstream system depends on. Every change approved. Every value traceable to its source.

Register interest → What it does
Fund Master command center — approval queue, launch readiness and document alerts
1Approval queue
3At-risk funds & classes
2Launch readiness
4Scheduled changes
5Document expiry
6Connected systems
1 Approval queueEvery pending change in one maker-checker queue — field changes, enrollments, all of it. Nothing becomes master data without approval.
2 Launch readinessCompleteness scored per fund and class against required data points — and only fully approved values count as ready.
3 At-risk funds & classesGo-live dates approaching with required data still missing — surfaced by name, with the exact fields, while there's time to act.
4 Scheduled changesApproved values waiting on their effective date — approval and going live are separate events, applied automatically on the day.
5 Document expiry & refreshHard expiries and refresh targets tracked separately per document, alerted before they bite.
6 Connected systemsWhere the data flows: authoritative push into Veracis apps, reconcile-and-flag against external platforms.

The Fund Master command center — preview build; data shown is illustrative.

The gap it closes

Static data lives everywhere.
So it's owned nowhere.

Every system in the chain — accounting, TA, custody, ETF servicing — keeps its own copy of the same fund facts. Each was keyed by hand from the same documents, at different times, by different people.

📑
Re-keyed at every launch
A new fund means the same prospectus data entered separately into every platform that services it — slow, duplicated effort with a mistake risk at every keyboard.
🔀
Versions drift
A supplement changes a fee, a benchmark, a dealing deadline. Some systems get updated, some don't — and nobody can say which copy is right.
🚦
Launches wait on data
Go-lives slip because nobody can see, in one place, which required data points are still missing for which target date.
What it does

Master data, governed
like it matters.

🗂️
The full master record
Umbrella, fund and share-class hierarchy, with the parties, named contacts, benchmarks and per-system detail that hang off it.
  • Administrator, TA, custody & ETF detail per fund
  • Effective-dated party appointments
  • Benchmark assignments with history
✅
Maker-checker on everything
Nothing becomes master data without approval — not a manual edit, not a file load, not an extracted value. Four-eyes as the default, a second checker where you configure it.
  • Every change proposed, then approved
  • Field-level approval rules per tenant
  • Batch approval without all-or-nothing
📅
Effective-dated go-lives
Approval and taking effect are separate events. Approve the fee change today; it becomes master data on the date the supplement says — automatically.
  • Scheduled changes with one pending value per field
  • Downstream push triggered on the effective date
  • Full history of what applied when
🎯
Launch readiness
Required data points are tracked in tiers against each fund's target launch and each class's go-live date — so the missing pieces are visible while there's still time.
  • Completeness scoring per fund and class
  • At-risk launches surfaced on the dashboard
  • Go-live gates that block until data is approved
📄
Documents, versioned
Prospectuses, supplements and agreements with a proper lifecycle — draft to live to superseded — plus expiry and refresh dates tracked separately.
  • One live version per document, always
  • Expiry alerts before they bite
  • Values keep provenance back to their source document
↔️
Authority that respects reality
Into Veracis products, Fund Master pushes authoritatively and the receiving field locks. Against external systems it reconciles only — differences are flagged for review, never overwritten.
  • Authoritative push to Veracis apps
  • Reconcile-and-flag for external systems
  • Per-system enrollment controls the scope
Built-in intelligence

Vera reads the documents. In development

When a new supplement lands, Vera is being taught to do two jobs: check it for consistency against its sibling documents in the same umbrella — the fields that should match, and the ones that legitimately differ — and extract the static data points it contains.

Nothing Vera extracts skips governance. Every extracted value enters the same maker-checker pipeline as a manual edit, pending human approval, with provenance back to the exact document it came from.

More about Vera →

A launch, tracked — illustrative
Fund structure & identifiersApproved
Party appointmentsApproved
Benchmark assignmentApproved
TA dealing detail2 fields pending
Custody detailAwaiting approval
Go-live readiness87%
Illustrative example — figures shown are for demonstration only.
Where it fits

Standalone, or the spine
of the platform.

Fund Master stands on its own as a governed data platform. Run alongside Fund Attribution, it becomes the authoritative source feeding validated static data into the rest of the Veracis suite — one entry, everywhere it's needed.

Available now
Fund Attribution
Daily NAV attribution and tracking-difference decomposition, to the security.
In design
Depositary Oversight
Daily, factual UCITS investment-limit breach detection for depositaries and trustees.
In design
ETF Transfer Agency
The primary-market dealing lifecycle — actual-cost dealing, straight through.
Early access

Master data,
mastered.

Fund Master is in preview. If governed static data would change how your operation onboards and maintains funds, register your interest and we'll keep you close to the rollout.

Register interest

Tell us a little about your organisation and we'll be in touch within one business day.

By submitting, you agree to our Privacy Policy.

No commitment required Responses within one business day Early-access programme