Dynamics 365 Finance

The financial dimension string to use in the excel add-in for journals is derived from the menu item Financial dimension configuration for integrating applications and is not legal entity specific. In instances where an instance has many legal entities with various financial dimensions, the use of the excel add-in becomes difficult and overwhelming for users to navigate how to enter their Main account plus relevant financial dimensions.

Proposal should be to either make this parameter legal entity specific or create a new menu item to determine which financial dimensions should be used when the excel add-in is being used to enter journal entries. In either case, this would make the use of the excel add-in more accessible and friendly for users who may not be familiar with dimension sets of all legal entities in their instance.

External codes on units are mandatory setup to issue electronic invoices. In D365 you can have a lot of units in different instances. Setup of these codes will be a time consuming task.

Please provide an data entities to import external codes for units!

These kind of entities are already in place in a lot of other areas like on VAT codes.:

• External code classes for tax code (TaxCodeExternalCodeClassEntity)
• External codes for tax code (TaxCodeExternalCodeEntity)

We cannot select more than one user's group to access to a specific module in the GL calendars access level form.

Since we can only select one user group to access to one specific module, we have to edit this user's group to add or remove users frequently. It would be convenient to be able to select more than one user's group to access the module.

Allow attachments to Party Records to also be available to the related master data records, i.e. Vendors, Customers, Employees, etc.

We need the ability to automate Partial Ledger Settlement. As the current functionality stands in the build 10.0.43, Process Automation for Ledger Settlement does not support Partial Ledger Settlement. Implementing automatic Partial Ledger Settlement could significantly enhance the efficiency of customers' daily operations.

Often time employees have both a different first and last name they prefer to go by depending on their country, marriage status or other factors. This differs from their legal first and legal last name. Often times HR wants to use Known As to put their Nickname and Search Name to put their alternative last name. When viewing workers or resources, it is desired to have the option to build a Name Sequence that is "Known As + Search Name". However, Search Name is not currently an available option. The request is to allow Search Name to be an available Name sequence option.

Every time users process ledger allocation rules, they have to remember to set the as at date, Zero source, Proposal options and GL posting date. To save time and avoid issues, it would be better if the dates were dynamic, using date intervals, and the remainder reflected usage data.

Many companies use posting layers to prepare their accounting under different frameworks (e.g., IFRS, GAAP). Some accounts may be relevant only to a specific framework and should therefore contain postings exclusively from the corresponding posting layer. For this reason it would be beneficial to implement validation rules based on the posting layer for each main account. The suggestion is to add an option for posting layer validation in the main account's posting validation section.

In the invoicing process using Peppol Billing BIS 3.0 for customer electronic invoices in Norway (as described in the Microsoft Learn documentation - https://learn.microsoft.com/en-us/dynamics365/finance/localizations/norway/emea-nor-e-invoices), a PDF copy of the invoice is created as an attachment when the following conditions are met:

• ER configuration is enabled via electronic documents (Accounts receivable parameters > Electronic documents).
• The "eInvoice attachment" option is activated on the customer card.
• The user posts a project invoice or a customer invoice with the "Print" option set to "Yes."

This PDF attachment is automatically generated based on the selected report format—either standard SSRS or Business Documents—and is added to CustInvoiceJour and ProjInvoiceJour. However, the current implementation uses a generic attachment description that is the same for all invoices, regardless of the format applied.

Problem: Since this attachment is embedded in the e-invoice file, a generic description does not provide meaningful or unique identification for attachments. This creates challenges when managing e-invoice files efficiently.

Proposed Solution: To improve usability and traceability, the attachment description should dynamically reflect the naming conventions of the associated business document or SSRS report. Specifically:

• For Business Documents: The attachment description should match the Business Document file name.
• For SSRS reports: The description should follow a custom format incorporating key identifiers, such as the company ID, invoice number, and customer ID.

Examples of File Names for Attachments (AS-IS):

• Customer Invoice: SalesInvoice.Report.pdf
• Free Text Invoice: FreeTextInvoice.Report.pdf
• Collection Letter Note: CustCollectionJour.Report.pdf
• Project Invoice without Billing Rules: ProjInvoice.Report.pdf
• User-Defined Project Invoice: ProjInvoice.Report.pdf



By implementing this enhancement, the attachment descriptions will become more informative and aligned with the content of the invoice files. This will result in improved efficiency and accuracy in managing e-invoice files, ultimately benefiting users handling large volumes of transactions.

While a user can view and select singular journal entries in the Global General Journal form, you're not actually able to post or delete multiple entries unless they're all from the same branch/company/D365 Legal Entity. This is very time consuming, and we'd like the functionality to be expanded.