> For the complete documentation index, see [llms.txt](https://docs.mastersoftgroup.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mastersoftgroup.com/harmony-suite/release-notes/version-4.2.0.md).

# Version 4.2.0

Planned release in November 2026

## Enhancements

### **NZ address standardisation aligned with NZ reference data**&#x20;

NZ address standardisation now keeps street types in their full form (for example, "Street", "Road", "Place") to match the NZAD, NZPAF and CNAR reference datasets. Previously, street types were abbreviated during standardisation, which caused some addresses to fail to match during validation. Customers using standardisation before NZ validation should see more addresses matched to a valid DPID.

## Restored functionality

### **Legacy SOAP service (WSNRABean) reinstated**&#x20;

The legacy SOAP service for rapid address search, available in Harmony 3.2.1 and removed in Harmony 4.0, is available again with improved security posture. Customers upgrading from Harmony 3.x who rely on this service can upgrade without changing their integration.

## Bug fixes

### **NZPAF/NZAD validation of addresses with a town but no postcode**

Fixed an issue where validating an NZ address that had a town but no postcode raised an internal error during the perfect-match check. The correct delivery point was found and then discarded, and validation fell back to a slower locality-correction rule. Such addresses are now matched by the primary rule, which makes validation faster (about 2 ms instead of about 44 ms per address in testing) and greatly reduces DEBUG log output.

## Upgrade notes

No configuration changes are required.

Customers who apply NZ address standardisation before validation may see changed (improved) match results.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mastersoftgroup.com/harmony-suite/release-notes/version-4.2.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
