Skip to content
RegTech Codex
สารบัญ
ต้นฉบับ English (/briefings) →

ไทย

บทความและบันทึกแหล่งข้อมูล

ดูบทความและบันทึกแหล่งข้อมูลของสถาบัน เนื้อหาบทความเป็นภาษาอังกฤษ โปรดตรวจสอบแหล่งข้อมูลต้นฉบับโดยตรง

บทความและบันทึกแหล่งข้อมูล

TH · REGTECH-CODEX

บทความและบันทึกแหล่งข้อมูล

ดูบทความและบันทึกแหล่งข้อมูลของสถาบัน เนื้อหาบทความเป็นภาษาอังกฤษ โปรดตรวจสอบแหล่งข้อมูลต้นฉบับโดยตรง

Emir Refit Mifir Trade Reporting

EMIR Refit, MiFIR & Global ISO 20022 Trade Reporting Master Guide (2026)

Regulatory derivatives and transaction reporting across EU EMIR Refit, UK EMIR, MiFIR Article 26, CFTC Rewrite, and APAC ISO 20022 mandates now demands deterministic XML schema validation, bilateral UTI/UPI synchronization, and automated T+1 reconciliation.

ประเด็นสำคัญ: EU EMIR Refit (effective April 29, 2024) and UK EMIR Refit (effective September 30, 2024) retired legacy CSV/FpML pipes in favor of strict end-to-end ISO 20022 auth.030 XML schemas spanning 203-204 fields.

Emir Refit Mifir Trade Reporting

ISO 20022 auth.030 XML Schema Validation: Engineering EMIR Refit’s 203 Data Fields

Under EU ITS 2022/1860 and UK EMIR technical standards, every derivative lifecycle submission must conform to the ISO 20022 auth.030.001.03 XML message definition and pass over 450 conditional cross-field validation rules.

ประเด็นสำคัญ: EMIR Refit’s 203 EU fields (204 in UK) partition cleanly across Table 1 Counterparty Data (Fields 1.1–1.20), Table 2 Common Trade/Lifecycle Data (Fields 2.1–2.154), and Table 3 Margin/Collateral Data (reported via auth.108).

Emir Refit Mifir Trade Reporting

Bilateral UTI Generation Waterfall: EMIR Refit ITS Article 7 Tie-Breakers & Pairing SLAs

Unpaired Trade Repository submissions almost always trace back to bilateral counterparties independently minting two different Unique Transaction Identifiers—cured by coding the exact ITS 2022/1860 Article 7 waterfall.

ประเด็นสำคัญ: Under ISO 23897 and Commission Implementing Regulation (EU) 2022/1860 Article 7, every ISO 20022 UTI consists of up to 52 uppercase alphanumeric characters ([A-Z0-9]{1,52}), prefixed by the 20-character LEI of the generating entity.

Emir Refit Mifir Trade Reporting

ANNA DSB UPI (ISO 4914) & ISO 10962 CFI Validation for OTC Derivatives Reporting

Global ISO 20022 rewrites across EU/UK EMIR Refit, US CFTC, ASIC, MAS, and HKMA mandate the 12-character ISO 4914 Unique Product Identifier from ANNA DSB for OTC derivatives lacking a venue ISIN.

ประเด็นสำคัญ: Designated by the FSB and overseen by the Regulatory Oversight Committee (ROC), the ANNA Derivatives Service Bureau (DSB) serves as sole global issuer of 12-character ISO 4914 Unique Product Identifiers (QZ prefix + 9 alphanumerics + check character).

Emir Refit Mifir Trade Reporting

EMIR Refit Inter-TR Pairing, Phase-2 Matching & Valuation Tolerance Bands

Under RTS (EU) 2022/1856, Trade Repositories exchange bilateral derivative reports nightly—enforcing Phase-1 (87 fields) and Phase-2 (148 fields, live since April 29, 2026) matching tolerances across price, notional, and valuation.

ประเด็นสำคัญ: RTS (EU) 2022/1856 expanded TR reconciliation in two waves: Phase 1 (87 core fields from April 29, 2024) and Phase 2 (61 valuation, delta, schedule, and package fields—148 total—live since April 29, 2026).

Emir Refit Mifir Trade Reporting

UK EMIR (FCA / Bank of England) vs EU ESMA Refit: 204 vs 203 Field Schema Divergences

While the FCA and Bank of England deliberately aligned 99% of UK EMIR Refit with ESMA’s ISO 20022 specification, critical divergences in Field 1.21 Execution Agent, intragroup exemptions, UK TR perimeters, and error notifications trip up dual-regulated firms.

ประเด็นสำคัญ: Joint FCA/Bank of England Policy Statement PS23/2 took effect on September 30, 2024 (5 months after EU EMIR Refit), adopting ISO 20022 auth.030.001.03 with 204 fields—one more than ESMA’s 203 fields.

Emir Refit Mifir Trade Reporting

US CFTC Part 43/45 Swap Data Rewrite & SEC Regulation SBSR Audit Guide

