Dynamics 365 Finance

Manage personalizations at the organization level with views - A small suggestion for improvement to published views

We would like to publish and pin the view per menu item but unfortunately whenever menu items are sharing the same table, the published views will overide themself.

E. g. creating a saved view in the invoice approval and publishing it leads to default view of this view also in fixed assets and general journal (all of them are sharing the LedgerJournalTable). The problem is, however, that each menu item requires different views with a different structure of information and column layout and that it is very confusing if the general ledger displays a separate view from the accounts payable module by default and vice versa.

It should be possible to publish 1 view per menu item. Every menu item has its own requirements and structure. So we suggest that the published views be linked to the menu items or the corresponding work masks instead oft he table.

Then there should be no more unwanted overlaps between the different published views showing all data from the same table. And as a small side effect, one could read MS's handouts on published views with more serenity.

In the month end closing process, when closing application modules separately there is an option to close the "project" module.

This will block any entries on the project subledger for that period. This will block both the registration of revenue transactions (new project invoices) and the registration of cost transactions (hour, item and expense transactions).

This closing is perceived as being too strict by our customers and is also not in line with the closing of other modules.

Our proposal is to either align the closing of the project subledger with the closing of the other subledgers or split the closing of the project modules into at least 2 domains: revenue & cost.

The end result of this request is providing the possibility to close the revenue side of a project in a period while still allowing to make cost entries: allow to enter expenses, hours and item consumption on a project while the generation of new project invoices is not allowed for that period.

--> Typically the customer ledger is closed in the first days of the new period while the vendor subledger and expense subledger is still open.

Below an example of a scenario that is categorised as intended behaviour but is perceived as a bug by customers:

• Customer subledger closed
• Project subledger open

When you try to create a new customer transaction via the account receivable module that is not allowed. (customer is closed) However, when you create a new customer transaction via the project module that is allowed.

In the above scenario you would expect that closing the customer module means:

• no entries are allowed in the customer subledger.
• With the current functionality this means: no entries are allowed from module X but entries are allowed from module Y

To achieve the scenario where new entries of all types of customer transactions are blocked in a period (and allow cost transactions on a project) the current 'customer' application module closing should be adjusted or a new application module 'project revenue' is required.

Ref. TrackingID#2303310010000933 regarding the parameter "Safety level of invoiced orders" on Accounts receivable parameters - Updates. When selecting "Locked", you are not able to delete invoiced lines. However, you are not able to create credit notes on invoiced sales orders either. Therefore, the suggestion is to expand the possible alternatives to select for this parameter. For example adding an alternative as "Lock invoiced lines only", with this alternative it will still be possible to create credit notes from invoiced sales orders. The alternative which is named as "Locked" today can be renamed to for example "Lock invoiced orders", which still means that it is not possible to delete invoiced lines or create credit notes.

Extending customer payment calendar configuration in order to:

1) let the configuration to be applied for specific customers, not only for specific payment terms/methods (it is not user-friendly asking to create a lot of similar payment terms/methods only for managing calendar holiday date)

2) let the possibility to move the due date not only in the previous/next business date (based on the actual standard “Due date update” field in Terms of payment setup), but in a longer period, for example, letting the system use the Payment days setup in order to let the system calculates the needed due date

When enabling Belgian localization, a default functionality regarding posting validation is available. This functionality allows finance administrators to enter a date range in which a number sequence can be used. If a transaction is posted outside the date range, the transaction will not be posted due to a check on the number sequence with the allow date.

If we could have this functionality for other countries we could allow finance to have a smoother period close due to the fact that we can enforce the number sequence used in a transaction.

Good Morning

I've not been able to find any suitable tool to be able to export data from D365 to show the approval values at each step of a Purchase Invoice Approval Workflow

As many companies have multiple departments with mutiple flows in multiple legal entities this can soon run into hundreds of decision flows

I agree that this data could be retrieved one flow at a time and recorded somewhere but we know staff, flows. approval amounts can change on a frequent basis and it's not practical to have to manage seperate reports outside of D365

Also when organisations are audited the data in the system could be vastly different to a sepreate external report

If this information was available to be exported or have an entity it would be possible to develop a solution via the PowerPlatfrom, or that data could be exported to excel and feed into other excel sheets

Whatever could be exported would be useful - But I would like to have

Workflow Name

Sub Workflow Name

User Group Name / Person Name

User Group Code / User ID

Workflow Amount

For example:

WORKFLOW: Invoice Approval Workflow for Stores

SUB WORKFLOW: RS REPAIR APPROVAL

USER GROUP NAME USER GROUP CODE WORKFLOW AMOUNT (PARAMETER)

Retail Store Repairs Coordinator RSRC

Property Manager (UK & Eire) PMUK >500

Support Manager SPM >5000

Head of Retail (UK, EUR and ASIA) HR (ROW) >50000

Group Financial Director CFO >500000

Chief Executive Officer CEO >5000000

Customers have an additional delivery address in an other EU-Country, with a separate Tax exempt number.

When we create or edit a sales order and choose this delivery address, the Tax exempt number has also automatically be changed.

This must depend on the Delivery Term where we can select the source for the "Sales Tax address" and the account receivable parameter (Updates - Update Order lines)

Proposal:

Introduce a new feature allowing businesses to seamlessly include business documents as embedded attachments within e-Invoice files.

Current behavior:

When activating "eInvoice attachment" for a customer in D365FO, a copy of the invoice layout in PDF format from SSRS is embedded in the e-invoice file. However, there is an issue when using business documents instead of SSRS, as attaching the invoice file in PDF format is inaccurately executed.

<cbc:EmbeddedDocumentBinaryObject mimeCode="application/pdf" filename="FreeTextInvoice.Report.pdf">JVBERi0xLjcNCjIgMC</cbc:EmbeddedDocumentBinaryObject>

Proposed Solution:

Upon activating "eInvoice attachment" on the customer card, the system will use the Report format specified in the print management setup and ER destination setup. It will convert the document into PDF, if "Convert to pdf" is activated on Electronic reporting destination, attach it to the invoice journal, and seamlessly embed it in the e-invoice file as an embedded document. This enhancement allows customers to include business documents designed in Excel or Word as attachments to e-Invoices, providing a more versatile and accurate solution.

System is not calculating Prepaid expense amount correctly via Accrual schemes based on Number of days. A voucher is entered in the general journal on 1/17/2022 and then assigned the accrual schema. The result is that the system ends the calculations with date of 12/31/2022. The expectation is that the system would perform the calculations through 1/16/2023, utilizing the 365 days.