Alaa ElQadi

Currently, when generating the sales tax deviation report, the system generates a high number of rows which takes a lot of time to process. This can be particularly problematic when dealing with data sets that have a large number of entries, or when applying a wider range of time.

We suggest adding an option to the report generation that allows users to club the results by specific criteria. This would narrow down the results and make the report generation process faster and more efficient.

Feedback has been received from one of our customers requesting an extension of the fixed asset field to allow for more than 60 characters.

Currently, the field has been reduced from 150 to 60 characters due to an error on the trial balance if the fixed asset is used as a financial dimension. However, it has been noted that this customer is not using fixed asset as a financial dimension and would like to be able to input more than 60 characters.

It is believed that this change would be beneficial for other customers who are not using fixed asset as a financial dimension as well. We kindly request that this suggestion be considered.

Description: Currently, there is a bug in the 'Change Fixed Asset Group' function where it adds the "Leave net book value at" to the depreciation amount.

Although it has been acknowledged this as a bug, it was decided that Microsoft will not pursue a fix and instead suggested a workaround to change the transaction type from "Depreciation" to "Depreciation" Adjustment in the Fixed assets journal.

However, this workaround is not suitable for customers who need to restructure high numbers of Fixed assets at once. Changing the transaction type on a line level for each asset manually is not time efficient and can lead to errors. We suggest that Microsoft's product group reconsiders their decision to mark this issue as "won't fix" and instead provides a fix for the 'Change Fixed Asset Group' function. This will greatly improve the user experience and prevent any further confusion or frustration.

Currently, the Ledger parameters do not include 100% of the fields needed to copy general ledger parameters between legal entities. To address this issue, we propose creating a new data entity that includes all general ledger parameters. This would make it easier for customers with multiple legal entities to copy general ledger parameters between them, reducing the risk of errors and saving time. By creating an inclusive general ledger data entity, customers will be able to manage their financial data across multiple entities more efficiently