Unlike EMIR’s dual-sided universal derivative mandate, the US Dodd-Frank Title VII split assigns CFTC Part 43/45 oversight over swaps and SEC Regulation SBSR oversight over single-name/narrow-index security-based swaps under strict single-sided hierarchies.

ประเด็นสำคัญ: Dodd-Frank Title VII splits US OTC derivatives: CFTC Parts 43 & 45 govern Rates, Broad-Index Credit, FX, and Commodity swaps, while SEC Reg SBSR governs single-name CDS and narrow-index/equity swaps.

Emir Refit Mifir Trade Reporting

APAC OTC Derivatives Rewrite (2024–2026): ASIC, MAS, HKMA & JFSA ISO 20022 Synchronization

Between April 2024 and late 2025, Japan’s JFSA, Australia’s ASIC, Singapore’s MAS, and Hong Kong’s HKMA/SFC rolled out staggered ISO 20022 OTC derivatives rewrites—expanding APAC scope over retail CFDs, Nexus booked-or-traded rules, and safe-harbor delegated reporting.

ประเด็นสำคัญ: Four major APAC regimes migrated to CPMI-IOSCO CDE + ISO 20022 XML on staggered dates: JFSA Japan (April 1, 2024), ASIC Australia (October 21, 2024), MAS Singapore (October 21, 2024), and HKMA/SFC Hong Kong (September 29, 2025).

Emir Refit Mifir Trade Reporting

EMIR Refit Action Type & Event Type Lifecycle Matrix: NEWT, MODI, TERM, ERRO & REVI

Replacing legacy single-dimensional action codes, EMIR Refit pairs eight Action Types with twelve business Event Types inside a strict finite-state machine—where sending ERRO instead of TERM or MODI after maturity triggers instant NACKs.

ประเด็นสำคัญ: EMIR Refit separates technical database actions (Field 2.151 Action Type: NEWT, MODI, CORR, TERM, ERRO, REVI, VALU, POSC) from business causes (Field 2.152 Event Type: TRAD, NOVA, COMP, ETRM, INCP, etc.).

Emir Refit Mifir Trade Reporting

FC, SFC & NFC-/NFC+ Clearing Thresholds: EMIR Article 9(1a) Delegated Liability

Under EMIR Article 9(1a), Financial Counterparties bear statutory legal responsibility for reporting both sides of OTC derivatives traded with NFC- corporates—unless strict onboarding attestations, hedging-exemption math, and AIFM/UCITS rules are tracked.

ประเด็นสำคัญ: EMIR classifies counterparties into four buckets: standard Financial Counterparties (FC+), Small Financial Counterparties (FC-), Non-Financials above any threshold (NFC+), and below all thresholds (NFC-).

Emir Refit Mifir Trade Reporting

GLEIF LEI Lapsed Status & Renewal Rejections in EMIR Refit & MiFIR Reporting

Trade Repositories and Approved Reporting Mechanisms enforce action-sensitive GLEIF RegistrationStatus checks—where a LAPSED Counterparty 1 LEI triggers hard NACK rejections on NEWT and MODI filings while MiFIR enforces strict pre-trade "No LEI, No Trade" blocks.

ประเด็นสำคัญ: In EMIR Refit, Counterparty 1 (Field 1.4) and ERR (Field 1.3) MUST hold an active GLEIF status (ISSUED, PENDING_TRANSFER) on NEWT, MODI, and REVI—a LAPSED own-LEI triggers a hard NACK!

Emir Refit Mifir Trade Reporting

MiFIR Article 26 & RTS 22 Transaction Reporting: ARM auth.016, TOTV & CONCAT IDs

While EMIR monitors open derivative positions, MiFIR Article 26 (RTS 22) polices market abuse—requiring T+1 submission of 65-field ISO 20022 auth.016 reports via an Approved Reporting Mechanism with strict Annex II natural-person identifiers and INTC aggregation.

ประเด็นสำคัญ: MiFIR Article 26 (RTS 22) mandates T+1 ARM reporting (auth.016) on instruments Traded on a Trading Venue (TOTV) or OTC derivatives whose underlying security or index constituent is TOTV.

Emir Refit Mifir Trade Reporting

EMIR Refit Article 9(1) Breach Notifications: Reporting "Significant Issues" to NCAs

ITS (EU) 2022/1860 Article 9(1) codified a binding self-reporting duty: whenever misreporting, late filings, or unreconciled breaks breach ESMA’s quantitative or qualitative materiality triggers, the Entity Responsible for Reporting must notify its NCA promptly.

ประเด็นสำคัญ: ITS (EU) 2022/1860 Article 9(1) obligates the Entity Responsible for Reporting (ERR) to notify its NCA—and any represented counterparty’s NCA—promptly upon discovering significant misreporting or obstacles.

Emir Refit Mifir Trade Reporting

Daily Margin, Collateral & Valuation Reporting: ISO 20022 auth.108 & ISDA SIMM

