Skip to content

Main content

LEI Entity Suffix Case Fold Check

Compare explicit ASCII alphanumeric entity-suffix text with an optional case-fold policy without validating a complete LEI.

Loading tool…

Description

Compare alphanumeric entity suffixes with optional ASCII case folding.

Identifier systems separate whole-identifier validity from local spelling and suffix comparison. ASCII case folding can make two labels compare equal while leaving checksums, registry assignment and legal identity unresolved. Preserve original identifier context before interpreting a match as anything more than equality under the chosen text rule.

Compare alphanumeric entity suffixes with optional ASCII case folding.

When to use this tool

Use LEI Entity Suffix Case Fold Check when you already have entitySuffix, expectedSuffix, foldAsciiCase and need to compare alphanumeric entity suffixes with optional ASCII case folding.

How to use the tool and how it works

  1. Enter entitySuffix, expectedSuffix, foldAsciiCase. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read matches. Inspect matches before interpreting the associated values.

Require both suffixes to match nonempty ASCII letters/digits only; compare literally or after uppercasing when foldAsciiCase=true.1

Input fieldMeaning and unitsAccepted input
entitySuffixEntity SuffixRequired. Text; maximum UTF-16 length 8192.
expectedSuffixExpected SuffixRequired. Text; maximum UTF-16 length 8192.
foldAsciiCaseCompare after uppercasing the already restricted ASCII alphanumeric suffixes.Required. Boolean.
Output fieldInterpretationReturned shape
matchesMatchesRequired. Boolean.
json
{
  "input": {
    "entitySuffix": "ab12",
    "expectedSuffix": "AB12",
    "foldAsciiCase": true
  },
  "output": {
    "matches": true
  }
}

Limitations and assumptions

  • This is a suffix comparison, not full LEI syntax, checksum, registry, entity identity or legal-status validation.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Validate the complete identifier structure and checksum, then consult its authoritative assignment record when entity identity matters. Keep case-folded suffix equality as a separate, narrower check.

References

  1. Calculation and input contract: validate/lei-entity-suffix-case-fold-check — tool.io

Similar or alternative tools