web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

VAT validation Customer Engagement

(0) ShareShare
ReportReport
Posted on by 14
Does anyone know how to implement VAT validation in Customer Engagement?
Categories:
I have the same question (0)
  • Suggested answer
    11manish Profile Picture
    394 on at
    you can use below for VAT Validation 
     
    • Validate format (regex per country) by JavaScript
    • Call external API (e.g., VIES) by plugin 
  • Suggested answer
    ManoVerse Profile Picture
    961 Super User 2026 Season 1 on at
    Just to elaborate Manish's answer here  and to cover your question:
     
    VAT validation in Dynamics 365 Customer Engagement (Dataverse) is commonly implemented in EU projects, most of the customers wants to 
    • Validate a VAT ID format
    • Verify the VAT ID exists and is active (for EU VAT -> VAT Information Exchange System[VIES] )
    • Store the validation result and status
    • Optionally block record save if invalid
    For most validation requirement are EU B2B and customer wants no cost and supported solutions where Powerautomate + VIES fits perfectly.
    and there are three ways you can implement this in customer Engagement:
    Option 1: Power Automate + VIES API call ( Recommened common approach) 
    1. User enters VAT number (e.g. on Account or Contact)
    2. A Power Automate cloud flow is triggered:
    3. On create/update of VAT field
    4. The flow Calls an external VAT service (most often EU VIES SOAP/REST) , parse the response and updates
    • VAT valid (Yes/No)
    • Company name
    • Validation date
    Pros
    • No code
    • Fully supported
    • Easy to maintain
    • Works with Dataverse security
    Cons : 
    • Not strictly synchronous (few seconds delay)
    Option 2:   Real‑time validation using a Plug‑in (C#)
    1. Register a synchronous plug‑in on Pre‑Create / Pre‑Update
    2. The plug‑in Calls a VAT validation API (VIES or 3rd‑party service) , Throws an exception if VAT is invalid
    Pros
    • Real‑time
    • Can hard‑block saving invalid VAT
    Cons
    • External calls inside plug‑ins can cause:
    • Performance issues
    • Timeouts
    • Dependency on service availability
    best practice is to avoid external HTTP calls in synchronous plug‑ins unless absolutely required.
     
    Option 3: Client‑side validation (format only)
    1. JavaScript on form Validates VAT structure/regex, Shows warning before save
    Pros
    • Fast & Simple
    Cons
    • Does not verify existence
    • Easy to bypass (API, imports)
    • Good for UX enhancement only

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 184 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 138

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans