You can associate data quality rules with the Legal Entity business entity fields to cleanse, standardize, and validate the field values. When you import the source records, the rule associations validate and transform the records in Customer 360.
Note: The predefined data quality rules are disabled for the Legal Entity business entity.
The following table lists the advanced rule associations for the Legal Entity business entity:
Rule Association Name
Rule Specification Name
Applied Field
Description
DUNSSSNValidation_AlternateIdentifier
DUNS SSN Validation
Identifier.Identifier Value
Validates whether a DUNS or social security number has a valid format.
Identifier Check
IdentifierCheck
Identifier.Identifier Value
Validates whether the identifier value has a valid format.
Legal Entity 360 for Banking includes rule logic for identifier types, such as LEI, BIC, IBAN, FDIC Certificate ID, and RSSD ID. Based on the identifier type, you can apply the rule logic. The rule logic validates whether the identifier value has a valid format.
Rule specification assets
A rule specification is a data quality asset that represents the data requirements of a business rule in logical form. Legal Entity 360 for Banking uses rule specifications to define the conditions that the input data must satisfy. Also, the rule specifications define the actions to take when input values satisfy the conditions.
Rule sets define the logical flow of data through the rule specification. A rule set contains rule statements. A rule statement reads a column of input data and verifies that the input data meets the conditions that you specify. Rule logic displays the rule statements in the rule set.
Legal Entity 360 for Banking includes rule statements to define the conditions and operations that a rule specification applies to input data. Based on the identifier type, the rule statement validates the format of the input data. An action generates an output value when the conditions in the rule statement validate an input value. If the input string conforms to the condition, the rule returns the input value, else the rule returns "INVALID".
To generate an output, Legal Entity 360 for Banking uses rule logic and regular expressions to input values.
The following table lists the rule logic and their regular expression descriptions:
Rule Logic
Description
LEI IdentifierType
Validates the format of a Legal Entity Identifier (LEI) number. The rule validates the values based on the following conditions:
- Length of the input is 20.
- First four characters are numeric.
- Characters 5 and 6 are numeric.
- Characters 7 to18 are alphanumeric.
- Characters 19 and 20 are numeric.
BIC IdentifierType
Validates the format of a Business Identifier Code (BIC) number. The rule validates the values based on the following conditions:
- Length of the input is 14.
- First four characters are alphabets.
- Character 5 is a hyphen.
- Characters 6 and 7 are alphabets.
- Character 8 is a hyphen.
- Characters 9 and 10 are alphanumeric.
- Character 11 is a hyphen.
- Characters 12, 13, and 14 are alphanumeric.
IBAN IdentifierType
Validates the format of a International Bank Account Number (IBAN). The rule validates the values based on the following conditions:
- Length of the input is less than or equal to 34.
- First 2 characters are alphabets.
- Characters 3 and 4 are numeric.
- Characters 5 to 34 are alphanumeric.
FDIC Certificate ID IdentifierType
Validates the format of a Federal Deposit Insurance Corporation (FDIC) Certificate ID. The rule returns validates the values based on the following conditions:
- Length of the input is less than or equal to 20.
- Characters are numeric.
RSSD ID IdentifierType
Validates the format of a Research, Statistics, Supervision and Regulation, and Discount and Credit Database (RSSD) ID. The rule validates the values based on the following conditions:
- Length of the input is less than or equal to 10.