import { Callout } from "zudoku/ui/Callout";

# What is 365 business Address Validation?

365 business Address Validation validates, completes, and predicts address data in Microsoft Dynamics 365 Business Central.

The app extends Business Central with automatic and manual address validation, address prediction while typing, and an address directory that reuses already validated addresses for future checks. Your users keep working on the familiar cards and documents, for example the Customer Card or the Sales Order.

## Value

Incorrect or incomplete addresses lead to undeliverable mail, incorrect master data, and extra effort for re-entry. 365 business Address Validation reduces this effort by completing addresses as they are entered and automatically validating them against a reference database whenever they change. When a check returns several possible matches, the app shows them on a dedicated comparison page where you accept the suggested address, reject it, or adjust individual fields manually.

## Functions at a glance

- **Address validation:** Automatically when an address changes on a Contact, Customer, Vendor, Alternative Address, Order Address, Ship-to Address, or sales and purchase document, individually enabled per table.
- **Address prediction:** Address suggestions while typing on the Contact, Customer, Vendor, Resource, and Employee cards, and on sales and purchase documents.
- **Address directory:** Stores validated and manually confirmed addresses, so the same address is not sent to the validation service repeatedly.
- **Bulk validation:** Batch reports for Contacts, Customers, Vendors, and Resources, plus a page for processing several results in bulk.
- **Address field highlighting:** Marks unvalidated or ambiguous address fields with a color on cards and documents.
- **Notifications:** Notifies you about suggested changes and about field values that had to be shortened due to field length.

See [Supported records](records/index.mdx) for the full overview of supported records, and [How address validation works](concepts/how-validation-works.mdx) for how the automatic check works.

## Typical use cases

- **Ongoing master data maintenance:** New or changed addresses on the Contact, Customer, and Vendor cards are validated automatically as soon as the change is saved.
- **Bulk validation of existing data:** After a data migration or before a large mailing, validate your existing records in bulk through [Validate addresses in bulk](batch-validation.mdx).
- **Data from third-party systems and marketplaces:** Orders and master data that reach Business Central through web services or the public API without a user interface, for example from a marketplace or online shop, can be validated through the **bdev.Address Validation API** codeunit. A complete example is shown in [Validate orders from external systems](../../al-developer/365businessaddressvalidation/examples/validate-api-orders.mdx).

## Limitations

<Callout type="info" title="What validation does not do">
365 business Address Validation does not replace a postal deliverability check and does not block documents.
</Callout>

- **No deliverability check:** Validation compares an address with the validation service's reference databases. Whether mail can actually be delivered to that address depends on factors outside this check.
- **No document blocking:** A changed, ambiguous, or unconfirmed address does not prevent a sales or purchase document from being released or posted.
- **Validation only on change:** Automatic validation runs when an address on an existing record is changed, not when a record is newly created. See [How address validation works](concepts/how-validation-works.mdx) for details.

The [FAQ](faq.mdx) answers common questions about licensing, API orders, and multiple companies.

## See also

- [Get started](get-started.mdx)
- [Concepts](concepts/index.mdx)
- [Supported records](records/index.mdx)
- [FAQ](faq.mdx)