Reporting

One book. Many jurisdictions. Two reporting families.

Trade and transaction reports, and non-financial / conduct / ESG / supervisory packs, are projections of the same event log — not a second warehouse rebuilt per regulator.

How it works

Report shapes from the lifecycle, not a nightly extract

Eligibility, UTI, LEI, instrument flags, and lifecycle actions sit on the trade. Each regime is a projection. Live trade-repository submission and counsel attestation remain the firm’s.

Family 1

Trade & transaction reporting

OTC derivatives, securities, SFT, commodity, and listed paths — UK, EU, MAS, HK, AU, US, JP, CH — from the same booked events.

Family 2

Non-financial & supervisory

Conduct, ESG and sustainability, IFRS disclosures, settlement discipline, resolution stay, outsourcing and operational-resilience evidence — same book, different pack.

Trade & transaction

Multi-jurisdiction regimes on one spine

A firm that books in London, reports in Singapore, and clears a US swap should not maintain three reporting stacks. Sylgate projects each regime from the lifecycle.

JurisdictionTrade / transaction projections
United KingdomUK EMIR · MiFID RTS 22 · SFTR
SingaporeMAS SF(RDC)R OTC
Hong KongHKTR OTC
AustraliaASIC OTC
United StatesCFTC Part 45 swap data · Part 43 public dissemination
JapanJFSA TREND
European UnionEMIR REFIT · MiFIR · EU SFTR · REMIT — same mapper spine
SwitzerlandFINMA FMIA — same mapper spine
Lifecycle

UTI and actions

  • New, amend, terminate on the same trade_id
  • EMIR CRM — confirm, portfolio recon, dispute
  • NFC / FC classification driving eligibility
  • Intragroup exemption evidence
Financing

SFTR and repo

  • UK and EU SFTR shapes
  • Conventional and tokenised repo
  • Haircut and collateral economics
  • NEWT / TERM on close and roll
Honesty

What the firm still owns

  • Live trade-repository connectivity
  • Counsel on interpretation and exemption
  • Supervisory filing credentials
  • Hosted production environment

Non-financial

Conduct, ESG, disclosures, resilience — still the same book

Non-financial reporting is not a side consultancy pack. It reads positions, parties, and events the desk already produced.

Conduct

Market integrity

  • MAR STOR / suspicious transaction packs
  • Insider list and wall-crossing evidence
  • Short-selling notification shapes
  • COBS client classification
  • Commodity position-limit utilisation
ESG & sustainability

Portfolio datapoints

  • CSRD / ESRS portfolio extracts
  • SFDR Article 6 / 8 / 9 shapes
  • TCFD / ISSB / TNFD climate tables
  • PCAF financed-emissions attribution
  • EU Taxonomy and UK SDR labelling
Disclosures

Accounting & funds

  • IFRS 9 / 13 / 7 disclosure tables
  • Hedge-accounting effectiveness packs
  • AIFMD Annex IV projection
  • MiFID costs & charges / PRIIPs shapes
Settlement

CSDR discipline

  • Fails and cash-penalty allocation
  • Internalised settlement reporting
  • Buy-in case packs
Resilience

Ops, outsourcing, stay

  • MAS Notice 644 depth evidence
  • IBS / impact-tolerance narrative
  • BRRD / QFC stay classification
  • ISDA stay-protocol adherence register
Supervisory

Returns and collateral

  • BoE / PRA statistical return shapes
  • COREP / FINREP template bridges
  • UMR margin and collateral fields
  • UK IFPR K-factor projection

Design rule

One trade_id through every report

If Finance marks the position and Compliance projects EMIR, they are not arguing about two extracts. Non-financial packs inherit the same events. Change the book once; every jurisdiction and every family updates from that log.

Next

Walk reporting on the portal