-
Different Per Diem rates for travel to multiple locations in single trip
Ability to create a single expense report for per diem for a user that has traveled in the same trip to different locations. The user should receive a per diem rate that is reduced on the travel days, first and last, but only reduced on the rate that is for the location the user is flying to. The policy is both the first and last day are considered travel days so the system is setup to do the automatic reduction as ‘both’ under the rate tiers. However, this then causes an issue for the second line that is created for the second location because you are either double dipping and getting per diem for two locations for the same day at a reduced rate or you are being shorted because the second day you are at the second location is being treated by the system as a travel day even though it is not. Example, Location A per diem rate is $100 and the tier is set to 75% of meals and other on travel days (first and last) Location B per diem rate is $200 and the tier is set to 50% of meals and other on travel days (first and last) What we would expect is the following: Day 1 travel to location A - per diem is 75% of the per diem rate since it is travel day = $75 Day 2 is full day in location A - per diem is 100% of the per diem rate since no travel - $100 Day 3 is travel day from location A to location B - per diem is 50% of the per diem rate of location B since it is a travel day to location B (currently this is where we see the issue with out of the box functionality) = $100 Day 4 is full day in location B – per diem is 100% of the per diem rate since no travel = $200 Day 5 is travel day from location B home so the per diem rate is 50% since it is a travel day =$100 Total per diem for the employee should be $575 There should be a way to indicate which day is a travel day on the expense report. The user currently has to enter the to and from date on the expense report line for each location but the system calculation is not correct: Expense Report line #1 for Location A (user traveled from Location A to B on March 3): March 1 to March 3 - system treats the first and last day at 75% of location As rate of $100 = $250 Expense Report line #2 for Location B: March 3 to March 5 - system treats the first and last day at 50% of location Bs rate of $200 =$400 With this way of entering the data the user would receive per diem totaling $650 The only other option to enter the data would be: Expense Report line #1 for Location A (user traveled from Location A to B on March 3): March 1 to March 2 - system treats the first and last day at 75% of location As rate of $100 = $150 Expense Report line #2 for Location B: March 3 to March 5 - system treats the first and last day at 50% of location Bs rate of $200 =$400 With this way of entering the data the user would receive per diem totaling $550 -
Cash Advance - financial dimension validation prior to submitting to workflow
Currently, if a user creates a cash advance and forgets to fill in the financial dimensions or they are incorrect, the system will not catch the error until the 'post and transfer' step (finance). This causes delays in the process because finance will need to set the cash advance back to a draft status and notify the user via email (outside of D365) that the cash advance coding needs to be corrected.
Validation on the financial dimensions should be done at the time the user clicks on submit.
-
Ledger to Expense Management reconciliation for Cash Advances
Similar to the way we have a ledger to AP reconciliation report, we need the ability to reconcile against the cash advance balances within the expense management module.
-
Expense Management - retain link between receipt and expense line after deleting from expense report
When an expense line is removed from the expense report and it becomes available to be attached to a new expense report, the link between the expense line and the receipt has been broken when it was removed from the original report. For users that have already associated the receipt with the expense and for whatever reason have to remove it from one expense report to add to another, they have to go through the process of linking the two again. This is a usability issue
-
Ability to have "Known as" name displayed in D365FO and in notifications while keeping Legal Name as First and Last Name
The system should allow the 'Known as' name, which would be the preferred name that an employee goes by, to be displayed on all forms throughout the system (Workflows, PR requestor, Expense Reports, email notifications, username etc). This field would allow the legal name to be used as well for the vendor record for payment but still searchable by "known as".
Currently the only option is to use either the legal name or the preferred name for the first and last name on the global address book which is the link between the employee record and vendor records.