Finance | Project Operations, Human Resources, ...

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

(4) Share

Report

Posted on by Shooowtek

845

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.

https://learn.microsoft.com/en-us/dynamics365/finance/localizations/poland/gs-e-invoicing-pol-get-started

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:

Dynamics 365 Finance

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

CA Neeraj Kumar 5,130 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @Shooowtek,

The Key Vault setup is global and environment-specific, so you don’t need to configure a separate Key Vault for each legal entity.

In Dynamics, you’ll need to reference the secret or certificate using the exact same name as defined in Azure. When you import a feature in Globalization Studio, the system will prompt you to specify which secret or certificate from the Key Vault should be used. This is how Dynamics determines the correct value at runtime.

Additionally, while configuring response parameters in Organization administration, you can define them at the legal entity level to ensure the correct values are applied, especially since multiple entities may share similar feature setups.

Regarding the globalization studio feature setup, it is enabled through feature, and in the ER workspace you need to create a local configuration provider apart from Microsoft. This way, the feature will first be needed to be imported under Microsoft in Globalization studio, there after it should later be derived under the local configuration provider you created, to tag the required values and deploy into the system.

Regards,
Neeraj Kumar

1 people found this reply helpful.

Was this reply helpful? Yes No
CA Neeraj Kumar 5,130 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @Shooowtek,

Are there any further followup questions regarding your query and given suggestion? Please let us know.

Regards, NK

Was this reply helpful? Yes No