Rajiv Nayan Ganjikunta

Under GST law. if a fixed asset is transferred from one registration number to another, then GST should be computed, however, there is no such provision in the system. 1.In the Navigation pane, go to Modules > Fixed assets > Fixed assets > Fixed assets. 2.In the list, find and select the fixed asset to transfer. 3.On the Action Pane, click Fixed asset. 4. Click Transfer fixed assets. 5.In the Transfer date field, enter a date. Enter comments to describe the transfer. 6.This list shows the existing financial dimension values for the selected book. Select the financial dimension you want to update for the selected fixed asset book. 7.In the Financial dimension field, click the drop down button to open the lookup. Set other financial dimension values as appropriate. 8.Click Update. 9.Click Transfer. The GST should be calculated based in GST law. There is no such provision in the system.

GSTR- 9 is an annual GST report, that needs to be filed with the Government. The data required for the filing of the return currently has to be extracted from 4-5 reports. Request you to provide a comprehensive report for this in the future release

Kindly extend Withholding tax to project invoice transaction. Some of the customers will not use sales order. They may consider Project Invoices are used to book revenue on customer. As of now this functionality is not available for project invoice transaction. Please extend it to project invoice transaction

Microsoft has made available a new functionality to create a sales order from a time and material project with multiple funding sources on a project contract. - These customers have each a different customer tax group.- The general parameter setting on the project module for Project Sales Tax is customer account.- The general parameter setting on Default customer on sales order is funding sources On this basis, I expected that when creating my sales order from the project, I would inherit the tax group of the selected funding source (cf. step by step). This is not the case. For me, this is an oversight. Note: unlike the "tax group", the "VAT identification number" is correct. When the customer is trying to create a project with multiple funding resources of different countries with different sales tax. The customer is facing issue when going and selecting the different funding resource other than the default customer in the project. He can see the sales tax of the default customer instead of original sales of for that customer. And the tax-exempt number is remaining same of that customer.

1. Voucher should be the same as Interest note or Reversal transactions 2. Invoice number should have Interest note number - not invoice number 3. Transaction type should be Interest - not customer 4. Voucher posting type should be customer interest - not customer revenue. Just parameters should be the same as original transaction. I cannot see any info on interest note when was waived. just to compare if transactions type Interest are equal to GL account for interest notes. Expected Result: Voucher number sequence should be like in interest note or reversal transaction. Invoice should be original interest note number. Transaction type should be Interests. Voucher posting type should be customer interests.

Thailand wants 7 aging period/Buckets for reporting it management

Hi, We are started to import customer payments to F&O using CAMT.054 Electronic reporting payment format and we noticed that due date is calculated based on term of payments set up. With legacy format we don't see this behavior and due date is always equal to Transaction date. Do you know what is the business justification for due date calculation for incoming customer payment? Should not be due date calculated only for invoices? After our internal investigation, we found that if Due Date is not mapped in payment format, it's defaulted according to term of payment in LedgerJournalTransType.defaultDue method.

Customer credit and collection is not showing the correct values for collection letter visuals. We have noticed that the collections letter in power BI is showing that data if you have same value, it will club both the value and collection letter code and it is based on product limitation.

How to handle the package weight for weight item (material) in D365? We want to know if we can define the package weight for item and even per vendor/customers is better. Then we can use this package weight during we receive these material which need to be weighted. Just like, it we get the material weight which include package weight, then during we register the weight items, system can reduce the package weight auto and register the net weight(without package weight) directly in D365. Or do we have other solutions to handle the package weight in D365?

The issue is with selecting the UOM in the product master and assigning a standard conversion. The system is inconsistent, and it does not always pick up prices from the Trade agreement if the UOM is selected other than the one specified in the product master. Expected Result: The prices should be picked up from the Trade agreement either way since the UOM is specified and the standard conversion is also updated between Dz and Ea. The system should be consistent with both Ea and Dz when the Product is set up with default UOM as either Ea or Dz.