FinDatEx EMT Validation Reference (V4.3)

Spec: /spec/emt/EMT_V4_3_20251217.xlsx
Manifest: /spec/emt/emt-v43-info.json
Released: 2025-12-17 · Sheet: EMT V4.3
Profiles: EMT (Mandatory) (EMT_BASE)

Generated file — do not edit by hand. Regenerate via mvn -pl core -Pdocs exec:java -Dexec.args="docs/rules".

1. How this validator scores your file

The overall quality score is a weighted blend of five sub-scores. Only Severity.ERROR findings lower the score; WARNING and INFO are reported but ignored by the scorer.

Dimension	Weight	Computation
MANDATORY_COMPLETENESS	40 %	1 − (missing M-cells / total M-cells) across active profiles
FORMAT_CONFORMANCE	20 %	1 − (format errors / non-empty cells)
CLOSED_LIST_CONFORMANCE	15 %	1 − (closed-list errors / non-empty closed-list cells)
CROSS_FIELD_CONSISTENCY	15 %	1 − (XF errors / max(distinct XF rules × rows, 1))
PROFILE_COMPLETENESS	10 %	mean over profiles of (0.7 × M-completeness + 0.3 × C-completeness)

Findings are routed to dimensions by their rule-id prefix:

Rule prefix	Dimension
`PRESENCE/`	MANDATORY_COMPLETENESS + PROFILE (M leg)
`COND_PRESENCE/`	PROFILE_COMPLETENESS (C leg)
`FORMAT/` (closed-list message)	CLOSED_LIST_CONFORMANCE
`FORMAT/` (other)	FORMAT_CONFORMANCE
`ISIN/`, `LEI/`	FORMAT_CONFORMANCE
`XF-…`, template `-XF-`	CROSS_FIELD_CONSISTENCY
`*-ONLINE` (GLEIF / OpenFIGI)	not scored (advisory)

2. Profiles

Selecting a profile in the UI tells the validator to enforce the M (mandatory) and C (conditional) flags from that profile's column in the spec. Multiple profiles can be selected simultaneously — a field is mandatory if any selected profile says so.

Code	Display name	Mandatory fields	Conditional fields
`EMT_BASE`	EMT (Mandatory)	40	33

3. General rules

The engines below run on every applicable field/row independently of the template-specific cross-field block in §4.

Version rule

Rule ID: EMT-XF-VERSION
Severity: ERROR (INFO if the version cell is absent)
Expected token: V4.3
Trigger: the version cell of the file does not contain the expected token.
Score impact: Each ERROR lowers CROSS_FIELD_CONSISTENCY (15 %) by 1 / max(distinct cross-field rules × rows, 1).

Presence engine (`PRESENCE/{numKey}/{profile}`)

What it checks: for every FieldSpec flagged M for an active profile and applicable to the row's CIC, the cell value must be non-empty.
Severity: ERROR.
Score impact: Each missing cell lowers MANDATORY_COMPLETENESS (40 %) by 1 / total mandatory slots, and lowers the per-profile PROFILE_COMPLETENESS leg (10 %, M-weighted 0.7).
Active rule instances: 40 (one per field × profile).

Conditional-presence engine (`COND_PRESENCE/{numKey}/{profile}`)

What it checks: for every FieldSpec flagged C for an active profile and whose CIC applicability matches the row's CIC, the cell value must be non-empty.
Severity: WARNING.
Score impact: Each missing cell lowers PROFILE_COMPLETENESS (10 %, C-weighted 0.3) by 1 / total conditional slots. Severity = WARNING — does not affect MANDATORY_COMPLETENESS or FORMAT_CONFORMANCE.
Active rule instances: 33 (one per CIC-restricted field × profile).

Format engine (`FORMAT/{numKey}`)

What it checks: every populated cell is validated against its codification kind: ISO 4217 currency, ISO 3166-A2 country, ISO 8601 date, NACE, CIC 4-char, alphanumeric length, numeric, closed-list membership.
Severity: ERROR.
Score impact: Each ERROR lowers FORMAT_CONFORMANCE (20 %) by 1 / non-empty cells. Closed-list mismatches (message contains "closed list") instead lower CLOSED_LIST_CONFORMANCE (15 %) by 1 / populated closed-list cells.
Active rule instances: 114 (one per field).

External validation (opt-in)

Off by default. Operators enable it via the Settings dialog (desktop) or the FINDATEX_WEB_EXTERNAL_ENABLED env var (web).
ISIN lookup (OpenFIGI): field 9 (when type field 10 = 1)
LEI lookup (GLEIF): field 9 (when type field 10 = 10); field 20 (single-purpose, no type flag); field 3 (single-purpose, no type flag)
Score impact: External-validation findings are advisory and do not affect any score dimension.

4. Cross-field rules

No cross-field rules are wired for this template/version. Regulatory cross-field logic for EMT is deferred — see docs/SME_QUESTIONS/emt-cross-field-rules.md for the open SME briefs.

Field reference

One page per field, with its flag in every profile, the codification it must match and every rule that can fire on it.

Check your own file against these rules

Upload a TPT, EET, EMT or EPT file and get a quality score, every finding grouped by rule, and an Excel report. No login; the file is never stored.

Open the validator