Aymen CHELBI Consultant D365

Dear Microsoft team,

As part of our current global rollout of Dynamics 365 Finance & Operations across our international subsidiaries, we are facing several limitations related to the Ledger account alias in the General Journal, which negatively impact the efficiency of our Global Business Services (GBS) teams.

Our goal is to ensure that GBS teams can use standardized processes across countries that share a common national chart of accounts, while still supporting local compliance and configurations. Unfortunately, we are currently facing multiple blocking points:

Limitations Identified

• Alias tied only to company, not to Chart of Accounts : General ledger>Chart of accounts>Accounts>Ledger account alias
• We cannot define an alias that applies across all companies using the same Chart of Accounts.
• This leads to unnecessary duplication of alias definitions per company, even when the underlying structure is the same.
• This increases maintenance effort, creates potential for inconsistencies, and limits the scalability of our global model.
• No separate description field in the Alias table
• There is only one field for the Alias value, without a dedicated field for a user-friendly description. This description should be displayed in the lookup field within the General Journal (General ledger>Journal entries>General journals). However, this lookup is not customizable, as confirmed by Microsoft Support. Here is the support ticket where we were advised to submit this as an idea: [2505271420003174] Issue with Lookup Display on the Ledger Account Field Lookup in General Journal Lines

Suggested Enhancements

We would greatly benefit from the following improvements in future releases:

Allow Alias definitions to be tied to a Chart of Accounts instead of only companies

• This would enable centralized definitions shared across entities using the same COA.

Add a dedicated “Description” field to the Alias table

• This would separate the code from the human-readable label, improving usability and reducing confusion.

Allow configuration or extension of the Lookup control in the General Journal

• Making it responsive to field size or allowing easier extension would provide better UX.

These changes would significantly improve user experience and reduce administrative overhead in multi-country, centralized finance operations.

We would be happy to discuss this further or provide additional examples if needed.

Thank you in advance for considering this feedback.

Best regards,