Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | - |
Dec 26, 2025 |
Business value
This enhancement streamlines the expense entry process. You can use the split functionality even if there are policy violations or if you didn't fill in certain mandatory fields, such as guest information for meals, based on your organization's configuration. This flexibility reduces friction during the initial entry stage. Users can focus on organizing and splitting expenses without needing to input all policy-required details first. This update improves process efficiency and provides a more user-friendly experience.
Feature details
This feature works through a feature flag and a parameter that controls the split expense functionality. When you turn on the feature, you can split credit card transactions even if there are policy violations or if you didn't fill in certain mandatory fields. The mandatory fields come from your organization's policies and include guest information for meals.
Before, you had to fix all policy-mandated fields before you could start a split. This requirement often interrupted your workflow and created a risk of data loss when you tried to split transactions after updating required information. With this enhancement, you can split expenses right away without fixing all violations.
This feature gives you more flexibility to efficiently manage and split expenses on the go. It reduces friction, improves the data entry flow, and makes your overall experience better.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.
Dec 26, 2025