-
Timesheet Delegates - Ability to access timesheets
Delegates are currently only able to access timesheets for employees that they have created the timesheet for, this functionality should be extended to include the following: "All timesheets for delegated user" This would grant access to all timesheets (that fall within date boundaries for delegation rights), regardless of if the delegate created them or not.... The primary issue is delegates can change over time and they are presently hindered from accessing timesheets created by the resource or a former delegate, therefore rendering their delegation useless in helping the resource. The above filter should also be added to the "My Timesheet" view to support simple filtering -
Project budgets - Create new menu option for Project budget inquiry to globally enquire/maintain project budgets
Create new feature to globally manage project budgets (very similar to current function estimate enquiry). You should be able to easily see all budgets created for projects and then jump into maintenance mode to update/revise. Current option to access project budgets via project maintenance is time consuming and requires users to search for each and every project in turn. -
Project Budget - Create data entity to support ability to allocate project budgets to periods
Currently when allocating a project budget plan to periods you have a choice of annual, quarterly and by period -This allocated in equal instalments any budget entries. After allocation the user has to re-allocate balances to the correct period if budget values are not evenly distributed - This can be complex and time consuming if the allocation method is complex.... Creation of a data entity to extract and reload balances by period would greatly help this process.... If the design could also incorporate the ability to access a project direct from the data entity it would aid businesses with project budget maintenance. -
Project Timesheet - Mobile APP, opens on draft timesheet when deleted it opens another when it should default to menu
Presently, when a user is using the Project mobile timesheet app it opens on draft timesheet. This is a welcome feature to the app as it can speed up data entry and make it more efficient to use. However, in certain cases the user may not require the draft timesheet so they attempt to delete . Whilst the APP does delete the timesheet it defaults back to the same screen so effectively re-creates the open timesheet. This is confusing for the user and gives them the feeling that they cannot control/remove draft timesheets. We would expect that when selected for deleting the user is returned to the main menu so they can continue to administer other timesheets etc.... -
Project Management - Timesheet Entries, bulk update
Create the ability for mass creation of timesheet entries (for administration purposes) or allow project journals (time) to be included into timesheet data. If multiple calendar types are defined then D365 does not support worker/resource changes. Currently timesheets and missing timesheet routines work within calendar type, so we need a process to ab able to maintain records and gaps in data. Option A - Project Management - Create a periodic task to generate timesheets (based on similar process to missing timesheet report), then create a data entity to allow extraction of timesheet/timesheet lines and bulk update. The ability to create timesheets should be parameter driven so you can define the worker/resource, date range and calendar type. The subsequent data entity to support updating timesheet lines should support multiple timesheets per worker/resource. Option B - Project Management - On creating timesheet journals include a column that allows the user to define if a timesheet record. These journals should then be included with timesheet records when reporting on timesheet data (and Missing Timesheets). Project journals are not bound by the same controls over worker periods and as such allow for bulk updates. Limitation of this option is the support for intercompany transactions and automated project recharge process. -
Currency revaluation (General Ledger) - Expand ability to select account and FD combinations
Currently when selecting to revalue Balance Sheet or Profit & Loss accounts you are limited on your selection to just currency, date range, legal entity and main account. Expand the ability to select by allowing the filter criteria to use any combination of Financial Dimensions... This will support a more targeted approach to revaluing balance sheet accounts. -
Project Budget Create ability to change allocation method/principal
Project budget allocation method - When defining project budgets you have three current options to allocate the budget "By Time period":
- By year
- By Quarter
- By Period
Once defined this sets the principle for all subsequent allocations/project revisions - Create the ability to reset the principle allocation method on project budgets (for each sub-project). You should be able to update the allocation principle and switch between each type, currently you cannot do so. To rectify this issue you have to create a new sub-project and migrate all transactions, so you can enter a new budget.
-
Vendor Profile Diversity ability to configure and add new options
The Vendor record in Accounts Payable fast tab VENDOR PROFILE should be configurable by region (or legal entity) to ensure compliance and consistency across organisations.
Currently Microsoft define the values by region (organisation location) based off statutory requirements - If an organisation elects to use Vendor DEI reporting it should not be constrained, you should also have the ability to add new categories/options to the defined list.
Currently it is configurable within VENDOR COLLABORATION so you would also expect VENDOR PROFILE to support.
Vendor DEI Reporting examples currently defined (Minority Owned, Ethnic Origin, Owner is a veteran, Owner is disabled, Hubzone)
Vendor DEI Reporting examples to be added (LGBTQ+, Certified Minority Business, Disadvantaged Business)
All of teh above should be represented within Vendor Record, Vendor Diverse Lists and Procurement based reporting.
-
Intercompany Transactions - Create ability to remove/settle or place on hold pending intercompany transactions in project sub-ledger
It can be common for intercompany charges to be credited or re-allocated to other legal entity projects prior to the lending legal entity issuing the intercompany recharge invoice. Currently there is no process to hold, settle or allocate pending intercompany charges (credit vs debit) to avoid a recharge taking place (even if the recharge is an error or has been subsequently been corrected).
This results in a legal entity receiving incorrect charges which they need to account for and be aware of when completing recharges or revenue recognition.
It would be ideal if you could monitor pending intercompany charges and place on hold and settle pending transactions - The hold status would allow for transactions to be excluded from intercompany invoicing and the settle process would allow you to match an invoice to credit note (and subsequently remove from the IC invoicing process).
-
Audit Workbench Duplicate Transactions
In Audit Workbench you have the ability to configure a policy rule type to identify duplicate transactions but the selection criteria for this rule type does not work as it should do, this issue has been reported by the user community but has been pushed back as stated working as per design.
To correctly work you need to define two date ranges:
- Document selection date range - To select the base documents you wish to evaluate
- Duplicate evaluation date range - Selects the date range of documents you wish to evaluate documents identified in section 1 above against
You should be able to achieve (1) by using start date / End Date, achieving (2) should be Start Date + Additional Days / End Date - Currently the system uses Start Date + Additional Days for both the selection of reports and the evaluation period for duplicate entries. This means that a batch process cannot be established which will evaluate new expense claims against historic entries without creating duplicate cases (if additional days are utilised). If you choose to not use utilise additional days then the volume of your audit cases is impacted and you will miss potential duplicate reports (based off Transaction Date)...
Please update the selection criteria to accommodate the above when checking for duplicate transactions....
You’re offline. This is a read only version of the page.
