-
In Aged balance, if any of the Invoice has Payment schedule applied during posting of the invoice or after posting of the invoice, requirement is the aged balances form to split the invoice based on the invoice due date.
In Aged balance form, if any of the Customer Invoice has Payment schedule applied during posting of the invoice or after posting of the invoice, require the aged balances form to split the invoice based on the invoice due date. -
When a customer payment transaction are settled outside the Payment journal process the collection status is not updating correctly even after executing the Age customer balance. The collection history is also not updating correctly
Whenever a customer Settlement is done from the Customer master level, the collection status and collection history form should get updated accordingly in “ Aged Balances “ form. Since the Payment is made as promised and later settled it manually the system should consider updating the Collection status as “Promise to pay kept” instead of “ Promise to pay broken “ and also reflect accordingly in Collection History form. -
Credit in reporting currency amount is coming different than credit in accounting currency on running depreciation proposal for asset group & FA number is visible on journal line if asset group depreciation is set to Yes on asset book.
Currently, Credit in reporting currency amount is coming different than credit in accounting currency on running depreciation proposal for asset group and not allowing to post FA journal & FA number is visible on journal line if asset group depreciation is set to Yes on asset book. The expectation is that system should have same values in reporting currency and accounting currency and allow to post journals. Also when using FA depreciation proposal for Asset group depreciation, it should not display any individual asset id and should be blank so that no ambiguity happens whether it is for an individual asset or a group. -
Error shown when completing collection case through workflow
While completing the collection case through workflow, below error is thrown. "Unable to cast object of type 'Dynamics.AX.Application.CustCollectionsCaseDetail' to type 'Dynamics.AX.Application.CaseDetail'. Expected Results: User should be able to complete the collection case successfully. -
Excel add in does not update default dimension in Journal Lines
Excel add in does not update default dimension in Journal Lines. When the transactions are created manually inside Dynamics, default dimension (company function) set up at main account LE overrides is populating automatically however once the lines are created using excel add in they are not populating automatically , although in posted voucher dimension value are defaulted as per MA LE overrides setup. Considering the fact Excel add in is used for creating journal, behavior should be aligned. -
One budget control limit to be applicable on all entities.
Customer has the requirement to setup a Budget control for only 1 Legal entity and the same should be applicable across all entities. Further, if a Main Account has budget control set to 40Lacs & in 1 legal entity, 15Lacs has been used, then remaining 25Lacs budget should be available across all entities. -
System is not calculating GST and Withholding tax in Asset leasing Invoice journals
Currently System is not calculating GST and Withholding tax in Asset leasing Invoice journals. But as per Indian taxation, Asset leasing Invoice journals should have the functionality to calculate GST as well as withholding tax. -
Fixed Asset Reclassification
After running the fixed assets reclassification proposal, the book in the newly created fixed asset remains the same of previous fixed asset group.
Since we have reclassified assets to a new group, that new group’s book should be reflected in the newly classified asset so that the accounting impact can be done as per new book.
-
Delegate is unable to create expense reports for a terminated employee or for an employee whose last date has been surpassed.
Delegate should be able to create expense reports for a terminated employee or for an employee whose last date has been surpassed.
-
Accounts Receivable Foreign Currency Revaluation Simulation process should have Invoice reference field
Currently the AR foreign currency Simulation process does not have an Invoice reference to verify the invoice details. The request is to have the Invoice reference field in AR Simulation process for easy verification of the details included in the foreign currency revaluation process.
You’re offline. This is a read only version of the page.
