Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | - | 
Jun 5, 2026 |
Business value
Many jurisdictions require that invoices and financial documents include not only the legal entity’s primary registration number but also identifiers for specific branches or establishments involved in the transaction. This feature introduces a standardized way to manage and apply establishment-level registration data across all relevant financial processes in Dynamics 365 Finance.
By enabling organizations to define and associate multiple establishments within a single legal entity, this functionality ensures that the correct registration IDs are automatically applied to customer and vendor invoices, purchase and sales orders, and project transactions. This capability reduces manual data entry, improves audit readiness, and supports compliance with evolving global e-invoicing and tax reporting mandates.
Feature details
This feature introduces the concept of an Establishment within a legal entity, allowing organizations to manage and apply establishment-specific registration identifiers such as branch IDs and local registration numbers across invoices.
The feature provides the following key capabilities:
Establishment modeling: Establishments of the legal entity are modeled using Operating units, with a new organization hierarchy purpose called Enterprise establishment structure. Each establishment can be assigned unique registration identifiers through the Global address book.
A new Establishment field is added to key transaction documents, including:
- Free text invoices
- Sales orders
- Purchase orders
- Vendor invoices
- Pending vendor invoices
- Project invoice proposals
- Intercompany customer invoices
- General journals
The establishment can default based on context, such as site or financial dimension, or be selected manually. After a transaction is posted, the establishment reference is stored immutably for audit and compliance purposes.
Vendor ship-from address tracking: A new Ship-from address field is introduced on vendor-facing documents, allowing users to specify the originating establishment of goods or services. The associated registration identifiers are captured and stored on the invoice.
Registration ID validation rules: Administrators can configure validation rules to enforce the presence and format of registration IDs based on address purpose and role such as invoice or delivery. The system validates these rules during transaction posting, ensuring data completeness and consistency.
Post‑posting review of registration IDs: After an invoice is posted, the registration IDs that were applied and stored can be reviewed directly on:
- Customer invoice journals
- Vendor invoice journals
- Project invoice journals
Use cases:
- Organizations with multiple branches or operational sites under a single legal entity.
- Businesses operating in jurisdictions that require branch-level registration data on invoices.
- Enterprises preparing for or complying with e-invoicing mandates or tax authority reporting requirements.
Note
Register for the upcoming TechTalk: Establishments, Vendor Ship-From and Registration ID governance on Invoices - Dynamics 365 Finance on the TechTalk registration page.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.