Dynamics 365 Finance

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!

Enhancement to the feature Awareness between ledger settlement and year-end close

Issue: If we are using ledger settlement and above feature retrospectively we are facing an issue related to same. Since the ledger settlement page does not allow to post the cross year settlements in the system and it throws an error that we need to select the same fiscal year. This type of the cross year settled transactions are generated and are related to AP or AR transactions which is a standard process followed in the business.

Solution:

To identify whether the settled transactions are done through the ledger settlement functionality when reviewing the cross year settlement page, we can add a flag indicating if the customers has generated this transactions using the ledger settlement functionality or not. This will allow customers to implement ledger settlement functionality retrospectively by not reversing the cross year settled transactions.

Additionally to the above process we can have a field indicating date when the ledger settlement functionality and advanced awareness options parameters was turned on and also history related to when the toggles were set to No.(As provided in the budget control configuration change history. Path: Budgeting > Setup > Budget control > Budget control configuration)

Ability to define the settlement ID number sequence to be used in the ledger settlement functionality and advanced awareness option.

Example: We are currently using 10.0.41 version and wanted to use the ledger settlement functionality and advanced awareness option retrospectively. For example for the year 2020 we wanted to use both the features and there were cross year settled transactions which we did not want to reverse the transactions as those transactions were related to AP or AR module. Hence, we were not able to use the functionality in the system.

Conclusion:

By implementing these changes, customers will be able to effectively leverage the ledger settlement functionality without disrupting their historical transactions or requiring reversals, even for cross-year settled AP/AR transactions. This solution will improve operational efficiency and ensure that the system supports both new and legacy business processes.

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.

Hi Team,

We need the ability to exclude charges like freight from the cash discount calculation on vendor payments. Almost all of our vendors do not allow us to apply the cash discount to freight.

NOTE: Most of our payments are automated, so manually adjusting the cash discount amount on each payment line is not really an option unless we want to move to manual payment processing.

Thanks,

Steven

When adjusting a lease via the wizard it automatically updates the lease start date to the date of the adjustment. This should not be updated and should remain the date of the start of the lease contract. My suggestion is to change this to stop the lease start date from being updated.

We have found out that action Tax\Declarations\Sales tax\Settle and post sales tax can duplicate records in table TaxTransGeneralJournalAccountEntry. Those duplicate records have reference to non existing TaxTrans records.

Based on our investigation, we think the issue in with variable taxReportVoucherTransCombine in class TaxReport. When SQL transient error occurs, it is catched in run method and posting is retried, but unposted and rollbacked data are still in variable taxReportVoucherTransCombine.

The variable is initialized only in constructor method new, but it should be initialized in method updateNow.