IOSCO Benchmark Principles

When You Need This

The 19 IOSCO Principles for Financial Benchmarks are the international standard that EU BMR is based on — BMR translates these principles into binding EU law. Most regulators worldwide reference these principles. This note maps each principle to what the data engineering team must provide.

The 19 Principles by Theme

Governance (Principles 1-5)

Quote

“Benchmarks are so important to global financial markets that their integrity must be beyond question.”

IOSCO Board, Principles for Financial Benchmarks (2013)

#PrincipleDE Team Responsibility
1Overall responsibility of administratorEnsure systems support oversight function access
2Oversight of third partiesVendor SLA monitoring, fallback procedures
3Conflicts of interestSegregated service accounts (read vs write)
4Control frameworkAutomated quality gates, circuit breakers
5Internal oversightAudit logs, pipeline lineage, quarterly reviews — see compliance-and-auditability for implementation

Quality of the Benchmark (Principles 6-10)

#PrincipleDE Team Responsibility
6Benchmark designMethodology-as-code in version control
7Data sufficiencyCoverage checks (>95% of universe), fallback logic
8Hierarchy of data inputsPriority: exchange data > broker quotes > estimates
9Transparency of determinationsPublished methodology, reproducible calculations
10Periodic reviewAnnual review of data sources, quality metrics, methodology

Quality of Methodology (Principles 11-13)

#PrincipleDE Team Responsibility
11Content of methodologyAll formulas, parameters, rules documented and versioned
12Changes to methodologyADR process, consultation period, migration plan
13TransitionParallel calculation during methodology changes

Accountability (Principles 14-19)

#PrincipleDE Team Responsibility
14ComplaintsComplaint log accessible to oversight function
15Audit trail5-year retention, lineage metadata, reproducibility
16Cooperation with authoritiesData export capability for regulatory requests
17AuditExternal audit access to all systems and data
18Benchmark cessation6-month notice, transition plan, data archive
19Submitter code of conductIf applicable: contributor data governance

Compliance Checkpoints for Data Engineers

IOSCO Compliance — Every Pipeline Run

  • Source data hash recorded in lineage table
  • Row count and null rate within expected bounds
  • Weights sum to 1.00000000
  • No missing constituents

IOSCO Compliance — Weekly Checks

  • Vendor SLA compliance reviewed
  • Data quality metrics trending correctly
  • No unresolved quarantined records

IOSCO Compliance — Quarterly Reviews

  • Reproducibility test on randomly selected historical dates
  • Cross-system reconciliation (SQL Server vs BigQuery)
  • Corporate action audit review
  • ESG score coverage assessment

IOSCO Compliance — Annual Reviews

  • Full methodology review with oversight function
  • Data source review (are vendors still appropriate?)
  • Quality metric trends over the year
  • Record retention verification (5-year compliance)
  • Disaster recovery test (backup restore drill)