Configure Data Quality > Orchestrating data enrichment and validations > Configuring cleansing and standardization

Configuring cleansing and standardization

You can configure rule associations to cleanse and standardize data.

When you configure rule associations to cleanse and standardize data, the rule associations first validate the data and enrich the fields with cleansed data based on the validation results. When you configure cleansing and standardization, you can choose to downgrade the trust scores of fields that fail validations by specifying the percentage of trust score to downgrade.

The following table lists the plugin that you can use to cleanse and standardize data:

Plugin Name	Service that the plugin uses
Address Verification	DaaS
Application Integration-based Cleansing	Application Integration
Crosswalk standardization	MDM SaaS
DaaS Real-Time Email Verification	DaaS
DaaS Real-Time Phone Verification	DaaS

Address Verification

To validate and enrich address values in batch or real time, use the Address Verification plugin.

To validate and enrich addresses in records imported in bulk, enable the objective for ingress on the Triggers tab in the Advanced Settings dialog box.

To validate and enrich addresses in records in real time, enable the objective for business applications and REST APIs on the Triggers tab in the Advanced Settings dialog box.

For more information about setting the objectives for ingress, business applications, and REST APIs, see Step 2. Adding objectives to an objective group.

Address verification for batch processing

If your organizations were created after the October 2025 release, use the Address Verification plugin to verify addresses in predefined address field groups of records that you ingress or import in bulk. The Address Verification plugin uses Enrichment and Validation Orchestrator to cleanse, verify, and standardize addresses in the records.

By default, the DaaS rule association is disabled. Enable the rule association to verify the addresses in predefined address field groups in batch by using Enrichment and Validation Orchestrator.

If your organizations were created after the October 2025 release, you can configure objective groups and create rule associations to verify addresses in custom address field groups of records that you ingress or import in bulk using the Address Verification plugin.

For more information about adding rule associations to objectives, see Step 3. Creating rule associations.

If your organizations were created before the October 2025 release, use the predefined address verifier asset or configure objective groups and create rule associations by using the Address Verification plugin.

Address verification for real-time processing

To verify address values in real time, use the Address Verification plugin. The address verification plugin uses Enrichment and Validation Orchestrator to cleanse, verify, and standardize addresses in records.

MDM SaaS provides a predefined Address Verification data enhancement rule that uses Enrichment and Validation Orchestrator to verify addresses in real time. You can also configure a rule association for address verification using the predefined data enhancement rule. When objectives are run, Enrichment and Validation Orchestrator validates, cleanses, and standardizes address values in real time.

The existing DaaS real-time address verification uses Informatica Address Verification as the default DaaS provider. If you have configured DaaS real-time address verification in organizations created before the October 2025 release, you can continue to use it to verify addresses. However, if you want to use Enrichment and Validation Orchestrator to verify addresses in real time, disable the existing DaaS real-time address verification and then create a rule association with the Address Verification plugin.

If your organizations were created after the October 2025 release, configure objective groups and create a rule association to verify address values in real time using the Address Verification plugin.

For more information about adding rule associations to objectives, see Step 3. Creating rule associations.

The predefined Address Verification provider contains input and output fields, which you can map to the business entity fields.

The following table lists the input fields of the Address Verification data provider that you can map to business entity fields:

Address Verification Data Provider Field	Field Type	Business Entity Field
Address Elements > Country	Text	Country
Postal Code > Postal Code 1	Text	Postal Code
Locality > Locality 1	Text	City
Administrative Division > Administrative Division 1 > Extended	Text	County
Preformatted data > Postal Delivery Address Lines > Address Lines 1	Text	Address Line 1
Preformatted data > Postal Delivery Address Lines > Address Lines 2	Text	Address Line 2
Preformatted data > Postal Delivery Address Lines > Address Lines 3	Text	Address Line 3
Additional Fields > Text Field 1	Text	State
Additional Fields > Text Field 2	Text	Address Type
Additional Fields > Text Field 3	Text	Usage Type
Additional Fields > Text Field 4	Text	Address Status
Additional Fields > Text Field 5	Text	Postal Code Extension
Additional Fields > Boolean Field 1	Boolean	Default Indicator
Additional Fields > DateTime Field 1	DateTime	Start Date
Additional Fields > DateTime Field 2	DateTime	End Date

The following table lists the output fields of the business entity that you can map to Address Verification data provider fields:

