Description
Compare a supplied LEI record country with supplied reference metadata; no country is decoded from the LEI itself.
Identifier validation can involve several distinct questions: whether text has the expected shape, whether a checksum is consistent, and whether an authority actually assigned the identifier. Formatting and field extraction address narrower questions. Each result must be read according to the particular property the tool checks.
Compare a supplied LEI record country with supplied reference metadata; no country is decoded from the LEI itself.
When to use this tool
Use LEI Country Code Source Match when you need the particular shape, formatting, field, or checksum property as one explicit stage in an identifier workflow.
How to use the tool and how it works
- Enter suppliedCountry, referenceCountry, source, sourceDate. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read matches, provenance. Inspect matches before interpreting the associated values.
Require nonempty suppliedCountry, referenceCountry, and source. Compare the country strings exactly and return provenance as a serialized tuple of source, sourceDate, and referenceCountry.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| suppliedCountry | Supplied Country | Required. Text; maximum UTF-16 length 8192. |
| referenceCountry | Reference Country | Required. Text; maximum UTF-16 length 8192. |
| source | Source | Required. Text; maximum UTF-16 length 8192. |
| sourceDate | Source-date text preserved without date validation. | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| matches | Whether the supplied values match under the particular stated rule. | Required. Boolean. |
| provenance | Provenance | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"suppliedCountry": "DE",
"referenceCountry": "DE",
"source": "registry",
"sourceDate": "2026-01-01"
},
"output": {
"matches": true,
"provenance": "[\"registry\",\"2026-01-01\",\"DE\"]"
}
}Limitations and assumptions
- The date is preserved as supplied rather than parsed or verified. No country registry or LEI record is fetched, and a string match does not establish a legal entity's jurisdiction.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
Alternative or Complementary methods
Use a complete format and checksum validator when required, then consult the issuing registry or verification process for assignment and identity. Preserve meaningful leading zeros as text.
References
Similar or alternative tools
- ISO 6346 Equipment Category Source Match
Compare a shaped container code's equipment-category character with a supplied category.
- Iban Country Check Digit Field Split
Split an IBAN-shaped token into country letters, check digits, and BBAN without country or checksum validation.