# Master data

365 business Address Validation checks the address fields of every master data record, with differences in scope by table.

It checks the fields **Address**, **Address 2**, **Post Code**, **City**, **County**, and **Country/Region Code**. In Microsoft Dynamics 365 Business Central, [automatic validation](../concepts/how-validation-works.mdx) only runs when one of these fields is changed, not when a record is created.

## Contact

Automatic validation is enabled by default through the **Contact Address Validation** switch. The Contact Card and the Contact List provide the **Validate Address** action; the **Check Contact Address** report processes multiple contacts in one run.

In addition to the address, [address prediction](../concepts/validation-and-prediction.mdx) also completes the name: for contacts of **type** *Company*, it suggests company names with their postal address; for contacts of type *Person*, only the postal address.

Field highlighting marks **Address**, **Address 2**, **Post Code**, **City**, and **Country/Region Code**, but not **County**.

- Source: `app/src/Integration/View/ContactCard.PageExt.al`.

## Customer

Automatic validation is enabled by default through **Customer Address Validation**, with the **Validate Address** action on the Customer Card and the **Check Customer Address** report. Field highlighting covers all six address fields, including **County**.

When validation applies a new address, Business Central also updates the contact linked to the customer in the same step, the way the standard `CustCont-Update` function does for every address change on a customer.

- Source: `app/src/Integration/View/CustomerCard.PageExt.al`; contact update
  `app/src/Integration/AddressValidationMgmt.Codeunit.al:1407-1411` (`custContUpdate.OnModify`).

## Vendor

Works the same as Customer: automatic validation enabled by default through **Vendor Address Validation**, the **Validate Address** action, the **Check Vendor Address** report, and field highlighting on all six fields. Here too, the standard `VendCont-Update` function updates the linked contact.

- Source: `app/src/Integration/View/VendorCard.PageExt.al`; contact update
  `app/src/Integration/AddressValidationMgmt.Codeunit.al:1498-1502` (`vendContUpdate.OnModify`).

## Employee

The **Employee Address Validation** switch enables automatic validation for employees; it is disabled by default. The **Validate Address** action on the Employee Card is available independently of this switch, as is field highlighting on all six address fields. There is no batch report for employees.

Address prediction is enabled by default through **Employee Address Prediction**.

- Source: `app/src/Integration/View/EmployeeCard.PageExt.al`.

## Resource

The **Resource Address Validation** switch enables automatic validation for resources; it is disabled by default. The **Validate Address** action on the Resource Card and the **Check Resource Address** report are available independently of this switch. The report has no entry of its own in the Role Center.

Address prediction is controlled through **Resource Address Prediction**; this switch is disabled by default, while the other prediction switches are enabled out of the box.

- Source: `app/src/Integration/View/ResourceCard.PageExt.al`; report
  `app/src/AddressValidation/Report/CheckResourceAddress.Report.al`.

## Ship-to Address

Automatic validation is disabled by default through **Ship-To Address Validation**. The **Validate Address** action is available on the Ship-to Address; a selection from the Ship-to Address list can also be checked through [bulk compare](../batch-validation.mdx). There is no dedicated batch report.

Address prediction is controlled through **Ship-To Address Prediction**. Field highlighting covers **Address**, **Address 2**, **Post Code**, **City**, and **Country/Region Code**, but not **County**.

- Source: `app/src/Integration/View/ShipToAddress.PageExt.al`.

## Alternative Address and Order Address

For **Alternative Address** and **Order Address**, only automatic validation is available, through **Alternative Address Validation** and **Order Address Validation**, both disabled by default. Neither an action, a batch report, address prediction, nor field highlighting is available for these two tables.

- Source: `app/src/Integration/AddressValidationEvents.Codeunit.al:104` (Alternative Address), `:136` (Order Address).

## See also

- [Supported records](index.mdx)
- [Sales and purchase documents](documents.mdx)
- [Validate an address](../address-validation.mdx)
- [Validate addresses in bulk](../batch-validation.mdx)
- [Address prediction](../address-prediction.mdx)