You’re offline. This is a read only version of the page.
In the Dynamics 365 Finance version 10.0.18 (PU42) the design of Mileage tier setup has been modified to better reflect customer needs. Below you find explanation of old design and new design and recommendation how to proceed once you upgrade customer database to 10.0.18 version.
When the employee reports expense in with mileage category, the amount for that expense line is calculated according to the “rate per mileage” amount. The “rate per mileage” is determined by mileage tiers setup or standard rate of mileage.
Mileage expense category has dedicated form for setting up mileage tiers (Category setup > Mileage rate tiers). There you can setup different rules for different ranges.
For example customer expects following mileage calculation:
Setup to meet the requirement in version before 10.0.18:
The Quantity field represents lower limit of mileage. If accumulated miles/kilometers for a user crosses quantity in the field - the related rate is used. If there's no line with Zero quantity - system will use 'Standard rate of mileage' from Expense management setup.
Expense report after posting with 2 lines - 1000 (rate 0.45) + 500 (rate 0.25) = 575
In the 10.0.18 the design of mileage tiers has changed. The Quantity field represent upper limit of the tier. If all upper limits are exceeded, system will use 'Standard rate of mileage setup' from Expense management parameters.
To calculate correctly scenario from previous example we need to change the tier setup as follows:
If any employee exceeds total quantity of miles/kilometers 999 999 999.00 - system will use rate from 'Standard rate of mileage' from Expense management parameters.
Expense report after posting with 2 lines - 1000 (rate 0.45) + 500 (rate 0.25) = 575
The difference between old a design of Mileage rate tiers is in Quantity field processing. Before 10.0.18 the Quantity field was considered as lower limit - when accumulation crosses that particular Quantity - rate was used. From 10.0.18 over the Quantity field is considered as upper limit - rate is used if the accumulation is below the particular Quantity field.
It is necessary to setup new tiers after upgrade to 10.0.18 to reflect new design of Mileage tiers setup. All approved expense reports will be recalculated during posting according to the new design . We recommend to test the setup first in UAT/TEST environment and validate results.
Hi Michal,
Great information. Thank you for sharing.
Wouldn't it be better to use the blog spaces on this forum to provide this type of announcement and information?
Share
Report
All responses (
Answers (
299,022
