> 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/user-guides/version-3.0.0/business-lookup-and-validation/guides/understanding-business-verification-code.md).

# Understanding Business Verification Code

Business Validation provides the `business_ver_code` which serves as a key component in providing insights into the quality and reliability of the validated business.

Business Verification Code (BVC) comprises of 3 indicators rule name, number of potential candidates for match and the match score that signifies the reliability of match expressed into a single string.

Business Verification Code (BVC) expression: 

{Rule Name} {delimiter} {Number of Potential Candidates} {delimiter} {Match Score} 

where {delimiter} is underscore "\_".

* **Rule Name**: The rule name can be one of the following: 
  * ID, 
  * MainName, 
  * OriginalInput, 
  * BeneficiaryName, 
  * TradingName, 
  * NoMatch
* **Number of Potential Candidates**: This indicates the number of potential matches:
  * 0: No match found.
  * 1: One match found.
  * 2 or more: Ambiguous matches found.
* **Match Score**: The match score signifies the reliability of the match between 0.0 and 1.0:
  * 0.0:  is no match.
  * 1.0: Represents a exact match.
  * Between 0.0 and 1.0: Indicates a partial match.

**business\_ver\_code examples**

* `MainName_1_1.0`: MainName used for business validation with 1 candidate found, achieving an exact match with a score of 1.0.
* `OriginalInput_1_0.14285714285714285`: OriginalInput used for business validation with 1 candidate found, resulting in a partial match with a score of 0.14.
* `BeneficiaryName_6_1.0`: BeneficiaryName used for business validation with 6 candidates found, indicating ambiguity, yet achieving an exact match with a score of 1.0.
* `NoMatch_0_0.0`: No match found.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.mastersoftgroup.com/harmony-suite/user-guides/version-3.0.0/business-lookup-and-validation/guides/understanding-business-verification-code.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.