Dynamics 365 Finance

Dear Team,

I would like to propose the introduction of Greek localization for Dynamics 365 for Finance and Supply Chain through the Idea Portal.

During a recent visit to Greece with a client, I observed a substantial interest in Dynamics 365 and the Power Platform among local businesses. Despite this interest, the market is predominantly dominated by SAP. Introducing Greek localization could significantly enhance the adoption of Dynamics 365 in this region, providing a competitive edge and meeting the needs of numerous potential customers.

Additionally, while there is a strong presence of Independent Software Vendors (ISVs) in Greece, their solutions are often not affordable for many businesses. Furthermore, several overseas companies with sister companies in Greece face restrictions in rolling out Dynamics 365 due to the absence of Greek localization, especially when ISV solutions are beyond their budget.

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

The mapping information is only available to the employee who submits the cash advance and does the mapping with expense line in their Expense management workspace. However, the user also wants to check this information for management purpose. They already face with the problem about user map expense with incorrect cash advance.

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.

There are currently few options available under bank reconciliation rules to set for finding and sorting bank transactions. Since each bank have its own way to produce statements and provide references in the statement, it is found that the current available fields are not enough to set up rules and would lead to do customer a manual reconciliation, which involves much human efforts and increase client cost to run the process.

It would be beneficial if bank reconciliation rules have the followings fields for the D365 bank transaction to setup additional criteria and grouping.

Voucher: A voucher on the customer/vendor payment line is mostly unique and can help to sort out the transactions easily.

Document number: A document number available on the customer/vendor payment line (not the deposit slip document number.

Method of payment and Payment specification, Category purpose, Charge bearer, Local instrument, Service level -

Methods of payment, payment specification, and various purpose selected on the journal lines could.

Cheque number - Cheque number on journal line.

Reason code - Reason code selected on journal line

FINANCIAL DIMENSIONS - financial dimension selected on journal line.

These fields are most commonly used for vendor/customer payment journal. Currently these are not available in additional criteria for bank reconciliation rules. With having these fields, it would be more easy to sort out the bank transaction and thus enables the bank transactions to match transaction with bank statement transactions. It reduce the client manual activity to find out the transactions manually.

Also, D365 should provide option to auto generate two field value in vendor payment journal / customer payment journal based on journal names and number sequence.

The field basis on the journal name will allow to fill a default fixed value on vendor payment journal / customer payment journal. This will help in the group condition setup, where a bank provide one line amount for multiple transactions.

The field basis on number sequence allow to have a value in vendor/customer payment journal which can be mapped to the file sent to bank for payment and thus getting the same value back in bank statement.

We are using reporting three duplicate of organization hierarchy.

We have two legal entities and many departments at dimension level. 

We are trying to consolidate financial statement with transaction level through reporting tree using, department financial dimensions, but financial reporter do generate consolidation report at financial, account level not at transaction level.

Even in consolidation at reporting tree, one issue we face again and again in Financial Reporter is consolidation across a large number of entities. We have three entities using D365 finance that will have issues when their report trees need a row for each entity and dimension combination. For example; we have 30 department's dimension values want a consolidated report view for their 3 entities . To make matters worse, they also want a drill-down by the department. While a tree becomes very big and almost unmanageable, because combinations must be created for each entity as a separate row (level) in the tree. 

Suggestion: We have @any in reporting tree which supported to generate consolidate report at financial details level but coming to account detail level, the consolidation would generate with three different legal entities level and transaction level we have to drill with each entity wise, If @any function is consolidating financial at same level, we drill down can see consolidated transaction for all legal entities with financial dimension might be very useful .

It basically instructs the reporting tree to use @any generating the report and requires to generate consolidation at transaction details level.

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.

As of 2022, in the French tax mandatory requirement, il is mandatory to generate a customer prepayment invoice. When creating a prepayment from a Sales order, it is mandatory now to generate a customer invoice for this prepayment.

Currently in Dynamics 365 Finance, it is not possible to create a prepayment invoice. The prepayment invoice has the same legal data as the final customer invoice. In the standard version, a prepayment is just entered as a payment (without an invoice as justification) and then settled manually with the sales invoice.

French description from the Tax regulation : Le Code général des impôts prévoit que tout assujetti est tenu d’émettre une facture pour les acomptes qui lui sont versés avant que se produise le fait générateur qui doit normalement donner lieu à l’émission de la facture.

Facture d’acompte : les 9 mentions obligatoires en 2022 (legalplace.fr)

The customer is sending the R-2010 event tax obligation, but the system is sending data from different months in the same file, causing the record of this obligation to be rejected.

Error: MS1041, quando temos notas fiscais com data de emissão com períodos anteriores dentro do registro temos rejeição.