Financial Counterparties and NFC+ firms must submit daily T+1 contract valuations (auth.030 VALU) alongside portfolio-level Initial Margin, Variation Margin, and Excess Collateral balances (auth.108 MARU) both pre-haircut and post-haircut.

ประเด็นสำคัญ: Under EMIR Article 9, both FC+ and FC- (SFC) plus NFC+ firms must report daily T+1 Valuation (auth.030 VALU) and Margin (auth.108 MARU) updates—only NFC- corporates are exempt.

Emir Refit Mifir Trade Reporting

ETD & CFD Position-Level vs Trade-Level EMIR Reporting: POSC, INCP & Netting

Exchange-Traded Derivatives and netted retail CFD accounts execute millions of intraday fills that settle into a single end-of-day net open interest—modeled in EMIR Refit via coordinated Trade-Level POSC and Position-Level PSTN reporting.

ประเด็นสำคัญ: Under RTS 2022/1855 Article 3, Position-Level (PSTN) reporting is allowed only when legal risk nets into a position, intraday fills were reported, and both counterparties mutually agree.

Emir Refit Mifir Trade Reporting

FX Swaps, Deliverable Forwards & NDFs: Two-Leg EMIR Refit ISO 20022 XML Mapping

Foreign exchange derivatives generate massive inter-TR pairing and leg-ordering breaks under EMIR Refit—requiring exact ESMA mapping of FX Swap Near/Far legs, Package Identifiers, Exchange Rate Basis, and MiFID II Article 10 spot/commercial exemptions.

ประเด็นสำคัญ: Under ESMA EMIR Refit Guidelines, an FX Swap (Near Leg + Far Leg) MUST be reported as two separate auth.030 reports (2 UTIs) linked via Field 2.6 Package Identifier—including a <=T+2 Near Leg!

Emir Refit Mifir Trade Reporting

Retail CFD & Rolling-Spot FX Brokers: Dual EMIR Refit & MiFIR Reporting Architecture

Multi-asset CFD and rolling-spot FX brokers face the highest per-firm message volumes in European regulatory reporting—navigating single-sided retail EMIR legs, dual-sided A-Book liquidity-provider hedges, and MiFIR TOTV underlier triggers.

ประเด็นสำคัญ: For natural-person retail CFD traders, brokers submit one single-sided EMIR report (1.8=False, Broker_LEI + ClientID), whereas corporate NFC- clients require a GLEIF LEI and two Art. 9(1a) reports.

Emir Refit Mifir Trade Reporting

SFTR ISO 20022 Reporting: Repo, Securities Lending, Margin Lending & Collateral Reuse

Parallel to EMIR Refit, Regulation (EU) 2015/2365 (SFTR) mandates T+1 ISO 20022 reporting of repos, buy-sell backs, securities/commodities lending, and prime-broker margin lending across 155 data elements—with a critical UK NFC exemption divergence.

ประเด็นสำคัญ: SFTR Article 4 (ISO 20022 auth.052/070/071) captures four SFT types: Repos (REPO), Buy-Sell Backs (BSBK), Securities/Commodities Lending (SLEB), and Prime Margin Lending (MLEN).

Emir Refit Mifir Trade Reporting

SEC Rule 17a-4, CFTC Rule 1.31 & MiFID II Art. 16(7): WORM Audit-Trail & Trade Reconstruction

Over $3.3 billion in SEC and CFTC "off-channel communications" fines—combined with 72-hour CFTC swap-reconstruction tests—force broker-dealers, swap dealers, and MiFID firms to bind every trade UTI to immutable WORM/audit-trail records.

ประเด็นสำคัญ: Amended SEC Rule 17a-4(f) permits broker-dealers to preserve electronic records using EITHER non-rewritable WORM object-lock storage OR a time-stamped Audit-Trail Alternative tracking every modification.

Emir Refit Mifir Trade Reporting

Automated T+1 Three-Way Reconciliation: Front-Office OMS vs Middleware vs Trade Repository

Testing middleware against its own outbound XML only proves your reporting hub agrees with itself—satisfying FCA Market Watch, ESMA EMIR Refit, and CFTC 45.14 requires independent three-way reconciliation from raw front-office source ledgers directly to Trade Repository and NCA state files.

ประเด็นสำคัญ: FCA Market Watch and ESMA condemn two-way middleware-to-TR checks: if an upstream filter drops a trading book before middleware, middleware-to-TR shows 100% green while thousands of trades go unreported.

ข้อมูลสถาบันจากแหล่งที่มา

ข้อมูลสถาบันจากแหล่งที่มา

ดูข้อมูลสถาบัน หน่วยงานกำกับ และตลาดที่นำเข้า ข้อมูลอาจไม่ครบถ้วนหรือล้าสมัย โปรดยืนยันข้อมูลปัจจุบันกับแหล่งข้อมูลต้นฉบับ

บทความและบันทึกแหล่งข้อมูล | RegTech Codex | RegTech Codex