Business Validation using Harmony WS

This document provides instructions on utilizing the Harmony Restful WebServices for the Validation of business samples using Business Validation PDPs in different locales.

API:

http://localhost:8080/HarmonyWS/rest/parseCustomerData

Role used in Webservice Request

Sample Request and Response for Australia

Response 1 to 3 illustrates single company entity. Irrespective of whether the input is a main entity name, trading name, business names or other entity name the response will always depict the rule name as MainName in business_ver_code.

chevron-rightRequest 1: Input main entity name.hashtag
chevron-rightResponse 1: Exact match to the inputhashtag
chevron-rightRequest 2: Input misspelt business name.hashtag
chevron-rightResponse 2: Response shows validated business information. business_display_name holds the corrected business_name.hashtag
chevron-rightRequest 3: Input Trading Namehashtag
chevron-rightResponse 3: Response shows validated business information. business_display_name holds the trading name.hashtag

Response 4 to 9 illustrates complex business structures with multiple entities.

These samples depict the order of priority for rules as listed in matching rules list.

chevron-rightRequest 4: Validate a Complex business with multiple entities, person name trading as another business name. hashtag
chevron-rightResponse 4: Match found using MainNamehashtag
chevron-rightRequest 5: Validate a Complex business with main entity trading as a business in trust for beneficiary. Sample for an ambiguous match.hashtag

Sample for an ambiguous match

chevron-rightResponse 5: Response shows an ambiguous match using BeneficiaryName. No further rules are validated due to ambiguity. hashtag

These samples depict the order of priority for rules as listed in matching rules list.

chevron-rightRequest 6: Complex business entity, match found on BeneficiaryName.hashtag
chevron-rightResponse 6: Exact Match found on BeneficiaryName.hashtag
chevron-rightRequest 7: Complex business entity, match found on MainNamehashtag
chevron-rightResponse 7: Exact match found on MainNamehashtag
chevron-rightRequest 8: Complex business entity, match found on TradingNamehashtag
chevron-rightResponse 8: Exact Match found on TradingNamehashtag
chevron-rightRequest 9: Validate business using OriginalInputhashtag
chevron-rightResponse:9 Partial match was found with a very weak matchhashtag

Response 10 illustrates business validation utilizing multiple data models: ID and companyName. The ID can represent either a business number or a company number, while the companyName can denote a person's name or a complex company entity.

chevron-rightRequest 10: Validate business input with both business number and company name.hashtag
chevron-rightResponse 10: Exact match found on business number. No further rules are processed.hashtag
chevron-rightRequest 11: Validate Family Partnership entity.hashtag
chevron-rightResponse 11: Exact match using OriginalInputhashtag

Response 12 to 14 illustrates business validation when custom rules are set in business_validation_config.yml file.

chevron-rightRequest 12: Validate business using custom rule for taxStatus. Configure business_validation_config.yml with taxStatus: "ACT" for au.hashtag
chevron-rightResponse 12: Input business is validated against active business tax status only.hashtag
chevron-rightRequest 13: Validate business using custom rule for nameTypes. Configure business_validation_config.yml including an additional nameType "OTN" for au.hashtag

nameTypes:

- "MN"

- "LGL"

- "TRD"

- "BN"

- "OTN"

chevron-rightResponse 13: Input business is validated against various nameTypes including other names.hashtag
chevron-rightRequest 14: Validate business using custom scoreThreshold. Configure business_validation_config.yml with scoreThreshold: 0.2 for au. Same Input record as in Request 9.hashtag
chevron-rightResponse 14: Score of the validated input falls below the threshold, hence it is categorized as a NoMatch on OriginalInput. Nevertheless, if there is a match found on the BeneficiaryName, it signifies an alternate outcome.hashtag

Response 15 illustrates how business names can surpass parsing failures through the utilization of configuration in $HARMONY_HOME/config/scrubbing/harmony_scrubbing_descriptor.xml.

default configuration is false.

Set the configuration to true, as below to surpass parse failure and proceed with business validation.

<h:passthrough-name-on-parse-failure>true</h:passthrough-name-on-parse-failure>.

chevron-rightRequest 15: Validate an alphanumeric business namehashtag
chevron-rightResponse 15: Validated business information using OriginalInput.hashtag

Sample Request and Response for New Zealand

Response 1 and 2 illustrates single company entity. Irrespective of whether the input is a main entity name, trading name, business names or other entity name the response will always depict the rule name as MainName in business_ver_code.

chevron-rightRequest 1: Input exact main entity name.hashtag
chevron-rightResponse 1: Exact match to the inputhashtag
chevron-rightRequest 2: Validate a misspelt Trading Namehashtag
chevron-rightResponse 2: Response shows validated trading name information. business_display_name holds the corrected trading_namehashtag

Response 3 to 7 illustrates business validation utilizing multiple data models: ID and companyName. The ID can represent either a business number or a company number, while the companyName can denote a person's name or a company name with multiple entities. These samples depict the order of priority for rules as listed in matching rules list.

chevron-rightRequest 3: Validate an input with multiple data models ID, Company name trading as another business name. hashtag
chevron-rightResponse 3: Match is obtained on ID. No further rules are processed.hashtag
chevron-rightRequest 4: Validate an input containing multiple data models, including an ID and a company name operating under another business name entrusted to a trust (Beneficiary). The ID yields no matches.hashtag
chevron-rightResponse 4: Exact match obtained on BeneficiaryName.hashtag
chevron-rightRequest 5: Validate an input containing multiple data models, including an ID and a company name operating under another business name entrusted to a trust (Beneficiary). The provided ID and trust name do not yield matches.hashtag
chevron-rightResponse 5: Partial match obtained on MainName 0.071hashtag
chevron-rightRequest 6: Validate an input containing multiple data models, including an ID and a company name operating under another business name entrusted to a trust (Beneficiary). The provided ID and trust name do not yield matches.hashtag
chevron-rightResponse 6: Ambiguous match obtained on MainNamehashtag
chevron-rightRequest 7: Validate an input containing multiple data models, including an ID and a company name operating under another business name entrusted to a trust (Beneficiary). The provided ID, trust name and main name do not yield matches.hashtag
chevron-rightResponse 7: Exact match obtained on TradingNamehashtag

Response 9 illustrates how business names can surpass parsing failures through the utilization of configuration in $HARMONY_HOME/config/scrubbing/harmony_scrubbing_descriptor.xml.

default configuration is false.

Set the configuration to true, as below to surpass parse failure and proceed with business validation.

<h:passthrough-name-on-parse-failure>true</h:passthrough-name-on-parse-failure>

chevron-rightRequest 9: Validate an alphanumeric business name.hashtag
chevron-rightResponse 9: Validated business information using OriginalInput.hashtag

Response 10 illustrates business names that are failed to parse.

chevron-rightRequest 10: Business names that are failed to parse.hashtag
chevron-rightResponse 10: Business Validation will not be processed for failed to parse names.hashtag

Last updated