Business Entity Field	Field Type	Address Verification Data Provider Field
Default Indicator	Boolean	Enrichments > Additional Fields > Boolean Field 1
Address Type	Text	Enrichments > Additional Fields > Text Field 2
Usage Type	Text	Enrichments > Additional Fields > Text Field 3
Address Status	Text	Enrichments > Additional Fields > Text Field 4
Address Line 1	Text	Preformatted data > Postal Delivery Address Lines > Address Lines 1
Address Line 2	Text	Preformatted data > Postal Delivery Address Lines > Address Lines 2
Address Line 3	Text	Preformatted data > Postal Delivery Address Lines > Address Lines 3
Country	Text	Address Elements > Country > Code
State	Text	Enrichments > Additional Fields > Text Field 1
City	Text	Address Elements > Locality > Locality 1
County	Text	Address Elements > Administrative Division > Administrative Division 2 > Extended
Postal Code	Text	Address Elements > Postal Code > Postal Code 1
Postal Code Extension	Text	Enrichments > Additional Fields > Text Field 5
Coordinate System	Text	Enrichments > Geo Codes > Arrival Point > Coordinates
Start Date	DateTime	Enrichments > Additional Fields > DateTime Field 1
End Date	DateTime	Enrichments > Additional Fields > DateTime Field 2
Latitude	Text	Enrichments > Geo Codes > Arrival Point > Latitude
Longitude	Text	Enrichments > Geo Codes > Arrival Point > Longitude
Enriched Indicator	Text	Enrichments > Status Codes > Enriched Indicator
Verification Status Code	Text	Enrichments > Status Codes > Verification Status Code
Verification Message	Text	Enrichments > Status Codes > Verification Status Message

Application Integration-based Cleansing plugin

To validate and cleanse data by connecting to an external data provider, use the Application Integration-based Cleansing plugin.

You need to create Application Integration processes that you can use with this plugin. For more information about creating a process for Application Integration-based cleansing, see Payload formats for Application Integration-based cleansing.

The following table lists the properties of the plugin:

Property	Description
CAI Process Identifier	Identifier of the Application Integration process that the plugin uses.
CAI Process Name	The API name of the process that's specified in the CAI Process Identifier property.
Include only new or updated field group entries	Determines whether the input payload includes only new or updated field group entries. To send all entries of a field group to the Application Integration process, disable the property. For example, if you want to ensure that a record has at least one address entry, disable this property so that the validation service can count the entries in the Address section. Note: When you enable the option to include only new or updated field group entries in the payload, the associated rule association runs only if users add or update entries for the mapped field groups. It doesn’t run even if users add or update a value only in an input root field without adding or updating the field group entries.
Run the selected process even when all input fields are empty	Indicates whether to run the Application Integration process when all input fields are empty. By default, when all input fields are empty, the status of the rule association is automatically set to successful without running the Application Integration process.

Crosswalk Standardization

To standardize picklist values with values in enterprise code list from Reference 360, use the Crosswalk Standardization plugin.

For example, your organization contains a country picklist. You ingress records from different data sources, such as CRM, ERP, and Salesforce. The CRM source system uses USA for United States in the country picklist. The ERP source system uses US and the Salesforce source system uses United States of America. To standardize these values in all records, you define source systems and associate the country picklist with an enterprise code list from Reference 360.

For more information about associating picklists to enterprise code lists in Reference 360, see Create a source system.

When you ingress records, MDM SaaS standardizes values of the country picklist. After the values are standardized, if your goal is to transform picklist values that aren't included in the enterprise code list, configure a rule association with the Data Quality - Transformation plugin.

To achieve this goal, use the predefined Crosswalk data enhancement rule and configure a rule association to standardize picklist values. Then, you can configure an objective group, add an objective within the objective group, and run rule associations in a sequence. In the objective, you can add the rule association configured with the Crosswalk data enhancement rule, and include the rule association configured with the Data Quality - Transformation plugin.

When MDM SaaS runs objectives, Enrichment and Validation Orchestrator runs these rule associations in a sequence. MDM SaaS first standardizes picklist values and then, based on the rule logic configured for the rule specification in Data Quality, MDM SaaS transforms picklist values that aren't part of the enterprise code list.

The Crosswalk data enhancement rule uses the picklist as the input field and the enterprise code list as the output field. You can map the corresponding business entity fields to the input and output fields.

Note: If the enterprise code list in Reference 360 contains more than 10,000 code values, MDM SaaS can't standardize picklist values using the crosswalk standardization plugin.

DaaS Real-Time Email Verification

To validate and enrich email addresses in real time, use the DaaS Real-Time Email Verification plugin. The plugin uses Enrichment and Validation Orchestrator to cleanse, verify, and standardize email addresses in records.

Note: To validate and enrich addresses in records in real time, enable the objective for business applications and REST APIs on the Triggers tab in the Advanced Settings dialog box.

