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

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Electronic Invoicing for Multiple Legal Entities - Globalization Studio & Key Vault Setup

(1) ShareShare
ReportReport
Posted on by 831
Hi everyone,
 
We're currently in the process of implementing the standard Electronic Invoicing feature in D365 F&O, specifically for the national e-invoicing system integration using Globalization Studio.
 
The process for a single legal entity is pretty clear to us:
  • Set up the Electronic Invoicing service.
  • In D365's Globalization Studio, import and configure e-invoicing feature from the Global Repository.
  • Create an Azure Key Vault to store the system authentication token as a secret.
  • Connect everything in D365, and it works as expected.
 
However, the main challenge arises when we need to configure this for our environment, which has several active legal entities. Each company has its own unique Tax ID and will need to use its own unique token to authenticate with system.
 
I have a few specific questions and would be grateful for your insights and experience:
  • Azure Key Vault Setup: Should we create a separate Key Vault for each legal entity, or is it best practice to use a single, central Key Vault and store the tokens for all companies as different secrets (e.g., Token-CompanyA, =Token-CompanyB, etc.)?
  • Token Selection Logic: This is the crucial part. How does the Electronic Invoicing service know which secret to pull from the Key Vault for an invoice being issued from a specific company? Where is this dynamic lookup logic configured?
  • Globalization Studio Configuration: Is this logic handled within the feature setup in Globalization Studio? I'm suspecting it has something to do with Application-specific parameters within the format configuration, where we could set up a condition based on the legal entity's Tax ID (e.g., LegalEntity.TaxRegistrationNumber). Is this the right approach?
Has anyone here gone through a similar multi-company setup and could share how to configure this correctly? Any guidance on best practices to avoid future issues would be greatly appreciated.
 
Thanks in advance!
Categories:
I have the same question (0)

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Sohaib Cheema Profile Picture

Sohaib Cheema 823 User Group Leader

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 673 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 491 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans