We have recently seen somewhere that the mileage totals calculation by fiscal year is becoming a mandatory feature. Previously, when we had this feature enabled, we found that the mileage to date is stored in a different column, and this column isn’t in our custom mileage data entity. Without being able to use this data entity we will be unable to perform the mileage reset to zero process which we perform in the respective months across our different regions. We also wouldn’t be able to migrate in mileage to date for any new entities.
Please can someone advise if this will become mandatory and if so when or if it has already happened i.e. in what version?
As of the latest available information from Microsoft, the mileage totals calculation by fiscal year is not currently a mandatory feature across all environments. However, it has been introduced as part of recent updates to improve tracking and compliance for organizations managing mileage reimbursements and benefits, particularly in regions with fiscal-based reset requirements. We understand your concern regarding the mileage-to-date data being stored in a different column, which is currently not exposed through your custom mileage data entity. This limitation affects both your regional mileage reset processes and data migration for new legal entities.
Recommended Actions:
Check Your Environment Version First, confirm the Application version and Platform update your environment is on by navigating to System administration > About. Look for versions 10.0.39 or later, as significant updates to expense management and mileage tracking have been rolled out incrementally.
Review Feature Management Go to System administration > Workspaces > Feature management, and check the status of the “Mileage totals calculation by fiscal year” feature. If it's listed as mandatory or automatically enabled, it will be indicated here with a lock icon or enforced status. If it’s still optional, you may choose to leave it disabled.
Custom Data Entity Extension Since the mileage-to-date column is not present in your custom data entity, we recommend extending the data entity (if not sealed) or creating a new composite entity that includes the required mileage fields. This will allow you to:
Perform zero-reset operations per fiscal policy.
Import legacy or new mileage-to-date values during migrations.
Raise a Microsoft Support Request (if needed) If the field storing mileage-to-date is system-managed and not currently extensible via X++ or data entity extension, it’s advisable to raise a Microsoft support ticket or consult with a partner. Microsoft has been responsive to such feedback, especially where functionality impacts regulatory or operational compliance.
Summary:
Not mandatory by default as of now, but you should monitor Feature Management and Release Plans.
Data model changes introduced with this feature require extension of custom data entities for proper integration.
We recommend reviewing your version and preparing your data model to accommodate this change, should it become enforced in a future release.
If mandatory enforcement is confirmed in a future release (e.g., Wave 2 2025), Microsoft will typically provide at least 6 months' advance notice via Release Plans and the Message Center.
Please let us know if you'd like assistance with extending your data entity or evaluating the impact in your environment.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
64
Share
Report
All responses (
Answers (
