Dynamics 365 Finance

Path: Accounts Receivable > Intent letters

In the customer intent letters form the field "Name" is missing. There is only the customer account code.

The name should be included in order to enhance the standard functionality and to align the behaviour to the form on the passive part (vendor intent letters)

Issue Description:

When using the Post button on the Consolidated invoices for Japan page, a general journal entry is created and posted. However, the journal name used in this process cannot have approval and workflows configured. If such settings are applied, an error occurs when clicking Post button on the consolidated invoice page.

As a result, it is not possible to prevent a malicious user from using the journal name on the general journal page to post journal entries without any approval.

Request:

Please fix this so that malicious users cannot post journal entries using the posting function on Consolidated Invoices for Japan page without anyone's approval.

Currently, I haven’t found a way to capture the vendor account/bank details provided on an incoming invoice for payment purposes. It would be highly valuable to include these details and automatically verify them against the vendor’s bank accounts configured in Finance and Operations.

Proposed Functionality:

• Extract bank account information from the invoice.
• Cross-check the extracted account with the vendor’s bank accounts registered in FO.
• If a match exists, use that account for payment processing.

Users have the ability to put Vendors and Invoices on hold but if these are already in a Payment Batch and get submitted it causes major issues as it gets processed to bank and paid and then it does not post. Need a warning message either to user placing invoice on hold that the Invoice has been added to a Payment Batch or to Batch owner that an invoice has been changed before it's submitted. It would be great if the message was setup for both sides. We have different teams who did this and sometimes the communication does not get relayed. I can't imagine this company is the only company that has had this issue. We use TAS and once it's submitted for approval, approved it goes automatically to the bank. If we have to correct this, we have to create to a new batch and grab it before it reaches the bank which sometimes can't be done then we have to work with the bank to back out. A lot time and resources to fix when a warning would alleviate this. Thanks!

The inclusion of invoices created in the Project Management and Accounting module in the Collection Process Automation feature is necessary, as currently, only invoices originating from sales orders and tax-free invoices are being considered.

According to the SEPA Credit Transfer rulebook 2019 V1.0. The structured remittance info for extended remittance info occurrences mustn't exceed 280 characters in length.

However, in the payment model for ISO20022 for credit transfer, in the case of bundling a credit note with and a payment, along with using long Payment IDs, as in Finland (the RF number could be up to 25 character), the STRD tag for the payment file will exceed the mentioned 280 characters in total, which results the rejection by the bank.

In that case, some banks would suggest removing the referenced document number represented in the tag.

We suggest handling the document in the way you see fits to avoid the rejection of the bank in such cases and make it easier for the D365 ER users to handle these cases.

The standard feature of invoice matching, in case of discrepancies between received goods and invoices, creates zero amount transactions.

The request is to avoid creating of zero amount transactions for the Italian Localization.

Currently there is no system based control/approval over the use of journal reversal. To avoid risk including risk of non-compliance with our audit regulations, we are having to prevent anyone from being able to use this functionality. Please can Microsoft consider the introduction of either:

• A parameter that will allow reversals posted by 'reverse entire journal' to be routed to the applicable workflow for the journal type
• A parameter that would mean that rather than an automatic correction posting, a draft journal is created when the user clicks ' 'reverse entire journal' which would then go through existing workflow
• An out of the box workflow option for reversals

Improve the integration between the "Financial Analysis - All Companies" workspace and the "Accounting Source Explorer" by ensuring that when users drill down into a specific account, all relevant filters, especially the account-specific filters, are automatically applied in the Accounting Source Explorer. This will enable users to transition smoothly between analyzing overall financial data and examining detailed transactions for a particular account without the need to manually reapply filters, thereby enhancing efficiency and accuracy in financial analysis and reporting.

Currently the parameter "Require the calculated totals to equal the imported totals for workflow submission" is a do or die decision. (accounts payable parameters-> invoice -> invoice workflow) Similar to other parameters like "price and quantity matching" or "charges matching" (accounts payable parameters -> invoice validation) it makes sense to extend the "Require the calculated totals to equal the imported totals for workflow submission" parameter to also incluce a toleranz amount. It means not all invoices should be blocked from workflow submission when the imported totals differs from the calculated totals. Only those out of a toleranz e.g. 0,10 USD/EUR/GBP should be blocked.