-
Improving the functionality of the expense management workspace
The expense management workspace currently has a limitation when the expense re-imagined feature is enabled as it prompts error" The activity number is missing. The project that is associated with this expense requires you to enter an activity number, with a postponed bug (675860).
The workaround is to disable the feature which isn't ideal as it affects the user's ability to add cash advances to the expense lines.
The business requirement is to fix the bug to allow the users to benefit from the cash advance functionality introduced within the Expense reports re-imagined feature.
-
Improving the implementation of intercompany Submitted hours in a project and how they show in coast estimates.
Customer highlighted that if he has a project created in a legal entity with intercompany relation.
If hours are submitted in a timesheet to the secondary legal entity
it will not reflect in the coast estimates in the project for the main entity unless they are posted manually as pending invoices which is a very tedious process.
-
Addressing an issue with Project ID characters limit, causing an issue in wrong values showing in the forecast report
Advising with increasing the character limit allowed for the project ID
Currently, if a project ID is entered with more than 20 characters the system does not fetch the data assigned to that project ID and regardless of whatever the value that is assigned to that project ID, it appears as 0 value in the forecast report.
-
Unblock foreign currency revaluation in cash and bank management for Polish legal entity
A request to have foreign currency revaluation enabled for polish legal entities since it would streamline lots of business processes and help improve overall functionality and save time.
For Poland accountancy in D365 there is FIFO revaluation run every month to recalculate bank funds in foreign currency. Our customer besides that have requirement to recalculate balances in standard way for group reporting purposes. Unfortunately standard functionality is disabled for polish localization. Recalculation is made with different exchange rate and with different method than Poland currency revaluation. It is done at month end, reported in group consolidation tool. Then reversed at beginning of next period.
-
Budget encumbrance amounts for PO'S with exceeded budget
we would like to suggest adding the possibility of Allowing users without budget exceeding access to post po's if they made a prior reservation on the budget encumbrance amounts (In cases the overall budget is exceeded) according to the following example:
there is a total budget amount of1000 USD and a total of two users one with access to exceed budget and the other not.
- the first user (Not allowed to exceed budget) processes the PO for – 600 USD – and does not confirm it.
- The system makes reservation for encumbrances:
- Budget reservations for encumbrances 600 USD
- Total revised budget 1000 USD
- Budget funds available 400 USD
The PO has a reserved budget at a draft status
2. the second user (Allowed to exceed budget) process the PO for – 500 USD – and confirm it.
- The system made reservation for encumbrances:
- Budget reservations for encumbrances 500 USD
- Total revised budget 1000 USD
- Budget funds available -100 USD
Now the first users return and attempts to confirm the PO , when trying, the user is not able to proceed due to an error from the system suggesting that the budget is exceeded even though an encumbrance reservation was made prior with an amount that does not exceed the overall reserved budget