The entry lists the feature as in development, with estimated general availability in December 2026 for the Web platform in the Worldwide (Standard Multi-Tenant) cloud. That is a planning target, not confirmation that the feature is available. Microsoft explicitly warns that roadmap descriptions and estimated release dates can change.
What kilometer support would change
The roadmap’s stated goal is straightforward: let organizations record mileage expenses in kilometers rather than requiring miles. For employees whose travel records use kilometers, the practical benefit could be less manual conversion before entering an expense. That is an implication of the planned capability, not a confirmed description of the future interface.
The announcement does not specify whether the setting will apply at organization, legal-entity, employee, or expense-category level. It also provides no configuration procedure, version number, or explanation of what happens to existing records.
Those omissions matter. “Configurable” should not be read as a promise that every employee will receive a miles-or-kilometers selector on every expense line.
The important caveat: units and prices must match
Microsoft Learn’s Set up cost and sales rates for expenses documentation adds a useful administrative warning. For Project Operations Core and Project Operations Integrated with ERP, expense prices are matched using the transaction category and unit. A kilometer quantity is therefore more than a different label on the same number.
The documentation explicitly says that expense unit conversions are not supported in this pricing context. If a travel price is defined in miles, the expense must also use miles—even when the unit group contains a conversion factor. Microsoft’s documented alternative is to add a separate kilometer price to the price list.
The practical conclusion is to review matching category-and-unit rates before adopting kilometer entry. The roadmap does not announce automatic conversion of existing per-mile prices. Switching the distance unit should not be treated as a substitute for validating pricing configuration.
Why existing kilometer references do not prove availability
Microsoft already refers to accumulated “miles or kilometers” in its mileage-tier documentation for Project Operations Integrated with ERP. That documentation explains how mileage amounts use configured tiers or a standard rate.
This establishes that kilometers appear in related Project Operations scenarios. It does not establish that roadmap item 573707 is already delivered, or that its planned Web configuration will use the same controls. The distinction is between an existing deployment-specific calculation model and the newly announced configurable expense-entry capability.
What administrators should prepare
A sensible preparation plan is to:
- Decide which distance unit the business intends employees to report.
- Review relevant expense pricing for matching kilometer rates where applicable.
- Wait for feature-specific documentation before changing configuration or employee instructions.
- Validate entry, pricing, and downstream results in a test environment once the capability becomes available.
These are preparation recommendations, not activation steps for the unreleased feature.
The bottom line: kilometer entry is a modest but useful planned improvement for regional expense reporting. The administrative catch is equally modest—and important: the distance unit and the applicable price must agree. A shorter journey through the expense form should not become a longer journey through finance corrections.