MDM SaaS provides a predefined Email Verification data enhancement rule that uses Enrichment and Validation Orchestrator to verify email addresses in real time. You can also configure a rule association for email verification using the predefined data enhancement rule. When objectives are run, Enrichment and Validation Orchestrator validates, cleanses, and standardizes email addresses in real time.

For more information about adding rule associations to objectives, see Step 3. Creating rule associations.

The default input field that the Email Verification data enhancement rule uses is electronicAddress of the text data type. The input contains email addresses that users enter in real time. You can map the electronicAddress input field to the email address business entity field.

The following table describes the output fields:

Output Field	Description
EnrichedIndicator	Indicates whether the verification process enriched the email addresses with additional details.
NetProtectedBy	Determines whether the domain of the email address is protected by a security service.
StatusDescription	Status of the verification process.
StatusNbr	Status code of the verification process.
HygieneResult	Describes the outcome of additional quality checks on the email address. Unlike the statusDescription field, the HygieneResult field describes whether the email address is secure.
electronicAddress	Displays the verified email address.

The following table lists the output fields of the Email Verification data provider and their mapped business entity fields:

Email Verification Data Provider Fields	Mapped Business Entity Field
NetProtectedBy	Email > Net Protected By
StatusDescription	Email > Verification Message
StatusNbr	Email > Verification Status Code
HygieneResult	Email > Hygiene Status
electronicAddress	Email > Electronic Address

You can map the EnrichedIndicator boolean data type output field to the Enriched Indicator business entity field.

When you edit email addresses of records in bulk, MDM SaaS doesn't cleanse and standardize email addresses in records.

DaaS Real-Time Phone Verification

To validate and enrich phone numbers in real time, use the DaaS Real-Time Phone Verification plugin. The plugin uses Enrichment and Validation Orchestrator to cleanse, verify, and standardize phone numbers in records.

Note: To validate and enrich addresses in records in real time, enable the objective for business applications and REST APIs on the Triggers tab in the Advanced Settings dialog box.

MDM SaaS includes the predefined Global Phone Verification data enhancement rule that uses Enrichment and Validation Orchestrator to verify phone numbers in real time. You can also configure a rule association for phone verification using the predefined data enhancement rule. When objectives are run, Enrichment and Validation Orchestrator validates, cleanses, and standardizes phone numbers in real time.

For more information about adding rule associations to objectives, see Step 3. Creating rule associations.

You can use the predefined input and output fields of the Global Phone Verification data enhancement rule and map the corresponding business entity fields.

The following table describes the input fields:

Input Field	Description
prefixNumber	Denotes the prefix of the phone number.
phoneNumber	Contains the phone number that the user enters in real time.

You can map the prefix and phone number input fields to the corresponding business entity fields.

The following table describes the output fields:

Output Field	Description
EnrichedIndicator	Indicates whether the verification process enriched the phone numbers.
ISO	Determines the country code of the phone number, such as IN for India and US for the United States.
prefixNumber	Denotes the country dial code of the phone number, such as 91 for India and 1 for USA.
NDC	Code that identifies a specific region or city within a country.
StatusNbr	Code that represents the verification result.
NationalPrefix	Code that's used to dial a number within the same country.
InternationalPrefix	Code that's used to dial a number outside the country.
InternationalFormat	Verified phone number in the international format.
phoneNumber	Displays the phone number.
NationalFormat	Verified phone number in the national format.
StatusDescription	Status of the verification process.
NumberType	Type of phone number, such as mobile, landline, or VoIP.
Uses NDC	Indicates whether the phone number uses a national destination code.

The following table lists the output fields of predefined Global Phone Verification and their mapped business entity fields of the text data type:

Global Phone Data Provider Fields	Mapped Business Entity Field
ISO	Phone > ISO
NDC	Phone > National Destination Code
StatusNbr	Phone > Verification Status Code
NationalPrefix	Phone > National Prefix
InternationalPrefix	Phone > International Prefix
InternationalFormat	Phone > International Format
NationalFormat	Phone > National Format
StatusDescription	Phone > Verification Message
Number Type	Phone > Phone Type
Uses NDC	Phone > Phone Number Extension

You can map the EnrichedIndicator boolean data type output field to the Enriched Indicator business entity field.

When you edit phone numbers of records in bulk, MDM SaaS doesn't cleanse and standardize phone numbers in records.

Note: If you want to exclude prefix number from your phone numbers, Informatica recommends that you don't map the prefixNumber and phoneNumber Global Phone Data Provider output fields to the business entity output fields.

If you map the prefixNumber and phoneNumber, MDM SaaS returns inconsistent results.