Story: Party schemes and FPML reference data
Table of Contents
This page documents a story in Sprint 10. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Implement the 13 reference-data types party requires before its domain layer can land. Drive the work from FpML XML through codegen and the DQ artefact workflow.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 10 |
| Now | Completed 2026-01-23. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2026-01-23 |
Continued from: Party database groundwork (sprint 09) — that story documented the party table; this one lands the 13 reference-data types needed before party can be implemented.
Continued in: GLEIF data integration (sprint 12) — turns the download script + CSV subsets into proper datasets. Also followed by Party database and domain (sprint 12), which finally implements party + counterparty on top of these reference-data types.
Acceptance
- Party-identifier schemes catalogued.
- 13 reference-data types implemented end-to-end via FpML codegen + DQ artefact workflow.
- GLEIF Golden Copy subset available for development.
- Business centres linked to country flags for visual identity.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Party identifier scheme analysis | DONE | 2026-05-19 | 2026-01-21 | Analysis pass: catalogue the party identifier schemes we need (LEI, BIC, MIC, CEDB, Natural Person, National ID, Internal, ACER, DTCC, AII/MPID). |
| Implement party-related schemes via FPML codegen | DONE | 2026-05-19 | 2026-01-22 | 13 reference-data types (entity_type, party_role, business_center, person_role, account_types, entity_classifications, local_jurisdictions, party_relationships, regulatory_corporate_sectors, reporting_regimes, supervisory_bodies, etc.); codegen parses FpML XML to SQL; per-entity SQL files; business centres linked to country flags. |
| Download and split GLEIF data | DONE | 2026-05-19 | 2026-01-23 | Script to fetch the GLEIF Golden Copy and produce a representative subset for development use. |
Decisions
- Drive from FpML XML
- hand-writing 13 reference tables wasn't realistic in one sprint; codegen makes it tractable.
- Per-entity SQL files, not concatenated
- improves modularity and matches the prefix-naming convention.
Out of scope
- Party domain layer itself — this story unblocks it but doesn't implement it.
See also
- Party database groundwork (sprint 09) — predecessor (party table structure).