Schema Registry Monitoring

Fynrex continuously watches official NCA schema registries for version updates — so you hear about changes in hours, not after a rejection.

How Fynrex monitors NCA schema registries

  1. 01
    Registry polling
    Fynrex maintains a polling schedule for each NCA's official schema registry publication endpoint. FCA uses the Connect repository; BaFin publishes via the MVP portal developer area; ACPR via the ACPR Open Data API; DNB via its XBRL taxonomy hub.
  2. 02
    Version diff parsing
    When a new schema version is detected, Fynrex downloads both the current and previous XSD file and produces a structured field-level diff — identifying added, changed, and removed elements and their cardinality or type constraints.
  3. 03
    Impact mapping
    The diff is mapped against your institution's transaction data model. Fynrex identifies which changed fields affect your report generation pipeline and flags the specific mapping adjustments required.
  4. 04
    Notification and regeneration
    Your compliance team receives an impact report by email. Fynrex triggers automatic regeneration of your XML report package against the new schema version and queues it for your review before the submission window.

Supported schemas and current versions

NCA Schema Type Tracked Version Standard Last Registry Update Status
FCAPAIN.001 (Credit Transfer)v3.1.3ISO 200222026-02-14Current
FCAPAIN.002 (Return)v2.0.5ISO 200222025-09-19Current
BaFinPAIN.001 (Credit Transfer)pain.001.001.04ISO 200222026-01-22Current
BaFinMVP Portal Schemav6.2BaFin-specific2025-08-08Current
ACPRTransaction Reportv2.4.1ISO 200222025-12-11Current
DNBISO 20022 XMLpain.001.001.03ISO 200222025-07-30Current
DNBXBRL Taxonomyv4.3XBRL2025-11-05Current
CBITransaction Reportv1.8.2ISO 200222025-06-14Current

Never discover a schema change from a failed submission