# Business Validation using Harmony Batch System

The designation of Client Role and Locale within the batch setup indicates the PDP utilized for business validation processes across various geographical contexts.

## Pre Reading

Please ensure you have read and understanding the previous configuration steps for Australia and New Zealand.

{% content-ref url="/pages/T6mRBgTGIk6q6JVoxLvf" %}
[Business Validation](/harmony-suite/user-guides/version-3.0.0/business-lookup-and-validation/business-validation.md)
{% endcontent-ref %}

Below is the simple illustration of our business validation processing using a small file in New Zealand with Harmony Batch System. A more comprehensive guide detailing the instructions on how to set up a batch job can be checked here [Harmony Batch System Cleanse Reference Guide](/harmony-suite/user-guides/version-3.0.0/batch-system-cleanse-reference-guide.md).

## **Steps to run Batch Job** 

### **1. Job Config**

It is expected that the customer has configured the [Setup NzBusinessValidation PDP](/harmony-suite/user-guides/version-3.0.0/business-lookup-and-validation/business-validation/business-validation-configurations.md#setup-nzbusinessvalidation-pdp) prior to executing a batch process.

Log in to HBS UI and select New Cleanse

Select the required Client Role that is attached to the component group that has NzBusinessValidation PDP added.

Select the Locale as New Zealand

*Example 1: NZ Cleanse job profile*

<figure><img src="/files/mCIesOmDOEUOlfrpd2Lj" alt=""><figcaption></figcaption></figure>

### 2. Input

#### **Click Input on the left panel to display the Input Reader panel. There are seven tabs in this panel, each with its own set of fields.**

Refer Page No 14 of the [**Harmony Batch System Cleanse Reference Guide**](/harmony-suite/user-guides/version-3.0.0/batch-system-match-reference-guide.md) to get an idea on how to configure the Input file for batch processing.

Quick configuration on how to configure an input file that consists of the fields below is provided here.

**Input File:** File comprises of Id, Input business number or company number, Input Company Name.

*Example 2: NZ Mock Input with intentional errors*

<div align="left"><figure><img src="/files/d10IaY1gdKDnbm6jB4uU" alt=""><figcaption></figcaption></figure></div>

#### **General panel**

Choose your input file and correct configuration for your business file.

Full description of the panel is within [Harmony Batch System Cleanse Reference Guide](/harmony-suite/user-guides/version-3.0.0/batch-system-cleanse-reference-guide.md).

<figure><img src="/files/uXbYwwgYBKM51XKCPUfB" alt=""><figcaption></figcaption></figure>

#### **Detail Record panel**

Ensure you correctly check the details versus your input file.

Full description of the panel is within [Harmony Batch System Cleanse Reference Guide](/harmony-suite/user-guides/version-3.0.0/batch-system-cleanse-reference-guide.md).

<figure><img src="/files/rpf9lQLqZnDurDkiRYHL" alt=""><figcaption></figcaption></figure>

**Baseline Fields panel**

Very important step as this information forms part of the Logical Record mapping between your input file and what the HBS system requires to process.

***Auto populate fields:*** If you have ticked 'first detail record represents baseline fields' then right click on white panel and retrieve the field names. This will auto populate the fields.

***Manually enter fields:*** Type your input column names into the table within the panel.

Full description of the panel is within [Harmony Batch System Cleanse Reference Guide](/harmony-suite/user-guides/version-3.0.0/batch-system-cleanse-reference-guide.md).

<figure><img src="/files/gtHXECZIARZdku2aZRt3" alt=""><figcaption></figcaption></figure>

#### **Logical Record**&#x20;

**HBS Logical Record represents the input baseline fields that are mapped to Harmony data models for batch processing.**

The left column "Name" is Harmony name representation for a field.&#x20;

The right column "Generated By" is the Input File name for the field with the same meaning.

**For example:**

Input business number or company number( Inputbnorcnnumber) from the baseline fields has been mapped to HARMONY\_INDIVIDUAL\_IDENTIFIER

Input company name (InputCompanyName) from the baseline fields has been mapped to HARMONY\_COMPANY\_NAME&#x20;

Input Id is the sequential id from baseline fields, it can be mapped to HARMONY\_ID.

Full description of the panel is within [Harmony Batch System Cleanse Reference Guide](/harmony-suite/user-guides/version-3.0.0/batch-system-cleanse-reference-guide.md).

*Example 3: Mock Logical Record mapping*

<figure><img src="/files/tq7ggqOBmGGjQxeHGxDW" alt=""><figcaption></figcaption></figure>

### **3. Preprocessor**

Not Applicable

### **4. Output**

#### **Harmony Output on the left panel represents the configuration of the output file and the fields to be returned in the output file.**

**General tab:** To configure the file layout specifications.&#x20;

<figure><img src="/files/pM5TAqbZwZ82Xn4a0D4h" alt=""><figcaption></figcaption></figure>

**Field Definition:** Defines the fields to be output to the output file.

click on ![](/files/k1lfZnb3b67g6mkjI53G) to open the Logical field creation window and then select the input baseline fields the user wish to see in the output file, click Done.  The selected field will then be added to the Name column.

To add parsed Company name as an output field in the output file, define party.name.companyName

To add the Output fields from NzBusinessValidation PDP to be shown in the output file, click on ![](/files/k1lfZnb3b67g6mkjI53G) to add party.CustomAttributes.fieldname

&#x20;party.CustomAttributes.business\_name -->represents validated business name.

party.CustomAttributes.business\_bn--> represents validated business number.

<figure><img src="/files/TIkulyyj2UwoiH5fARx6" alt=""><figcaption></figcaption></figure>

**Sample text output:**

The HBS Output text file may contain multiple denormalized occurrences of the same Input ID, especially when the input includes company names with party relationships. Basically, the number of record occurrences are proportional to the number of identified parties.

In the output, only one occurrence displays the enriched CustomAttributes of the **validated entity**. However, we can associate the output records with the parsed company name output to track which parsed entity was used for validation and enrichment. Please refer records 3 to 5 in the output for examples.

*Example : Complex Output within multiple entity types*

<figure><img src="/files/eHiCINuNgO14Pj4MpZ9X" alt=""><figcaption></figcaption></figure>

### **5. Exceptions**

Please refer to the [Harmony Batch System Cleanse System Reference Guide](/harmony-suite/user-guides/version-3.0.0/batch-system-cleanse-reference-guide.md).

### **6. Report**

Please refer to the [Harmony Batch System Cleanse Reference Guide](/harmony-suite/user-guides/version-3.0.0/batch-system-cleanse-reference-guide.md).

### **7. History**

Please refer to the [Harmony Batch System Cleanse Reference Guide](/harmony-suite/user-guides/version-3.0.0/batch-system-cleanse-reference-guide.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mastersoftgroup.com/harmony-suite/user-guides/version-3.0.0/business-lookup-and-validation/business-validation/business-validation-using-harmony-batch-system.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.